ASP/IIS errors on Custom COM call

[Steve]

All --

This occasionally happens, and there's no set pattern on why this
is... perhaps it happens a few times every few months or so.

I have a custom ATL COM object that handles data from multiple pages
and sites on my server. Occasionally, I'll get the following errors:

ASP_0241|Create Object_Exceptio n|-|ASP_0241|Creat eObject_Excepti on|42|ASP_0177_ :_c0000005|Serv er.CreateObject _Failed
500

Which sometimes is followed by (in no particular order)
800a01fb|An_exc eption_occurred :_'function name'

function name isn't always the same, but is always one in my COM
object.

The problem associated with this error is that the object cannot be
created again until IIS is restarted. This object controls a very
vital part of the site, and all users will typically get the:

Active Server Pages error 'ASP 0241'

CreateObject Exception

/Site/account.asp

The CreateObject of '(null)' caused exception C0000005.

Server object error 'ASP 0177 : c0000005'

Server.CreateOb ject Failed

/Site/account.asp, line 42

c0000005
This custom COM object has been successfully deployed for nearly two
years, and under intense traffic at times. One of the things I'm
thinking is that I return an S_OK when I trap an error... so

try{
blah
}
catch (mycustomerrorc lass& err)
{}
catch (...)
{
tell something an odd error occured

}
return S_OK;

It seems like once the (...) is caught, the other errors appear... or
vice versa. Do you think I should be returning E_FAIL in that catch
all statement?

This COM object uses no external COM objects (ado, etc). The only
idea I can think of if to try the E_FAIL, but I thought I successfully
have caught the error. Is this not the case?

Thanks -- Steve

[Aaron Bertrand - MVP]

Permissions issue maybe?

http://www.aspfaq.com/2355
http://www.aspfaq.com/search.asp?q=c0000005

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/


"Steve" <st**********@t icketmaster.com > wrote in message
news:b7******** *************** **@posting.goog le.com...

All --

This occasionally happens, and there's no set pattern on why this
is... perhaps it happens a few times every few months or so.

I have a custom ATL COM object that handles data from multiple pages
and sites on my server. Occasionally, I'll get the following errors:

ASP_0241|Create Object_Exceptio n|-|ASP_0241|Creat eObject_Excepti on|42|ASP_017
7_:_c0000005|Se rver.CreateObje ct_Failed 500

Which sometimes is followed by (in no particular order)
800a01fb|An_exc eption_occurred :_'function name'

function name isn't always the same, but is always one in my COM
object.

The problem associated with this error is that the object cannot be
created again until IIS is restarted. This object controls a very
vital part of the site, and all users will typically get the:

Active Server Pages error 'ASP 0241'

CreateObject Exception

/Site/account.asp

The CreateObject of '(null)' caused exception C0000005.

Server object error 'ASP 0177 : c0000005'

Server.CreateOb ject Failed

/Site/account.asp, line 42

c0000005
This custom COM object has been successfully deployed for nearly two
years, and under intense traffic at times. One of the things I'm
thinking is that I return an S_OK when I trap an error... so

try{
blah
}
catch (mycustomerrorc lass& err)
{}
catch (...)
{
tell something an odd error occured

}
return S_OK;

It seems like once the (...) is caught, the other errors appear... or
vice versa. Do you think I should be returning E_FAIL in that catch
all statement?

This COM object uses no external COM objects (ado, etc). The only
idea I can think of if to try the E_FAIL, but I thought I successfully
have caught the error. Is this not the case?

Thanks -- Steve

[Steve]

Doesn't appear so. I would imagine if it were a permissions thing it
would do it consistiently. Hasn't happened in two days (so far) so
I'm still trying to track it down.

Thanks for your reply though!

"Aaron Bertrand - MVP" <aa***@TRASHasp faq.com> wrote in message news:<O2******* *******@tk2msft ngp13.phx.gbl>. ..

Permissions issue maybe?

http://www.aspfaq.com/2355
http://www.aspfaq.com/search.asp?q=c0000005

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/


"Steve" <st**********@t icketmaster.com > wrote in message
news:b7******** *************** **@posting.goog le.com...

All --

This occasionally happens, and there's no set pattern on why this
is... perhaps it happens a few times every few months or so.

I have a custom ATL COM object that handles data from multiple pages
and sites on my server. Occasionally, I'll get the following errors:

ASP_0241|Create Object_Exceptio n|-|ASP_0241|Creat eObject_Excepti on|42|ASP_017
7_:_c0000005|Se rver.CreateObje ct_Failed

500

Which sometimes is followed by (in no particular order)
800a01fb|An_exc eption_occurred :_'function name'

function name isn't always the same, but is always one in my COM
object.

The problem associated with this error is that the object cannot be
created again until IIS is restarted. This object controls a very
vital part of the site, and all users will typically get the:

Active Server Pages error 'ASP 0241'

CreateObject Exception

/Site/account.asp

The CreateObject of '(null)' caused exception C0000005.

Server object error 'ASP 0177 : c0000005'

Server.CreateOb ject Failed

/Site/account.asp, line 42

c0000005
This custom COM object has been successfully deployed for nearly two
years, and under intense traffic at times. One of the things I'm
thinking is that I return an S_OK when I trap an error... so

try{
blah
}
catch (mycustomerrorc lass& err)
{}
catch (...)
{
tell something an odd error occured

}
return S_OK;

It seems like once the (...) is caught, the other errors appear... or
vice versa. Do you think I should be returning E_FAIL in that catch
all statement?

This COM object uses no external COM objects (ado, etc). The only
idea I can think of if to try the E_FAIL, but I thought I successfully
have caught the error. Is this not the case?

Thanks -- Steve

[Craig]

Any luck in resolving this issue? We seem to suddenly experience the same
thing. Sometimes, after a server reboot, we will start getting the same
error. I can usually fix it by installing MDAC and Windows Script, then
rebooting the server, but it will eventually creep back. We also have a
custom COM object which has ran successfully for nearly three years.
"Steve" <st**********@t icketmaster.com > wrote in message
news:b7******** *************** ***@posting.goo gle.com...

Doesn't appear so. I would imagine if it were a permissions thing it
would do it consistiently. Hasn't happened in two days (so far) so
I'm still trying to track it down.

Thanks for your reply though!

"Aaron Bertrand - MVP" <aa***@TRASHasp faq.com> wrote in message

news:<O2******* *******@tk2msft ngp13.phx.gbl>. ..

Permissions issue maybe?

http://www.aspfaq.com/2355
http://www.aspfaq.com/search.asp?q=c0000005

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/


"Steve" <st**********@t icketmaster.com > wrote in message
news:b7******** *************** **@posting.goog le.com...

All --

This occasionally happens, and there's no set pattern on why this
is... perhaps it happens a few times every few months or so.

I have a custom ATL COM object that handles data from multiple pages
and sites on my server. Occasionally, I'll get the following errors:

ASP_0241|Create Object_Exceptio n|-|ASP_0241|Creat eObject_Excepti on|42|ASP_017 7_:_c0000005|Se rver.CreateObje ct_Failed

500

Which sometimes is followed by (in no particular order)
800a01fb|An_exc eption_occurred :_'function name'

function name isn't always the same, but is always one in my COM
object.

The problem associated with this error is that the object cannot be
created again until IIS is restarted. This object controls a very
vital part of the site, and all users will typically get the:

Active Server Pages error 'ASP 0241'

CreateObject Exception

/Site/account.asp

The CreateObject of '(null)' caused exception C0000005.

Server object error 'ASP 0177 : c0000005'

Server.CreateOb ject Failed

/Site/account.asp, line 42

c0000005
This custom COM object has been successfully deployed for nearly two
years, and under intense traffic at times. One of the things I'm
thinking is that I return an S_OK when I trap an error... so

try{
blah
}
catch (mycustomerrorc lass& err)
{}
catch (...)
{
tell something an odd error occured

}
return S_OK;

It seems like once the (...) is caught, the other errors appear... or
vice versa. Do you think I should be returning E_FAIL in that catch
all statement?

This COM object uses no external COM objects (ado, etc). The only
idea I can think of if to try the E_FAIL, but I thought I successfully
have caught the error. Is this not the case?

Thanks -- Steve