What to Include when Submitting a Bug Report

When submitting a bug report, in order for us to be able to analyze your problem, please consider providing the following information and attachments.

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

Step-by-step guide

Problem Statement

1. What was happening when the problem appeared? (e.g., I ran the Product Download for plant 3000)

2. What is the problem? (e.g., I got the following error from SAP in the event log)

3. What did you expect to happen? (e.g., When I ran this last night I got 312 entries in the interface table)

4. Is this problem new? Is it reproducible?

Information about the NLINK Environment

1. Operating system of the machine on which NLINK is installed

2. A list of other applications also installed on the NLINK machine

3. Information about the External Systems that are involved, such as version and installation location

 Attachments

Choose Tools >> Gather Logs from the NMM menu to easily collect all of the following in a single zip file.

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 https://junotsystems.atlassian.net/wiki/spaces/NLINK/pages/2545188885 for instructions.)

3. A copy of the sapnwrfc.ini file, if applicable

4. An NLINK trace folder covering the time period in question

5. Pertinent log files (please check the DateTimeStamp) from the NLINK Logs directory (use NMM menu Tools >> Gather Logs or Options >> Goto Logs Folder)

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