Issue:
Customer is receiving errors in their SedonaOffice company. Is there a way to get mor information on why the errors are occurring?
Resolution:
SQL server Profiler can be used to capture information from processes accessing the SQL server databases. Using SQL Server Profiler, you can create a trace that records and displays the commands sent to and the responses from the SQL server
Open SQL Server Management Studio
Connect to the correct server and select Tools then SQL Server Profiler.
It can also be launched from the Windows Menu.
In the Events Selection Tab, you’ll see the events it will monitor.
Be sure the options selected are the same as in the screenshot below.
To limit the results to the machine having the issue we use the ProcessID from the application.
You can get this from the Windows Task Manager on the Details tab.
Enter the PID from the application in the Column Filter for ClientProcessID.
Click OK
Once the events and filters are correct click Run on the Trace Properties.
Once running it will capture the activity between the application and the server.
Perform the action in the application that is causing the error. Once the error is received you can Stop the Trace and save the file.
The trace will show every transaction between the application and server and can be used to see what event caused the errors. The saved trace file can be attached to the support case or emailed to Support for analysis.
