cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec 10d agent failed to install with 80070005

junkets
Level 2

One XP pro machine in our backup has suddenly failed to backup.  It failed once before and I reinstalled locally to fix it for a couple of weeks.  It has failed again and will not install locally or remotely.  When the remote PC failed BE was running as LSA.

The local install (setup /rant32 -s) flashes for a moment and appears to do nothing.  No files are copied and no log entries appear.

The remote install give a file splash screen of: Attempting to connect to server \\PC-NAME failed with the following error: Access is denied.  Please wisit http://support.veritas.com/docs/269175 to view possible reasons why the remote installation cannot continue.

None of these suggestions helps.  The firewall is turned off.  I have stopped BEComReg, cleared both logs, deleted VERITAS Shared folder and started over.

With the remote install, the 2 files are copied to \\PC-NAME\Program Files\Common Files\VERITAS Shared.  The process BEComReg is started and here are the logs.

BEPUSHES.LOG
** LOG 1 STARTED **->(03/08/10 10:10:29)
1:(03/08/10 10:10:29)->SetDestinationConnection called:\\PC-NAME,DOMAIN-NAME\administrator,
1:(03/08/10 10:10:29)->SDC calling GetPrincipalSID:\\PC-NAME,DOMAIN-NAME\administrator
1:(03/08/10 10:10:29)->Destination connection established:0, GSLP:0, Returning:0
1:(03/08/10 10:10:29)->put_DestinationShare:C$
1:(03/08/10 10:10:29)->BE_InstallObjects called.
1:(03/08/10 10:10:29)->CopyComponents:C:\Program Files\Common Files\VERITAS Shared\BEComReg.exe,\\PC-NAME\C$\Program Files\Common Files\VERITAS Shared\BEComReg.exe
1:(03/08/10 10:10:30)->CopyComponents:C:\Program Files\Common Files\VERITAS Shared\BEComUtil.exe,\\PC-NAME\C$\Program Files\Common Files\VERITAS Shared\BEComUtil.exe
1:(03/08/10 10:10:30)->GetComputerDomain WkstaInfo:\\PC-NAME,DOMAIN-NAME
1:(03/08/10 10:10:30)->SecureRegComponent called:NON-BDC
1:(03/08/10 10:10:30)->Calling GetPrincipalSID:\\PC-NAME,DOMAIN-NAME\administrator
1:(03/08/10 10:10:30)->BE_InstallObjects Finished.
1:(03/08/10 10:10:30)->BE_CreateInstallJob called.
1:(03/08/10 10:10:30):80070005->

BEPUSH.LOG
** LOG 1 STARTED **->(03/08/10 10:10:30)
(03/08/10 10:10:30)->FinalConstruct called.
(03/08/10 10:10:30)->GetRunningObjectTable succeeded: MNK1
(03/08/10 10:10:30)->CreateFileMoniker succeeded.
(03/08/10 10:10:30)->Moniker registered.
(03/08/10 10:10:30)->SSPI Initialized.

3 REPLIES 3

junkets
Level 2
Anyone?

Turls
Level 6

I have escalated your question to the Support team. Hope they can get back with an answer sometime soon. Stay tuned.

junkets
Level 2
Still no response!  I have had more failures in the past couple of months than I have had successes and nothing changed on our system except updates to Symantec AV and maybe windows.  Should I look for a new solution for backup since this is still not working and apparently noone at Symantec can figure it out and now another machine is doing this also?