Hello Rosemary,
You'll probably need to run a dexsql.log of the error to see exactly what the system is pointing to. Looking for this error, it isn't one that we see all that much.
KB article 850996 - How to create a Dexsql.log file for Microsoft Dynamics GP and Great Plains
mbs.microsoft.com/.../KBDisplay.aspx
Also, if you haven't already, you can try the following:
**NOTE: Please ensure that you have a restorable BACKUP prior to performing any system maintenance.**
**NOTE: If possible, you may wish to test this in a test company created from a backup of your live data.**
1. Have all users exit Dynamics GP
2. Run the following scripts against the DYNAMICS database using Query Analyzer:
delete ACTIVITY
delete SY00800
delete SY00801
3. Run the following scripts against the tempdb database using Query Analyzer:
delete DEX_LOCK
delete DEX_SESSION
All of these tables are temporary tables and should be empty when all users are out of Great Plains. The information in the tables will be populated again once users log back into Great Plains.
My thinking is that a dexsql.log is going to need to be run in order to find out what is going on between Dynamics GP and the SQL objects when the error occurs.
Thanks