Table of Contents
SQL Server Error: 126 Error with SQL Server Linked Server
Event Logged or not: No
Description:
SQL Server Error : 126, Error with SQL Server Linked Server.
Description:
“System error 126” thrown when creating linked server from SQL Server Management Studio or using the Salesforce driver through any Windows service.
The test connect is successful using the ODBC Administrator.
Cannot initialize the data source object of OLE DB provider “NewSQL” for linked server “Newone”, OLE DB provider “New SQL” for linked server “Newone” returned message “Specified driver could not be loaded due to system error 126: The specified module could not be found (DataDirect 7.1 Salesforce, C:\Program Files\Progress\DataDirect\Connect_for_ODBC_71\Drivers\ivsfrc27.dll).”. (Microsoft SQL Server, error: 7303)
Cannot initialize the data source object of OLE DB provider “NewSQL” for linked server “Newone2”, OLE DB provider “NewSQL” for linked server “Newone2” returned message “Specified driver could not be loaded due to system error 126: The specified module could not be found (DataDirect 7.1 Salesforce, C:\Program Files\Progress\DataDirect\Connect64_for_ODBC_71\Drivers\ddsfrc27.dll).”. (Microsoft SQL Server, error: 7303)
Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.
USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go
The DataDirect installer adds the driver path installdir\Connect_for_ODBC_71\drivers to the system PATH. The Windows service does not automatically pick up the updated system PATH after the drivers are installed and Server/system needs to be restarted to pick it up.
Restart the Windows service to retrieve the system PATH, which contains the drivers directory.
SQL Server Error: 126
Severity: 15
Event Logged or not: No
Description:
Invalid pseudocolumn “%.*ls”.
Solution would be Restart of the Windows service to retrieve the system PATH, which contains the drivers directory.
Learn about SQL Server detecting logical consistency based issues and how to resolve them.
Learn about SQL Server error 1222 and how to resolve the lock request time out…
Discover the new features of Microsoft SQL Server 2022 and how they compare to previous…
SQL Server Error 1222 lock request time out period exceeded Lock request time out…
SQL Server Error : 427, Severity: 20. Could not load the definition for constraint ID…
SQL Server Error : 204, Severity: 20. Normalization error in node %ls.
This website uses cookies.