000035765 - How to use Microsoft Debug View to troubleshoot RSA Archer Services

Document created by RSA Customer Support Employee on Dec 1, 2017Last modified by RSA Customer Support Employee on Dec 1, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000035765
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer Services
RSA Version/Condition: All
IssueThese steps are to assist in troubleshooting issues that may be related to the services components of an Archer Installation.
The RSA Archer Configuration service
The RSA Archer Job engine Service
The RSA Archer LDAP service
or the RSA Archer Workflow Service
Utilizing Microsoft Debug view can give insight to what is going on behind the scenes and can expose bad configurations or unintended behaviors of current configurations that wouldn't normally be seen. It can also provide guidance on where to look in regards to troubleshooting and resolution of related issues.
  1. Download the Microsoft Debug View tool from the following link:
    1. https://docs.microsoft.com/en-us/sysinternals/downloads/debugview
  2. Copy and Extract it to the server that has the Archer service.  (If more than one server runs the same services (IE: Job Engine service or Workflow Service, you will have to do this on each server.)
  3. When you extract the Contents of the zip file, you will see three files.
    1. Open the Dbgview application
    2. Agree to the License Terms
    3. Your window should look like below
    4. User-added image
  4. Next you will need the Process ID of the Service you are wanting to log the activity of.
    1. Open your Task Manager and click on the Details Tab
    2. Locate your service that you are wanting to track
    3. User-added image
    4. In this case we are going to track the RSA Archer Workflow Service with a PID of 3352
      1. Note: If you do not see your PID column, right click on the name column header and click select columns.
      2. User-added image
      3. Next, check the PID check box and the PID column should appear.
      4. User-added image
  5. Now that we have our PID of the service we want to track. Go back to the Debug View application.
    1. Click on the funnel icon within Debug view to open the filter
    2. User-added image
    3. Here we are going to enter our process id or PID in the Include section of the filter within square brackets.
    4. User-added image
    5. Click OK
    6. Next, click Capture and enable Capture Global Win32
    7. User-added image
    8. Now Debug View should be ready to capture the activity of the service and in this case, it is the Workflow Service.
  6. To test the capture, perform an action that requires that service.  Note: Do not restart the service or it will reassign a new PID
    1. If you are tracking the job engine service, run a package job or a data feed.
    2. If you are testing LDAP service. Execute an LDAP sync
    3. If you are Testing Advanced workflow service, Access an application with advanced workflow enabled, activate/deactivate an advanced workflow service, or Access the Advanced workflow Job troubleshooter in the Administration pages.
      1. Note: Most of the time, the workflow service doesn’t perform any actions itself beyond startup of the service. If you truly want to see what is captured for the advanced workflow Service You may need to run the Debug view without a filter.
      2. In this case, the filter needed to be reset
      3. User-added image
      4. Then results such as below will appear (this is only in regards to the workflow service capturing normal traffic. If there were errors, they would appear as well.)
      5. User-added image
  7. These steps are valid for any of the Archer Services and the information can be beneficial for tracking down and determining troubleshooting steps to resolve service related issues.