Skip to main content
Skip table of contents

Enable Trace Output for Workflow

This section will explain how to enable Trace. BTTrace output is an important tool in helping troubleshoot various PC product issues.

Extended Text:

  1. Turning on "BTRACE" debug facility, using "Start/Run," run the program "regedit."
  2. Under HKEY_LOCAL_MACHINE/SOFTWARE/ WOW6432Node/bitech/Common there should be a folder called "Trace." If there is not one, create it using Edit/New/Key.
  3. Under "Trace," use Edit/New/DWORD Value to create a new value called - "Enable" with a value of "1."
  4. Under "Trace," use Edit/New/String Value to create a new value called: "Output Type" with a value of "F."
  5. Under "Trace," use Edit/New/String Value to create a new value called: "FilePath" with a value of some easily accessible directory such as "c:\temp." This directory must already be available in the user file system.
  6. Open the PC Product the user wants trace on and/or restart the service that the user wants to trace (Data Processing Services or Workflow).
  7. In regedit the user should now see a "Modules" directory under the "Trace" directory (the user may have to hit F5 to refresh the regedit view). Within "Modules," the user should see several modules. Click on the entries and change their values to "F." It does not hurt to just set them all to F. Again, open the PC Product the user wants trace on and/or restart the service that the user wants to trace (Data Processing Services or Workflow).
  8. Look in the directory specified in step 5. There should be a file called debug####.txt (#### is the process ID, so there may be more than one). The most recently created debug file is the one we are looking for here.
  9. After all this is done, the user can disable trace by setting the "Enabled" value back to "0" (under HKEY_LOCAL_MACHINE/SOFTWARE/ WOW6432Node/bitech/Common/Trace).
  10. Stop and restart Data Processing Services. If the user enabled BTSQL2 module, the user will need to stop and restart Workflow Services as well.

Note: Set the module values for those modules in question as 15 (F hex) instead of 1. This will produce a larger volume of trace but will probably provide better indications of where the problem occurs. 1 will only show errors, not exceptions.








JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.