1 2 Previous Next 15 Replies Latest reply on Jun 16, 2005 9:27 PM by 362437

ASP 'Catastropic Failure' error on Conn.open

362437 May 26, 2004 9:40 PM

We have an IIS/ASP multiuser web based application that uses Oracle Provider for OLE DB 9.2.0.1.0 and MDAC 2.71. One of our clients is having intermittent (1/2x day)trouble with their production server, intermittently receiving ONE of the following error messages on a random Connection.Open within the application:
--
ADODB.Command error '800a0e7d'
Requested operation requires an OLE DB Session object, which is not supported by the current provider.
--
Provider error '8000ffff'
Catastrophic failure
--
Active Server Pages error 'ASP 0115'
Unexpected error
A trappable error (C0000005) occurred in an external object. The script cannot continue running.
--
Regardless of the error message, the DLLHOST process refuses any further .open methods and we need to kill and restart in order to once again allow use of the application. We are very careful to close down all command and connection objects immediately after each query is run.
Code snippet is below. Thanks in advance for any guidance. --Rich

Set adoConn = Server.CreateObject("ADODB.Connection")
adoConn.Provider = "OraOLEDB.Oracle"
adoConn.Properties("Data Source").Value = ServerName
adoConn.Properties("User ID").Value = UserName
adoConn.Properties("Password").Value = Password
adoConn.Open *****crashes on this line

1. Re: ASP 'Catastropic Failure' error on Conn.open

15208 May 27, 2004 7:27 PM (in response to 362437)

Richard,
Does "MDAC 2.71" means you have applied ADO Version 2.7 Service Pack 1?

Sinclair
Like Show 0 Likes(0)

Actions
2. Re: ASP 'Catastropic Failure' error on Conn.open

15208 May 27, 2004 7:29 PM (in response to 362437)

Richard,
Does "MDAC 2.71" mean you have applied ADO Version 2.7 Service Pack 1?

Sinclair
Like Show 0 Likes(0)

Actions
3. Re: ASP 'Catastropic Failure' error on Conn.open

362437 May 27, 2004 8:11 PM (in response to 15208)

Yes, we are using MDAC 2.7 SP1, which also has a version ID of 2.71.9040.2.

Rich
Like Show 0 Likes(0)

Actions
4. Re: ASP 'Catastropic Failure' error on Conn.open

362437 Jun 3, 2004 2:27 PM (in response to 362437)

Any thoughts on this problem?

Thanks,

Rich
Like Show 0 Likes(0)

Actions
5. Re: ASP 'Catastropic Failure' error on Conn.open

15208 Jun 3, 2004 9:06 PM (in response to 362437)

Rich,
I wonder if this is related to OLEDB Resource Pooling. Turning off one or all services may make difference. Just a thought.

Sinclair
Like Show 0 Likes(0)

Actions
6. Re: ASP 'Catastropic Failure' error on Conn.open

362437 Jun 4, 2004 8:15 PM (in response to 15208)

Hi Sinclair,

I enumerated all properties on the connection, and saw that "OLE DB Services" is set to -7. This translates to all services on except pooling, enlistment, and cursor. What should I change this to?

Thanks,

Rich
Like Show 0 Likes(0)

Actions
7. Re: ASP 'Catastropic Failure' error on Conn.open

15208 Jun 4, 2004 8:33 PM (in response to 362437)

Rich,
I would suggest that use all services (which is default), i.e. OLE DB Services = -1. Let OLE DB do the pooling.

Sinclair
Like Show 0 Likes(0)

Actions
8. Re: ASP 'Catastropic Failure' error on Conn.open

362437 Jun 9, 2004 10:32 PM (in response to 15208)

Sinclair,

I have set the parameter to -1, and verified it was set correctly for all connections in our application.

The 8000ffff error still occurs.

Are there any other possibilities for the cause or methods I can use to troubleshoot this error?

Thanks,

Rich
Like Show 0 Likes(0)

Actions
9. Re: ASP 'Catastropic Failure' error on Conn.open

15208 Jun 12, 2004 2:08 AM (in response to 362437)

Rich,
I search Internet and find that that error also occurs with other providers. Furthermore, it even occurs with MDAC 2.8.

I suspect it mihgt have something to do with session pooling.

All except pooling, automatic transaction enlistment, and Client Cursor Engine "OLE DB Services = -8;"

You said yours was set to -7.

Sinclair
Like Show 0 Likes(0)

Actions
10. Re: ASP 'Catastropic Failure' error on Conn.open

429785 Sep 20, 2004 4:54 PM (in response to 362437)

We seem to be running into a similar problem using 9.0.1. Were you able to find a resolution?
Like Show 0 Likes(0)

Actions
11. Re: ASP 'Catastropic Failure' error on Conn.open

362437 Oct 1, 2004 5:00 PM (in response to 429785)

Our client simply moved the application to another server where the problem was no in evidence. We think it may have been due to an interaction of: application server load, db server load, and network topology and load.
Like Show 0 Likes(0)

Actions
12. Re: ASP 'Catastropic Failure' error on Conn.open

436300 Jan 13, 2005 11:22 PM (in response to 429785)

We're in the exact same situation. Any luck resolving problem?
Like Show 0 Likes(0)

Actions
13. Re: ASP 'Catastropic Failure' error on Conn.open

437566 Feb 2, 2005 9:37 AM (in response to 436300)

I encounter a similar error.
I use the Oracle client 9.2.0.1.0, the Oracle ODBC driver 9.2.0.6.5 and I update to MDAC 2.8.
I have an ASP website running under IIS.

here is my code :

"
Set ConSyt = Server.CreateObject("ADODB.Connection") '--- Ouverture Connection
ConSyt.ConnectionTimeout = 30
ConSyt.CommandTimeout = 15
ConSyt.Open Application("MAAFDB")

Set Cmd_S = Server.CreateObject("ADODB.Command")
Set RdS_S = Server.CreateObject("ADODB.Recordset")
Set Cmd_S.ActiveConnection = ConSyt
"

Sometimes I manage to execute the whole code.
Sometimes I get the following error on the last line of the code above :
Microsoft VBScript execution error (0x800A01FB)
An exception occured.: 'Cmd_S.ActiveConnection'
(I translate from the French sentence)
If I hit the refresh button, it then executes normally.

Any hint ?

Thanks in advance,

Michael.
Like Show 0 Likes(0)

Actions
14. Re: ASP 'Catastropic Failure' error on Conn.open

362437 Mar 24, 2005 9:53 PM (in response to 437566)

Unfortunately, no. We are still encountering this error on some of our client installations.

Rich
Like Show 0 Likes(0)

Actions

1 2 Previous Next

Go to original post