This subsection describes how to use the Asset Information Manager Subset server and the Web browser to check errors.

(a) How to check for errors using Asset Information Manager Subset

1. Check the message log file for any error messages.
2. Any error message that has been output will indicate one of the following causes:
   
   • Error in the Asset Information Manager Subset database
   • Error in a program linked to Asset Information Manager Subset
   • Error in Microsoft Internet Information Services
3. If an Asset Information Manager Subset database access error has occurred, check the message log.
4. If an error has occurred in a program linked to Asset Information Manager Subset, check the message log file and determine whether there is a problem with the program linkage.
5. If a Microsoft Internet Information Services error has occurred, check the Microsoft Internet Information Services log and determine whether there is a problem with the communication sequence.
   If there is no problem with the communication sequence, the error might have occurred between Microsoft Internet Information Services and the Web browser.
   

(b) How to check for errors using the Web browser

If a runtime error has occurred, your Microsoft Internet Explorer version might be too old. Make sure that an up-to-date version of Microsoft Internet Explorer and all required service packs have been installed. For details about the Microsoft Internet Explorer version, see 1.1.2(1) Components of JP1/Software Distribution Manager in the manual Setup Guide.

In the event of an error, first check the event log, standard output, and log file created by the Asset Information Manager Subset server for any error messages.

If an error message has been issued, you can identify the program resulting in the error and the cause of the error from the error message's message type. For details about error messages, see (3) How to interpret messages.

Asset Information Manager Subset messages related to serious errors are output to the event log file. Check the event log file.

Asset Information Manager Subset server outputs error messages as files that are stored at the following location:

JP1/Software-Distribution-Manager-installation-folder\jp1asset\log

The log folder is created by default when Asset Information Manager is installed. The following table lists and describes the message log files that are output by Asset Information Manager Subset to the log folder.

Table 6-18 Files created in the log folder

File name	Description
ASTCIMn.LOG	Contains message logs for database access APIs.
ASTMESn.LOG	Contains information messages (such as for Asset Information Manager Subset start and termination) and warning and error messages (such as for program, communication, and database errors). You can use the message logs to check the operating status of Asset Information Manager Subset.

Legend:

n: A sequence number (1 to 9) that is part of the file name.

Logs are output to the current file until the maximum file size is reached, at which point another log file is created with the sequence number incremented by 1. When the file with sequence number 9 becomes full, the sequence numbering is reset to 1. You can identify the most recent log file from the date and time file attribute.

Do not change JP1/Software-Distribution-Manager-installation-folder\jp1asset\log\exp.def.

This subsection describes how to interpret the standard output message logs and the messages that are output to the message log file.

(a) How to interpret standard message logs

Each message log output by the Asset Information Manager Subset server consists of a message ID followed by a message text, as shown below.

Message format

KDAM nnnn-m message-text

KDAM

Indicates that this message was issued from the Asset Information Manager Subset server.

nnnn

Indicates in the first n a code for the component that issued the message followed by a 3-digit sequence number. The following component codes are displayed:

• 7: Command
• 8: Import and export

m

Type of message:

• E (error)
  Fatal error occurred, resulting in program termination.
  
• W (warning)
  Error that does not result in program termination occurred, but some functions have been disabled.
  
• Q (question)
  Message requiring a response from the user.
  
• K (working)
  Message reporting continuation of processing.
  
• I (information)
  Message that provides information.
  

(b) How to interpret the message log file

The message log file output by the Asset Information Manager Subset server contains messages that consist of the message output time, a message ID, and a message text, as shown below.

Message format

yyyymmddhhmmss.ttt pid(tid) KDAM nnnn-m message-text

yyyymmddhhmmss.ttt

Date and time the message was issued.

pid

Process ID of the process that issued the message.

tid

Thread ID of the thread from which the message was issued.

KDAM

Indicates that this message was issued from the Asset Information Manager Subset server.

nnnn

Indicates in the first n a code for the component that issued the message followed by a 3-digit sequence number. The following component codes are displayed:

• 0: Installation and setup
• 1: Asset Information Manager Subset server
• 2 or 3: Extension
• 4 or 5: Database access DLL
• 6: Asset Information Manager Subset's LIB and DLL files
• 7: Command
• 8: Import and export
• 9: Common DLL

m

Type of message:

• E (error)
  Fatal error occurred, resulting in program termination.
  
• W (warning)
  Error that does not result in program termination occurred, but some functions have been disabled.
  
• Q (question)
  Message requiring a response from the user.
  
• K (working)
  Message reporting continuation of processing.
  
• I (information)
  Message that provides information
  

When an error occurs in Asset Information Manager Subset, the Asset Information Manager Subset server issues a message whose message type is E. This subsection describes the Asset Information Manager Subset functions that are limited in the event of such an error.

(a) In the event of a serious system error requiring immediate attention

In the event of a serious system error requiring immediate attention, such as an unrecoverable error or an error that might cause data corruption if operation continues, all Asset Information Manager Subset services are stopped.

The following are serious system errors requiring immediate action:

• Specification errors or environment definition file loading errors
• Detection of meta table corruption
• Program exceptions (such as general protection exceptions)
• Program internal errors

(b) In the event of a non-urgent error

In the event of a non-urgent error that requires some time to correct but does not pose a threat of data corruption if operation continues, the processing resulting in the error is canceled.

The following are non-urgent errors:

• Invalid Web browser message format
• Message log output error
• Database disconnected from DBMS
• Error in a program linked to Asset Information Manager Subset
• Access error when asset information is to be added, changed, or deleted (except when there is no key property data)
• Program internal errors

(c) In the event of an operation-related error

The Asset Information Manager Subset services are not stopped in the event of an operation-related error, such as the following:

• Login error due to invalid user ID or password
• Inventory information loading error during Asset Information Manager Subset operation

(d) In the event of a transient error

In the event of a transient error that might be recoverable by waiting a while and then re-executing the operation, the processing resulting in the error is canceled and the session is closed.

The following are examples of transient errors:

• Memory allocation error or database connection error
• Database lock error
• Inventory information loading error during Asset Information Manager Subset operation