web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Introducing our New Video Series: Community Spotlight
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP smGrantAccessOnAcco...
Microsoft Dynamics GP (Archived)
Unanswered

GP smGrantAccessOnAccountMSTR

(0) ShareShare
ReportReport
Posted on by melissaw1234 12

Good afternoon, trying to upgrade from GP 10.00.1868 to 12.00.2230. Running GP utilities, the Dynamics database upgrades fine. When trying to upgrade the company databases, receive the following error:

Microsoft Dynamics GP Utilities:
The stored procedure smGrantAccessOnAccountMSTR returned the following results: DBMS: 0 Microsoft Dynamics GP:

This happens for both company databases, and it happens at the point where Utilities is "Run Miscellaneous Scripts" at the Updating Account Table Permissions.

Any ideas would be greatly appreciated!

Thanks!

*This post is locked for comments

I have the same question (0)
  • L Vail Profile Picture
    L Vail 65,271 on at

    Have you created the DEXsql log?

  • L Vail Profile Picture
    L Vail 65,271 on at

    Hi,

    In this thread community.dynamics.com/.../112211 here's what they said the problem was:

    "This ended up being a red herring situation. We discovered that a core financial table AF40103 had been accidentally renamed 'iv'. Once we renamed it back to AF40103 we were able to upgrade to SP5."

    Another thing I've seen is the error coming up if DYNSA is not the owner of the database. Finally, I've gotten this answer when I used a Dynamics.set file that had the Synchronize=FALSE when it should have been Synchronize=TRUE.

    Leslie

  • melissaw1234 Profile Picture
    melissaw1234 12 on at

    Hi Leslie,

    Thank you for the reply. I have created the DEXsql log, but nothing is jumping out at me as the issue there.

    DYNSA is the owner of the database and the synchronize has been set to TRUE.

    I saw the post that you mentioned above, and was hoping that would help. I am thinking it is a table issue, but not sure which table. I guess a support incident with Microsoft is going to be my next step.

  • Richard Ottley Profile Picture
    Richard Ottley 140 on at

    I ran into this issue as well after working a full 12 hour day doing upgrades. 

    What happened is for some reason, one of our tables was not under he ownership of the DYNSA. 

    We ran the Grant70.SQL from the Installation folders and that resolved the issue. 

  • Daniel Quiroz Profile Picture
    Daniel Quiroz 5 on at

    I have the same issue, did you find any solution for this problem?

    i ran the Grant.sql script on Dynamics DB but still the same error.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Introducing our New Video Series: Community Spotlight

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Dan Liebl Profile Picture

Dan Liebl 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans