Microsoft Dynamics Forums Homepage

Forum Home Forum Home > Microsoft Dynamics GP (Great Plains) > GP - Installation and Administration
  New Posts New Posts RSS Feed - GP7.5SP7 to GP8.0SP4 upgrade
  FAQ FAQ  Forum Search   Register Register  Login Login


GP7.5SP7 to GP8.0SP4 upgrade

 Post Reply Post Reply
Author
Message
MrD1212 View Drop Down
MicrosoftDynamicsForums.com Member
MicrosoftDynamicsForums.com Member


Joined: September 18 2006
Status: Offline
Points: 20
Post Options Post Options   Thanks (0) Thanks(0)   Quote MrD1212 Quote  Post ReplyReply Direct Link To This Post Topic: GP7.5SP7 to GP8.0SP4 upgrade
    Posted: September 18 2006 at 4:31pm
New at this, so bare with me please.
 
I have been asked to upgrade our current GP7.5SP7 to GP8.0+SP4
 
So far I have figured out most of the steps.
 
I installed an old version of the server 7.5
upgraded it to 7.5
restored the data into it added the sp7
Then upgraded the server to 8.0
and then added the sp4
 
I then moved to the client, installed it and added the sp4
 
first issue:
I am only able to log in to my server and company file through the sa account.. both on the client and on the server... I cannot find anywhere on customersource a resolution to this.
 
I continue the installation of the client but having it upgrade the reports and forms, but it got very confusing:
 
manual tells me to select the 80 dynamics.dic and to select the module I want to update. In the details of the modules, I poitn to the 7.5 dictionary file of the module:
 
eg.
HR module
I use the 8.0 dynamics.dic and point the module to the 7.5 HR.dic file
 
that seems to work nicely, with some reporting issues...
 
it's all the other modules that don't work the same:
 
I notice that in the old 75 installation (let's say) I only have ADVSEC.dic file for the Advance Security module, but I have no ADVRPT.dic or ADVFRM.dic that the 8.0 dynamics is pointing to... so when I go to update that modules (and all the remaining ones) I ususally get the same:
 
file not found
 
How should I go about this?
Thanks for your time, as our time is running out ;)
 
Mr.D
 
 
Back to Top
Sponsored Links


Back to Top
Joseph A Nader View Drop Down
MicrosoftDynamicsForums.com Member
MicrosoftDynamicsForums.com Member


Joined: September 14 2006
Location: Lebanon
Status: Offline
Points: 360
Post Options Post Options   Thanks (0) Thanks(0)   Quote Joseph A Nader Quote  Post ReplyReply Direct Link To This Post Posted: September 19 2006 at 4:42am
I am afraid there has been an error during the upgrade, check the below script in order to restart the upgrade process:
 

To restart the upgrade of a company database to Microsoft Great Plains 8.0 or to Microsoft Great Plains 7.5, follow these steps:

1.

Restore the company database by using a backup version that was created before the unsuccessful upgrade attempt.

2.

Make a backup of the DYNAMICS database.

3.

Run the following script by using SQL Query Analyzer, SQL Server Management Studio, or the Support Administrator Console.

Note In the script, replace the following placeholders with the correct information:

Replace <Company_Database_Name> with the company database name. For example, if the company is named Adventure Works but has a database that is named TWO, replace the Company_Database_Name placeholder with TWO.

Replace <Major_version_number> with the correct major version number that you want to revert to.

Replace <Minor_version_number> with the correct minor version number that you want to revert to.

Replace <Old_major_version> with the correct major version number that you want to revert to.

Replace <Old_minor_version> with the correct minor version number that you want to revert to.

 

use DYNAMICS

declare @companyDBName as char(5),

@companyName as char(65),

@verMajor as int,       

@verMinor as int,

@verOldMajor as int,

@verOldMinor as int,

@companyID as smallint

set nocount on

set @companyDBName = '<Company_Database_Name>'

set @verMajor = <Major_version_number> 

set @verMinor = <Minor_version_number> 

set @verOldMajor = <Old_major_version> 

set @verOldMinor = <Old_minor_version> 

set @companyID = (select CMPANYID from SY01500 where INTERID = @companyDBName)

 

update DB_Upgrade set db_verMajor = @verMajor, db_verMinor = @verMinor,

    db_verOldMajor = @verOldMajor, db_verOldMinor = @verOldMinor, db_status = 0

    where db_name = @companyDBName

 

set @companyName = (select CMPNYNAM from SY01500 where INTERID = @companyDBName)

 

update DU000020 set versionMajor = @verMajor, versionMinor = @verMinor where companyID = @companyID

 

update DU000099 set versionMajor = @verMajor, versionMinor = @verMinor where CMPNYNAM = @companyName

 

delete DU000030 where companyID = @companyID

delete duLCK

set nocount off

Joseph Abou Nader, PMP



MCT
,MCTS,MCBMSS,MCSA
Back to Top
MrD1212 View Drop Down
MicrosoftDynamicsForums.com Member
MicrosoftDynamicsForums.com Member


Joined: September 18 2006
Status: Offline
Points: 20
Post Options Post Options   Thanks (0) Thanks(0)   Quote MrD1212 Quote  Post ReplyReply Direct Link To This Post Posted: September 19 2006 at 10:05am
Hi Joseph and thanks for answering so quickly.
 
Just to make sure I understood correctly...
I should and could:
 
1) delete the current unsuccessfull DB I tried to upgrade
2) create a new DB
3) restore previous DB data, structure and users onto the new DB
4) run the query
5) start GP8.0 installation/upgrade process from CD
6) install gp8.0 SP4
7) run GP Utilities
8) upgrade forms and reports
 
I do have a question:
 
You refer to  Major_version_number, Minor_version_number, Old_major_version, Old_minor_version
 
Where Major_version_number would be 8.0
Where Minor_version_number would be 66g
Where Old_major_version would be 7.5
Where Old_minor_version would be 53g (I think)
 
Did I understand this correctly?
 
Thanks again and have a wonderful day!
 
Mr.D
 
Back to Top
MrD1212 View Drop Down
MicrosoftDynamicsForums.com Member
MicrosoftDynamicsForums.com Member


Joined: September 18 2006
Status: Offline
Points: 20
Post Options Post Options   Thanks (0) Thanks(0)   Quote MrD1212 Quote  Post ReplyReply Direct Link To This Post Posted: September 19 2006 at 2:47pm
Interesting... as I was going through the tables that I would update with your script I noticed something odd.
 
While in Db_Upgrade and DU000020 the Maj and Min Versions are 7 and 50
 
in the DU000099 table, the maj and min versions for our company are 6 00 .. .. ..
 
I know that they originally upgraded from 6.0 to 7.5, but now I wonder if it is normal in this case to still have a reference to 6.0....
 
 
MrD
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down


Copyright 2013 microsoftdynamicsforums.com. All rights reserved. MicrosoftDynamicsForums.com is an independent non-Microsoft website.
Email: contact AT microsoftdynamicsforums DOT com