Microsoft Vbscript Runtime 0x800a01ad Activex Download. Runtime Error By using this site. Runtime Error 429 - ActiveX Component Can't Create Object CH. Microsoft VBScript runtime error: ActiveX component can't create object(800A01AD). Microsoft VBScript runtime error. Micromite T Manual. This is very inconsisitent.

Hello members, I am getting below problem while accessing an 64bit version of.NET DLL exposed as COM to work on ASP. HTTP 500.100 - Internal Server Error - ASP error Internet Information Services Microsoft VBScript runtime (0x800A01AD) ActiveX component can't create object: 'ABCpdf7.Doc' ASP site runs under 32bit mode on a webserver which has got Windows 2008 R2 64 bit version, IIS 7.5.

The ABCpdf compoent Separate application pool been set for the ASP website and identity it runs under is the default 'ApplicationPoolIdentity'. I have tried creating the component thru a simple VBS file and it works fine.

Stop Patent Leather Shoes Cracking here. So It looks like an security issue but no clue on where and what to look. Would appreciate of any help to resolve the issue.

Hi, I am trying to create an instance of the object MSXML2.ServerXMLHTTP in ASP, but I am getting the following error: Error Type: Microsoft VBScript runtime (0x800A01AD) ActiveX component can't create object: 'MSXML2.ServerXMLHTTP' This code was working before we updated IIS to a higher version. This is part of the code that I am using. That must be some pretty old code if your using 2, seems like an upgrade or security patch may have removed the following file: C: WINDOWS system32 msxml2 r.dll & C: WINDOWS system32 msxml2.dll are both on your server/machiine your running this on.

If you don't have these files you should be able to get them off an install cd. Once you place them into system32 you'll have to register them, I'm assuming you know how to register a dll. By the way msxml is up to 6r, and I think you could get MDAC2.5 - 2.7 should have your missing msxml files. Damey, >C: WINDOWS system32 msxml2 r.dll I am not sure that is entirely correct MSXML2.DOMDocument will pick up msxml3 old style to allow the Working Draft XSLT that microsoft implemented MSXML2.DOMDocument.3.0 will pick up msxml3, new style but changing the code is the way to go It is definitely not recommended to stick with the old msxmls msxml3 still comes with IE, I believe (at least with 6) as far as I know there is not too much difference between 4 and 6 I usually use the 4.0 objects cheers Geert.