Problem Statement
By default, Windows 64-bit starts the 64-bit version of wscript.exe (the VBS interpreter). This results in the “800a01ad Active X component can’t create object” error message.
Solutions
Chưa có cách nào tốt hết nhưng dưới đây là những cách tìm thấy do người ta đưa ra.
Có hai cách giải quyết vấn đề…
Cách thứ nhất
Create a batch file that contains the following line:
C:\WINDOWS\SysWOW64\wscript.exe yourVBSscript.VBS
This will start the VBS script using the 32-bit version of VBS.
Cách thứ nhì
Change the “VBS” file extension permanently to the 32-bit version of wscript.exe, làm theo ba bước dưới đây:
- Right-click a *. VBS file, and then click Open With.
- In the Open With dialog box, click Browse to locate the VBS version that you want: C:\WINDOWS\SysWOW64\wscript.exe
- Select the Always use the selected program to open this kind of file check box.
Tài liệu Tham khảo
- Error 800a01ad when starting a *.vbs file on Windows 64-bit
- 32-bit registry access from WSH script running in x64 Windows
- Solution for Error 800A01AD (Unbrowse scripting)
- BUG: You receive an “ActiveX component can’t create object” error message when you Use Windows Script Host to execute remote script
- Registry changes in x64-based versions of Windows Server 2003 and in Windows XP Professional x64 Edition
- Solving VBS Error ’800a01ad’ on CreateObject in ASP/IIS
- Overview of the compatibility considerations for 32-bit programs on 64-bit versions of Windows Server 2003 and Windows XP
Cách thứ ba
The VBScript interpreter (cscript.exe/wscript.exe) comes in two flavors on a 64-bit version of Windows: a 32-bit version and a 64-bit version.
The 32-bit version can create and use 32-bit COM components only, and the 64-bit version can create and use only 64-bit COM components.
By default, .vbs files are associated with the 64-bit version. You COM component is most likely a 32-bit one, hence the error.
You can find the 32-bit version in the %windir%\SysWOW64 folder. Launching this version should give you access to all 32-bit COM components:
%windir%\SysWOW64\wscript.exe myScript.vbs or
%windir%\SysWOW64\cscript.exe myScript.vbs Source 1: Cannot use CreateObject from VB scripts on Windows 7
To start a 32-bit command prompt, follow these steps:
* Click Start, click Run, type %windir%\SysWoW64\cmd.exe, and then click OK. Then type
cscript vbscriptfile.vbsCách thứ 4
Windows 2008/Vista/7 allows some virtual directories to run in the 32-bit mode, and others in the 64-bit mode. A virtual directory is configured to run in the 32-bit mode by configuring its Application Pool to enable 32-bit application, as shown below.
Therefore, you can run the 32-bit and 64-bit versions of the Persits components side by side on Windows 2008/Vista/7. You still need separate 32-bit and 64-bit keys for all the products except AspPDF, and the key locations in the system registry are as described above.
Source: http://support.persits.com/show.asp?code=PS080519170
