SHOPZIMPORT and PPAIMPORT cron task runtime errors

Edit online

Several runtime errors can occur after executing the SHOPZIMPORT and PPAIMPORT cron tasks. These errors can be logged in different locations, containing the information on the error.

Note: Importing Shopz license entitlements is not supported for Maximo IT.

If there are runtime errors that inhibit further processing of a file, then a runtime exception will appear. One possible location of a runtime exception and the details of the error is in the Runtime Error column in the History tab of the cron task instance. In addition to checking the Runtime Error column for any error details, you should open the JVM logs on the system, because the JVM logs can provide further error details.

If the error is limited to a particular row, then the error will be logged along with the data of the row where the error was found, the row will be skipped, and processing will proceed to the next row in the file. You can configure the AssetManagement Crons logger found under the AssetManagement root logger, Open menu > System Configuration > Platform Configuration > Logging, to debug any errors by changing the Log Level setting from ERROR to DEBUG. When you configure the Log Level setting to DEBUG, informational messages will appear in the log when any row is skipped. If all rows are skipped, the XML file is not generated and license load will not occur. The Log Level should only be turned to DEBUG to get more information on the error.

If the error is encountered by the Integration Framework while processing the XML file, the Message Reprocessing application should be checked to determine the nature of the error and determine if the fix is possible. You can check the Message Reprocessing application at Go To > Integration > Message Reprocessing. You can also view more details by configuring the Integration logger to ACTIVE, and setting it to DEBUG. The Integration logger should only be turned to DEBUG to get more information on the error.