Unhandled database exception Save operation on table 'ASI_SOP_HDR_MSTR_Explorer" has caused an unknown error (39)

What if you end up creating a reminder based on a long running SmartList? It had to happen, right? As it turns out, if you create a reminder based on a long running SmartList, you will run into a nasty unhandled exception leading to an error 39, when launching Microsoft Dynamics GP.

In this particular case, the user created a reminder based on the Sales Transactions SmartList to display existing Orders, except they did not filter out just the orders in the work table. When the user attempts to log into Dynamics GP, they get an hourglass cursor, which eventually ends up with the error:

"Unhandled database exception Save operation on table 'ASI_SOP_HDR_MSTR_Explorer" has caused an unknown error (39)."

Since the issue is caused by the reminder calling such a large SmartList query to be executed, it is best to eliminate the offending reminder. You can run the following T-SQL query to identify the reminder:
-- Created by Mariano Gomez, MVP
SELECT * FROM dbo.SY01404 WHERE USERNAME = 'GP_User_ID';

Once you identify the name of the reminder causing the issue, you can run a delete statement to remove it, as follows:

-- Created by Mariano Gomez, MVP
DELETE FROM dbo.SY01404 WHERE Report_Option_Name = 'Reminder_Name' and USERNAME = 'GP_User_ID';

The above queries need to be executed against your system database. I strongly suggest you do this in a test environment first, and backup all your production databases prior to executing the queries there.

Until next post!

MG.-
Mariano Gomez, MVP

Comments

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

eConnect Integration Service for Microsoft Dynamics GP 2010