Re: Microsoft VBScript runtime error '800a01ad'

Just an update for this post: After you pointed me in the right direction,
Dave, I found this article and, after following its instructions, got my DLL
to run successfully on the client machine. Thought I would post the link in
the hope that someone else might find it useful.

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/0aafb9a0-1b1c-4a39-ac9a-994adc902485.mspx?mfr=true


"Dave" <dave@xxxxxxxxxxx> wrote in message
news:eaGPMnU1GHA.4796@xxxxxxxxxxxxxxxxxxxxxxx
To run my foxpro components I have to run the server in 32bit mode

I got that error before swapping

My DLL's are in the C:\WINDOWS\SysWOW64 folder and registered there, and
if i test using wscript, i need to make sure the version of wscript
running is the syswow64 version

Debbie wrote:
Hi Dave

Yes, I believe it is. It's a Dell Server PE1800 and it says the
operating system is Windows Server 2003, Standard x64 Edition, Service
Pack 1. Why do you ask?

Debbie :)




"Dave" <dave@xxxxxxxxxxx> wrote in message
news:O3pUIwS1GHA.4392@xxxxxxxxxxxxxxxxxxxxxxx
Is the machine 64bit R2 ?

Debbie wrote:
I get the following error message when trying to create an instance of
a DLL on a Windows 2003 Server machine from an ASP page:
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object

The code that generates the error is as follows:

dim oWebCom
set oWebCom = Server.CreateObject("WebCOM.WebCOM")

I have the same page on dozens of other computers (some using Windows
2000 Server and some using Windows 2003 Server) and all of them are
working just fine. On the computer experiencing this problem, I have
double checked and made sure that, yes, the DLL is registered.

If anyone can point me in a direction to resolve this issue I would be
most grateful.

Thanks - Debbie






.

Relevant Pages

  • Re: Microsoft VBScript runtime error 800a01ad
    ... Debbie wrote: ... Dave, I found this article and, after following its instructions, got my DLL to run successfully on the client machine. ... It's a Dell Server PE1800 and it says the operating system is Windows Server 2003, Standard x64 Edition, Service Pack 1. ...
    (microsoft.public.inetserver.asp.components)
  • Re: Kerberos delegation trauma
    ... I have created a dll which has the code that creates a process that calls the ... > Kerberos delegation won't solve this. ... >> when the tool on my machine tries to access the server. ... On my machine I have set IE to have Enable Integrated Windows ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: The call to Server.CreateObject failed while checking permissions. Access is denied to this obje
    ... Why did I have to do this when using .NET and Windows Server 2003, ... > SERVICE account. ... When I compiled it in a DLL ... The server is running Windos Server 2003. ...
    (microsoft.public.dotnet.framework.component_services)
  • RE: Windows 2000 Server hangs so frequently
    ... This server keeps hanging at least once ... When I check on running processes on Windows Task Manager screen, ... it normalises and hangs again after a few days. ... that a COM+ .dll file can run in it's own process space. ...
    (microsoft.public.win2000.general)
  • Using secured COM+ component over a ASP.net WebService with impersonate
    ... a asp.net client with windows nt auth. ... a COM+ dll which is called over DCOM (the dll is on a remote W2k Server and ... only restiricted users can access this dll., the webservice server and the ...
    (microsoft.public.dotnet.framework.aspnet.security)