Error log shows ASPDB error

[Dave Berkson]

We have found an ASPDB error in our NT error log. At the same time, we have had some problems with IIS crashing randomly, and are wondering if the ASPDB problem is causing our IIS problem. Here is the ASPDB error message:

Failed on creation from object context: CoGetClassObject
(ProgId: ASP.DB) (CLSID:
{C043843D-89F9-11D4-9099-00500461754E}) (Interface:
IClassFactory) (IID: {00000001-0000-0000-C000-000000000046})
(Microsoft Transaction Server Internals Information: File:
i:vipersrc
untimecontextccontext.cpp, Line: 1355)

We are running UNO with the enterprise license on NT 4.0. Does anyone have an idea what could be causing the ASPDB error, and if this ASPDB error could make IIS crash?

[John]

Hi Dave,

We haven't experience this at all. Our main server at www.aspdb.com has been running ASPdb for two years and hasn't crashed or generated this error yet.

Is it possible you registered the dll with REGSVR32 instead of MTS? Or that you did it with both?

Maybe you should completely uninstall it (and test that it's out by running a sample program), then installing the latest version?

Thanks,
John



------------
Dave Berkson at 11/2/00 3:48:27 PM

We have found an ASPDB error in our NT error log. At the same time, we have had some problems with IIS crashing randomly, and are wondering if the ASPDB problem is causing our IIS problem. Here is the ASPDB error message:

Failed on creation from object context: CoGetClassObject
(ProgId: ASP.DB) (CLSID:
{C043843D-89F9-11D4-9099-00500461754E}) (Interface:
IClassFactory) (IID: {00000001-0000-0000-C000-000000000046})
(Microsoft Transaction Server Internals Information: File:
i:vipersrc
untimecontextccontext.cpp, Line: 1355)

We are running UNO with the enterprise license on NT 4.0. Does anyone have an idea what could be causing the ASPDB error, and if this ASPDB error could make IIS crash?

[John Rudnick]

Hi John,

We original started using the Enterprise component about 4 months ago. No problems at all. We upgraded to UNO and using the key to give Enterprise functionality about the same time the issues surfaced.

We are absolutely positive there is only one component registered.

First because we de-registered the old component then installed the new one.

Second because we are now trying it on our third server.

We wanted to rule out hardware and IIS install issues, so we have tried it on two additional machines. In the cases of box 2 and 3 the old component was never installed.

In all cases we use MTS to register and de-register.

Also it should be noted that the problem is highly intermittent. For example yesterday IIS shut down twice on two domains (we have 8 on the box) yesterday with approximatly 12 hours between shutdowns. Today so far no problems.

Any help would be greatly appreciated.

Thanks,

JR


------------
John at 11/2/00 7:41:56 PM

Hi Dave,

We haven't experience this at all. Our main server at www.aspdb.com has been running ASPdb for two years and hasn't crashed or generated this error yet.

Is it possible you registered the dll with REGSVR32 instead of MTS? Or that you did it with both?

Maybe you should completely uninstall it (and test that it's out by running a sample program), then installing the latest version?

Thanks,
John



------------
Dave Berkson at 11/2/00 3:48:27 PM

We have found an ASPDB error in our NT error log. At the same time, we have had some problems with IIS crashing randomly, and are wondering if the ASPDB problem is causing our IIS problem. Here is the ASPDB error message:

Failed on creation from object context: CoGetClassObject
(ProgId: ASP.DB) (CLSID:
{C043843D-89F9-11D4-9099-00500461754E}) (Interface:
IClassFactory) (IID: {00000001-0000-0000-C000-000000000046})
(Microsoft Transaction Server Internals Information: File:
i:vipersrc
untimecontextccontext.cpp, Line: 1355)

We are running UNO with the enterprise license on NT 4.0. Does anyone have an idea what could be causing the ASPDB error, and if this ASPDB error could make IIS crash?

[John]

Hi John,

If you unregister ASPdb, does IIS still crash?

Also, what kind of database / ODBC driver are you using?

Possibly we're making calls to your database which is causing problems? Is your database server running on the same machine as IIS?

Thanks,
John

------------
John Rudnick at 11/3/00 11:43:08 AM

Hi John,

We original started using the Enterprise component about 4 months ago. No problems at all. We upgraded to UNO and using the key to give Enterprise functionality about the same time the issues surfaced.

We are absolutely positive there is only one component registered.

First because we de-registered the old component then installed the new one.

Second because we are now trying it on our third server.

We wanted to rule out hardware and IIS install issues, so we have tried it on two additional machines. In the cases of box 2 and 3 the old component was never installed.

In all cases we use MTS to register and de-register.

Also it should be noted that the problem is highly intermittent. For example yesterday IIS shut down twice on two domains (we have 8 on the box) yesterday with approximatly 12 hours between shutdowns. Today so far no problems.

Any help would be greatly appreciated.

Thanks,

JR


------------
John at 11/2/00 7:41:56 PM

Hi Dave,

We haven't experience this at all. Our main server at www.aspdb.com has been running ASPdb for two years and hasn't crashed or generated this error yet.

Is it possible you registered the dll with REGSVR32 instead of MTS? Or that you did it with both?

Maybe you should completely uninstall it (and test that it's out by running a sample program), then installing the latest version?

Thanks,
John



------------
Dave Berkson at 11/2/00 3:48:27 PM

We have found an ASPDB error in our NT error log. At the same time, we have had some problems with IIS crashing randomly, and are wondering if the ASPDB problem is causing our IIS problem. Here is the ASPDB error message:

Failed on creation from object context: CoGetClassObject
(ProgId: ASP.DB) (CLSID:
{C043843D-89F9-11D4-9099-00500461754E}) (Interface:
IClassFactory) (IID: {00000001-0000-0000-C000-000000000046})
(Microsoft Transaction Server Internals Information: File:
i:vipersrc
untimecontextccontext.cpp, Line: 1355)

We are running UNO with the enterprise license on NT 4.0. Does anyone have an idea what could be causing the ASPDB error, and if this ASPDB error could make IIS crash?

Hi John,

Boxes without ASPDB do not crash (at least no more often than normal Windows NT 4). The difference is normal boxes that almost never crash as long as we reboot them once a week versus 2 crashes yesterday and 3 the day before.

In addition the one it is on now did not crash until it was installed. Plus the event log message Dave posted clearly shows errors comming from ASPDB.

We are connecting to a seperate SQL 7 box, using standard ODBC connections that work fine on our none ASPDB apps and also work fine with the ASPDB apps prior to the upgrade and also work fine with the current version in between crashes.

I am really stumped here and appreciate your help.

Thanks,

JR



------------
John at 11/3/00 12:00:25 PM


Hi John,

If you unregister ASPdb, does IIS still crash?

Also, what kind of database / ODBC driver are you using?

Possibly we're making calls to your database which is causing problems? Is your database server running on the same machine as IIS?

Thanks,
John

------------
John Rudnick at 11/3/00 11:43:08 AM

Hi John,

We original started using the Enterprise component about 4 months ago. No problems at all. We upgraded to UNO and using the key to give Enterprise functionality about the same time the issues surfaced.

We are absolutely positive there is only one component registered.

First because we de-registered the old component then installed the new one.

Second because we are now trying it on our third server.

We wanted to rule out hardware and IIS install issues, so we have tried it on two additional machines. In the cases of box 2 and 3 the old component was never installed.

In all cases we use MTS to register and de-register.

Also it should be noted that the problem is highly intermittent. For example yesterday IIS shut down twice on two domains (we have 8 on the box) yesterday with approximatly 12 hours between shutdowns. Today so far no problems.

Any help would be greatly appreciated.

Thanks,

JR


------------
John at 11/2/00 7:41:56 PM

Hi Dave,

We haven't experience this at all. Our main server at www.aspdb.com has been running ASPdb for two years and hasn't crashed or generated this error yet.

Is it possible you registered the dll with REGSVR32 instead of MTS? Or that you did it with both?

Maybe you should completely uninstall it (and test that it's out by running a sample program), then installing the latest version?

Thanks,
John



------------
Dave Berkson at 11/2/00 3:48:27 PM

We have found an ASPDB error in our NT error log. At the same time, we have had some problems with IIS crashing randomly, and are wondering if the ASPDB problem is causing our IIS problem. Here is the ASPDB error message:

Failed on creation from object context: CoGetClassObject
(ProgId: ASP.DB) (CLSID:
{C043843D-89F9-11D4-9099-00500461754E}) (Interface:
IClassFactory) (IID: {00000001-0000-0000-C000-000000000046})
(Microsoft Transaction Server Internals Information: File:
i:vipersrc
untimecontextccontext.cpp, Line: 1355)

We are running UNO with the enterprise license on NT 4.0. Does anyone have an idea what could be causing the ASPDB error, and if this ASPDB error could make IIS crash?

[John]

Hi JR,

I might have a lead on this... Microsoft's knowledge base has an article at:

http://support.microsoft.com/support/kb/articles/Q241/0/57.ASP

which indicates that you can get this when you register a package (like ASPdb) using Interactive User instead of a fixed user account (like an Admin). Then, when whoever is logged onto your server happens to log off, the component can't get the security to run and it blows up. As we mention in step #9 of our installation instructions in registering the component in MTS, you should use "This User" and specify a user, "otherwise someone must be logged onto the server in order for ASPdb to run".

This could be just the ticket. Please try it and let us know if it solves the problem.

Thanks,
John


------------
at 11/3/00 12:16:26 PM

Hi John,

Boxes without ASPDB do not crash (at least no more often than normal Windows NT 4). The difference is normal boxes that almost never crash as long as we reboot them once a week versus 2 crashes yesterday and 3 the day before.

In addition the one it is on now did not crash until it was installed. Plus the event log message Dave posted clearly shows errors comming from ASPDB.

We are connecting to a seperate SQL 7 box, using standard ODBC connections that work fine on our none ASPDB apps and also work fine with the ASPDB apps prior to the upgrade and also work fine with the current version in between crashes.

I am really stumped here and appreciate your help.

Thanks,

JR



------------
John at 11/3/00 12:00:25 PM


Hi John,

If you unregister ASPdb, does IIS still crash?

Also, what kind of database / ODBC driver are you using?

Possibly we're making calls to your database which is causing problems? Is your database server running on the same machine as IIS?

Thanks,
John

------------
John Rudnick at 11/3/00 11:43:08 AM

Hi John,

We original started using the Enterprise component about 4 months ago. No problems at all. We upgraded to UNO and using the key to give Enterprise functionality about the same time the issues surfaced.

We are absolutely positive there is only one component registered.

First because we de-registered the old component then installed the new one.

Second because we are now trying it on our third server.

We wanted to rule out hardware and IIS install issues, so we have tried it on two additional machines. In the cases of box 2 and 3 the old component was never installed.

In all cases we use MTS to register and de-register.

Also it should be noted that the problem is highly intermittent. For example yesterday IIS shut down twice on two domains (we have 8 on the box) yesterday with approximatly 12 hours between shutdowns. Today so far no problems.

Any help would be greatly appreciated.

Thanks,

JR


------------
John at 11/2/00 7:41:56 PM

Hi Dave,

We haven't experience this at all. Our main server at www.aspdb.com has been running ASPdb for two years and hasn't crashed or generated this error yet.

Is it possible you registered the dll with REGSVR32 instead of MTS? Or that you did it with both?

Maybe you should completely uninstall it (and test that it's out by running a sample program), then installing the latest version?

Thanks,
John



------------
Dave Berkson at 11/2/00 3:48:27 PM

We have found an ASPDB error in our NT error log. At the same time, we have had some problems with IIS crashing randomly, and are wondering if the ASPDB problem is causing our IIS problem. Here is the ASPDB error message:

Failed on creation from object context: CoGetClassObject
(ProgId: ASP.DB) (CLSID:
{C043843D-89F9-11D4-9099-00500461754E}) (Interface:
IClassFactory) (IID: {00000001-0000-0000-C000-000000000046})
(Microsoft Transaction Server Internals Information: File:
i:vipersrc
untimecontextccontext.cpp, Line: 1355)

We are running UNO with the enterprise license on NT 4.0. Does anyone have an idea what could be causing the ASPDB error, and if this ASPDB error could make IIS crash?

[John Rudnick]

Hi,

I'm afraid that is not it. We create a seperate account called aspdb that we give admin rights to.

Just out of curiosity even if that had been the problem what would have accounted for the intermitent nature of the issue?

Thanks,

JR


------------
John at 11/3/00 4:41:38 PM

Hi JR,

I might have a lead on this... Microsoft's knowledge base has an article at:

http://support.microsoft.com/support/kb/articles/Q241/0/57.ASP

which indicates that you can get this when you register a package (like ASPdb) using Interactive User instead of a fixed user account (like an Admin). Then, when whoever is logged onto your server happens to log off, the component can't get the security to run and it blows up. As we mention in step #9 of our installation instructions in registering the component in MTS, you should use "This User" and specify a user, "otherwise someone must be logged onto the server in order for ASPdb to run".

This could be just the ticket. Please try it and let us know if it solves the problem.

Thanks,
John


------------
at 11/3/00 12:16:26 PM

Hi John,

Boxes without ASPDB do not crash (at least no more often than normal Windows NT 4). The difference is normal boxes that almost never crash as long as we reboot them once a week versus 2 crashes yesterday and 3 the day before.

In addition the one it is on now did not crash until it was installed. Plus the event log message Dave posted clearly shows errors comming from ASPDB.

We are connecting to a seperate SQL 7 box, using standard ODBC connections that work fine on our none ASPDB apps and also work fine with the ASPDB apps prior to the upgrade and also work fine with the current version in between crashes.

I am really stumped here and appreciate your help.

Thanks,

JR



------------
John at 11/3/00 12:00:25 PM


Hi John,

If you unregister ASPdb, does IIS still crash?

Also, what kind of database / ODBC driver are you using?

Possibly we're making calls to your database which is causing problems? Is your database server running on the same machine as IIS?

Thanks,
John

------------
John Rudnick at 11/3/00 11:43:08 AM

Hi John,

We original started using the Enterprise component about 4 months ago. No problems at all. We upgraded to UNO and using the key to give Enterprise functionality about the same time the issues surfaced.

We are absolutely positive there is only one component registered.

First because we de-registered the old component then installed the new one.

Second because we are now trying it on our third server.

We wanted to rule out hardware and IIS install issues, so we have tried it on two additional machines. In the cases of box 2 and 3 the old component was never installed.

In all cases we use MTS to register and de-register.

Also it should be noted that the problem is highly intermittent. For example yesterday IIS shut down twice on two domains (we have 8 on the box) yesterday with approximatly 12 hours between shutdowns. Today so far no problems.

Any help would be greatly appreciated.

Thanks,

JR


------------
John at 11/2/00 7:41:56 PM

Hi Dave,

We haven't experience this at all. Our main server at www.aspdb.com has been running ASPdb for two years and hasn't crashed or generated this error yet.

Is it possible you registered the dll with REGSVR32 instead of MTS? Or that you did it with both?

Maybe you should completely uninstall it (and test that it's out by running a sample program), then installing the latest version?

Thanks,
John



------------
Dave Berkson at 11/2/00 3:48:27 PM

We have found an ASPDB error in our NT error log. At the same time, we have had some problems with IIS crashing randomly, and are wondering if the ASPDB problem is causing our IIS problem. Here is the ASPDB error message:

Failed on creation from object context: CoGetClassObject
(ProgId: ASP.DB) (CLSID:
{C043843D-89F9-11D4-9099-00500461754E}) (Interface:
IClassFactory) (IID: {00000001-0000-0000-C000-000000000046})
(Microsoft Transaction Server Internals Information: File:
i:vipersrc
untimecontextccontext.cpp, Line: 1355)

We are running UNO with the enterprise license on NT 4.0. Does anyone have an idea what could be causing the ASPDB error, and if this ASPDB error could make IIS crash?

[John Rudnick]

Hi,

I'm afraid that is not it. We create a seperate account called aspdb that we give admin rights to.

Just out of curiosity even if that had been the problem what would have accounted for the intermitent nature of the issue?

Thanks,

JR


------------
John at 11/3/00 4:41:38 PM

Hi JR,

I might have a lead on this... Microsoft's knowledge base has an article at:

http://support.microsoft.com/support/kb/articles/Q241/0/57.ASP

which indicates that you can get this when you register a package (like ASPdb) using Interactive User instead of a fixed user account (like an Admin). Then, when whoever is logged onto your server happens to log off, the component can't get the security to run and it blows up. As we mention in step #9 of our installation instructions in registering the component in MTS, you should use "This User" and specify a user, "otherwise someone must be logged onto the server in order for ASPdb to run".

This could be just the ticket. Please try it and let us know if it solves the problem.

Thanks,
John


------------
at 11/3/00 12:16:26 PM

Hi John,

Boxes without ASPDB do not crash (at least no more often than normal Windows NT 4). The difference is normal boxes that almost never crash as long as we reboot them once a week versus 2 crashes yesterday and 3 the day before.

In addition the one it is on now did not crash until it was installed. Plus the event log message Dave posted clearly shows errors comming from ASPDB.

We are connecting to a seperate SQL 7 box, using standard ODBC connections that work fine on our none ASPDB apps and also work fine with the ASPDB apps prior to the upgrade and also work fine with the current version in between crashes.

I am really stumped here and appreciate your help.

Thanks,

JR



------------
John at 11/3/00 12:00:25 PM


Hi John,

If you unregister ASPdb, does IIS still crash?

Also, what kind of database / ODBC driver are you using?

Possibly we're making calls to your database which is causing problems? Is your database server running on the same machine as IIS?

Thanks,
John

------------
John Rudnick at 11/3/00 11:43:08 AM

Hi John,

We original started using the Enterprise component about 4 months ago. No problems at all. We upgraded to UNO and using the key to give Enterprise functionality about the same time the issues surfaced.

We are absolutely positive there is only one component registered.

First because we de-registered the old component then installed the new one.

Second because we are now trying it on our third server.

We wanted to rule out hardware and IIS install issues, so we have tried it on two additional machines. In the cases of box 2 and 3 the old component was never installed.

In all cases we use MTS to register and de-register.

Also it should be noted that the problem is highly intermittent. For example yesterday IIS shut down twice on two domains (we have 8 on the box) yesterday with approximatly 12 hours between shutdowns. Today so far no problems.

Any help would be greatly appreciated.

Thanks,

JR


------------
John at 11/2/00 7:41:56 PM

Hi Dave,

We haven't experience this at all. Our main server at www.aspdb.com has been running ASPdb for two years and hasn't crashed or generated this error yet.

Is it possible you registered the dll with REGSVR32 instead of MTS? Or that you did it with both?

Maybe you should completely uninstall it (and test that it's out by running a sample program), then installing the latest version?

Thanks,
John



------------
Dave Berkson at 11/2/00 3:48:27 PM

We have found an ASPDB error in our NT error log. At the same time, we have had some problems with IIS crashing randomly, and are wondering if the ASPDB problem is causing our IIS problem. Here is the ASPDB error message:

Failed on creation from object context: CoGetClassObject
(ProgId: ASP.DB) (CLSID:
{C043843D-89F9-11D4-9099-00500461754E}) (Interface:
IClassFactory) (IID: {00000001-0000-0000-C000-000000000046})
(Microsoft Transaction Server Internals Information: File:
i:vipersrc
untimecontextccontext.cpp, Line: 1355)

We are running UNO with the enterprise license on NT 4.0. Does anyone have an idea what could be causing the ASPDB error, and if this ASPDB error could make IIS crash?

[John Rudnick]

Hi,

I'm afraid that is not it. We create a seperate account called aspdb that we give admin rights to.

Just out of curiosity even if that had been the problem what would have accounted for the intermitent nature of the issue?

Thanks,

JR


------------
John at 11/3/00 4:41:38 PM

Hi JR,

I might have a lead on this... Microsoft's knowledge base has an article at:

http://support.microsoft.com/support/kb/articles/Q241/0/57.ASP

which indicates that you can get this when you register a package (like ASPdb) using Interactive User instead of a fixed user account (like an Admin). Then, when whoever is logged onto your server happens to log off, the component can't get the security to run and it blows up. As we mention in step #9 of our installation instructions in registering the component in MTS, you should use "This User" and specify a user, "otherwise someone must be logged onto the server in order for ASPdb to run".

This could be just the ticket. Please try it and let us know if it solves the problem.

Thanks,
John


------------
at 11/3/00 12:16:26 PM

Hi John,

Boxes without ASPDB do not crash (at least no more often than normal Windows NT 4). The difference is normal boxes that almost never crash as long as we reboot them once a week versus 2 crashes yesterday and 3 the day before.

In addition the one it is on now did not crash until it was installed. Plus the event log message Dave posted clearly shows errors comming from ASPDB.

We are connecting to a seperate SQL 7 box, using standard ODBC connections that work fine on our none ASPDB apps and also work fine with the ASPDB apps prior to the upgrade and also work fine with the current version in between crashes.

I am really stumped here and appreciate your help.

Thanks,

JR



------------
John at 11/3/00 12:00:25 PM


Hi John,

If you unregister ASPdb, does IIS still crash?

Also, what kind of database / ODBC driver are you using?

Possibly we're making calls to your database which is causing problems? Is your database server running on the same machine as IIS?

Thanks,
John

------------
John Rudnick at 11/3/00 11:43:08 AM

Hi John,

We original started using the Enterprise component about 4 months ago. No problems at all. We upgraded to UNO and using the key to give Enterprise functionality about the same time the issues surfaced.

We are absolutely positive there is only one component registered.

First because we de-registered the old component then installed the new one.

Second because we are now trying it on our third server.

We wanted to rule out hardware and IIS install issues, so we have tried it on two additional machines. In the cases of box 2 and 3 the old component was never installed.

In all cases we use MTS to register and de-register.

Also it should be noted that the problem is highly intermittent. For example yesterday IIS shut down twice on two domains (we have 8 on the box) yesterday with approximatly 12 hours between shutdowns. Today so far no problems.

Any help would be greatly appreciated.

Thanks,

JR


------------
John at 11/2/00 7:41:56 PM

Hi Dave,

We haven't experience this at all. Our main server at www.aspdb.com has been running ASPdb for two years and hasn't crashed or generated this error yet.

Is it possible you registered the dll with REGSVR32 instead of MTS? Or that you did it with both?

Maybe you should completely uninstall it (and test that it's out by running a sample program), then installing the latest version?

Thanks,
John



------------
Dave Berkson at 11/2/00 3:48:27 PM

We have found an ASPDB error in our NT error log. At the same time, we have had some problems with IIS crashing randomly, and are wondering if the ASPDB problem is causing our IIS problem. Here is the ASPDB error message:

Failed on creation from object context: CoGetClassObject
(ProgId: ASP.DB) (CLSID:
{C043843D-89F9-11D4-9099-00500461754E}) (Interface:
IClassFactory) (IID: {00000001-0000-0000-C000-000000000046})
(Microsoft Transaction Server Internals Information: File:
i:vipersrc
untimecontextccontext.cpp, Line: 1355)

We are running UNO with the enterprise license on NT 4.0. Does anyone have an idea what could be causing the ASPDB error, and if this ASPDB error could make IIS crash?