This is a DCOM error. The use of CreateObject to create a COM component in an Active Server Pages (ASP) page may result in the following error:
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object
This error is usually generated because dynamic-link libraries (DLLs) on which the COM object depends are one of the following:
- Missing from the system
- Not in the system path
- Not accessible by the system because of security settings
Follow these steps only if you're receiving the 800A01AD error for Wscript.Shell component. For any other ActiveX object, the following steps do not apply:
Click Start, Run and type:
If the above does not help, or if you receive an error message when running the two commands above, then you may need to reinstall Windows Script 5.6 from Microsoft site. The download link is given below for Windows 2000 systems.
Check that you have MDAC 2.x installed.
Register \program files\common files\System\MSADO15.dll with RegSvr32.
Check permissions for both IUSR_<Server> AND IWAM_<Server>. In particular make sure that they have Read/Execute NTFS rights on these folders.
- \program files\common files\System
- \Windows (or Winnt)
Open Console and check that there is a valid IP Address for the Default Web Site.
Stop, and then restart the Web services, or reboot, depending on your operating system.
If the above fails to resolve the problem or seems less than germane, the problem is very likely that the server operating system and IIS are running as 64bit and not configured to support 32bit applications. After you install Microsoft Windows Server 2003 Service Pack 1 on the products that are listed in the "Applies To" section, you can configure Microsoft Internet Information Services (IIS) 6.0 to start 32-bit worker processes (W3wp.exe). A 32-bit worker process enables WOW64 compatibility for 32-bit Web applications on a server that runs a 64-bit version of Windows Server 2003. This WOW64 compatibility for 32-bit Web applications lets 32-bit DLLs such as ISAPI Filter DLLs and ISAPI Extension DLLs load in-process. This then, allows the 32bit CA OMWV application to run.