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

Announcements

🚀 Season of Sharing Community Challenge Launch!
Ask A Community Pro
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) / GP10 1779 release does...
Microsoft Dynamics GP (Archived)

GP10 1779 release doesn't update the database appropriately

(0) ShareShare
ReportReport
Posted on by jvwiv 105

I am in the process of upgrading my test environment to a GP2013 installation.  In order to do so, I need to upgrade my GP10 1579 installation to the 1779 installation.  I downloaded the .exe and ran it in the test environment.  I then ran thru the upgrade of both Dynamics and my company database.  This took approx 1 hour to complete.  I now can log into the GP10 1779 installation on my dev box.

However, when I move that database to the new 2013 server, I can't upgrade the database.  It says that the database is at the 1579 version.  In fact, when I look at the dbupgrade table and look at the 0 productid, I see that it still thinks we are at the 1579 version.  Attempting to upgrade the database from 1579 to 1779 on the test server results in no changes needed.  BTW, when I log into GP on the test box, the version shown is 1779.

Any idea on how to proceed?  Should i simply update the field to show 1779 and if so, will i have this same issue when copying my production data to the new server?  (I plan on moving the production data into the dev env, running the utilities to convert it to 1779, then moving it to the final 2013 server and upgrading there to 2013)

*This post is locked for comments

I have the same question (0)
  • Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,061 Moderator on at

    Hi JVWIV,

    When you say 'move the database to the new 2013 server', what server version are your talking about ? is the new server already setup with GP 2013 ? what databases are you moving over to the new server ? how do you proceed ? detach / attach or backup / restore ?... What's your SQL server version on the two servers ?

    Lots of questions to answer before you even look at the minor GP version issues... There are strict procedures to follow when you move your GP companies from one server to the another... :  KB878449

  • jvwiv Profile Picture
    jvwiv 105 on at

    I have a SQL2008 install on the Test server, with a SQL2008r2 installation on the new server.  The 2008 server is running GP 10, sp5, and has had the 1779 service pack installed.  On that box,  we then ran GPUtilities and upgraded the dynamics and company databases.

    On the new server (sql2008r2) we are running gp2013SP1.  

    To move the db, i simply detached copie and pasted and reattached the db on the back end.  I moved both the Dynamics and the company databases. There is one company database.  

  • Suggested answer
    Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,061 Moderator on at

    This is not going to work....

    You can't override an existing GP2013 setup and databases by restoring your GP10 DB over the DB's...

    You have to follow the upgrade path that is provided by Micrsoft in their documentation :

    technet.microsoft.com/.../jj673201%28v=gp.30%29.aspx

    In your case you'll probably have to run the GP Utilities again on the new server, because your client is already on GP 2013, but your SYSTEM and Company DB's are not...

    Aside of that, detaching and attaching DB's to move to another server is never a good idea... because a lots of SQL objects are not taken care of (like user accounts and security roles in SQL). And if your DB's are in 'Full Recovery' mode, than you just broke your life-line to a potential restore in point...

    Microsoft's directions are to backup all your DB's and restore them on the new server.. Plus the restore will take care of eventual DB upgrades (likely the case when moving to a different SQL version).

    Chapter 11 from the GP2013 Upgrade guide will provide all the infos about the upgrade from GP 10.0 .

  • jvwiv Profile Picture
    jvwiv 105 on at

    OK, but the documentation says to take my GP10 database, restore it to the GP2013 db server, and run the gpUtilities against the db to perform the upgrade.  I'm doing essentially that except that I'm not doing the restore.  I understand the issues I may have long term with security as I'm just trying to prove out the upgrade path.  Once I have it working, I'll do it the right way with a copy of production data.  The issue that I believe I'm having is that my current production environment is a gp10 - 1579 installation.  There is no upgrade path from that version.  So, I'm taking the test env, upgrading to 1779 and then moving that to the new 2013 sql box.  The issue is that the gp10 databases are not showing a 1779 version level.  Here's the select statement that I'm running to get that information:

    select * from DYNAMICS..DB_Upgrade where db_name = 'DYNAMICS' and PRODID in(0,258,309)

    Prodid = 0 shows 1579, even though I've run thru the GP10 utilities and it shows 1779 as I launch GP.  How do I fix that?

  • jvwiv Profile Picture
    jvwiv 105 on at

    One thing you said seemed to resonate with me.  The fact that you think I'm laying a gp10 env over a gp2013 env.  Essentially your saying the Dynamics database should be a 2013 database, not an upgraded db.  So, That is what I did.  Put the original 2013 database back and then tried to upgrade the company database only.  Still no luck, but now it's a different message. I'll dig into that a bit more to ensure I did everything right before reporting that error.

    Thanks for the insight.

  • Suggested answer
    Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,061 Moderator on at

    Uhm...

    When you say that you take your 'test environment', are you talking about a Test company or a full TEST bed server running under GP10 ? Not following the instructions may end up in a different result and thus not guarantying a smooth upgrade path...

    Why would you detach/attach your DB's rather take a backup and restore ? I don't see the benefits of doing so...

    What does your DYNAMICS..DU000020  table contain ?

    If you're running in a virtualized environment (which is the easiest way to test the upgrade to 2013), take a clone of your production server, rename the server to have it not entering in conflict with your Prod system and rename the SQL server name as well (not the DYNAMICS instance).

    Apply the latest GP10 SP5 to bring you to 10.0.1779 on that TEST bed system. Once you've ensured your GP client is running fine on the new system with the latest version, apply the steps in the GP2013 Upgrade documentation. This means you basically install the GP2013 client on top of your GP10 and then run the GP Utilities to upgrade your SYSTEM (DYNAMICS) and company database...

    You have to understand that doing it the other way around is a sure step for failure... You cannot migrate a company DB without considering the DYNAMICS DB as well.. you may upgrade only one company at the time with the GP UTilities, but the System DB comes first in all cases...

  • jvwiv Profile Picture
    jvwiv 105 on at

    basically that is what I did, with one exception.  I have a test server that has GP10, SP5 installed on it.  I applied the 1779 patch to it and run the GP Utiliz.  For GP2013, I want a New, Clean install of a Database server, sql2008r2.  So I created a new server, installed sql r2, and installed GP2013 on it.  Now I simply want to upgrade the company database. As I've followed the directions from Microsoft and can not get this to work, I have to be doing something wrong.  The reason for the database copy is due to disk space.  Either method works per microsoft sql team, but yes, the restore does other things.  I'll add more disk to the server and try that next.

    I understand the upgrading the server logic, but that won't get me to a production environment, which is why I'm going thru this pain today. :)

    Thanks for the assistance.

  • Derek Albaugh Profile Picture
    Derek Albaugh Microsoft Employee on at

    Hello JVWIV,

    If you're still running into an issue with the upgrade to Dynamics GP 2013, it may be better to open a support case so one of us can remote onto your server(s) and see exactly what you're doing, and then we can let you know why you're running into the issues you're running into.

    From the case notes above, it seems that there is some confusion on what exactly has been done between the different server environments and sometimes it's easier just to look at the actual server and find out what is the cause of the issues you're seeing.

    Let us know if you have any further questions or you've resolved the issue since this was entered on June 6th.

    Thank you,

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

🚀 Season of Sharing Community Challenge Launch!
Ask A Community Pro
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

#2
Shravan Attelli Profile Picture

Shravan Attelli 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans