From: avrbadri on
Hi - I have all my web apps, coded in classic ASP and VB 6.0. I am
trying to do a migration of apps. to a new WIN 2000 server. I am
getting this error

Server object error 'ASP 0177 : 800a801d'
Server.CreateObject Failed

I am unable to fix this issue for days and it is driving me nuts.For
the sake of testing, I have given full control to 'IUSR_account' on my
web folders,WINNT folders and given permission to registry nodes as
specifed in Microsoft site. I also observed that .NET applications are
working.

I also took a look at metabase.xml file and security policies.But i
cant find anything concretely.

I am sure that this has to do with conflict between .NET and classic
environment . Can anyone point me in the right direction? Thanks

From: Anthony Jones on
<avrbadri(a)gmail.com> wrote in message
news:1193279500.212167.305990(a)e34g2000pro.googlegroups.com...
> Hi - I have all my web apps, coded in classic ASP and VB 6.0. I am
> trying to do a migration of apps. to a new WIN 2000 server. I am
> getting this error
>
> Server object error 'ASP 0177 : 800a801d'
> Server.CreateObject Failed
>
> I am unable to fix this issue for days and it is driving me nuts.For
> the sake of testing, I have given full control to 'IUSR_account' on my
> web folders,WINNT folders and given permission to registry nodes as
> specifed in Microsoft site. I also observed that .NET applications are
> working.
>
> I also took a look at metabase.xml file and security policies.But i
> cant find anything concretely.
>
> I am sure that this has to do with conflict between .NET and classic
> environment . Can anyone point me in the right direction? Thanks
>

My guess is that 800A801D is the VB component passing on an internal
80028101D generated internally. Which is a "Library not registered" error.

I suggest you check that all the components dependancies are installed
correctly include ones you might expect to be there out of the box such ADO,
MSXML, scrrun etc.


--
Anthony Jones - MVP ASP/ASP.NET


From: avrbadri on
On Oct 25, 2:37 am, "Anthony Jones" <A...(a)yadayadayada.com> wrote:
> <avrba...(a)gmail.com> wrote in message
>
> news:1193279500.212167.305990(a)e34g2000pro.googlegroups.com...
>
>
>
>
>
> > Hi - I have all my web apps, coded in classic ASP and VB 6.0. I am
> > trying to do a migration of apps. to a new WIN 2000 server. I am
> > getting this error
>
> > Server object error 'ASP 0177 : 800a801d'
> > Server.CreateObject Failed
>
> > I am unable to fix this issue for days and it is driving me nuts.For
> > the sake of testing, I have given full control to 'IUSR_account' on my
> > web folders,WINNT folders and given permission to registry nodes as
> > specifed in Microsoft site. I also observed that .NET applications are
> > working.
>
> > I also took a look at metabase.xml file and security policies.But i
> > cant find anything concretely.
>
> > I am sure that this has to do with conflict between .NET and classic
> > environment . Can anyone point me in the right direction? Thanks
>
> My guess is that 800A801D is the VB component passing on an internal
> 80028101D generated internally. Which is a "Library not registered" error.
>
> I suggest you check that all the components dependancies are installed
> correctly include ones you might expect to be there out of the box such ADO,
> MSXML, scrrun etc.
>
> --
> Anthony Jones - MVP ASP/ASP.NET- Hide quoted text -
>
> - Show quoted text -

Thanks Anthony - I will give it a shot . Can you pls. send me a list
of main dependency components on a WIN 2003 box ?

From: Rick Barber on
When I see an error such as that, it usually turns out that the object that
you are trying to create doesn't have the appropriate .dll registered on the
server. For your initial testing you can register a component using
regsvr32 dllname.dll. Ultimately I recommend that you try running the .dll
in a COM+ package

--
Rick Barber

http://www.orcsweb.com
Managed Complex Hosting
#1 in Service and Support

"Anthony Jones" <Ant(a)yadayadayada.com> wrote in message
news:%23jnW3quFIHA.1212(a)TK2MSFTNGP05.phx.gbl...
> <avrbadri(a)gmail.com> wrote in message
> news:1193279500.212167.305990(a)e34g2000pro.googlegroups.com...
>> Hi - I have all my web apps, coded in classic ASP and VB 6.0. I am
>> trying to do a migration of apps. to a new WIN 2000 server. I am
>> getting this error
>>
>> Server object error 'ASP 0177 : 800a801d'
>> Server.CreateObject Failed
>>
>> I am unable to fix this issue for days and it is driving me nuts.For
>> the sake of testing, I have given full control to 'IUSR_account' on my
>> web folders,WINNT folders and given permission to registry nodes as
>> specifed in Microsoft site. I also observed that .NET applications are
>> working.
>>
>> I also took a look at metabase.xml file and security policies.But i
>> cant find anything concretely.
>>
>> I am sure that this has to do with conflict between .NET and classic
>> environment . Can anyone point me in the right direction? Thanks
>>
>
> My guess is that 800A801D is the VB component passing on an internal
> 80028101D generated internally. Which is a "Library not registered"
> error.
>
> I suggest you check that all the components dependancies are installed
> correctly include ones you might expect to be there out of the box such
> ADO,
> MSXML, scrrun etc.
>
>
> --
> Anthony Jones - MVP ASP/ASP.NET
>
>


From: Anthony Jones on
"Rick Barber" <rick(a)orcsweb.com> wrote in message
news:ufeY$pyFIHA.484(a)TK2MSFTNGP06.phx.gbl...
> When I see an error such as that, it usually turns out that the object
that
> you are trying to create doesn't have the appropriate .dll registered on
the
> server. For your initial testing you can register a component using
> regsvr32 dllname.dll. Ultimately I recommend that you try running the
..dll
> in a COM+ package
>

Why COM+?


--
Anthony Jones - MVP ASP/ASP.NET