Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

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. In the NMM, choose Tools >> Gather Logs from the menu
      1. If you have an older version of NLINK, this option may not be available. In this case, use the File Explorer to open the Logs directory and gather the files by hand.
    2. Choose to include at least the NLINK.trc file
    3. Depending on your configuration, there may be other log files of interest as well
    4. Gather any files with a current datetimestamp and include them in the zip with the trace file
    5. An Event Log is often also helpful

 

Note
 NLINK trace files can become very large. Be careful to monitor the size of the NLINK trace file so that it does not either become too large to send to Customer Support or fill up your hard disk.

Video

Product Note: How to make a trace file

 

 

  • No labels