Dexterity Tables causing error... GrantAccess()

(0) Share

Report

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

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

Derek Albaugh Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Richard Wheeler 75,852 Moderator on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Suggested answer

David Musgrave MVP ... 14,151 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No