Have you tried to register again the DLL ? (regsvr32).
The easisest way to test a permission issue whould be liekly to add the IUSR
account to the local admin group.
Of course remove it then. If this is really a permission issue you could use
"Component services" that is in the "admin tools". Here you can create a new
"COM+ Application". The identity tab allows to run all components under a
particular identity. Then you can register the DLL below this COM+
application.
As a result the DLL will run under the specified identity.
As it works on another machine wihtout doing this, I would rather thought of
some kind of registration problem (or a missing dependencty ?)...
--
Patrice
<gr********@earthlink.net> a écrit dans le message de
news:11**********************@g14g2000cwa.googlegr oups.com...
Patrice wrote: What do you do ? What is the exact message ? How do you have given this
account all those rights ?
You could try perhaps try with the "component manager" that allows to
run just the DLL under a particular identity...
--
Patrice
Thanks for the reply. All I'm doing is:
Set obj = Server.CreateObject("object.progid")
and I get the error. It used to work until I had to rebuild the .dll.
I also get Server.CreateObject errors when trying to instantiate other
ActiveX objects/3rd party COM components w/anonymous access enabled. I
don't have this problem on another machine, so there appears to be some
type of permission issue, specifically with ISR_<machinename>.
Are you talking about DCOMCNFG.EXE? I'm using Windows XP Pro. Can you
or anyone else step me through this to enable whatever I need to for
the ISR_<machinename> account?
