CreateObject fails in .VBS script file but works in .ASP file !

Hi,

I can't instantiate an ActiveX component in a .VBS script file with
this code :
set myObject = createObject("ChilkatMail2.ChilkatMailMan2")
This component is used to send mails and it's really an "ActiveX
component".
I receive the following error message : "Could not create object named
ChilkatMail2.ChilkatMailMan2"
Note that if I run this .vbs with Cscript or WScript I receive the same
error message.

I also tried to create object with this code :
set myObject = Wscript.createObject("ChilkatMail2.ChilkatMailMan2")
... the result is the same.

But now, if I try exactly the same code in an .ASP page it WORKS !!!!!
The only difference is that I use Server.CreateObject (because it's
ASP).

This means that :
- the component is correctly registered (I checked all the entry points
with COM explorer)
- all the dependencies are present on the system (I think so...)

I'm logged on as Administrator, my system is Windows Server 2003 SP1
(x64)

I spend two days searching the web and I didn't find the solution,
could you please help me ?

Thanks a lot !!!

Regards

Thierry

Joe
Sun May 07 03:31:21 CDT 2006

"thierry38080" <thierryschneider@gmail.com> wrote in message
news:1146931059.400592.41330@j33g2000cwa.googlegroups.com...
> Hi,
>
> I can't instantiate an ActiveX component in a .VBS script file with
> this code :
> set myObject = createObject("ChilkatMail2.ChilkatMailMan2")
> This component is used to send mails and it's really an "ActiveX
> component".
> I receive the following error message : "Could not create object named
> ChilkatMail2.ChilkatMailMan2"
> Note that if I run this .vbs with Cscript or WScript I receive the same
> error message.
>
> I also tried to create object with this code :
> set myObject = Wscript.createObject("ChilkatMail2.ChilkatMailMan2")
> ... the result is the same.
>
> But now, if I try exactly the same code in an .ASP page it WORKS !!!!!
> The only difference is that I use Server.CreateObject (because it's
> ASP).
>
> This means that :
> - the component is correctly registered (I checked all the entry points
> with COM explorer)
> - all the dependencies are present on the system (I think so...)
>
> I'm logged on as Administrator, my system is Windows Server 2003 SP1
> (x64)
>
> I spend two days searching the web and I didn't find the solution,
> could you please help me ?
>
> Thanks a lot !!!
>
> Regards
>
> Thierry
>
Perhaps client-side activation is disabled, either via IE's security
settings or a third-party anti-virus/malware application.

--

Joe Fawcett - MVP

http://joe.fawcett.name

thierry38080
Tue May 09 04:05:26 CDT 2006

I still didn't find the solution with Windows Server 64 bits.
So I tried to re-install a 32 bits version of Windows Server and it
works !!!

Thanks

Joe Fawcett a =E9crit :

> "thierry38080" <thierryschneider@gmail.com> wrote in message
> news:1146931059.400592.41330@j33g2000cwa.googlegroups.com...
> > Hi,
> >
> > I can't instantiate an ActiveX component in a .VBS script file with
> > this code :
> > set myObject =3D createObject("ChilkatMail2.ChilkatMailMan2")
> > This component is used to send mails and it's really an "ActiveX
> > component".
> > I receive the following error message : "Could not create object named
> > ChilkatMail2.ChilkatMailMan2"
> > Note that if I run this .vbs with Cscript or WScript I receive the same
> > error message.
> >
> > I also tried to create object with this code :
> > set myObject =3D Wscript.createObject("ChilkatMail2.ChilkatMailMan2")
> > ... the result is the same.
> >
> > But now, if I try exactly the same code in an .ASP page it WORKS !!!!!
> > The only difference is that I use Server.CreateObject (because it's
> > ASP).
> >
> > This means that :
> > - the component is correctly registered (I checked all the entry points
> > with COM explorer)
> > - all the dependencies are present on the system (I think so...)
> >
> > I'm logged on as Administrator, my system is Windows Server 2003 SP1
> > (x64)
> >
> > I spend two days searching the web and I didn't find the solution,
> > could you please help me ?
> >
> > Thanks a lot !!!
> >
> > Regards
> >
> > Thierry
> >
> Perhaps client-side activation is disabled, either via IE's security
> settings or a third-party anti-virus/malware application.
>=20
> --=20
>=20
> Joe Fawcett - MVP
>=20
> http://joe.fawcett.name