Troubleshooting data and workflow import issues
During installation, if you encounter data import issues (.ARX file) or workflow import issues (.DEF file), perform the following steps for troubleshooting:
- Examine the ProductName_Install_log.txt file located in the Temp directory.
- Look for a statement with RIKj exceptions, followed by -n and -l parameters, where -n indicates the name of the log file and -l indicates the location of the log file.
- Refer to the log file, for example logfilename.log, indicated by the -n parameter for specific information on the failure. Ideally, this file is located in the InstallDirectory\Logs directory.
- If an error has occurred while importing a particular file, a message is written to the corresponding error file, for example logfilename_error.log file, located in the InstallDirectory\Logs directory.
The message indicates the reason for the import failure.
- In the logfilename_error.log file, note the time stamp of the failure entry.
- Scan the logfilename.log file for the entries immediately preceding the failure entry in the chronological order.
- If the error message in the log file does not describe the issue, enable SQL and API logging and import the .DEF or .ARX file again. This will reproduce the error with additional information.
When you enable these logging options, log files are created in the following directory:
- (Microsoft Windows) ApplicationInstallDirectory\db
- (UNIX) ApplicationInstallDirectory/db
You can change the log file names and their locations at any time:
- In the BMC Remedy AR System Administration Console, click on System > General > Server Information > Log Files
- On the Log Files tab, change the name and location of the required log files.
To enable SQL and API logging:
- In the BMC Remedy AR System Administration Console, click on System > General > Server Information> Log Files.
On the Log Files tab, select the API Log and SQL Log checkboxes.
- Examine the status of all the data and workflow imports in the ApplicationInstallDirectory\Logs\applicationName_error.html file, which is generated when an installation fails.
- Examine the arerror.log for issues with the server. For more information about arerror.log, see from the BMC Atrium Core documentation.