DBMS: 15151 Warning While Upgrading Dynamics GP Database to 18.8

(3) Share

Report

Posted on by PP-27011140-0

Hi,

While upgrading our GP Database 18.8.1941, the warning mentioned below was displayed for 2 of our Company Database Upgrades.

Please note that we have 4 Companies configured in our GP and only 2 of them are throwing this warning.

Please help us identify the impact it has.

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (9)

Answers (1)

Sort by

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

Like (1)

Report
Copy link

Link copied!

A quick search of SQL Server error 15151 says it is related to a missing or invalid login.

Are you running the upgrade using the 'sa' account?

Do you have any connections to a secondary SQL server?

Kind regards

David

Was this reply helpful? Yes No
PP-27011140-0 63 on at

Like (0)

Report
Copy link

Link copied!

Yes, I am using sa account. No, we only use single SQL Server Database.

Was this reply helpful? Yes No
PP-27011140-0 63 on at

Like (0)

Report
Copy link

Link copied!

PS: Is there a way to rerun the GP database upgrade while switching on the DexSQL Logs so that we find the Root Cause.

Thanks for the reply!!

Was this reply helpful? Yes No
Suggested answer

Lisa at AonC.com 1,154 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Regarding the GP Utilities error on GrantAllToTableZDPs(), here is a link to a community post with a verified answer: Error when running GP Utilities

Regarding restarting GP Utilities, here is a blog post on Upgrade Troubleshooting that includes information on restarting the upgrade. (Spoiler: Just launch GP Utilities again.) Microsoft Dynamics GP Upgrade 2025 - Upgrade Troubleshooting

Was this reply helpful? Yes No
PP-27011140-0 63 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the response Lisa, as per the article shared by you, I had remove the references of GL00100 in different schemas other than dbo. I have a schema named api and one stored procedure with a reference to GL00100. I dropped the procedure, confirmed that the dropped stored procedure does not have any references and reran the GP Utilities, and I am still facing the same challenge.

Was this reply helpful? Yes No
Suggested answer

Lisa at AonC.com 1,154 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Thank you for the update. I'm sure I have run into this recently so I'm going to throw this one out as another thing to check since you found issues with the account data: Do you have any tables in those two databases that have a period in the name? If so, rename the table to remove the period.

How about this blog post? Upgrading Microsoft Dynamics GP Error: The stored procedure smGrantAccessOnAccountMSTR returned the following results: DBMS: 0 Microsoft Dynamics GP

The gem that was buried in this post is this:

Was this reply helpful? Yes No
PP-27011140-0 63 on at

Like (0)

Report
Copy link

Link copied!

Hi Lisa,

There are no tables with a period in those 2 Databases. Here is the evidence from one of the Company Databases.

Was this reply helpful? Yes No
Verified answer

Assisted by AI

Lisa at AonC.com 1,154 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Thank you for checking!

How about trying to locate the GrantAllToTableZDPs stored procedure and manually executing the code?

****Bing CoPilot returned the following results with the prompt: dynamics gp GrantAllToTableZDPs****

In Microsoft Dynamics GP, the object GrantAllToTableZDPs is not a standard stored procedure, table, or view that ships with GP.

It is most likely a custom SQL script or utility that was created during an upgrade or deployment to grant permissions to ZDP tables.

What are ZDP tables in Dynamics GP?

ZDP stands for "Zero Downtime Procedures" or "ZDP tables" in the context of GP upgrades.

They are temporary or shadow tables created during an upgrade process to allow users to keep working while schema changes are applied.

These tables usually have names like ZDP_<TableName> and are used by the upgrade scripts to stage data.

Purpose of GrantAllToTableZDPs

From upgrade scripts and partner documentation:

It is typically a SQL stored procedure or script that:

Iterates through all ZDP tables in the company database.

Grants the necessary SELECT, INSERT, UPDATE, DELETE permissions to the DYNGRP SQL role (the standard Dynamics GP database role).

This ensures that after the upgrade, GP users can access the new or modified tables without permission errors.

Why you might not find it

It is not permanent — it may be created and dropped automatically by the upgrade process.

If you search after the upgrade is complete, it may already be gone.

It might exist only in the upgrade scripts provided by Microsoft or your GP partner, not in the live database.

If you are troubleshooting

If you are getting errors about GrantAllToTableZDPs missing:

Check the GP upgrade logs — see if the script failed to run.

Look in the GP upgrade folder for .sql files — you may find a script that creates and runs GrantAllToTableZDPs.

Manually grant permissions to ZDP tables if needed:

Sql

DECLARE @sql NVARCHAR(MAX) = ''; SELECT @sql += 'GRANT SELECT, INSERT, UPDATE, DELETE ON [' + name + '] TO DYNGRP;' FROM sys.tables WHERE name LIKE 'ZDP_%'; EXEC sp_executesql @sql;

(Run in the company database; make sure you have a full backup first.)

✅ Summary:

GrantAllToTableZDPs is a temporary upgrade helper for granting permissions to ZDP tables in Dynamics GP. It’s not part of the normal GP runtime and may not exist after the upgrade completes.

Was this reply helpful? Yes No
PP-27011140-0 63 on at

Like (0)

Report
Copy link

Link copied!

Thanks Lisa!

You are a life saver.

One Last Question: Our team wants to know the impact it has if the SQL Script does not resolve the challenge.

I mean, will there be any surprises once we move to Production/Live?

Is there a way to find out that the upgrade really succeeded?

Was this reply helpful? Yes No