When attempting to access the DSP-Directory Sync Pro Console you may receive the following error(s) when logging onto the DS/AD Pro console. Especially when you have upgraded from an earlier version of the code to the latest GA.
401 UNAUTHORIZED
or
Server Error in '/' Application
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.
Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
Unable to restart the Directory Sync service
Windows could not start the BinaryTree Directory Sync service on Local Computer
Error 1053: The service did not respond to the start or control request in a timely fashion
OS Application vent Viewer Log
Faulting application name: BinaryTree.DirSync.Exchange.exe, version: 20.10.7683.18934, time stamp: 0x5fff204d Faulting module name: KERNELBASE.dll, version: 10.0.14393.4350, time stamp: 0x606eafeb Exception code: 0xe0434352 Fault offset: 0x0000000000034f38 Faulting process id: 0x1f44 Faulting application start time: 0x01d800e23911c0d8 Faulting application path: C:\Program Files\Binary Tree\DirSync\BinaryTree.DirSync.Exchange.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 51feb8f8-1aca-49ea-8ad3-99b71197eb38
Faulting package full name:
Faulting package-relative application ID:
Application: BinaryTree.DirSync.Exchange.exe Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Data.SqlClient.SqlException
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(System.Data.ProviderBase.DbConnectionPoolIdentity, System.Data.SqlClient.SqlConnectionString, System.Data.SqlClient.SqlCredential, System.Object, System.String, System.Security.SecureString, Boolean, System.Data.SqlClient.SqlConnectionString, System.Data.SqlClient.SessionData, System.Data.ProviderBase.DbConnectionPool, System.String, Boolean, System.Data.SqlClient.SqlAuthenticationProviderManager)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(System.Data.Common.DbConnectionOptions, System.Data.Common.DbConnectionPoolKey, System.Object, System.Data.ProviderBase.DbConnectionPool, System.Data.Common.DbConnection, System.Data.Common.DbConnectionOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(System.Data.ProviderBase.DbConnectionPool, System.Data.Common.DbConnection, System.Data.Common.DbConnectionOptions, System.Data.Common.DbConnectionPoolKey, System.Data.Common.DbConnectionOptions)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(System.Data.Common.DbConnection, System.Data.Common.DbConnectionOptions, System.Data.ProviderBase.DbConnectionInternal)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(System.Data...
The SQL account password expired.
or an incorrect configuration of the Dirsync Site | Authentication section in IIS.
or a Windows Update has changed this configuration
or something has changed in the environment
Confirm the SQL password has not expired. If it has correct this.
If the password is not expired and is working perform the following steps
1. In IIS navigate to the Dirsync Site | Authentication section in IIS
2. Modify the authentication ASP .NET Impersonation to disabled.
3. Ensure all other options are disabled except for Windows Authentication (see attached)
4. Restart IIS or perform a IIS reset
5. Restart the 'BinaryTree Directory Sync' service
Confirm access to the Dirsync/ADPro console after performing the above steps.
If this did not resolve the issue, follow these steps:
This issue and it was related to the SQL Server is not accessible so the Service will not start
- A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
Please check the SQL Server configured for that Dirsync Server is available.
We advise applying the following Computer Management & SQL steps:
Open Computer Management | Local Users and Groups | Groups | BTDirSyncPro | BTDirSyncPro Properties | Select the "Add" option so you can add access to specific users. Confirm the "service account" is a member of the BTDirSyncPro local group.
In SQL, expand "Security" | "Logins" |Right-click the "service account" among the list & select Properties | Select User Mappings | From here, you want to ensure “DirSyncPro” & “DirsyncProLog” are checked | Check the Database Owner-DBO role check box for each of these and then “Ok”
After these steps are completed, try to open the Dirsync/ADPro console again.
If you are attempting to remotely access the console, this only works with the SQL authentication login/installation method. If you used the Windows Login option when you installed, you want to uninstall & reinstall using the SQL login instead.
Follow and implement the IIS configuration steps shown in the KB: https://support.quest.com/binary-tree-migrator-pro-for-active-directory/kb/333373/unable-to-connect-via-a-remote-session-to-dirsync-pro-console-333373
If the above does not resolve the issue contact Product Support and include the details troubleshooting steps and export the Windows Event Viewer Application Log and include in your service request.
