01-15-2013 02:13 PM
Hi all :)
Odd problem has just cropped up. All of a sudden when I try to open BE 2012 (on the actual BE server) it asks for logon credentials.
Nothing has changed regarding this and when I type in the appropriate creds I then get a "could not connect to server" error and under additional info it says that the BE management service was unable to start... although it and all the BE services are started.
Anyone know what might be causing this?
thanks
Tracy
01-15-2013 02:34 PM
good thinking :)
event viewer error for BE management service:
01-15-2013 02:37 PM
Hi
As you have not given any error for management service why it is not starting ,I would request to given the error message in event viewer once by going to application tab and system tab.
Have you tried restarting the server once and then checked
If the error in event viewer is come thing similar the would request you to open a case with Symantec as this issue is been still investigated
the Application event log also contains an Event ID 0 message: "BackupExec Management Service startup in EXCEPTION mode"
http://www.symantec.com/docs/TECH188675
http://www.symantec.com/docs/TECH195492
Hope that helps
Thanks
01-15-2013 04:47 PM
Make sure that the BE SQL instance BACKUPEXEC and all the BE services are started. If the BE SQL instance is not started up, the BE services will not start.
01-31-2013 12:25 PM
yes they are all started. Thats the thing, although the error says a service isn't started they are all started
01-31-2013 09:25 PM
It will show the service as running, however since it started in exception mode, the error is reported about the service not running..
Would recommend contacting support so they can check as to why the connection to the database cannot be made.
02-02-2013 02:23 AM
I will suggest you to once try to repair the backupexec database through BEutility. And then try...
02-03-2013 07:27 PM
Same. I have removed and reinstalled BE...same
02-03-2013 09:30 PM
11-08-2016 12:49 AM
It says access denied. I am logged into symantec community and still cannot access it. What kind of crazy secret info is that and how do I get there please?
11-08-2016 06:27 AM
Since the split, Symantec does not have access to Veritas stuff and Veritas doesn't have access to Symantec stuff. Everything that was in Symantec has been move to Veritas, but numbers and links have changed. You'll have to google search the topic to find it. I think I found it here:
https://vox.veritas.com/t5/Backup-Exec/cannot-open-Backup-Exec-2012-console/td-p/544217