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 can use the Database Name.
Enter the database name for the QA Machine you are using. from the application in the Column Filter for DatabaseName.

Click OK
Once the events and filters are correct click Run on the Trace Properties.
Start the trace right before performing the action
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, 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.

If the trace is stopped as soon as the error occurs, you can see the last transactions that may have caused the error.
You can select the line in the trace to see what transaction took place.

You can copy and paste this in an SSMS Query window to execute the transaction. To see if there is a problem.
The trace file can also be useful to developers looking into the case.

If it is a stored procedure, you can copy and paste the statement also. Be careful of procedures that are an update, add, Delete, or an Insert. If executed these may add or change records that should not be changed.

If you need to test something like this, always use the Sandbox company.
If it is a Select or a stored procedure to GET information, it is OK to run in the live company. This is OK to run since it is a stored procedure to get the Master Account information.

This will help narrow down where the problem is.