| Info |
|---|
This page is for NLINK version 8x, or version 7x (7.0.0.150 or newer). Please see How to Create and Gather NLINK Trace Files (NLINK 7x) if you are using NLINK version 7x prior to 7.0.0.150. Please see How to Create an NLINK Trace File (NLINK 6x, 5x) if you are using NLINK version 6x or 5x. |
Video
Product Note: NLINK Traces and Logs
Step-by-step guide
Follow these steps to create and gather NLINK Trace Files (aka "workset dumps" or "dump files") to send to Junot Support for help with troubleshooting data problems.
...
Gather Logs
Use the NLINK Management Module (NMM) to gather diagnostic trace files:
...
| Panel | ||
|---|---|---|
| ||
NLINK trace files tend to be small, but they do accumulate over time. Use the System Property Keep logs for n days to let the NLINK Manager service clean up the contents of the Logs folder automatically based on file modification date. Note that cumulative log files may not get purged if they are written to frequently, so you should still monitor the Logs folder to purge obsolete files on a regular basis. |
Video
...
Capturing NLINK crash logs
If the NLINK Server is suspected of crashing then the Windows OS generated crash logs are needed for further analysis. Typical symptoms of an NLINK Server crash are:
NLINK Server stopped without any Stopped message, or
Windows Application log will have error message entry about NLINK Server crashing.
Starting with NLINK 7.0.0.193, the registry entries required to capture Windows OS crash logs can be found in the file [NLINK Install]\Documentation\Crash Dump NLINK.reg. Run this file as administrator to create the necessary registry entries. With proper registry settings when NLINK Server crash occurs, a file (typically NLINK.dmp) will be created in the NLINK Logs folder C:\ProgramData\Junot Systems\Logs. If required, you can change the folder in the registry file before running it, or in the registry itself after creating the entry.