I have known about the Support Debugging Tool for a while but have never had to install and use it at a client location. I took advantage of a recent client upgrade from GP9 to GP2010 to install it on all of the workstations while we rolled out GP2010. It has already paid dividends!

One user was getting an error on posting "Not privileged to run this report" when they posted Receivings Transaction Entry batches.  That's a standard error, and typically I haven't found it tough to resolve. Since it was received on posting, I did what I normally do: I went into a test company and posted a batch with a POWERUSER user to see what posting reports were turned on. However, I received the same 3 posting journals that this user did, except I did not get an error message. Hmmm….

SDT to the rescue

I turned to the Support Debugging Tool's Security Profiler feature, and it was a very quick way to find the problem. The steps were as follows:

  • Enable the Security Profiler on the user's workstation.
  • The user posted a test batch to get to the point of the permission error.
  • The user exported the information to the shared drive for debugging information.
  • I logged on as 'sa' and imported the information.
  • The SDT showed me it was the report "POP Backordered Items Received" that the user did not have access to.
  • I opened security via the shortcut, made the necessary change, problem solved!


There are a TON of things in this tool that I don't know how to use effectively yet and will be looking at other features I can take advantage of. One very cool thing is the colour customization of the GP windows which this client is using for test companies. They wanted to ensure the users don't accidentally forget they are in a test company and post something they want to be "live" data.

The second very cool thing is the option to rename the window titles when GP is minimized. In this case, the power users tend to have multiple instances of GP launched at once and with GP2010 having the user interface display all windows individually, their taskbar gets busy in a hurry. 

Check out David Musgrave's site for the Support Debugging Tool Portal for more information and lots of articles and information.

October 2017 update: this tool is now called GP Power Tools, from Winthrop Development Consultants. This post still refers to it as the Support Debugging Tool.