Hi all,
Hopefully someone here can help me with a very interesting problem I am having.
I have a COM object on a web server. The component is access through ASP pages through the Server.CreateObject call, and everything works fine ... but after a while, the ASP pages would crashed with the "ClassFactory cannot supply requested class" error. If I shut down the COM using "Compenent Services" and restarted it, everything is ok again.
The COM object was created in Visual Basic 6.0. I registered the dll using "Component Services" as a Server Application with Security = Identity and run as an Administrator.
I have been searching all over the web for similar problems, but every sources I find contain the solution that the COM needs to be registered. This is not the case.
The COM is registered, and is working fine ... it just chokes every now and then and required me to restart the COM service, or if I wait long enough, I assume the COM died from idle'ing and everything would be ok again.
What's going on here? Has anybody else encounter this problem? or have any clues to what is goin on?
Hopefully someone here can help me with a very interesting problem I am having.
I have a COM object on a web server. The component is access through ASP pages through the Server.CreateObject call, and everything works fine ... but after a while, the ASP pages would crashed with the "ClassFactory cannot supply requested class" error. If I shut down the COM using "Compenent Services" and restarted it, everything is ok again.
The COM object was created in Visual Basic 6.0. I registered the dll using "Component Services" as a Server Application with Security = Identity and run as an Administrator.
I have been searching all over the web for similar problems, but every sources I find contain the solution that the COM needs to be registered. This is not the case.
The COM is registered, and is working fine ... it just chokes every now and then and required me to restart the COM service, or if I wait long enough, I assume the COM died from idle'ing and everything would be ok again.
What's going on here? Has anybody else encounter this problem? or have any clues to what is goin on?