Patrick-Dussault

Debug Diag to Diagnostic Problems as Starting a Process

Blog Post created by Patrick-Dussault Employee on Apr 5, 2017

On Windows, if you have problem to start a process, like Policy Server to illustrate it, you
can use Debug Diag to get the traces of the failure. Because the process doesn't start completely,
then you won't have any log from the Policy Server, and no dump from the process itself neither.
To get the traces and indication on the reason of that problem, follow this procedure. The resulting
files will give you a "trace" of what happens when loading .dll and modules. These indication might
be useful to have an idea where the start process stopped and its reason.

 

1 - To run Debug Diag against a Policy Server :

 

  - Insure that there's no Policy Server running on the system;
  - Double click on C:\Program Files\DebugDiag\DebugDiag.Collection
  - Click "Add Rule...";
  - Select "Crash";
  - Click "Next";
  - Select "A specific process";
  - Click "Next";
  - In "Selected Process", write "smpolicysrv.exe"
  - Click "Next";
  - Click "Exceptions...";
  - Click "Add Exception...";
    - For each "Exception code", select it and click "OK", and repeat until you have selected all "Exception code";
    - When you add all of them, click "Save & Close";
  - Click "Breakpoints...";
  - Click "Add Breakpoints...;
    - For each "Offset Expression", select it and click "OK", and repeat until you have selected all "Exception code";
    - When you add all of them, click "Save & Close";
  - Click "Events..."
    - For each the "Event Code", select it and click "OK", and repeat until you have selected all "Event Code";
    - When you add all of them, click "Save & Close";
  - Click "Next";
  - Click "Next";
  - Select "Activate the rule now";
  - Click "Finish";
  - Open the service pane, and make sure that "Debug Diagnostic Service" (DbgSvc) is up and running;
  - Make sure the Policy Server service is stopped and there's no running Policy Server;
  - As administrator, open a Dos console;
  - Go to the bin repository of your Policy Servert : c:/> cd /path/to/policyserver/bin
  - Write down the current date and hour on the Server;
  - Run the following command : c:\> smpolicysrv
  - Take a screenshot of any popup that might show up;
  - Go to folder : C:\Program Files\DebugDiag\Logs
  - Collect all the logs files starting with DbgSVC_ and smpolicysrv_ you find under this repository;
  - Collect all the dmp files you may find under this repository;

Outcomes