Troubleshooting

Troubleshooting Data Protector Services and Daemons

Changed service account properties

If the service account does not have permission to start the service or if the service account properties (the password, for example) have been changed, you get the following error message:

The Data Protector Inet service failed to start due to the following error:

The service did not start due to a logon failure.

Action

1.

Modify the service parameters: in the Windows Control Panel, go to

 

 

Services (Windows NT) or Administrative Tools, Services

 

 

(other Windows systems).

 

2.

If this does not solve the problem, contact your system administrator

 

 

to set up the account with appropriate permissions. The account

 

 

should be a member of the Admin group and should have the Log on

 

 

as a service user right set.

 

A specific service has not been found

 

The location of the service is registered in the ImagePath key. If the

 

executable does not exist in the location specified under this key, the

 

following error message is displayed:

 

Could not start the <Service_Name> on <System_Name>. The

 

system can not find the file specified!

Action

1.

On the Cell Manager, copy the <Data_Protector_home>\db40 and

 

 

<Data_Protector_home>\config directories to a safe location

 

 

before uninstalling Data Protector.

 

2.

Copy the <Data_Protector_home>\db40 and

 

 

<Data_Protector_home>\config directories back in place.

 

3.

Uninstall the current Data Protector installation either on the client

 

 

or on the Cell Manager, and then reinstall the software.

 

This guarantees a clean installation with all the binaries in place.

 

MMD fails upon starting the CRS service

 

If the Data Protector CRS service fails to start and mmd.exe invokes a

 

Dr.Watson diagnosis, this points to a corruption in the database log files.

Action

1.

Delete the mmd.ctx file on the <Data_Protector_home>\tmp

570

Chapter 12