04-13-2018 03:15 AM
After upgrading version 16 to 20.1 the Backup Exec server service won't start. Message: The Backup Exec Server service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
Solved! Go to Solution.
04-16-2018 06:29 AM
04-13-2018 03:53 AM
whats the error in the event viewer -> application logs
Was the Issue present before the upgrade ?
can you also provide the output of beserver.exe --console
https://www.veritas.com/support/en_US/article.100019347
04-16-2018 01:50 AM
Problem found - I installed the Managed Backup Exec Server option. I only have one stand-alone Backup Exec server. No I must unstall this option.
I found article ID 100031115 - but the Managed Backup Exec server option stays grayed out.
04-16-2018 03:22 AM
Disabled virusscanner - unstalled Backup Exec - reboot - installed Backup Exec. All working fin. But: all of my jobs, history and storage are gone.
04-16-2018 04:26 AM
04-16-2018 04:38 AM
The new version 20.1 installs in the ..\program files\Veritas folder, where the former version 16 installed in the ..\program files\Symantec folder. Therefor I still have both the catalog and data folder available.
Can you please point out how to import?
04-16-2018 04:55 AM
04-16-2018 06:04 AM
bedb is from version 16. No I'm uninstalling version 20.1 and re-installing version 16, hoping to connect to the 'old' data.
04-16-2018 06:14 AM
04-16-2018 06:21 AM
Where and how can I open a tech support case?
Now i'm encoutering an error: eventID 57802 The Backup Exec Server Service did not start. An internal error (10) occurred in object 13.
When I look it up via google i come across article ID:100007915. The mentioned path is valid and the file is in the folder. When I try to manually register the file via regsvr32 I get the message: the module c:\program files\veritas\backup exec\u2lbe9.dll was loaded but the entry point dllregisterserver was not found. Make sure that c:\program files\veritas\backup exec\u2lbe9.dll is a valid dll or ocx and then try again.
04-16-2018 06:22 AM
By the way - a repair installation did not solve this problem.
04-16-2018 06:29 AM
04-17-2018 01:51 AM