Backup Exec Server service not starting.
Mr Happy
downloaded Backup Exec v9.1 from Veritas. When I first started Backup
Exec after the install, I clicked the devices "tab" then right
clicked the tape drive and selected Inventory. It came back
immediately with an error saying that the connection with the Backup
Exec database had been lost and to check my cables. Then it would show
the Backup Exec login screen, when I try to login it gives an
unexpected error. I then stopped and tried to restart the services but
got an error when trying to start the backup exec server service.
Event ID 57802 I checked everywhere I know to check to find out how to
fix the issue and here is what I have done so far.
I disabled the Removable Storage service.
I opened each of the Backup Exec services and made sure they were being
started with a Domain Administrator ID and password.
I registered the schedmgrur.dll as instructed by Veritas.
http://support.veritas.com/docs/263295
I edited the default access permissions in DCOM
http://support.veritas.com/docs/275032
I even tried this one. I quickly removed what I added when this did
not help.
http://support.veritas.com/docs/275017
I have also removed and reinstalled the program with no success as of
yet.
DevDude
If you can look in the event log there should be an indication of what is
failing. That would help to know the complete error being returned.
Thanks
Nick
"Mr Happy" <cdo...@gmail.com> wrote in message
news:1141238437....@i39g2000cwa.googlegroups.com...
Mr Happy
9.1.4691.65 and downloaded SP4 for this version. I installed the SP4
and it didn't fix the problem. So I decided to make sure nothing was
corrupted with my tinkering from earlier. I uninstalled it then
deleted all registry keys with Veritas in them and then deleted the
Program Files\Veritas directory. Then I reinstalled and applied the
SP4 update and am now beating my head against the wall because it still
is now working.
BTW; I found out that it is a Terminal Server so I checked and made
sure that it was in Administration mode and not Application mode. Not
the problem it was in Administrative mode.
I have found the SGMon tool I was unaware Backup Exec had and have got
a log file showing what is not working and am now trying to find the
answer with this new info. I captured this log when trying to start
the Backup Exec Server service.
Capturing to C:\Program Files\VERITAS\Backup Exec\NT\logs\SGMon.log
1892: 0x0288 -1-0302:134855:Starting beserver system service
application
beserver: 0x089c -1-0302:134855:Entered RpcXfaceServiceMain.
beserver: 0x089c -1-0302:134855:Sending start status to scm...
beserver: 0x089c -1-0302:134855:Initializing work queue...
beserver: 0x089c -1-0302:134855:Initializing Persistent Store
(*****SERVER\BkupExec, BEDB, Backup Exec Server)...
beserver: 0x089c -1-0302:134855:InitializePartition() Shared Storage
Option is not licensed.
beserver: 0x089c -1-0302:134855:InitializePartition() Data partition ID
from registry=0
beserver: 0x089c -1-0302:134855:GetMyPartition() Data partition to use
for '*****SERVER' is 0
beserver: 0x089c -1-0302:134855:InitializePartition() returning 0x0
beserver: 0x089c -1-0302:134855:InitializePartition() ok,
partitionID=0, oldComputerName=
beserver: 0x089c -1-0302:134855:Creating Business Objects...
beserver: 0x089c 00-0302:134855:VSN BO Initialization succeeded.
beserver: 0x089c -1-0302:134855:FillServerInfo: cw.Open() failed.
beserver: 0x089c -1-0302:134855:ServerName:*****SERVER,
ActiveNodeName:,
InstanceName:BkupExec, DatabaseName:BEDB.
beserver: 0x089c 01-0302:134855:Server Configuration: BEServer schema
version checks OK.
beserver: 0x089c 01-0302:134855:Server Configuration: Initialization
Complete.
beserver: 0x089c 02-0302:134855:Ownership: Initialization Complete.
beserver: 0x089c 03-0302:134855:CAuditLogBO: Initialization completed.
beserver: 0x089c 04-0302:134855:LoginAccount: Initialization Complete.
BO=4.
beserver: 0x089c 05-0302:134855:Resource: Initialization Complete.
beserver: 0x089c 06-0302:134855:ServersBO: Initialization Complete.
beserver: 0x089c 07-0302:134855:ScriptMgrBO: Initialization Complete.
BO=7.
beserver: 0x089c 08-0302:134855:AdammAdminBO: Initialization Complete.
beserver: 0x089c 09-0302:134855:AdammUtilBO: Initialization Complete.
beserver: 0x089c 10-0302:134855:Reports: Loading any new reports.
beserver: 0x089c 10-0302:134855:Reports: Report Engine started.
beserver: 0x089c 10-0302:134855:Reports: Initialization Complete.
beserver: 0x089c 11-0302:134855:Job Completion BO: Initialization
Complete.
beserver: 0x089c 12-0302:134855:Job History: Initialization Complete.
beserver: 0x089c 13-0302:134855:JobManager: starting initialization...
beserver: 0x089c 13-0302:134914:JobManager: m_Schedule->Initialize()
failed, err=0x80004005
beserver: 0x089c -1-0302:134914:Business Object 13 failed to
initialize:14
beserver: 0x089c -1-0302:134914:RpcXfaceServiceMain: InitializeBOs()
failed, BO:13, nRet:14
beserver: 0x089c -1-0302:134914:Sending stop pending status to SCM...
beserver: 0x089c -1-0302:134914:RpcXfaceServiceMain exited.
beserver: 0x089c -1-0302:134914:Copy Job: Shutdown Complete.
beserver: 0x089c -1-0302:134914:PersistentStore: shutdown complete...
beserver: 0x089c -1-0302:134914:Catalog BO shutdown succeeded.
beserver: 0x089c -1-0302:134914:MessageQueue: Shutdown Complete.
beserver: 0x089c -1-0302:134914:JobLogBO: Shutdown Complete.
beserver: 0x089c -1-0302:134914:ServerObjects: Shutdown Complete.
beserver: 0x089c -1-0302:134914:Usershares: Shutdown Complete.
beserver: 0x089c -1-0302:134914:CAlertBO: Shutdown completed.
beserver: 0x089c -1-0302:134914:CAlertConfigurationBO: Shutdown
completed.
beserver: 0x089c -1-0302:134914:Notification: Shutdown Complete.
beserver: 0x09d0 -1-0302:134914:App stopped: SCM pending thread
exiting...
beserver: 0x089c 13-0302:134919:JobManager: shutdown complete...
beserver: 0x089c 12-0302:134919:Job History: Shutdown Complete.
beserver: 0x089c 11-0302:134919:Job Completion BO: Shutdown Complete.
beserver: 0x089c 10-0302:134919:Reports: Shutdown Complete.
beserver: 0x089c 09-0302:134919:AdammUtilBO: Shutdown Complete.
beserver: 0x089c 08-0302:134919:AdammAdminBO: Shutdown Complete.
beserver: 0x089c 08-0302:134919:AdammAdminBO: Shutdown Complete.
beserver: 0x089c 07-0302:134919:ScriptMgrBO: Shutdown Complete.
beserver: 0x089c 06-0302:134919:ServersBO: Shutdown Complete.
beserver: 0x089c 05-0302:134919:Resource: Shutdown Complete.
beserver: 0x089c 04-0302:134919:LoginAccount: Shutdown Complete.
beserver: 0x089c 03-0302:134919:CAuditLogBO: Shutdown completed.
beserver: 0x089c 02-0302:134919:Ownership: Shutdown Complete.
beserver: 0x089c 01-0302:134919:Server Configuration: Shutdown
Complete.
beserver: 0x089c 00-0302:134919:VSN BO shutdown succeeded.
beserver: 0x089c -1-0302:134919:BEServer shutdown completed.
I also looked a little deeper into the Event viewer and found other
ID's and am now looking into all the info I can find on these codes
as well as the errors in the log file and what to do for them.
Application Log
Event ID 1015
Failed to connect to server. Error: 0x800401F0
Event ID 34113
The description for Event ID ( 34113 ) in Source ( Backup Exec ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. The following information is part of the event: Backup Exec
Alert: Job Failed
(Server: "*****SERVER") -- The job failed with the following error:
Unable to load the job configuration information.
System Log
Event ID 7001
The Backup Exec Job Engine service depends on the Backup Exec Server
service which failed to start because of the following error:
%%0
Event ID 10005 (Not sure if this one pertains to my problem.)
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service NtmsSvc with arguments "-Service" in
order to run the server:
{D61A27C6-8F53-11D0-BFA0-00A024151983}
Event ID 7031
The Backup Exec Naming Service service terminated unexpectedly. It has
done this 2 time(s). The following corrective action will be taken in
0 milliseconds: No action.
Thanks for any replies
DevDude
beserver: 0x089c 13-0302:134914:JobManager: m_Schedule->Initialize() failed,
err=0x80004005
beserver: 0x089c -1-0302:134914:Business Object 13 failed to initialize:14
beserver: 0x089c -1-0302:134914:RpcXfaceServiceMain: InitializeBOs() failed,
BO:13, nRet:14
I also did a search on our http://support.veritas.com for that error and I
only find that a similar issue that was fixed with the build you have.
Deleting the HKLM\Software\Veritas\Backup Exec subkeys and directories
should have worked with a clean reinstall. So it must be related to some
other configuration on the system(Rights, directory permissions, COM+, etc).
So, Basically, there is something wrong with BEWS 9.1 being able to load the
scheduling component. I can't help much more than that. Your going to need
to call support and see if they can figure out why this component is failing
to load.
You always have the option of trying the latest release of 10d on
http://www.backupexec.com to see if that will resolve your problem.
Hope this helps,
Nick
"Mr Happy" <cdo...@gmail.com> wrote in message
news:1141413351.9...@p10g2000cwp.googlegroups.com...
mariobros
i need to make a drive image bootable into a DVD, is possible by acronis
true image 9.1 workstation?
is also possible to restore it automatically whitout other disks or tools
Greg Miller
trouble with Ghost on some of my PCs. I "think" (have not done it yet)
that you need to create the backup image, create an ISO image (I use
Nero) with the backup image in it. Then use Acronis TI to make the ISO
image bootable. The other (simpler) option would be to just make a boot
CD with the acronis tools and simply write the backup image to a
separate DVD.
Greg Miller
MillerNET Solutions
Get your free 200MB online backup account at
http://millernetprotect.com