Fixing Microsoft VBScript runtime error ‘800a01ad’ (Solved)

RECOMMENDED: Click here to fix Windows errors and optimize system performance

When you try to run a remote script with WSH on Windows, you may receive the following error message
Error: The ActiveX component cannot create an object.
Code: 800A01AD
Source: Microsoft VBScript runtime error

This problem is related to the permissions granted to your DLLs. The IUSR_computer and IWAM_computer accounts (where Computer is the machine name) do not have the necessary privileges to execute the DLLs to be instantiated in the Server.CreateObject line of the ASP code.

Quick correction in case of error 800a01ad

January 2021 Update:

We now recommend using this tool for your error. Additionally, this tool fixes common computer errors, protects you against file loss, malware, hardware failures and optimizes your PC for maximum performance. You can fix your PC problems quickly and prevent others from happening with this software:

  • Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
  • Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
  • Step 3 : Click “Repair All” to fix all issues.


With the help of MS Tech Support, this error message has been corrected by performing these steps.

  1. Make sure you have MDAC 2.x installed.
  2. Save \program files\program files\common files\system\MSADO15.dll with RegSvr32.
  3. Make sure that the IUSR_<< AND IWAM_ accounts both have NTFS read/execute privileges for the following folders that are cascaded.
    – Program files common files system
    – Winner
    – \InetPub\WWWRoot
  4. Open the console and make sure there is a valid IP address under “Web Standard”.
    Site properties”. If the permissions have already been breached and you’ve opened them.
    Console, it is likely that the IP will become “All Unassigned”.
  5. Restart the server. Do not assume that the abandonment/startup service works.
    it’s true.

Enable 32-bit applications

  • On a 64-bit version of Windows, this error may occur if there is a difference between the 32-bit version of the component and the 64-bit mode of the IIS, or vice versa.
  • In Windows 2008 and 7, the Enable 32-bit applications from the application pool associated with your virtual directory option must match the bit-ness of the component. For example, if the 32-bit version of the component is installed, the option must be set to True.
  • Under Windows 2003, it is not possible to configure individual virtual directories to operate in a particular mode (32-bit or 64-bit).

RECOMMENDED: Click here to troubleshoot Windows errors and optimize system performance