03-15-07 12:23 PM
It sounds like the 3rd party client software is not installed or
functioning properly on Windows Server 2003. Please verify with the
vendor that the software version you are using is supported on Windows
Server 2003 SP1. The fact that it ran on IIS5/W2K is not relevant for
discussion because the code could be written to not run on Windows
Server 2003 -- so it would work on IIS5/W2K but fail on IIS6/WS03 --
and who has the responsibility to make the application work? The
application vendor.
Failure to create the object indicates it is not registered properly.
Are you running Windows Server 2003 SP1 on a 64bit machine? If so,
then the 3rd party component is 32bit only and registered for 32bit
processes only -- and IIS runs in native 64bit on 64bit Windows by
default, so it will not be able to create that object.
In any case, the issue has to be resolved with the 3rd party client
software support. You need to determine if your specific version
supports Windows Server 2003 SP1 of the right processor architecture,
and if it is supported, you need to obtain further support from them
on how to make the application work.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Mar 15, 12:58 am, Kenneth <Kenn...@discussions.microsoft.com>
wrote:
> Hello,
>
> Recently, I am working on a web server migration from W2K with IIS5 to
> Window 2003 SP1 with IIS6. There is an ASP page in my web site that use
> VBScript to create object from DLL. I have enable ASP in IIS6 and when I r
un
> the ASP page, an error "Microsoft VBScript runtime error '800a01ad' Active
X
> component can't create object: 'iPGClientCOM.iPGClient' shown in the brows
er.
> I want to know if there is any setting that I have missed.
>
> Kenneth
>
> P.S. iPGClientCOM.iPGClient is a thrid-party client software install in th
e
> server. It works fine in W2K IIS5.
[ Post a follow-up to this message ]
|