Forum Discussion

Skyline231's avatar
Skyline231
Level 3
10 years ago
Solved

Can't install Agent on Windows server 2003R2

Hi,

 

I have Backup Exec 2015 on Windows server 2012. Std, and several Servers on Win 2003. When i try install agent on it, I get error :

11-11-2015,14:57:44 : C:\VCRedist\V10.0\vcredist_x64.exe /q /norestart /log "C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\V10.0_x64_msruntime_install.log"

+ 11-11-2015,14:57:44 : ERROR - 3: Failed to create process as user.

11-11-2015,14:57:44 : Return Value of Microsoft Visual C++ 2010 Redistributable (x64) : 1603

+ 11-11-2015,14:57:44 : V-225-299: ERROR: Failed to execute VC 10.0 runtime installer. Error code 1603. ***To search for information about this error, click here 

+ 11-11-2015,14:57:44 : Review this log file for details: C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\V10.0_x64_msruntime_install.log

11-11-2015,14:57:44 : The return value for Распространяемые пакеты Microsoft VC++ (x64) returned error code: 1603

11-11-2015,14:57:44 : Clean up Symantec installer keys.

11-11-2015,15:12:38 : AgentSeqDlgs::Misc_BE_CommonOps

11-11-2015,15:12:38 : Dialog Sequence Returning errorlevel 1603

+ 11-11-2015,15:12:38 : The Installation Failed!

I installed VC++ and msxml6-KB2957482-enu-amd64 but I still have this error.

Please help me.

15
Backup and Recovery
Backup Exec
Windows Server (2003-2008)
  • pkh's avatar
    pkh
    10 years ago
    From the BE installation DVD, copy the VCDIST directory to C:\ of the remote server and do a manual install of the remote agent

4 Replies

Sort By
  • AmolB's avatar
    AmolB
    Moderator
    10 years ago

    Hope you have installed SP2 for WIn 2003 R2 server.

    Refer to BE15 SCL https://www.veritas.com/support/en_US/article.TECH227896

  • pkh's avatar
    pkh
    Moderator
    10 years ago
    From the BE installation DVD, copy the VCDIST directory to C:\ of the remote server and do a manual install of the remote agent
  • Nick_Elmer's avatar
    Nick_Elmer
    Level 6
    10 years ago

    I remember seeing this in the past and it was due to a patch that Microsoft released which affected MSI installers (https://support.microsoft.com/en-us/kb/2918614). They have released a revised patch a few months ago that should address it. Please make sure that your system has all of the latest Windows Update patches applied and try again.

  • CraigV's avatar
    CraigV
    Moderator
    10 years ago

    The TN below addresses BE 15, but try what it suggests in the work around section (although just move the HFs to another location):

    https://www.veritas.com/support/en_US/article.TECH73454

    If you're not on BE 15 FP2 then run LiveUpdate to install that, and run it again once done to install any additional patches. Then push-install these to the remote servers you have.

    Thanks!