Backup Exec Server hangs at "Getting Network Configuration"
I recently upgraded from Backup Exec 12.5. I ran for about 2 weeks on the Trial Version while getting my upgrade licensing straightened around. I got that straightened around yesterday, entered my serial numbers, and went home for the night. I came in this morning to find that Backup Exec had failed overnight. No big deal, I just rebooted. And Backup Exec did not restart. I did some troubleshooting and ended up trying to start BEServer from the command line. The below was generated as the user that Backup Exec Server is set to run as:
C:\Program Files\Symantec\Backup Exec>beserver.exe -console
[0628] 02/09/10 16:16:20 -1 Starting beserver console application
[7828] 02/09/10 16:16:20 -1 Starting Service: BackupExecRPCService
[7828] 02/09/10 16:16:20 -1 Entered RpcXfaceServiceMain.
[7828] 02/09/10 16:16:20 -1 Sending start status to scm. (hint 300000)..
[7828] 02/09/10 16:16:20 -1 SetServiceStatus: state: SERVICE_START_PENDING check point: 1 wait hint: 300000
[7828] 02/09/10 16:16:20 -1 Checking service rights and pending reboots.
[7828] 02/09/10 16:16:20 -1 Checking for pending install reboot.
[7828] 02/09/10 16:16:20 -1 Pending install reboot not detected.
[7828] 02/09/10 16:16:20 -1 Checking to see if start up checks have been disabled.
[7828] 02/09/10 16:16:20 -1 No start up checks have been disabled.
[7828] 02/09/10 16:16:20 -1 Opening process token.
[7828] 02/09/10 16:16:20 -1 Getting token SID.
[7828] 02/09/10 16:16:20 -1 Got current SID: '<SID Withheld>'.
[7828] 02/09/10 16:16:20 -1 Checking for local system account.
[7828] 02/09/10 16:16:20 -1 Got local system SID: '<SID Withheld>'.
[7828] 02/09/10 16:16:20 -1 Not running as local system account.
[7828] 02/09/10 16:16:20 -1 Checking for admin privileges.
[7828] 02/09/10 16:16:20 -1 Current user does have admin privileges.
[7828] 02/09/10 16:16:20 -1 Checking for specific required rights.
[7828] 02/09/10 16:16:20 -1 Checking for 'Backup Files and Directories' privilege.
[7828] 02/09/10 16:16:20 -1 LookupPrivilegeValue( ) found privilege.
[7828] 02/09/10 16:16:20 -1 Privilege is enabled.
[7828] 02/09/10 16:16:20 -1 Checking for 'Restore Files and Directories' privilege.
[7828] 02/09/10 16:16:20 -1 LookupPrivilegeValue( ) found privilege.
[7828] 02/09/10 16:16:20 -1 Privilege is enabled.
[7828] 02/09/10 16:16:20 -1 Checking for 'Create a Token Object' privilege.
[7828] 02/09/10 16:16:20 -1 LookupPrivilegeValue( ) found privilege.
[7828] 02/09/10 16:16:20 -1 Privilege is enabled.
[7828] 02/09/10 16:16:20 -1 Checking for 'Manage Auditing and Security Log' privilege.
[7828] 02/09/10 16:16:20 -1 LookupPrivilegeValue( ) found privilege.
[7828] 02/09/10 16:16:20 -1 Privilege is enabled.
[7828] 02/09/10 16:16:20 -1 Checking for 'Take ownership of files and other objects' privilege.
[7828] 02/09/10 16:16:20 -1 LookupPrivilegeValue( ) found privilege.
[7828] 02/09/10 16:16:20 -1 Privilege is enabled.
[7828] 02/09/10 16:16:20 -1 Not checking for 'Act as part of the operating system' privilege as it is not needed for this environment.
[7828] 02/09/10 16:16:20 -1 Initializing ACE...
[7828] 02/09/10 16:16:20 -1 Cblmanger, shutdown Immenient: started.
[7828] 02/09/10 16:16:20 -1 Cblmanger, shutdown Immenient: complete.
[7828] 02/09/10 16:16:20 -1 Cblmanger, check shutdown Ready: started.
[7828] 02/09/10 16:16:20 -1 Cblmanger, check shutdown ready: complete.
[7828] 02/09/10 16:16:21 -1 Initializing work queue...
[7828] 02/09/10 16:16:21 -1 Read from Registry: DBTimeoutInSec=30 ServerInternal=0x0
[7828] 02/09/10 16:16:21 -1 Server Connection String = Application Name=BEWS Server;Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BEDB;Data Source=<Computer Name Withheld>\BkupExec;Locale Identifier=1033;
[7828] 02/09/10 16:16:21 -1 Initializing Persistent Store (<Computer Name Withheld>\BkupExec, BEDB, Backup Exec Server, 30 seconds)...
[7828] 02/09/10 16:16:21 -1 Attemp to GetMyPartition ComputerName=<Computer Name Withheld> PartitionID=0 PartitionGUID=d10681e2-e0d4-46d5-83b9-d24b172b4f4c
[7828] 02/09/10 16:16:21 -1 InitializePartition() Data partition ID from registry=0
[7828] 02/09/10 16:16:21 -1 GetMyPartition() Data partition to use for '<Computer Name Withheld>' is 0
[7828] 02/09/10 16:16:21 -1 InitializePartition() returning 0x0
[7828] 02/09/10 16:16:21 -1 Successfully GetMyPartition ComputerName=<Computer Name Withheld> PartitionID=0PartitionGUID=d10681e2-e0d4-46d5-83b9-d24b172b4f4c OldComputerName=<Computer Name Withheld>
[7828] 02/09/10 16:16:21 -1 InitializePartition() ok, partitionID=0, oldComputerName=<Computer Name Withheld>
[7828] 02/09/10 16:16:21 -1 Creating Business Objects...
[7828] 02/09/10 16:16:21 -1 SetServiceStatus: state: SERVICE_START_PENDING check point: 2 wait hint: 300000
[7828] 02/09/10 16:16:21 00 VSN BO Initialization succeeded.
[7828] 02/09/10 16:16:21 -1 SetServiceStatus: state: SERVICE_START_PENDING check point: 3 wait hint: 300000
[7828] 02/09/10 16:16:21 -1 Server Configuration: Getting network configuration.
..
Kommentare
A thought occurred to me that
A thought occurred to me that I saw a patch available in LiveUpdate, although I had not run it yet. So, I found this hotfix was available, started to read and found that "Adding a license keys to an install of Backup Exec causes the Backup Exec Server Service to hang."
I'm installing the patch right now and am hopeful that this solves the problem.
Thank you so so much for posting this.
As it is I've just wasted 2 hours of my life, reinstalling, trying this and that, but fortunately I stumbled upon SGMon.exe in the program folder and, like you did, I found the real error message.
I've been using Backup Exec since 8.6 and I've heard some ridiculous stuff over the years from Veritas/Symantec - "Upgrades are officially unsupported, always clean install", "Don't use AOFO to back up SQL", "Never install from Remote Desktop" etc. I was an early adopter of 11d when it barely worked, and now this: AN INSTALLER THAT BREAKS THE PRODUCT WHEN YOU PUT IN THE LICENCE KEYS AT INSTALL TIME.
Bravo Symantec - you've really outdone yourselves this time!
Möchten Sie antworten?
Einloggen oder registrieren, um Ihren Kommentar zu veröffentlichen.