Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Dexterity Tables causi...
Finance | Project Operations, Human Resources, ...
Answered

Dexterity Tables causing error... GrantAccess()

(0) ShareShare
ReportReport
Posted on by Douglas Meade 125

I have a custom Dexterity Application  that creates many new tables...  When it is installed from the chunk and the tables are created, logging into any company gives the following error:

The stored procedure GrantAccess() of from SQL Maintenance: 69: Pass Through SQL returned the following results: DBMS: 15151, Microsoft Dynamics GP: 0

I remember getting this error years ago and don't remember how I resolved it.

I'm pretty sure that it has to do with security on the new tables or procedures and it is can be resolved on the sql level and not a direct dexterity code issue.

If the custom dictionary is removed, there is no error.

Any assistance would be appreciated.

Thanks,

Douglas

Categories:
Microsoft Dynamics GP
  • Suggested answer
    David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 13,928 Most Valuable Professional on at
    RE: Dexterity Tables causing error... GrantAccess()

    I would turn on DexSql logging or capture a profile trace to see what is actually happening.

    It could be that you are passing the wrong database for the table series and it is looking for the tables and associated stored procedures in the wrong location.

    This is the usual error I have seen which causes this error.

    Regards

    David

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Dexterity Tables causing error... GrantAccess()

    I am not sure how your SQL script is structured but make sure any GRANT statements are proceeded with GO statement as a separator.

    MY SQL STATEMENT to create stored procedure

    GO

    GRANT EXECUTE ON MYSP TO DYNGRP

    GO

  • Verified answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Dexterity Tables causing error... GrantAccess()

    It sounds like the system is trying to run the equivalent of the Grant.sql script against the SQL objects created by your customization, but failing to do so.

    We often see DBMS: 15151 errors during upgrades when GP Utilities is running Grant permissions against all GP objects and it can't find or doesn't know what to do with an object, which is usually third-party or custom.

    For the tables that your customization creates in the GP databases, can you assign the SELECT, INSERT, UPDATE and DELETE permissions to the DYNGRP database role under the GP database they are created in, whether manually or via the Grant.sql script?

    If you're getting an error logging into a company database, a dexsql.log and/or SQL Profiler trace may also help point to the error message being seen.

    Thanks

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

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans