Invalid class string (ASP)

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   In my previous post, I mentioned that I wanted to do more testing of my ASP code on a second computer before asking my web host to 'install' the component. Doing so opened up another issue, that I've yet to resolve..

After registering the ActiveX DLL (iSED.DLL), ASP reports my (previously working) class string as invalid - as if the DLL wasn't registered after all.

I've unregistered it, registered again, also with a newly downloaded file (in case the copying corrupted it), with no luck. 

Any suggestions on how to attack this problem?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Autodidact Members Profile Find Members Posts Team Player Joined: 03 Feb 06 Status: Offline Points: 21	Post Options Post Reply Quote Autodidact Report Post Thanks(0) Quote Reply Topic: Invalid class string (ASP) Posted: 17 Dec 07 at 5:56PM
	In my previous post, I mentioned that I wanted to do more testing of my ASP code on a second computer before asking my web host to 'install' the component. Doing so opened up another issue, that I've yet to resolve.. After registering the ActiveX DLL (iSED.DLL), ASP reports my (previously working) class string as invalid - as if the DLL wasn't registered after all. I've unregistered it, registered again, also with a newly downloaded file (in case the copying corrupted it), with no luck. Any suggestions on how to attack this problem?

marian_pascalau Members Profile Find Members Posts Debenu Quick PDF Library Expert Joined: 28 Mar 06 Location: Germany Status: Offline Points: 278	Post Options Post Reply Quote marian_pascalau Report Post Thanks(0) Quote Reply Posted: 18 Dec 07 at 5:11AM
	Hi there, there are 2x possible sollutions: 1. You have to pay attention if your ASP environment, the user under which is hosted de ASP application has access to your DLL folder (ACCESS-DENIED ERROR). 2. In case of ASP.NET application there is a workaround with which you can expose the ActiveX dll without using the COM engine. But this solution works only for ASP.NET in case you have the source code available (or, in case you don't have the source code with a custom solution provided though sponsoring).