Remote agent installation fails

[Rosss]

Hi everybody,

I just installed a brand new Backup Exec 2010 R2 media server and I'm trying to push the remote agent to a bunch of servers..

The push installation (and the local installation from the RAW32 folders) constantly fails on a Windows 2003 Terminal Server.

The push installation process gives a ERROR: Installation failed with error .1. GetLastError = :0 error message.

The local installation just brings up the Symantec Backup Exec splash screen and nothing happens.

I rebooted either the media server and the Terminal Server but it was no help.

Any suggestions? Thanks!

[CraigV]

Hi Rosss,

If you are remoting in, I would suggest using the console option (mstsc /console). Try this, and do the installation again, and post the results.

THanks,

Craig

[Ayush]

Hi Ross,

on the remote server on which you are trying to push the RAWS check the task manager for process if msiexec.exe is already running before running installation, if yes then kill it 1st and then try the installation.

[Rosss]

Hi Craig,

it doesn't work...

Ross

[Rosss]

Hi Ayush,

there's no msiexec.exe process before running installation.

I even copied the whole Agents folder locally. From a command prompt I enter "change user /install" for a proper Terminal server installation, then I enter "setup.exe /RANT32: -s -boot"

Well, nothing happens. If I just click the setup.exe file, I get a splash screen and nothing else.

Ross

[Rosss]

These are the final entries of the log file of the push installation from the media server. I'm using the Domain Admin credentials.

01:(12/21/10 22.08.48)->Getting process: 264

01:(12/21/10 22.08.48)->Executing WMI query: select Name from Win32_Process where ProcessId='264'

01:(12/21/10 22.08.48)->ERROR Error reading remote registry HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SymcInstall\Total Percent Done

01:(12/21/10 22.08.48)->ERROR: Win32: -1

01:(12/21/10 22.08.48)->Checking process status: 264

01:(12/21/10 22.08.48)->Getting process: 264

01:(12/21/10 22.08.48)->Executing WMI query: select Name from Win32_Process where ProcessId='264'

01:(12/21/10 22.08.49)->Cleaning up push install...

01:(12/21/10 22.08.49)->ERROR Error deleting file: \\server-ts\BEW-af8b4dff66f2464e9777e86d5b4efcee with error: Accessing path '\\server-ts\BEW-af8b4dff66f2464e9777e86d5b4efcee' denied.

01:(12/21/10 22.08.49)->ERROR: Win32: -1

01:(12/21/10 22.08.49)->Removing map to remote install directory...

01:(12/21/10 22.08.49)->Removing map: *

01:(12/21/10 22.08.49)->Removed map: *

01:(12/21/10 22.08.49)->Deleting share: C:\BEW-af8b4dff66f2464e9777e86d5b4efcee

01:(12/21/10 22.08.49)->Deleting entire folder: C:\BEW-af8b4dff66f2464e9777e86d5b4efcee

01:(12/21/10 22.08.49)->Deleting entire folder by api: C:\BEW-af8b4dff66f2464e9777e86d5b4efcee

01:(12/21/10 22.08.49)->Deleting folder files: C:\BEW-af8b4dff66f2464e9777e86d5b4efcee

01:(12/21/10 22.08.49)->Executing WMI query: ASSOCIATORS OF {Win32_Directory.Name='C:\BEW-af8b4dff66f2464e9777e86d5b4efcee'} Where ResultClass = CIM_DataFile

01:(12/21/10 22.08.50)->Getting sub folders: C:\BEW-af8b4dff66f2464e9777e86d5b4efcee

01:(12/21/10 22.08.50)->Executing WMI query: ASSOCIATORS OF {Win32_Directory.Name='C:\BEW-af8b4dff66f2464e9777e86d5b4efcee'} WHERE ResultClass=Win32_Directory ResultRole=PartComponent

01:(12/21/10 22.08.50)->Deleting folder: C:\BEW-af8b4dff66f2464e9777e86d5b4efcee

01:(12/21/10 22.08.50)->Executing WMI query: select * from Win32_Directory where Name='C:\\BEW-af8b4dff66f2464e9777e86d5b4efcee'

01:(12/21/10 22.08.50)->Push install cleaned.