RAWSBulkUpdate.exe ERROR 1219

[MitchR]

I recently downloaded & applied the new BackupExec v12.5 service pack 3.  The release notes say I need to reinstall all of the agents, so off to "RAWSBulkUpdate.exe" we go.

When I enter my credentials, and validate, everything is OK.  When I try to actually run the install, the process dies.  The last few lines from my "bepushes.log" are:

1:(12/01/09 16:23:54)->Creating remote install directory...
1:(12/01/09 16:23:54)->Creating folder: C:\BEW-95601FFF3E9C44E58199EA9339AAA3A1
1:(12/01/09 16:23:54)->Creating process: cmd.exe /c md C:\BEW-95601FFF3E9C44E58199EA9339AAA3A1
1:(12/01/09 16:23:56)->Creating share: BEW-95601FFF3E9C44E58199EA9339AAA3A1, C:\BEW-95601FFF3E9C44E58199EA9339AAA3A1, BEWPush Temporary Directory
1:(12/01/09 16:23:56)->Creating security descriptor...
1:(12/01/09 16:23:56)->Creating security DACL...
1:(12/01/09 16:23:56)->Establishing connection to network resource: \\BackupServer.MyDomain.com\BEW-95601FFF3E9C44E58199EA9339AAA3A1, ems.com\MitchR
1:(12/01/09 16:23:56)->ERROR: Code(1219): Failed to establish connection: \\BackupServer.MyDomain.com\BEW-95601FFF3E9C44E58199EA9339AAA3A1, ems.com\MitchR, 0

I've tried multiple domain admin accounts.  Always the same result.

Google tells me that "1219" is from conflicting credentials - however I can verify via Computer Managment that there are no other active sessions or open files between the backup server and the agent computer.

I'd really like to fix this problem.  If I can't, I'd rather not uninstall-reboot-reinstall all of my agents.  Is there a manual way to apply the updates that RAWSBulkUpdate is attempting?

[DominikG]

You can of course push the update through the wizard.
Therefore just remove all .msp files except for SP3 from .../Backup Exec/Agents/RAWSxx/Updates/ and then run the push wizard on the machines you want to update.

The other possibility is to copy the SP3 .msp file to the remote server and to run it manually.


best regards

Dominik

[MitchR · Accepted solution]

I found the solution.  There are conflicting updates being applied as part of the deployment process.  The solution is as follows:

From the agents directory, delete all but the SP3 update.  On a typical install, this should be:
   C:\Program Files\Symantec\Backup Exec\Agents\RAWS32\Updates
   C:\Program Files\Symantec\Backup Exec\Agents\RAWSX64\Updates
The files to leave are:
   RAWS322213RSP3.msp
   RAWSx642213RSP3.msp

Note to Symantec:  new patches should remove older patches that aren't needed- or at the very least, play nice when them so they don't break agent deployments.