Solution To: ActiveX Scripting unable to initialize the script engine

[JohnBates]

hi DTS people,

Today, we had a DTS Package (SQL Server 2000) that failed with the following error - (You must turn on package logging, then exec package to be able to see the actual cause of this failure).

The Package Log showed:

Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:ActiveX Scripting was not able to initialize the script execution engine.

But it failed on only 1 client machine. The package ran successfully on several others.

Anyway, the solution was to re-register this .dll on the problem PC:

Regsvr32.exe "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\axscphst.dll"

(Of course you will need to change the path to fit your installation of SQL Server 7 or 2000)


Then the PC was able to execute the package.

I found this, thanks to google.com

Maybe this will help someone else.

John

 

[timmylodge]

We had similar problems with axcsphst.dll would not start.
Registered all the dlls as everyone recommended still did not work. We noted that the SQL licensing also stopped working in Control Panel.

I found that on the SQL2000 CD if you go to Install there are Advanced Options - and one is a Registry Rebuild - you re-point the server to the databases and select licensing mode and it cured the problems.

It looked like Veritas BackupExec 10 was to blame but we have since reinstalled it - and that is working too.

I would imagine it is a real last resort - but the registry rebuild option did not come up on the search engines as a fix for much - but it worked for us.

Regards

Tom

 

[JohnBates]

That's good info Tom. Who would have suspected Veritas as the culprit? - you just never know.

John

 

[mutley1]

Hi guys,

Having this problem on one node of a cluster......DTS fine on one node and not on the other. Have registered the 3 files as per before and rebooted dodgy node, but nothing happening.Have you had any experience of this on a cluster and do you think the reg rebuild would do the trick on node 2 or maybe mess up node 1 as well? Will take a backup before any attempt but just asking the question first!

Cheers,

M.