Post reply

Script Execution Engine

  • December 11, 2002 at 12:33 am

    #357669

    When I attempting to execute my package containing ActiveX objects, I got the error "Active X Scripting was not able to initialize the script execution engine"

    How to remedy?

  • December 11, 2002 at 4:13 am

    #444047

    Write a simple VBS file like so.

    MsgBox "Test"

    And save as test.vbs

    Double click and see if runs.

    If you get a similar eror or don't see the message box with Test popup you could have an issue with the Active X Scripting Engine install.

    Goto http://msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid=28001169 and download if this does happen.

    Also, if message box shows up then check both the SQL Server Logs and Event Viewer Logs to see if anything was logged perchance.

    Then please try your package again and post update here with complete message returned.

  • December 11, 2002 at 10:59 am

    #444119

    Thank-you for the help, but no joy. The Test.VBS ran fine, no info in either Event Viewer or SQL Server Log.

    I'm suspecting something interfered with my client-side install of SQL Server.

  • December 11, 2002 at 3:12 pm

    #444158

    If just the client side an issue on one machine try reinstalling the client tools to see if corrects. Also, you did run the test vbs file from the client right?

  • December 12, 2002 at 8:51 am

    #444257

    This is what I found

    Johnny....

    The ActiveX Scripting Host, used by all tasks that have ActiveX script capability, may become unregistered. This can lead to one of the errors below:

    "ActiveX Scripting was not able to initialize the script engine."

    "ActiveX Scripting Transform 'DTSTransformation__x' was not able to initialize the script engine."

    "ActiveX scripting was not able to initialize the script execution engine"

    Normally you can fix this by simply re-registering the DTS ActiveX Script Host DLL (axscphst.dll), using the Regsvr32.exe utility. If this does not solve the problem, then try re-registering the following DLLs in the same way: dtspkg.dll, dtspump.dll.

    If you have installed SQL Server in the default location you may use the appropriate command below in the windows Run dialog or the command prompt:

    Regsvr32.exe c:\mssql7\binn\axscphst.dll

    (SQL Server 7.0)

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

    (SQL Server 2000)

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply