April 1, 2004 at 12:08 am
Hi Guys,
Has anyone come accross something similar below...I will let you know more details if Yes.
Please let me know on what occasion this could occur.
1. Automation error
Catastrophic failure |GetArray|Table ID : 8|-2147418113||.
2. [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'stride_demolaptop'.|General_SetMemObj||5||.
Levi
Jesus My Saviour
April 1, 2004 at 11:51 am
Here's what I found in the Knowledge Base.
FIX: "Catastrophic Failure" Error Message When You Use adPromptAlways to Connect to SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;314635
PRB: Catastrophic Error Occurs Referencing ADO Recordset
K. Brian Kelley
@kbriankelley
April 1, 2004 at 10:40 pm
Thanks Kelly,
But we use ODBC and this does not seems to be the cause...anyway...let me know if you have something more on this..
Levi
Jesus My Saviour
April 2, 2004 at 1:30 am
Check your service accounts are not locked out if they are network accounts. If this does not work then set your service accounts to local system and try again.
April 2, 2004 at 2:22 am
Hi
The SQL Server7.0 is clustered and replication enabled...and the user account is in the local admin group, cannot change the service accounts to local
Levi
Jesus My Saviour
April 2, 2004 at 6:56 am
Both articles use OLE DB as an example to reproduce the behavior but they leave it generic to ADO in general. If you are using ADO, these could apply. Also, even if you're using ODBC, you may have an OLE DB interconnectivity in there somewhere...
SQL Server Connection Basics (MSDN)
K. Brian Kelley
@kbriankelley
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply