17.9 Principal causes of errors during linkage to JP1/IT Desktop Management 2 - Manager and how to handle them
The following table describes the errors that might occur during linkage to JP1/IT Desktop Management 2 - Manager. It also explains principal causes of those errors and what actions to take.
|
No. |
Error |
Principal cause |
Action |
|---|---|---|---|
|
1 |
Database access error (connection target: JP1/IT Desktop Management 2 - Asset Console). |
Under Database Information in the Server Setup dialog box, the specified ID (for Login ID) and password might not be set correctly. |
Specify the correct ID and password. |
|
2 |
Under Database Information in the Server Setup dialog box, the service name specified for Service name might not be set correctly. |
Use ODBC Data Source Administrator to check the data source, and set the correct service name. If no data source has been created, from Products for connection in the Create Data Source dialog box, select JP1/IT Desktop Management 2 - Asset Console to create a data source. |
|
|
3 |
Database access error (connection target: JP1/IT Desktop Management 2 - Manager). |
Under ITDM2 linkage in the Server Setup dialog box, the specified ID (for JP1/ITDM2-Manager database login ID) and password might not be set correctly. |
Specify the correct ID and password. |
|
4 |
Under ITDM2 linkage in the Server Setup dialog box, the service name specified for Name of the service connecting to the JP1/ITDM2-Manager database might not be set correctly. |
Use ODBC Data Source Administrator to check the data source, and set the correct service name. If no data source has been created, from Products for connection in the Create Data Source dialog box, select JP1/IT Desktop Management 2 - Manager to create a data source. |
|
|
5 |
The connection target of the data source might not be set correctly. |
For the connection target, specify the IP address that was set for database access in JP1/IT Desktop Management 2 - Manager setup. |
|
|
6 |
JP1/IT Desktop Management 2 - Manager might not be running. |
Check the operating status of JP1/IT Desktop Management 2 - Manager. |
|
|
7 |
The network might be temporarily unstable. |
Wait a while, and then re-execute the operation. |
|
|
8 |
Some devices are not registered or updated. |
Multiple assets might be assigned to the same asset information set because the values for the item specified as the assigned key are the same for different assets. |
For the assigned key, specify an item whose value is different for every asset. |
|
9 |
Device information might be already acquired. |
Update JP1/IT Desktop Management 2 - Manager's device information, or acquire management information by specifying the -ALL option. |
|
|
10 |
The time might not match in JP1/IT Desktop Management 2 - Manager and in JP1/IT Desktop Management 2 - Asset Console. |
Check the OS time, and match the time in JP1/IT Desktop Management 2 - Manager and in JP1/IT Desktop Management 2 - Asset Console. After the time matches, acquire management information by specifying the -ALL option. |
|
|
11 |
Device information in JP1/IT Desktop Management 2 - Manager is not deleted. |
JP1/IT Desktop Management 2 - Manager might not be running. |
Check the operating status of JP1/IT Desktop Management 2 - Manager. |
|
12 |
The network might be temporarily unstable. |
Wait a while, and then check the JP1/IT Desktop Management 2 - Manager's device information. |