Forum Discussion

dmendhekar's avatar
dmendhekar
Level 3
10 years ago

NB 7.6.0.1 Client Installation is failing.

Client Windows 2008 R2 Standard 64 bit.

 

Here is the installation log. ( *** Moved to attachment *** )

Error in log:

05-19-2015,13:16:36 :  DEBUG: Error 2738:  Could not access VBScript runtime for custom action 
05-19-2015,13:16:36 :  ERROR: Internal Error 2738. 
05-19-2015,13:16:40 :  Action ended 13:16:40: setRegistryValues.B2D5B6C9_4698_42F7_AC9D_955789A69556. Return value 3.

 

Technical Document followed to resolve this issue but still installation is failing.

https://support.symantec.com/en_US/article.TECH57368.html
https://support.symantec.com/en_US/article.TECH69937.html
http://csi-windows.com/blog/all/27-csi-news-general/161-fixing-windows-installer-error-2738

Reference link from Microsoft.
http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/error-2738-could-not-access-vbscript-run-time-for/1a4499ae-8bc1-4534-9c6f-4d399ac70d9a
 

 

 

 

7.6
Backup and Recovery
NetBackup
Windows Server (2003-2008)
  • Marianne's avatar
    Marianne
    10 years ago
    Seems you need to open a Support call with Microsoft. This is not a NetBackup issue.
  • Pritesh_Pisal's avatar
    Pritesh_Pisal
    Level 5
    10 years ago

    See if this helps

    Before installion go to start -> run -> Regsvr32 vbscript.dll

    Then try to Install again.

    if that didnt help then you may need reboot.

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago
    Seems you need to open a Support call with Microsoft. This is not a NetBackup issue.
  • Yogesh_Patil's avatar
    Yogesh_Patil
    Level 4
    10 years ago

    Disable AV before install software and try to install client with admin rights.

    Some time AV will not allow to install new softwares.

     

  • mph999's avatar
    mph999
    Level 6
    10 years ago

    You could try the following:

    https://support.symantec.com/en_US/article.TECH57368.html

    If this still fails, then I agree with Marianne that it would be best to speak with MS to determine why it is happening.

    You could also try disabling any anti-virus or similar software you have and retry - this has been known to occassionally fix the issue.