Database Maintenance Utility

(0) Share

Report

Posted on by Rennecia Barran

Hi, I have upgraded a client to GP 2018R2 and now the Database Maintenance Utility cannot be launched as the dbmaintenance.exe file is missing.

Has this happened to anyone else?

I have reinstalled on a new machine and same issue.

Please help!

*This post is locked for comments

I have the same question (0)

All responses (15)

Answers (1)

Verified answer

Derek Albaugh on at

Like (1)

Report
Copy link

Link copied!

Yes, for whatever reason, the Database Maintenance Utility file got removed from the GP 2018 R2 installs, but does exist in GP 2018 installs and prior.

If you copy the DBMaintenance application file to the GP 2018 R2 directory, it will work.

Was this reply helpful? Yes No
Rennecia Barran on at

Like (0)

Report
Copy link

Link copied!

I will try this and let you know. I had 2018 installed and then ran the kb file to get it to 2018R2 so i cannot verify if the 2018 install had the exe file for the dbmaintenance.

Was this reply helpful? Yes No
Rennecia Barran on at

Like (0)

Report
Copy link

Link copied!

Thanks, this worked. I wonder if Microsoft is planning to fix this or if it is intentional.

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

Like (0)

Report
Copy link

Link copied!

What if this is a fresh installation of GP 2018 R2 and there is no file to copy? Is it found in any of the subfolders in the install media or do we need to find a copy from some other installation?

Was this reply helpful? Yes No
Rennecia Barran on at

Like (0)

Report
Copy link

Link copied!

Hi Richard,

What I found is once I install 2018 the plain version, the dbmaintenance file is there. When I apply hotfix MicrosoftDynamicsGP18-KB4099101-ENU the file is wiped out. I didn't try installing plain 2018R2.

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

Like (0)

Report
Copy link

Link copied!

Ali, I will need to install GP 2018 on a non-GP workstation and then copy that file to an installation folder for GP 2018 R2. All of our GP workstations have now been upgraded to R2. Looks like Microsoft has got to start beefing up their QA/QC. Too many omissions like this lately.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report
Copy link

Link copied!

Derek Albaugh,

I'm currently testing the GP Maintenance utility following a process I used to rename a GP instance and/or setup a different instance name.

However, when trying to run the tool, it works only against the Company DB's, but the DYNGP (system DB) doesn't do anything, no matter what objects I select, nor which module I try to run this against..

This is GP 2015R2 on a SQL 2014.. Tried both Windows & SQL authentication..

The blog post I'm referring to is here : https://blogs.msdn.microsoft.com/developingfordynamicsgp/2012/09/25/using-the-named-system-database-feature-for-microsoft-dynamics-gp-2013/

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report
Copy link

Link copied!

Hello,

I actually may have re-created the same thing on my GP 2015 R2 instance and it isn't even a changed system database.

When I run the DMU against both the system and company databases, it does nothing and doesn't throw an error at the end.

If I choose just the company database it runs fine.

I also restarted the SQL service to make sure all connections were dropped.

Let me look at this more, probably next week, and I'll let you know what I find out.

Thanks,

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report
Copy link

Link copied!

Thanks Derek,

I was just thinking I was foolish.. as it is working with the GP 2013 version... I don't have a 2018 right now to test.. so can't speak for that version.

Thanks for confirming that it's not my system DB :-) (tried 2 different names instances and none was working, except for the company DB's).

There is no rush, but I'd like to get this fixed as I may soon have to use it for a migration ..

B@

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report
Copy link

Link copied!

I was testing this some more and I can actually duplicate the issue in GP 2015, GP 2016 and GP 2018, using more than one install on each version.

What I found with all of them is that I could select the system and company database, modules and objects, then click Next and nothing would happen. Try it again without marking the system database as the only difference, and it would go through.

I found that this was/is a known issue and I was able to use this information to get the DMU to run through even on the system database:

1. Log into DB Maintenance.

2. Select all company databases and the Dynamics database.

3. Select all products

4. Select all options

5. Stop at this window

6. Open SQL Server Management Studio and run the following command in a new query: SP_WHO2

7. Look through the results and find your Dynamics/system database.

8. You will want to look at the SPID column and take note to the second SPID value

9. You will then run the following command in a new query, replacing the SPID number replacing 52 in this example: Kill 52

10. Then go back to DB Maintenance and click Next.

11. You will see it start to go through the progress and then see a results page with green check marks next to all products and databases.

I tested this and the system and company databases, for all features and all objects ran successfully.

Apparently the issue is because the DMU is creating two connections to the same databases, thus the reason why it hangs and doesn't do anything until we kill one of the connections.

Let me know if this doesn't work for you.

Thanks

Was this reply helpful? Yes No