Filter
Top Products
Troubleshooting
Troubleshooting Data Protector Services and Daemons
Chapter 12 569
Troubleshooting Data Protector Services and
Daemons
The Data Protector services and daemons run on the Cell Manager. Run
the omnisv -status command to check whether services are running.
If the Data Protector services seem to be stopped or have not been
installed on the target Data Protector client, ensure first that you don’t
have a name resolution problem. Refer to “Troubleshooting Networking
and Communication” on page 565 for more information.
You can run into the following problems with Data Protector services and
daemons:
• “Problems Starting Data Protector Services on Windows” on page 569
• “Problems Starting Data Protector Daemons on UNIX” on page 571
Problems Starting Data Protector Services on
Windows
You do not have permission to start the services
The following error message displays:
Could not start the <Service_Name> on <System_Name>.
Access is denied.
Action The system administrator should grant you permission to start, stop,
and modify services on the system that you administer. You have to log
off and log on again on Windows NT system for the changes to take effect
or log off and log on as system administrator and then start/stop or
modify the services. On other Windows systems you do not have to log off
the system in order to start/stop or modify the services. Instead, you can
run the services.msc (located in the <%SystemRoot%>\system32
directory) as an administrator by right-clicking the file while holding
down the
Shift button and selecting Run as from the pop-up menu. Then
provide administrator’s user name and password.