Windows 7 - WSH 5.8 issue "Automation server can't create object" on new ActiveXObject - not an issue with WSH 5.7

Question

4.00/5 (1 vote)

See more:

Hi,

I created a simple DLL using ATL Project Wizard with one simple class added (of Simple ATL Object type) under MS Visual Studio 2008 (C++).

The solution was built fine and dll registration went successfully.

However when I tried to create new ActiveXObject() in JavaScript the WSH 5.8 aborts with the following message: "Automation server can't create object". The script is not used in under any browser.

After I tried the same script on other Windows 7 machine with WSH 5.7 (!) script went through successfully.

Can anyone please help me with this issue since my project demand to stick with Windows 7 and WSH 5.8 WSH.

Thank you,
Brad

Posted 7-Mar-11 9:27am

Member 2818312

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 2818312 · Answer 1 · 2011-03-08T07:48:00

Problem solved. The issue was about the dll built for x32 platform. Running the script on x64 platform resulted the problem while loading the dll. WSH 5.7 on x64 platform still runs in x32 mode which explains why the script was successfully loading the dll. On the other hand WSH 5.8 runs in x64 mode. Once the dll was rebuilt for x64 the script went through successfully under 5.8 as well.