This subsection discusses the errors that might occur when inventory information is loaded from the managing server, the main causes of the errors, and the actions to be taken.

(a) A message such as Error occurred during command execution. For details, see the log file is displayed

An ASTCIMn.LOG file containing the following information is output to the log folder:

• The datasource name not found and no default driver specified (in Microsoft SQL Server)
• There was no SQL Server or access was denied (in Microsoft SQL Server)
• Connection error occurred (in Microsoft SQL Server)
• Invalid password for authorization identifier HiRDB (in Embedded RDB)
• Could not resolve service name (in Oracle)
• No listener (in Oracle)
• Invalid username/password; logon denied (in Oracle)

Check the following:

• In the Server Setup dialog box, one of the following settings might be invalid:
  
  • Login ID or Password in Database Information
  • Service name in Database Information
  • JP1/SD database login ID or Password in Link with JP1/SD
  • Connection service for JP1/SD database in Link with JP1/SD
  Specify each item correctly. Also check the database connection settings.
  
• If the Asset Information Manager Subset database has been created successfully, Connection service for JP1/SD database might not be specified correctly in Link with JP1/SD in the Server Setup dialog box.
  Specify Connection service for JP1/SD database correctly in Link with JP1/SD in the Server Setup dialog box.
  
• The service might not have been created correctly when database connection was set up.
  Make sure that the service has been created correctly. Also, use the test function to check the connection.
  
• The DBMS might not be running.
  Start the DBMS.
  

(b) A message such as Connection error occurred is displayed

An ASTMESn.LOG file containing the following information is output to the log folder:

• Connection error occurred (in Microsoft SQL Server)
• Invalid password for authorization identifier HiRDB (in Embedded RDB)
• Invalid username/password; logon denied (in Oracle)

Check the following:

• The DBMS server might be inactive, shut down, or engaged in termination processing.
  Make sure that the DBMS is running correctly.
  
• The user ID or password specified to establish connection might be invalid.
  Check the entries for any error.
  
• A timeout might have occurred due to a DBMS server error.
  Check the DBMS's operating status.
  
• Settings might not have been specified in the Server Setup dialog box.
  Specify the settings in the Server Setup dialog box.
  
• The connection target might not be a Managing server database.
  Specify the correct database connection settings; also specify in the Server Setup dialog box the correct value for Connection service for JP1/SD database in Link with JP1/SD.
  

(c) ASTMES.LOG file containing a message such as "Asset No. cannot be automatically assigned." is output to the log folder

If you have selected Use asset number in Assign key for asset information in Link with JP1/SD in the Server Setup dialog box, Auto cannot be specified for asset numbers.

Change the asset numbering setting from the Assign Inventory window or change Assign key for asset information to Use working key.

(d) A message such as Initialization failed is output to the log folder

The operating environment for Asset Information Manager Subset might have become corrupted.

Re-install Asset Information Manager Subset.

This subsection discusses the errors that might occur when inventory information is viewed by choosing the Inventory tab in the Device Details dialog box, the main causes of the errors, and the actions to be taken.

(a) A message such as There is no applicable device on JP1/Software Distribution is displayed, and no inventory information is displayed

• The device information might not have been imported from the managing server. Only device information imported from the managing server can be displayed.
• The managing server's database might not contain information about the corresponding device. Use JP1/Software Distribution's Remote Installation Manager to check for system configuration information and system information for that device.

(b) A message such as Inventory information cannot be displayed is displayed, and no inventory information is displayed

The connection target might not be the managing server's database, or the connection settings might be invalid.

Specify the correct database connection settings; also specify in the Server Setup dialog box the correct values for JP1/SD database login ID and Connection service for JP1/SD database in Link with JP1/SD.

This subsection discusses the errors that might occur during software distribution, the main causes of the errors, and the actions to be taken.

(a) When a package is added in the Software Applied window, an error message such as Unable to display JP1/Software Distribution Package is displayed

• The connection target might not be the managing server's database, or the connection settings might not be valid.
  Specify the correct database connection settings; also specify in the Server Setup dialog box the correct values for JP1/SD database login ID and Connection service for JP1/SD database in Link with JP1/SD.
  
• A database connection failure might have occurred in the managing server. Check the database and network status.

(b) When the contents of a cabinet are displayed in the Select Cabinet dialog box, an error message such as Unable to display JP1/Software Distribution Package is displayed

• The connection target might not be the managing server's database, or the connection settings might not be valid.
  Specify the correct database connection settings; also specify in the Server Setup dialog box the correct values for JP1/SD database login ID and Connection service for JP1/SD database in Link with JP1/SD.
  
• A database connection failure might have occurred in the managing server. Check the database and network status.

(c) When the Distribution Status job menu is selected or the execution status of a job is viewed in the Distribution Status window, an error message such as Unable to display distribution status is displayed

• The connection target might not be the managing server's database, or the connection settings might not be valid.
  Specify the correct database connection settings; also specify in the Server Setup dialog box the correct values for JP1/SD database login ID and Connection service for JP1/SD database in Link with JP1/SD.
  
• A database connection failure might have occurred in the managing server. Check the database and network status.

(d) Software distribution cannot be performed in the Software Applied window

The connection target might not be a Managing server database. Specify the correct database connection settings; also specify in the Server Setup dialog box the correct values for JP1/SD database login ID and Password in Link with JP1/SD and Connection service for JP1/SD database.

If a message that begins with KDAM2G15-E and reads If the message An error occurred in dmAPIOpenEx() of JP1/Software Distribution. See the JP1/Software Distribution log. is output to the log, install Remote Installation Manager on the Asset Information Manager Subset server and configure the Remote Installation Manager. For details, see 2.2 Installing Remote Installation Manager in the manual Setup Guide.

For details about the error, see 4.10 dcminst.exe (creating and executing a job), 4.11 dcmjbrm.exe (deleting a job), and 4.19 dcmrtry.exe (retrying a job).

(e) Jobs cannot be deleted or re-executed in the Distribution Status window

The connection target might not be a Managing server database. Specify the correct database connection settings; also specify in the Server Setup dialog box the correct values for JP1/SD database login ID and Password in Link with JP1/SD and Connection service for JP1/SD database.

For details about the error, see 4.10 dcminst.exe (creating and executing a job), 4.11 dcmjbrm.exe (deleting a job), and 4.19 dcmrtry.exe (retrying a job).

This subsection discusses the errors that might occur during acquisition of operation logs, the main causes of the errors, and the actions to be taken.

(a) The message "An error occurred during SQL issuance. (netmdm_monitoring_security:15)" is output to the log

The version of the managing server's database at the operation log reference target might be out of date.

Upgrade the managing server's database version to 08-00 or later.

(b) The message "The column name of the search condition is invalid. (netmdm_monitoring_security)" is output to the message log

This message is displayed when the managing server's database version is 08-51 or earlier and a search is performed with one of the following conditions specified in the Operation Log List window:

• Selecting File operation log in Logs to display and selecting Printed, Printing suppression, or Print suppression released in Type
• Selecting File operation log in Logs to display and specifying Document name
• Selecting Web access log in Logs to display
• Selecting External media log in Logs to display

Cancel the specification of the search condition.

This section describes possible causes of problems that may occur when Asset Information Manager Subset is installed or the Operation Log List window is used, as well as actions to be taken for such problems.

Table 6-19 Causes of problems with Asset Information Manager Subset and actions to be taken

Problem	Cause	Action
The Operation Log List window is not displayed.	An incorrect URL was specified on the AIM page during JP1/Software Distribution setup.	Check the URL, and specify the correct URL.
	World Wide Web Publishing Service is stopped in the connection destination server.	Start World Wide Web Publishing Service.
	In the browser settings, Active scripting is set to Disable.	Set to Enable.
	In the browser settings, Allow per-session cookies is set to Disable.	Set to Enable.
	In the browser settings, Submit nonencrypted form data is set to Disable.	Set to Enable.
	In the browser settings, Allow META REFRESH is set to Disable (for Windows Server 2003).	Set to Enable.
	In the browser settings, Binary and script behaviors is set to Disable (for Windows Server 2003).	Set to Enable.
The message The maximum number of users has been reached is displayed in the Operation Log List window.	The sessions connected to the Operation Log List window exceeded 300.	Wait awhile, and then open the Operation Log List window again.
The message KDAM3208-E The connection to the server was released is displayed in the Operation Log List window.	The session that connects to the Operation Log List window was disconnected.	If the Operation Log List window remains idle for one hour, all sessions are disconnected. Restart the Operation Log List window from Remote Installation Manager.
	If the OS is Windows Server 2003, the setting for the application pool to be used for Default Web Site and the jplasset virtual directory was incorrectly specified in the Microsoft Internet Information Services settings.	For details about how to set Microsoft Internet Information Services, see 2.3 Installing Asset Information Manager Subset in the manual Setup Guide.
The message An attempt to log in failed because the product version and the database version are different is displayed in the Operation Log List window.	The database version was not upgraded after version upgrade or a correction patch was applied to Asset Information Manager Subset.	Upgrade the version of the Asset Information Manager Subset database, and then reopen the Operation Log List window.
Search results are not displayed in the Operation Log List window.	An incorrect URL was specified on the AIM page for JP1/Software Distribution setup.	Check the URL, and specify the correct URL.