Job Management Partner 1/Base User's Guide

[Contents][Glossary][Index][Back][Next]

16.5.2 Problems in Windows

The following problems might occur in Windows:

Table 16-4 Problems in Windows

No. Problem
1 The JP1/Base event service fails to start.
2 The Event Console window for JP1/IM - View displays incorrect times for JP1 events.
3 The authentication server fails to start.
4 The message Service specific error 3004. appears and the JP1/Base EventlogTrap service does not start.
5 The startup control function (JP1/Base Control Service) could not start or stop a service normally.
6 The startup control function (JP1/Base Control Service) could not stop a system when the system terminated.
7 To start the services in a specific order, you used the startup control to define the sequence of each service to start after the previous service had finished starting. However, the service started before the previous service finished starting, and an error message was displayed.
8 When you used the startup control (JP1/Base Control Service) to start a service, the following warning was displayed: The service indicated in XXXX has already started.
9 When you used the startup control (JP1/Base Control Service) to start a service, the following message is output to the event viewer's application log: Could not verify that the XXXX service has started within the specified time.
10 When you used the startup control (JP1/Base Control Service) to start a service, the message KAVA4003-E The XXXX service could not start because an unexpected error occurred. is output and the service does not start.
11 Cannot log in when the directory server linkage function is enabled.
Organization of this subsection
(1) The JP1/Base event service fails to start.
(2) The Event Console window for JP1/IM - View displays incorrect times for JP1 events.
(3) The authentication server fails to start.
(4) The JP1/Base EventlogTrap service fails to start, and the following message is displayed: "Service specific error 3004."
(5) The startup control function (JP1/Base Control Service) could not start or stop a service normally.
(6) The startup control function (JP1/Base Control Service) could not stop a system when the system terminated.
(7) To start the services in a specific order, you used the startup control to define the sequence of each service to start after the previous service had finished starting. However, the service started before the previous service finished starting, and an error message was displayed.
(8) When you used the startup control (JP1/Base Control Service) to start a service, the following warning was displayed: "The service indicated in XXXX has already started."
(9) When you used the startup control (JP1/Base Control Service) to start a service, the message "Could not verify that the XXXX service has started within the specified time." is output to the event viewer's application log.
(10) When you used the startup control (JP1/Base Control Service) to start a service, the message "KAVA4003-E The XXXX service could not start because an unexpected error occurred." is output and the service does not start.
(11) Cannot log in when the directory server linkage function is enabled.

(1) The JP1/Base event service fails to start.

The following describes why the JP1/Base event service does not start on a Windows host, and the action you should take.

Causes
You might have installed JP1/Base on a computer that is using an existing instance of JP1/IM. In this case, selecting Auto (in the Services dialog box that opens from the Control Panel) for the JP1/IM Control Service or JP1/IM Event service might prevent the JP1/Base Event service from starting.

Action
Change the settings for the JP1/IM Control Service and JP1/IM Event service to the manual mode. In addition, set the other JP1/Base-related services to the manual mode.

(2) The Event Console window for JP1/IM - View displays incorrect times for JP1 events.

The following describes why the time for JP1 events displayed on the Event Console window for JP1/IM - View is incorrect, and the action you should take.

Causes
The system is using an old version of msvcrt.dll.

Action
When installing JP1/Base, be sure to choose Restart in the dialog box that asks whether you want to replace msvcrt.dll. After replacing the file, restart the system.
If a malfunction such as incorrect event time occurs after installing other products, re-install JP1/Base.

(3) The authentication server fails to start.

The following describes why the authentication server does not start, and the action you should take.

Causes
The authentication server will not start unless you select the local host under Order of authentication server in the Authentication Server page of the JP1/Base Environment Settings window. By default, the authentication server does not start if you do not select automatic setup when installing JP1/Base for the first time.

Action
Specify the local host under Order of authentication server in the Authentication Server page of the JP1/Base Environment Settings window.

(4) The JP1/Base EventlogTrap service fails to start, and the following message is displayed: "Service specific error 3004."

The reason this message displays and the JP1/Base EventlogTrap service does not start, and the necessary action to correct the error, are described below:

Causes
This error occurred because the event log trapping service (JP1/Base EventlogTrap) started before the event service (JP1/Base Event) starts. This might occur if you select Auto as the startup method for the event log trapping service (JP1/Base EventlogTrap) in the Services dialog box that opens from the Control Panel.

Action
To automatically start the event log trapping service (JP1/Base EventlogTrap), use the startup control (JP1/Base Control Service) and set the event log trapping service (JP1/Base EventlogTrap) to start after the event service (JP1/Base Event) starts. For details on the startup control (JP1/Base Control Service), see 7. Setting the Service Start and Stop Sequences (Windows Only).

(5) The startup control function (JP1/Base Control Service) could not start or stop a service normally.

The following describes why you might not be able to start or stop a service normally using the JP1/Base Control Service, and the action you should take.

Causes
The possible causes are as follows:
  1. An interactive command or a command that displays a dialog box is registered in the start sequence definition file (JP1SVPRM.DAT).
  2. The path for a command in the start sequence definition file (JP1SVPRM.DAT) includes spaces, but has not been enclosed in double quotation marks (").

Action
To correct the problem, perform one of the following actions. Each number corresponds to the respective number of the causes described above:
  1. Check whether there is any interactive command or a command that displays a dialog box. Do not register these commands.
  2. Enclose the path in double quotation marks or register a reference path in the PATH environment variable. Write only the executable file name in the start sequence definition file (JP1SVPRM.DAT).

(6) The startup control function (JP1/Base Control Service) could not stop a system when the system terminated.

The following describes why you might not be able to stop a service using the JP1/Base Control Service when the system terminates, and the action you should take.

Causes
The possible causes are as follows:
  1. JP1/Power Monitor is not installed.
  2. You have shut down from the Start menu.
  3. Although you executed a forced shutdown from JP1/Power Monitor, the [Control Value] section is not registered in the definition file.
  4. The shutdown command for the OS was executed by a program other than JP1/Power Monitor.
  5. The startup method for the service is set to Auto in the Services dialog box that opens from the Control Panel.
  6. You have stopped the JP1/Base Control Service manually.

Action
To correct the problem, perform one of the following actions. Each number corresponds to the respective number of the causes described above:
  1. Install JP1/Power Monitor.
  2. Use JP1/Power Monitor to perform planned shutdown or forced shutdown.
  3. Register the [Control Value] section in the definition file.
  4. Use JP1/Power Monitor to perform planned shutdown or forced shutdown.
  5. Change the startup method for the service to Manual in the Services dialog box that opens from the Control Panel.
  6. Use JP1/Power Monitor to perform planned shutdown or forced shutdown.

(7) To start the services in a specific order, you used the startup control to define the sequence of each service to start after the previous service had finished starting. However, the service started before the previous service finished starting, and an error message was displayed.

The following describes why a service might start before the previous service has finished starting, and the action you should take. An error message is output when this happens. This might occur even though the start sequence has been defined for each service.

Causes
The possible causes are as follows:
  1. The startup control (JP1/Base Control Service) tried to complete the previous service's startup processing before starting the next service's startup processing. However, it did not finish before the specified maximum timeout, and the startup control started the startup processing of the service defined as the next one.
  2. The start sequence definition file (JP1SVPRM.DAT) specifies that the next service's startup processing is to start without waiting for the previous service's startup processing to finish.

Action
To correct the problem, perform one of the following actions. Each number corresponds to the respective number of the causes described above:
  1. Check the time necessary to start the service that caused the timeout. Then, in the start sequence definition file (JP1SVPRM.DAT), increase the value of the Wait= parameter for the service so that there will be no timeout.
  2. In the start sequence definition file (JP1SVPRM.DAT), consider changing the value of the Parallel= parameter for the service. For details, see Start sequence definition file (Windows only) in 14. Definition Files.

(8) When you used the startup control (JP1/Base Control Service) to start a service, the following warning was displayed: "The service indicated in XXXX has already started."

The following describes why, when you start a service using the startup control (JP1/Base Control Service), the warning The service indicated in XXXX has already started is displayed, and the action you should take.

Causes
This warning message is displayed when the service to be started using the startup control has already started. A possible cause of this warning message is that the service's startup settings have been set to start the service automatically.

Action
If you use the startup control to start the services, set the services' startup settings so that you can start the services manually.

(9) When you used the startup control (JP1/Base Control Service) to start a service, the message "Could not verify that the XXXX service has started within the specified time." is output to the event viewer's application log.

When you start a service using the startup control (JP1/Base Control Service), the following message might be output to the application log of the event viewer: Could not verify that the XXXX service has started within the specified time. If the specified service has already started, check the settings described below. If this message is displayed while the specified service has not started, consult the developer of the service about the possible cause of the startup failure.

If the Wait= parameter is not set in the section applicable to the service:
The service needs more than 60 seconds (the default timeout) to complete startup. Place the Wait= parameter in the service's section, and set its value to more than 60 seconds.

If the Wait= parameter is set in the section applicable to the service:
The service needs a period longer than the specified timeout to complete startup. Set the service's Wait= parameter to a value larger than the current one.

(10) When you used the startup control (JP1/Base Control Service) to start a service, the message "KAVA4003-E The XXXX service could not start because an unexpected error occurred." is output and the service does not start.

The following describes why, when you start a service using the startup control (JP1/Base Control Service), the service fails to start and the following message is displayed, and the action you should take: KAVA4003-E The service-name service could not start because an unexpected error occurred

Causes
This error might occur when startup of the service controlled by the JP1/Base startup control coincides with automatic startup of the same service by the Windows Service Control Manager.

Action
Set a slightly later time for the service to start under the startup control. This will prevent startup failure due to overloading at service startup.
For details, see 7.3 Setting the timing for starting services.

(11) Cannot log in when the directory server linkage function is enabled.

If the directory server linkage function has been enabled and a login attempt fails, refer to the integrated trace log to find the source of the error. If any of the following error messages is included, see the manual Job Management Partner 1/Base Messages to check the cause and action. After you check the cause and the necessary action to correct the problem, contact your directory server administrator:

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.