Hi @MasterSQL , Welcome to Microsoft Q&A,
Check Windows Script Host (WSH): Make sure Windows Script Host (WSH) is enabled on the server. VBScript requires WSH to run.
- To check if WSH is enabled, run the following command in a command prompt:
cscript //h:cscript
- You can also run a test VBScript file directly with
cscript
orwscript
to verify that WSH is working properly.
Make sure script execution is allowed on the server. Some servers have restrictions on executing scripts. - Make sure there are no Group Policy settings or security policies that block script execution on the server.
Make sure the account running the SSIS package on the server has sufficient permissions to execute the script. - Verify that the script can access the file system, registry, or any required resources on the server. - Permissions may be different if the package is running under a different user context than Visual Studio.
The VBScript may depend on external COM objects or libraries that are not registered on the server.
- Verify that any third-party components or DLLs used by the VBScript are installed and properly registered using
regsvr32
. - Compare COM registrations (such as ActiveX or other dependencies) between the development machine and the server.
Enable verbose logging for SSIS packages to capture error messages or stack traces during execution on the server. This will provide more information about why the script failed.
You can modify the VBScript to capture errors using On Error Resume Next
and log or display error details using Err.Description
and Err.Number
.
Best Regards,
Jiale
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.