How to Create an NLINK Trace File (NLINK 6x, 5x)

Follow these steps to create an NLINK Trace File (aka "workset dump" or "dump file") to send to Junot Support for help with troubleshooting data problems.

Step-by-step guide

Follow these steps to create the most economical trace file:

1. Reset the trace file (optional)

   1. If you can stop the NLINK Service, do so. This ensures that only the most recent actions are logged.

   2. While NLINK is stopped, clear out the Logs folder (under your default installation location). You may not be able to delete all the files if NLINK is still running, so don't worry about those.

2. Turn on the trace properties (this can be done while NLINK is running, in case you could not stop it)

   1. In the NMM, right-click on the top-most node (the server name).

   2. Choose System Properties from the context menu

   3. Set Create Dump File = Yes

   4. Set Debug Level = Debug

   5. Click the Save button

3. Create the trace file

   1. If you have previously stopped the NLINK Server, restart it.

   2. Do whatever you need to do to create the situation that needs to be traced (e.g., run an NLINK event)

4. Turn off the trace properties

   1. In the NMM, right-click on the top-most node (the server name).

   2. Choose System Properties from the context menu

   3. Set Create Dump File = No

   4. Set Debug Level = Production (or leave it at Debug if appropriate)

   5. Click the Save button

5. Gather logs

   1. Choose to include at least the NLINK.trc file and any other log files that are in the NLINK logs folder. 

   2. Make sure all the logs have some data in them (check that files are non zero bytes in length when checking in windows explorer. 

   3. An NLINK Event Log should also be included

   4. Gather all files and include them in a zip file.
      In NMM, menu option "Tools→Gather Logs" can be used gather logs, but in some OS the zip file created may not include all  the files. 

Video

Product Note: How to make a trace file

Related articles