My activities

Troubleshoot Workflow in Diagnostic Mode

If Workflow is behaving erratically or you need to troubleshoot other issues with the application, you can configure it in Diagnostic Mode to produce a .txt file with all the debugging information generated by the system. 

Note: The file paths referenced in this article will vary depending on your version of Perspective. If you're running version 4.6.2 or earlier, the path saved on your computer will contain a PPM 2000 Inc folder (i.e. C:\Program Files\PPM 2000 Inc\Perspective...). If you're running version 5.0 or later, it will contain a Resolver Inc folder (i.e. C:\Program Files\Resolver Inc\Perspective...).

    1. Open Control Panel > Administrative Tools > Services.

    2. Right-click the Perspective Workflow service, then click Stop.

    3. Run REGEDIT (Registry Editor):

      • For a 32-Bit server: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Resolver Inc\Perspective Workflow\General

      • For a 64-Bit server: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Resolver Inc\Perspective Workflow\General

    4. Double-click the Diagnostics registry to edit it.

    5. In the Edit String window, you may set the Diagnostics value to the following possible settings:

      • 0 No diagnostics

      • -1 All Servers in diagnostics

      • 1 Main Server diagnostics

      • 2 Schedule Server diagnostics

      • 3 Application Server diagnostics

      • 4 Email Server diagnostics

      • 5 Page Server diagnostics

      • 6 Fax Server diagnostics

      • 7 Copy Server diagnostics

      • 8 Report Server diagnostics

      • 9 Webcast Server diagnostics

      • 10 Action Server diagnostics

    6. After setting the Diagnostics value, exit the Registry Editor, then restart the Workflow service.

    7. Navigate to C:\Program Files\Resolver Inc\Workflow\Data\KS_Diagnostics.txt to retrieve the diagnostics log file.

    8. Once retrieved, follow the above steps and set the value to No diagnostics. Failure to do so will leave Workflow in diagnostics mode and will create a large .txt file that will consume space on your server hard drive.

    9. Once the files have been retrieved and Workflow returned to No Diagnostic mode.  Restart the Service again to ensure Workflow is running again.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk