Creating a Debug Dump

Customer Support may ask you for a debug dump when diagnosing an issue that the trace logs do not explain. A debug dump is a snapshot of what the FrameWorX Server is doing at the moment you take it: the sessions connected to it, the points those sessions hold, and the requests that are still pending. It complements a trace log, which records activity over time. Learn more

You create a debug dump with the DebugDump utility, a command-line tool installed with GENESIS. The FrameWorX Server must be running when you take the dump.

To create a debug dump:

1. Open a command prompt and navigate to:

   cd "C:\Program Files\ICONICS\GENESIS64\Services\FrameWorX"

2. Run the utility. Do one of the following:

   • To dump the FrameWorX Server alone, run the utility with no options.

     DebugDump.exe

   • To dump the FrameWorX Server together with the external point managers, add the --all option.

     DebugDump.exe --all

     A dump that includes the point managers describes more of the system, but it takes considerably longer to produce. Dump the FrameWorX Server alone when you need a result quickly, or when Customer Support has asked only about server behavior.

3. Read the path that the utility reports in Dump was created in:, and open the folder it names.

4. Attach the file to your correspondence with Customer Support.