6.8.1 Canceling and re-setting service dependencies
If the JP1/Base event server name is not a default name such as an FQDN, an attempt to start a JP1/AJS3 service results in output of a message reporting that the dependent service or group could not be started. If this message appears, the JP1/AJS3 service can no longer be started. In addition, a message explaining that the JP1/AJS3 service depends on the JP1/Base Event service that could not be started due to the indicated error is output to the Windows event log.
To set an event server name in JP1/Base that is not the default name, cancel the JP1/AJS3 service dependencies as described below.
If no dependencies have been set, make sure that the JP1/Base and JP1/Base Event services are running, and then start the JP1/AJS3 service.
For details about how to set an event server name that is not the default value, see the JP1/Base User's Guide.
- Organization of this subsection
(1) Procedure for canceling dependencies
To cancel dependencies:
-
If the JP1/AJS3 service is running, stop it.
-
Execute the following command to cancel the JP1/AJS3 service dependencies:
SpmSetSvcAjs.exe -setdepend no
-
Restart the JP1/AJS3 service.
To resume operation that uses the default event server, set the dependencies among the JP1/AJS3, JP1/Base, and JP1/Base Event services again.
(2) Procedure for setting dependencies
To set dependencies:
-
If the JP1/AJS3 service is running, stop it.
-
Execute the following command to set the JP1/AJS3 service dependencies:
SpmSetSvcAjs.exe -setdepend yes
-
Restart the JP1/AJS3 service.
(3) Note
Before you execute SpmSetSvcAjs.exe on a host running Windows, make sure that you open the Command Prompt window as an administrator. If the UAC function is disabled, you do not need to open the Command Prompt window as an administrator.