Does anyone know what these errors in my event log during an install mean?
Error: The specified domain does not exist or cannot be contacted.
Stack Trace:
at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)
at SoftPro.Select.Server.Security.WindowsSynchronization.DiscoverDomains()
Security synchronization pass for 'Windows Synchronizer' failed.
Error: Windows identity already exists with a different ID.
Stack Trace:
at SoftPro.Select.Server.Security.SecurityManager.SoftPro.Select.Client.Security.ISecurityManager.ApplyChanges(ISecurityUser[] users)
at SoftPro.Select.Server.Security.WindowsSyncDataProvider.Save()
at SoftPro.Select.Server.Security.SecurityIdentitySynchronizationManager.Synchronize()
An error occured while running scheduled job 'Security Identity Synchronization'.
One or more security identity synchronization routines failed to complete successfully.(exitcode -2146233088)
Error: One or more security identity synchronization routines failed to complete successfully.
Stack Trace:
at SoftPro.Select.Server.Security.SecurityIdentitySynchronizationJobHandler.OnExecute()
at SoftPro.Select.Server.Scheduler.JobController.RunJob(IJobInfo info)
These messages are coming out of the active directory integration feature in SoftPro Select.
When these message are being raised is not part of the install, but in instead where the install has completed and the services have started. After the services start, we being a number of continuously running jobs and routines. One of these routines polls the local active directory and integrates the Windows users into SoftPro Select.
This feature allows users to authenticate using their Windows credentials instead of having to manually log into SoftPro Select. This also allows users to be administered through active directory instead of requiring administrators to log into Select when adding new employees or when employee roles change.
The first message suggests that your domain has at least one outbound or bidirectional trust. We are trying to acquire a logical representation of this trust and due to permissions, network configuration, or some other issue are unable to contact that domain. This means that users and groups in that domain would not be expected to appear in SoftPro Select, and thus would not be able to authenticate with our services through Windows authentication until this issue is resolved.
The second message suggests that an attempt was made by our service to save a new record for a Windows user or group which already exists in our database. This is not a case that we expect to run into normally, since the service loads all Windows users into memory at the beginning of this process.
My best guess as to what has happened in this case is that while the synchronization process was running, someone added a user or group into the system which the synchronization was naturally going to pick up. For instance, the BUILTIN\Administrators group is automatically included in our system. If the synchronization process was not given time to retrieve these users and the administrator added themselves into the database as soon as the migration was done, then when the synchronization did complete it may run into a conflict with the record which was manually added. If this is the case, the issue will naturally work itself out in the next hour when the synchronization runs again, since it won't have this conflict at that time.
This sort of conflict could also occur if an administrator is adding new groups and then new users which are in those groups in rapid succession, or if multiple administrators are adding the same users and groups at the same time. In these cases, those administrators could encounter this message through the application as well.
The third message is a result of the second message. While the first message will not prevent us from attempting to retrieve users and groups from the immediate domain, the second message is a failure to persist all changes encountered. As such, the second message is a complete failure to synchronize our users and groups to the local domain. This failure has bubbled out of the immediate routine and has manifested itself as a higher level failure.
If you are continuously seeing the second and third error on approximately an hourly basis throughout the day then there may be a larger issue and it would be best for us to gather more information about what is happening.