06-21-2012 02:50 AM
we have upgraded backup exec 2010R3 to 2012. at the end of the installation, we have rebooted the server and ran liveupdate. it showed SP1a, so we have installed the SP.
when we start the BackupExec 2012, we cannot log in to the program. the error what is showing is:
The BackupExec Management Service was unable to start
when i look at the services, all the services are running
06-21-2012 04:50 AM
06-21-2012 04:58 AM
the second one i know about..
the first one is for envirement windows server 2003.. i cant find the ISS admin service on server 2008
06-21-2012 05:04 AM
I thinks it's best to contact Symantec Support about this issue, and point them to TECH188675.
06-21-2012 05:50 AM
SQL Server (BKUPEXEC) service was running??
I had a similar almost problem, my services not running at all!!!
I try the to run them with local system (default) but nothing, when i change them with the domain admin account then all services start and until know i don't have any problem!!
06-21-2012 12:50 PM
If you have the second one you should also see the Event log message. If your symptoms match then we are still investigating the issue.
One or two customers have indicated that regional language settings in the operating system appears to be the cause, so it might be worth trying to set English (American) settings. However I am not sure that has fixed all customers so you may still have to create a formal support case (as the article suggests)
06-22-2012 03:31 AM
i have opened a support case..
@Colin Weaver.. i have set the regional language settings to Engelish United States, but nothing changed
06-22-2012 06:54 AM
Hi Sander
I also suggest that if you have not installed Sp1a that you install this
http://www.symantec.com/docs/TECH186717
Colin
10-18-2012 04:00 AM
OK it looks like we have a solution
Issue is caused by an invalid .XML entry inside teh .NETFRAMEWORK machine.config files. Backup Exec 2012 cannot handle this invalid code and fails.
Fix is to correct the entries (you may have at least 2 versions of machine.config to check)
Article is here
http://www.symantec.com/docs/TECH195492