Akram,
You should be able to run a dexsql.log during the closing. This will give you a better idea on the data that is actually failing. Typically the error will be at or close to the bottom of the file.
In case you need them, the instructions to create the trace (log) file are beow:
To create a Dexsql.log file, follow these steps:
1. Open the Dex.ini file. By default, this file is in the following location, depending on the version that you are running:
• Microsoft Dynamics GP 10.0:
C:\Program Files\Microsoft Dynamics\GP\Data
• Microsoft Dynamics GP 9.0:
C:\Program Files\Microsoft Dynamics\GP
• Microsoft Business Solutions - Great Plains 8.0:
C:\Program Files\Microsoft Business Solutions\Great Plains
2. Locate the following statements in the Dex.ini file:
SQLLogSQLStmt=FALSE
SQLLogODBCMessages=FALSE
SQLLogAllODBCMessages=FALSE
3. If the statements are currently set to FALSE, change the statements to TRUE, as follows:
SQLLogSQLStmt=TRUE
SQLLogODBCMessages=TRUE
SQLLogAllODBCMessages=TRUE
4. Start Microsoft Dynamics GP. If Microsoft Dynamics GP is already started, exit Microsoft Dynamics GP, and then restart it.
5. Re-create the scenario in which you received the error message. Stop before you receive the error message.
6. In Windows Explorer, open the Microsoft Dynamics GP application folder that you opened in step 1. Locate the Dexsql.log file. Delete or rename this file.
If you do not see the Dexsql.log file, click View, and then click Refresh so that you can see the new file.
7. In Microsoft Dynamics GP, complete the final steps to re-create the error message. You now have a new Dexsql.log file in the Microsoft Dynamics GP application folder.
8. Open the Dex.ini file, and then reset the statements to FALSE or to the original settings.