Inventory or Deployment Solution Plug-in install fails with error code 1603

book

Article ID: 170261

calendar_today

Updated On:

Products

Inventory Solution Deployment Solution

Issue/Introduction

Inventory or Deployment Solution Plug-in install fails with error code 1603.

Error 2738. Could not access VBScript run time for custom action

Errors in the agent log:

Program 'Inventory Plug-in for Windows Install (x64)' completed. Exit code=1603. Execution context='Administrator'. RunAs='\'


MSI error log:
MSI (s) (E0:40) [00:00:01:373]: Hello, I'm your 64bit Elevated Non-remapped custom action server.
MSI (s) (E0:8C) [00:00:01:373]: Note: 1: 2205 2:  3: Error
MSI (s) (E0:8C) [00:00:01:373]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2738
Action start 0:00:01: DeleteDeploymentAgentRegistryKey.
DEBUG: Error 2738:  Could not access VBScript runtime for custom action
MSI (s) (E0:8C) [00:00:01:389]: Note: 1: 2205 2:  3: Error
MSI (s) (E0:8C) [00:00:01:389]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (E0:8C) [00:00:01:389]: Product: Deployment Solution Agent -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738. The arguments are: , ,
 
MSI (s) (E0:8C) [00:00:01:389]: Closing MSIHANDLE (3) of type 0 for thread 9612
MSI (s) (E0:8C) [00:00:01:389]: Closing MSIHANDLE (2) of type 790542 for thread 6712
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738. The arguments are: , ,
Action ended 0:00:01: DeleteDeploymentAgentRegistryKey. Return value 3.

Cause

This is caused by McAfee's script scanning where they take over the execution of VBScript in order to scan the contents before execution.

To verify this is the issue, check the following Registry keys. If one or more exist, this is causing the issue:

HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
   Value of the key (Default) will be McAfee ScriptScan, but should be VB Script Language.
     
HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
    Value of the key (Default) will be C:\Program Files\Common Files\McAfee\SystemCore\Scriptxxxxxxxxx.dll but should be C:\Windows\system32\vbscript.dll.
     
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
    Value of the key (Default) will be McAfee ScriptScan but should be VB Script Language.
     
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
   Value of the key (Default) will be C:\Program Files\Common Files\McAfee\SystemCore\Scriptxxxxxxxxx.dll but should be C:\Windows\SysWOW64\vbscript.dll.

Resolution

Disable script scanning on the McAfee side (check with their documentation on how to do this). Once the change is made, you may need to update the registry keys by using a reg script.

Here is an external site that provides guidance on how to do this:
https://stackoverflow.com/questions/130193/is-it-possible-to-modify-a-registry-entry-via-a-bat-cmd-script