Backup Exec 2010 R3 SBE. Remote agent will not start after applying SP3

Windows server 2008 with BackupExec 2010 R3. I ran Liveupdate and downloaded and installed SP3. After doing so tried to start BackupExec services but Remote Agent will not start. I get an error 1053 and then a windows popup that says "Agent for Windows systems has stopped working". I have rebooted but still cannot start the service. In the event viewer I see an error 1000 and the following:

"Faulting application beremote.exe, version 13.0.5204.1225, time stamp 0x51e07830, faulting module bedscomn.dll!?DLE_GetNext@@YAJPEAPEAUGENERIC, version 6.0.6002.18541, time stamp 0x4ec3e855, exception code 0xc0000139, fault offset 0x00000000000b6fc8, process id 0x788, application start time 0x01ceced320aaac11."

I then downloaded the 2010R3 SP3 file from Symantec site and ran it, rebooted and still cannot start service. From Program Files\Symantec\Bckupexec\agents\raws64 created a mst file and ran the installation of Remote agent but still unable to start the service.

This is the only server on the network. Other Symantec products on this server are Endpoint and System Recovery. Coincidentally I ran the same liveupdate on three servers for another client and everything was just fine.

Any help or suggestions would be greatly appreciated.

Thanks.
dashmanAsked:
Who is Participating?
 
dashmanConnect With a Mentor Author Commented:
I tried multiple things but none resolved the issue. I finally stopped all services,copied the catalogs and data folder then did a complete uninstall, rebooted and manually removed the remaining folders in windows explorer. Reinstalled the app, stopped all services, copied back the catalogs and data folder and now app running with all settings and jobs and history. Running current backups and once have those (has been several days so need them) I will run live update and hope the same thing does not happen.

Thanks to those that tried to help. I was hoping there was a fix but time wise I could have done this and been much better but one does not always learn anything from taking that route.
0
 
Rodney BarnhardtServer AdministratorCommented:
You didn't mention is this was a virtual environment or not, but there seems to be a hotfix for your error. Although, since you downloaded SP3 it should have been included.

http://www.symantec.com/business/support/index?page=content&id=TECH195395

It may also be a bad registry entry:
http://www.symantec.com/business/support/index?page=content&id=TECH145072
0
 
dashmanAuthor Commented:
This is not a virtual environment and a stand alone server.

 I have downloaded and installed the hotfix but it did not resolve the issue. As far as the second suggestion I do not have any of the registry keys mentioned in the article.

Any other suggestions?
0
 
dashmanAuthor Commented:
No one else could provide a solution so finally just did an uninstall and reinstall
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.