Video Screencast Help

Backup Exec services can't be started once we upgrade MS SQL Server from 2000 to 2005 on the backup server

Created: 07 Oct 2009 • Updated: 21 May 2010 | 16 comments
This issue has been solved. See solution.

Hi,

 

We are using Backup Exec V11d with SP4 on an application server. The application server had MS SQL server 2000, and we installed Backup Exec V11d on the server with a separate DB instance, and everything was working fine.

Our DBA upgraded MS SQL server 2000 to 2005, and after that all the Backup Exec services except "Device & Media servcie" can't be started on the server.

We have a test application server which has MS SQL server 2005, and I installed the same version(11d) of Backup Exec on the test server. Everything is working fine on this test server. 

Please advise. 

Thanks,
Anthony 

Comments 16 CommentsJump to latest comment

RahulG's picture

Please let me know the error message you get when you try to start the servcie . also check the error in the event log ...

Anthony Kim's picture

Hi

Thank you for the reply.

There is no relevant event logs.

The 2 following services status is "Starting" and it never ends, but I can see the 2 running processes(beserver.exe and beremote.exe) for the 2 services in the tassk manger.
- Backup Exec Server
- Backup Exec Remote Agent for Windows

Backup Exec Device & Media is running OK. 
Backup Exec Job Engine and Backup Exec Agent Browser can't be started due to the service dependencies with Backup Exec Server service. 

Anthony 

CraigV's picture

Hi Anthony,

Open up BEutility.exe and run a database repair.
If that SQL DB is sitting elsewhere, and not on the original server, it might be pointing to something that doesn't exist anymore.
Go too:

HKEY_LOCAL_MACHINE --> Software --> Symantec --> Backup Exec For Windows --> Adamm

Under the root of that key, make sure that Database Server Name and PreviousDjmPrimaryServer both point to the server running the SQL 2005 database.
Remember to backup your database if you make those registry changes.

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Anthony Kim's picture

Hi,

I deeply appreciate your advice.

This application is a productoin server, so I have to be very careful to do something to fix. The DB(MS SQL 2005) for the application server has been installed on E: drive, and the BE has been installed on C: drive. Our DBA upgraded MS SQL 2000 server to MS SQL 2005 server on the same server which the BE V11d is running on.

What is the BEutility.exe for?
Do I need to try both of your solutions(Run BEutility and fix the server name on the registry key?

I am not able to find the values(Database Server Name and PreviousDjmPrimaryServer) under the root of "Adamm" key, and I found a registry value(Backup server) which have the correct DB server name under DB2 key under
HKEY_LOCAL_MACHINE--> Software --> Symantec --> Backup Exec For Windows --> Backup Exec.

However, I found some similar value to PreviousDjmPrimaryServer named "DjmPrimaryServer" under Server key,  but it doesn't have any data. Do you think I need to point to the correct DB server for this value?

Thanks,
Anthony

BEsymc's picture

use beutility way, that would do the registry changes for you. Do not need to do anything in the registry, unless beutility fails to do so. Please note that beutility would not impact your SQL server. It is just going to make Backup Exec point to correct database. Also, can you post dbrecover.log file from c:\program files\symantec\backup exec\logs? Yes, there has to be something in the application log, if BE server service fails to start. So, please check that too.

Thanks

Anthony Kim's picture

Hi,

Here is the dbrecover.log.

Thanks,
Anthony

--------------------------------------------------------------------------------------------------------------------------
Backup Exec Database Recovery
10/08/09 08:44:19
-----------------------------
Initializing...
BEGetComputerName = 'KORSVR48700'
GetBeVirtualServerName = ''
Using node name for media server

CDBUtility::TrialConnectToSQL: sSQLServerInstanceName=KORSVR48700\BkupExec
Data for BE database:
Structure size: 6500
Media Server  : KORSVR48700
Node, if clust:
SQL Server    : KORSVR48700
Instance Name : BkupExec
SQL Instance  : KORSVR48700\BkupExec
SQL Service   : MSSQL$BkupExec
Database      : BEDB
App Data Path : C:\Program Files\Symantec\Backup Exec\Data
Database Path :
Database Log  :
Database File : C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf
Database Log  : C:\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf
Backup File   : C:\Program Files\Symantec\Backup Exec\Data\BEDB.bak
Base File     : C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.bak
Base Log File : C:\Program Files\Symantec\Backup Exec\Data\BEDB_log.bak
Is Local      : TRUE
IsDatabaseMgr : TRUE
Recover database using best method..
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=korsvr48700\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
Database BEDB is ONLINE
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=korsvr48700\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
Getting files for database 'BEDB'

GetDatabaseFiles: GetNextResult success dbRowCount=-1
Database exists - nothing to do
Setting up for IDR...
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=korsvr48700\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
Getting files for database 'master'

GetDatabaseFiles: GetNextResult success dbRowCount=-1
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=korsvr48700\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
Getting files for database 'model'

GetDatabaseFiles: GetNextResult success dbRowCount=-1
File Exist Check: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master$4idr
File Exist: TRUE
File Exist Check: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog$4idr
File Exist: TRUE
File Exist Check: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model$4idr
File Exist: TRUE
File Exist Check: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog$4idr
File Exist: TRUE
Deinitialize...

-----------------------------
Process completed
10/08/09 08:44:20
Status: DBU_SUCCESS
-----------------------------

CraigV's picture

Nope, I would use BEutility.exe (you can do a search for it) first, and only modify the registry if need be.
I don't have an issue doing this, but it would depend on how comfortable you would be touching your registry. It would simply end up putting the database server's details in manually. Restarting your services would mean that it would then redetect the settings change. If you still didn't come right, you would always be able to revert those settings to blank (and then restart the services again!).
Come to think of it, I think that Adamm folder is different to BE 11D...that's where my location for those 2 keys are.

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Anthony Kim's picture

Hi CraigV,

Thank you for the advice.

AS you can see the details of the dbrecover.log file which I posted, I don't find any error or problem in the log. I can see the correct media server name and SQL server name in the log.

Have you found any error or problem from the log?

Anthony

BEsymc's picture

Well, it seems it is your server service which is causing issue. dbrecover.log looks clean because your device and media service does start. Can you run sgmon.exe while starting Backup Exec server service, and see if there are some errors in there?

Thanks

CraigV's picture

Mmm...you can try with a blank database and see if this fixes it...
Stop your Backup Exec services, and then browse to your installation directory. THere is a folder called Data which contains the DB. Rename it to Data_Old.
Start up your BE services again, and then see if you get the same error. If you don't, and can do what you want, there was corruption in your original DB.
Just be aware you'll have to create autoloader partitions, media sets etc again as it will be a clean DB.
If you don't come right, stop your services again, delete that newly created Data folder, and then rename your Data_Old folder to Data. Start up your services, and everything will be there again (media information etc.)

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Anthony Kim's picture

Here the result of the sgmon.exe debugging tool  while starting Backup Exec Server service.

Can you please analyze it? Thanks!

Anthony

***************************************************************************
*****                  SGMon log for \\KORSVR48700                      *****
***************************************************************************
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = DEVICE_POOL_DEVICE_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00008000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6088] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - Parent = NULL , Entity = PARTITION
PVLSVR:   [10/21/09 22:13:35] [2160] PvlEntityDatabase::QueryEntity()
            ParentEntityType = NULL_ENTITY_TYPE
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = PARTITION_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00000000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6088] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - Parent = NULL , Entity = SLOT
PVLSVR:   [10/21/09 22:13:35] [4648] PvlEntityDatabase::QueryEntity()
            ParentEntityType = NULL_ENTITY_TYPE
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = SLOT_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00000000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6088] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - Parent = MACHINE , Entity = BACKUP_TO_DISK
PVLSVR:   [10/21/09 22:13:35] [2160] PvlEntityDatabase::QueryEntity()
            ParentEntityType = MACHINE_ENTITY_TYPE
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = BACKUP_TO_DISK_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00000000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6088] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - Parent = NULL , Entity = DEVICE_POOL
PVLSVR:   [10/21/09 22:13:35] [4648] PvlEntityDatabase::QueryEntity()
            ParentEntityType = NULL_ENTITY_TYPE
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = DEVICE_POOL_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00000000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6088] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - Parent = MACHINE , Entity = DRIVE
PVLSVR:   [10/21/09 22:13:35] [2160] PvlEntityDatabase::QueryEntity()
            ParentEntityType = MACHINE_ENTITY_TYPE
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = DRIVE_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00000000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6088] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - Parent = MACHINE , Entity = CHANGER
PVLSVR:   [10/21/09 22:13:35] [4648] PvlEntityDatabase::QueryEntity()
            ParentEntityType = MACHINE_ENTITY_TYPE
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = LIBRARY_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00000000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6088] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - Parent = NULL , Entity = MEDIA_SET
PVLSVR:   [10/21/09 22:13:35] [2160] PvlEntityDatabase::QueryEntity()
            ParentEntityType = NULL_ENTITY_TYPE
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = MEDIA_SET_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00000000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6088] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - Parent = NULL , Entity = VAULT
PVLSVR:   [10/21/09 22:13:35] [4648] PvlEntityDatabase::QueryEntity()
            ParentEntityType = NULL_ENTITY_TYPE
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = VAULT_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00000000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6088] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - Parent = NULL , Entity = VAULT_MEDIA_RULE
PVLSVR:   [10/21/09 22:13:35] [2160] PvlEntityDatabase::QueryEntity()
            ParentEntityType = NULL_ENTITY_TYPE
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = VAULT_MEDIA_RULE_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00000000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6088] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - Parent = NULL , Entity = MEDIA_SET_VAULT_MEDIA_RULE
PVLSVR:   [10/21/09 22:13:35] [4648] PvlEntityDatabase::QueryEntity()
            ParentEntityType = NULL_ENTITY_TYPE
            ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityType = MEDIA_SET_VAULT_MEDIA_RULE_ENTITY_TYPE
            EntityGuid = {00000000-0000-0000-0000-000000000000}
            EntityName = "
            EntityFlags = 0x00000000
BESERVER: [10/21/09 22:13:35] [6088] 12 AdammAdminBO::Query() - hr = 0x0
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::Deinitialize( ): killing dispatcher...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::Deinitialize( ): flushing cache...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::Deinitialize( ): empty cache...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::Deinitialize( ): remove alert monitor...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::Deinitialize( ): complete!
BESERVER: [10/21/09 22:13:35] [6020] 17 CJObManager::Initialize( ) - initializing cache...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::Initialize( ) - loading schedules...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::Initialize( ) - 2 schedules loaded
BESERVER: [10/21/09 22:13:35] [6020] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6020] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [10/21/09 22:13:35] [6020] 17 Job Dispatcher: GetServerIsRunningOnCluster()==FALSE
BESERVER: [10/21/09 22:13:35] [6020] 17 Job Dispatcher: UseClusterRestart=0
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): loading backup scripts...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): loading task definitions...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): loading solutions...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): loading work items...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): loading policies...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): making solution associations...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): generating workitem linkages...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): recovering tasks...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): DJM cleanup...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): flushing cache...
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): cached 0 policies
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): cached 0 solutions
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): cached 0 work items
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): cached 1 scripts
BESERVER: [10/21/09 22:13:35] [6020] 17 CJobManager::LoadAllJobData( ): starting dispatch processing thread
BESERVER: [10/21/09 22:13:35] [6020] 17 JobManager: m_JobManager->Initialize() err=0x0
BESERVER: [10/21/09 22:13:35] [6020] 17 JobManager: m_IsUsingJoinView = true
BESERVER: [10/21/09 22:13:35] [6020] 17 **** THE JOB MANAGER IS USING JOIN VIEW!!! ****
BESERVER: [10/21/09 22:13:35] [6020] 17 JobManager: initialization complete...
BESERVER: [10/21/09 22:13:35] [6020] 18 Notification: Initialization Starting.
BESERVER: [10/21/09 22:13:35] [6020] 18 DBConnection str Driver={SQL Server};Server=korsvr48700\BkupExec;database=BEDB;
BESERVER: [10/21/09 22:13:35] [4568] 17 CJobManager::GetConfigInfoFromRegistry( ) g_nMissedJobsTestConfig=0
BESERVER: [10/21/09 22:13:35] [4568] 17 CJobManager::Run( ): Delaying dispatch processing 30000 msecs
PVLSVR:   [10/21/09 22:13:36] [0000] HP 1 - TapeAlertFlags: 0x0000000000000000, hr = 0x0
PVLSVR:   [10/21/09 22:13:36] [5096] PvlDrive::DismountMedia()
            Session = {BE8BF116-AFB5-4167-B6F5-9DDE89E0E376}
            Drive = {F6016151-2071-4C5C-99C3-2C7C4BF9CAE4}, "HP 1"
            Slot = 0000
            Side = 4294967295
PVLSVR:   [10/21/09 22:13:36] [0000] HP 1 - TapeAlertFlags: 0x0000000000000000, hr = 0x0
PVLSVR:   [10/21/09 22:13:39] [1544] PvlDevice::MonitorThreadProc()
            DateTimeSync: Local = 2009/10/21 22:13:39, System = 2009/10/21 13:13:39 GMT, Database = 2009/10/21 13:13:39 GMT

Anthony Kim's picture

This is another result of the debug tool while Backup Exec remote agent service starting

Anthony

BEREMOTE: [10/21/09 22:26:39] [6844] Error accessing regkey: Software\Symantec\Backup Exec For Windows\Open File Option\ConfigOrphaned snaped can't be cleaned up. Maybe a privilage issue
BEREMOTE: [10/21/09 22:26:39] [6844] CleanupOrphanedSnapshots(). Lauching cleanup thread..
BEREMOTE: [10/21/09 22:26:39] [6844] CleanupOrphanedSnapshots(). Cleanup thread lauched. Exiting.
BEREMOTE: [10/21/09 22:26:40] [7640] FS_InitFileSys
BEREMOTE: [10/21/09 22:26:40] [7640]   loaded bedsnt5.dll
BEREMOTE: [10/21/09 22:26:40] [7640]   loaded bedsadc.dll
BEREMOTE: [10/21/09 22:26:40] [7640]   loaded bedssql2.dll
BEREMOTE: [10/21/09 22:26:40] [7640]   loaded bedsxchg.dll
BEREMOTE: [10/21/09 22:26:41] [7640] VirtApi DLL WAS LOADED FROM VirtApi.dll!  Virtual DB's WILL BE USED!
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedsxese.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedsmbox.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   bedspush.dll could not be loaded: The specified module could not be found.
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedsnote.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedsmdoc.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedssps2.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedssps3.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedsupfs.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedsshadow.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedsoffhost.dll
BEREMOTE: [10/21/09 22:26:41] [7640] ENTER DpmSettings::DpmSettings
BEREMOTE: [10/21/09 22:26:41] [7640]  EXIT DpmSettings::DpmSettings return=[0x0 SUCCESS]
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedsdpm.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedscps.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   bedsvx.dll could not be loaded: The specified module could not be found.
BEREMOTE: [10/21/09 22:26:41] [7640]   bedsorcl.dll could not be loaded: The specified module could not be found.
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedsagnt.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedssmsp.dll
BEREMOTE: [10/21/09 22:26:41] [7640]   loaded bedsra.dll
BEREMOTE: [10/21/09 22:26:42] [7640]   loaded bedsrman.dll
BEREMOTE: [10/21/09 22:26:42] [7640]   loaded bedsdb2.dll
BEREMOTE: [10/21/09 22:26:42] [7640]   loaded bedsss.dll
BEREMOTE: [10/21/09 22:26:42] [7640] VirtApi DLL WAS LOADED FROM VirtApi.dll!  Virtual DB's WILL BE USED!
BEREMOTE: [10/21/09 22:26:42] [7640]   loaded bedsadgran.dll
BEREMOTE: [10/21/09 22:26:42] [7640] Initializing FSs
BEREMOTE: [10/21/09 22:26:42] [7640] calling mapi initialize

Anthony Kim's picture

Hi,

Our DBA has confirmed that the BACKUPEXEC instance is working fine, and the dbrecover.log looks OK.

Any others can cause the Backup Exec server service and Backup Exec remote agent service hang(The service status is "Starting")
One interesting thing is that the processes(beserver.exe and beremote.exe) for the 2 services are running(I can see the processes in task manager), but the startup status of the 2 services is "Starting"

Any advices would be highly appreciated. 

Anthony 

BEsymc's picture

Is MS outlook installed on the media server? If yes, set it as your default mail client.

Thanks

SOLUTION
Anthony Kim's picture

Hi Hemant Jain,

Yes, the issue was resolved once I set MS Outlook as the default mail client instead of MS Outlook Express on Internet Explorer option --> Internet Programs.  

Unfortunately, your resolution was posted once I found this casue with the command, beserver.exe -console after about 12 hours trouble shooting effort!. I found the resolution just 1 hour before you posted your great solution. ;-)

Anyway, I deeply appreciate your great support on this issue. Thank you!!!

BTW, I don't find any relevant KB on this issue in Symantec KB site. Do you think this restriction should be posted as a KB.
And, Symantec must change the software architecture for this issue. For example, backup exec server service shouldn't require the default MAPI client configuration while the service is starting up. Instead when users run the backup exec software, the relevant alert should be popped up to notify users to set the default MAPI client.

Regards,
Anthony

BEsymc's picture

Anthony,
It was my mistake, it took time to understand that service is stuck on "starting" status. I was thinking, it was actually not able to start. This issue is known for long, and it is documented:
http://support.veritas.com/docs/269216
It was only evident from your last post that it is stuck on starting, and hence the solution. Good to know that it is fixed for you.

Thanks