Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When reporting errors, always include the Event Log if it is available. Workset dumps are especially helpful if we are chasing a data problem. If you are in a production environment and do not have a trace file, please let us know if the problem is reproducible and if you would be able to create a trace file if we need it.

Step-by-step guide

...

  1. A copy of the active NLINK meta-database (or the version number if we are keeping your meta-database in our source control system)
  2. The NLINK event log (exported from the NMM). (See Saving NLINK Event Log for instructions.)
  3. An NLINK trace file, including Workset dumps before and after the suspected problem when possible
  4. Pertinent log files (please check the DateTimeStamp) from the NLINK Logs directory (default installation path C:\Program Files\Junot Systems\Logsuse NMM menu Options->Goto Logs Folder)

See How to Find Files in an NLINK Installation if you need help locating any of these files. 

...

Filter by label (Content by label)
showLabelsfalse
max5
spacesNLINK
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "support" and type = "page" and space = "NLINK"
labelssupport

Page Properties
hiddentrue


 
Related issues