UltraData Online Interface Error: "Unable to get response from Interlinq...The specified DSN contains an architecture mismatch..."

UltraData Online Interface Error: "Unable to get response from Interlinq...The specified DSN contains an architecture mismatch..."

Unable to get response from Interlinq
StatusCode = "Success"InformationResults![CDATA]]ResultsConnectErrorsErrors

Version="3.3.2.0"Map_Name<Map Name here>Map_NameGeneral_Error
Error= "BOServer: The specified DSN contains an architecture mismatch between the Driver and Application&amp;amp;#xA;" General_Error Error="<Name Here>:

Failed to get a database for data source Servicing"

ErrorsConnectErrorsInformation


Root Cause:

The UltraData Interlinq Online Interface is required to log into the Connect service providing the interface to Servicing Director.

The error typically indicates your Connect service is provided by the E3 product, and you have upgraded your E3 product to a version which has this issue. 

The following information is for your local IT or administrator. 

This error occurs when upgrading E3 Connect on a Windows 64-bit architecture operating system, leading to a mismatch between the E3 Connect service 64-bit web application process and the E3 server ODBC 32-bit DSN for Servicing Director.


Workaround:

Create an E3 server ODBC 64-bit DSN for Servicing Director as follows: 

  1. On the 64-bit Windows E3 Connect server, go to Control Panel > System and Security > Administrative Tools > Data Sources (ODBC) or Data Sources ODBC (64-bit) if present.
  2. Select the System DSN tab on the ODBC Data Source Administrator screen.
  3. Click Add.
  4. Select SQL Server Native Client 10.0 as the driver for which you want to set up the data source.  Click Finish.
  5. Enter the Data Source name, Servicing. 
  6. Enter your Servicing Director SQL server name.  If you have a named instance of SQL Server, enter the instance name in the format "server name"\"SQL instance name".  Click Next.
  7. Select the SQL Server authentication option.  Only SQL Server authentication is supported for Servicing Director. 
  8. Enter your SA login and password. This login name and password you enter here is not used by the Servicing Director applications, but instead they are used only by the Microsoft ODBC wizard during the creation of the Data Source.  Click Next.
  9. Select the default database named, Service.  Make no other selections, accepting the default settings.  Click Next. Click Finish.

 

ArticleNumber:

000039136