Solved this.
Turned out to be the Process Model Identity setting in IIS on the target server. It had been set to 'NetworkService'. Once set back to 'ApplicationPoolIdentity' all was well. I registered with regasm(32 bit) with the /codebase switch.
I have a component created in VS2008 and compiled for 'any cpu'.
Once compiled I have registered the component with regasm (32 bit version), and can then create an instance of the object using server.createobject from an asp page.
This machine is running Windows7 and has a 64 bit processor...
thread796-1281495
I am having exactly the same problem as Andy was in this thread, but using the '/codebase' switch is not solving the issue.
I cannot use a strong-name when compiling as I am importing a 3rd party library that doesn't have a strong name.
It runs ok on the machine the object is...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.