Did you put the dll on the new server and regsvr32 it? If you're not sure
what that means, is the person who setup the IIS5 server still around. When
you create a custom component, you must regsvr32 it. That basically tells
the computer what to look for to create when you say
set x = CreateObject("MyCustom.Component")
Put the .dll in your %systemroot%\system32 directory, and then from the
command prompt, enter:
Try that anyway... Your next issue may be a permissions error. I'd hit up
an IIS group for that if that happens though.
Ray at home
"Geoff Conn" <geoff.connhoneywell.com> wrote in message
news:29f0d01c46529$1ac63b80$a301280aphx.gbl...> I can run an asp application on IIS 5.0 and 6.0. The
> application accesses a custom DLL which retrieves data.
> When the same app is run on an Site Server 3.0 then
> following error is returned
> '...ASP 0177 (0x800401F3) Invalid ProgID...' I'm not an
> IIS guru, I know the page works, What needs to be done on
> the Site Server in order to run the ASP page as expected?
> Thanks in Advance