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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Issue with upgrading G...
Microsoft Dynamics GP (Archived)

Issue with upgrading GP 9.0 to GP 10.00

(0) ShareShare
ReportReport
Posted on by TrevorL 335

Hi, I've gone through the upgrade process without problems on a stand-alone test SQL 2005 Server (Build 9.0.3073 on a windows XP Pro box) environment. However, when I attempt the upgrade on the live system SQL 2005 Server (Build 9.0.3282 on a Windows Server 2003 SP 2, 32-bit box), the process hangs at the stage when GP Utilities should start upgrading the databases.....no error messages.....the database table upgrade process just does not start....Could it be an issue with the DYNSA username and password not being created, or something else?Any help would be much appreciated! Cheers,Trevor.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Hi Trevor,

    Rather than spending a long time trying to figure out the error it might be easier to just do the upgrade on your test server then move it across to your production server. 

     Regards,
    James

  • TrevorL Profile Picture
    TrevorL 335 on at

    Hi James - many thanks for your reply. We considered this as an option....is it fairly common practice, and if so, is the way to go simply to copy/restore the upgraded databases across to the production server, and then launch GP, without launching GP utils again?

    Subsequent to my first post, I found another case almost identical to mine, and the solution was to manually create the DYNSA user and password in SQL, without relying on the GP install process to do that, or if it was already there, to delete and recreate it, with dbo permissions, like the SA password. This has worked for us in a test environment where we had an image of the production server, and we plan to give it a go on the production server tomorrow.

    Regards

    Trevor.

  • Community Member Profile Picture
    Community Member on at

     Hi Trevor,

     It wouldn't be uncommon to move data from one server to another, The easiest would be backup the data on the test server and restore it on your production one.

     I've never heard of that DYNSA problem, they DYNSA login should be there already on the v9 installation. You could trying running a SQL profile, it might point you what is stopping the installation but from your description is sounds like an application rather than a database problem. 

    There would no harm in trying the recreate option you describe above.

    Let me know how you get on.

     Regards,
    James

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans