Linked server error - SQL 2005 to MAS 90 via ODBC
I am using a system dns odbc connection to create a linked server to a MAS90 system.
The odbc driver is the MAS 90 32-Bit ODBC Driver.
The linked server is named MASDPK.
I have a number of queries and stored procedures.
It is a roll of the dice for it to work. Often, I can hit the linked server 4 or 5 times in a row with success, and then I will receive this message.
__________________________
Msg 7399, Level 16, State 1, Procedure UpdateRecipeDescription, Line 10
The OLE DB provider "MSDASQL" for linked server "MASDPK" reported an error. The provider reported an unexpected catastrophic failure.
Msg 7303, Level 16, State 1, Procedure UpdateRecipeDescription, Line 10
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "MASDPK".
__________________________
The way I can get around it is to close SQL 2005, use net start and stop for the MSSQLSERVER and restart SQL. Sometimes, if I wait awhile, it will work again on its own.
Everyting is being processed locally on a Server 2003 Service Pack 2.
Is there any way to get this to work consistently?
The odbc driver is the MAS 90 32-Bit ODBC Driver.
The linked server is named MASDPK.
I have a number of queries and stored procedures.
It is a roll of the dice for it to work. Often, I can hit the linked server 4 or 5 times in a row with success, and then I will receive this message.
__________________________
Msg 7399, Level 16, State 1, Procedure UpdateRecipeDescription, Line 10
The OLE DB provider "MSDASQL" for linked server "MASDPK" reported an error. The provider reported an unexpected catastrophic failure.
Msg 7303, Level 16, State 1, Procedure UpdateRecipeDescription, Line 10
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "MASDPK".
__________________________
The way I can get around it is to close SQL 2005, use net start and stop for the MSSQLSERVER and restart SQL. Sometimes, if I wait awhile, it will work again on its own.
Everyting is being processed locally on a Server 2003 Service Pack 2.
Is there any way to get this to work consistently?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I cannot say for sure, but I think that 7399 is due to an authentication failure. I know you'd think if that were the case, it would never work, but I have read that this happens with access.
maybe you could trace it
http://social.msdn.microsoft.com/Forums/en/sqldataaccess/thread/025b012d-82e1-416f-b1b8-00c59cb0ebf5
maybe you could trace it
http://social.msdn.microsoft.com/Forums/en/sqldataaccess/thread/025b012d-82e1-416f-b1b8-00c59cb0ebf5
ASKER
One of the links points to a problem with the driver. I have a feeling the MAS90 ODBC driver may not be 100%.
Thanks for the pointer.
Thanks for the pointer.
Glad you found it.
ASKER