Troubleshooting, Logging and Tracing

If your system does not work as anticipated, or an error occurs, you can troubleshoot your system.

For troubleshooting instructions, see Operation Guide.

Make sure that the error is not caused by system installation, configuration, or operation error, or environmental reason, such as network connection break.

If the problem seems to be caused by a product error and you need to contact support, you may need to provide them with the logs of the affected module. To do that you must set the logging level temporarily so that the error situation can be documented.

If you have IA and HAC versions 7.0 SP07 (7.0.7.0), or later, and your modules are 7.0 SP05 (7.0.5.0), or later, you can use Logging Configuration Wizard.
To download logs and traces, see Downloading Logs.

Dump File Folders

Sometimes dmp files are required for debugging.

As of SP09, the dmp files are written to the virtual unit’s log folder. The folder is defined during virtual unit installation as the variable Log File Directory of the Virtual Unit (VU_LOG_PATH).
Before SP09, dmp files are typically written to the folder where the crashing executable was located (typically the bin folder). An exception to this is debug-builds and if you had explicitly set registry setting LogWriteMethod to reliable. In that case, dmp files are written to virtual unit’s log folder as well.