I am using GP10. When I create a new account and click on Save, the following error message appears: "A Save operation on table GL_Account_MSTR (45)." and it is not allowing me to create and save new account. Any ideas how to get rid of this error message? Thanks.
*This post is locked for comments
Hi, atlast the problem is resolved.
I ran the grant.sql, but after that also the problem remained. I tried DexSql.log method to identify the issue. Then I found that insert, update, delete stored procedures had been corrupted. I altered all those procedures by copying them from the working Fabrikam database of another SQL server instance and ran them against company database. While doing so, I got a message that "aagGetCompanyStatus" object was missing in DYNAMICS database. I created that object also from that Fabrikam database.
Now the issue is completely resolved. All the master records in GP can now be created, updated and deleted without any issues.
Thanks for your support Day!
You can find the Grant.sql script to run on a machine that has a client installed under the C:\program files\Microsoft Dynamics\GP\SQL\Util. It is a script you can run against the dynamics and the company databases that will grant access to stored procedures, inserts, updates, etc... for DYNGRP.
As far as the DexSql Log, here is a link to the steps. Basically it creates a log file sort of recording what you are doing and all the SQL stuff going on behind the scenes. Get that error message again while the trace is going on and you might be able to track down the error that way. Remember to turn off the trace after you are done or you will get an enormous log file pretty quickly.
Hi, Thanks for your help. I feel that those two KB articles are out-dated and might not be useful to solve my current issue. But I am eager to know how to run Grant.sql and DEXSQL log and give a try. Also I would like to know what is the cause of this error message. I tried synchronizing account framework, tried check links for account master, but nothing seems to be solving this!
There are two KB articles on Customersource that talk about this, except that they are a little dated (older versions of GP). At the least, they might be able to point you in the right direction. One has to do with running the server based indexing scripts for FRx (older versions) that were wrong, the other had to do with the ODBC connection. I would also consider running the Grant.sql script that grants execute rights to stored procedures to the DYNGRP.
You could also run a DEXSQL log that might be able to help you. Let us know if you don't know how to do that.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (