Moving Dynamics Data Files From One Server To Another - New Install Method


TechKnowledge Content


The information in this document applies to:


- Great Plains Standard on c-tree

- Great Plains Standard on Pervasive.SQL


SUMMARY

How do I move my Great Plains data from one server to another?


MORE INFORMATION


NOTES

1. If Window Level or Record Level Notes are used, and the procedures below are used to copy the data, multiple notes will be attached to the window or record. Please contact Microsoft Business Solutions-Great Plains Support for further requirements.


2.If using FRx, see Knowledge Base Article 854726 for steps to move FRx to another server.



Use the following steps to move Great Plains data from one server to another.


1. Do a complete install of Dynamics on the new server. This must be the same release ofDynamics that is currently on the existing server.


Note -If the existing Dynamics data is using the Btrieve/Pervasive.SQL 2000 database, this engine must be installedon the new server prior to performing the new installation of Dynamics.


Note -If using Dynamics 5.0 Btrieve and updating to Dynamics 5.5 or 6.0 Pervasive.SQL 2000, you must rename theW32BTICM.dll and the WBTRV32.dll in the Dynamics 5.0 application folder to access Dynamics 5.0 data on Pervasive.SQL 2000.


2. After installing Dynamics, butbeforelaunching Dynamics Utilities, copy theSY003001.*and SY00302.* files from the Dynamics\System folder on theoriginal server to theDynamics\System folder on the new server. These arethe Account Definition files.


3.Launch Dynamics Utilities and synchronize the Dynamics dictionary to the account framework.If you have copied in theframework files correctly in the previous step,it should not ask youto set up your framework but will synchronize to the existingfiles.


4.Launch Dynamics and log into the lesson company as one of the lesson users. If thelessoncompany was not installed, launch Dynamics.


5.Create a new company for each existing company using the identical name andcompany IDas on the old server. Go toSetup| System| Companyto create anew company. If thelesson company was not installed, the option to create thecompany will come up automatically.


Note -It is very important to create the new companies in the exact same orderas they were created on the old server. This is to ensure the Company IDs are thesame for each company on the old server and new server.


6.After all of the companies have been created and user access has been set for thesecompanies,complete the following:


a. Exit Dynamics and open Windows Explorer.


b. Open the Dynamics Company folder that was just createdon the new server.


c.Delete the seven folders that are within the company folder (Company, Finance,Inventory, Payroll, Project, Purchasing, and Sales).


d.Browse to the old server and open thecorresponding company data folder. Copy theCompany, Finance, Inventory, Payroll, Project,Purchasing, and Sales folders from theold server into the Dynamics company folder on the newserver.


For Example, the samplecompany in Dynamics is The World On-line, Inc. The dataisstoredin a folder called Two_Inc. In the Two_Inc folder is where theCompany,Finance,Inventory, Payroll,Project, Purchasing, and Sales foldersare located. If youwere movingThe World On-line from theold server to the new server, you would copythe Company,Finance, Inventory, Payroll, Project, Purchasing, and Sales folders fromthe old Two_Incfolder to the new Two_Inc folder after deletingthose folders on thenew server. This stepshould berepeated for all companies that need to be moved.


7. To retain the same system information such as user setup,security setup, andpayrolltaxesthe followingfiles should also be copied from thethe old server totheto the newserver:


SYSTEMFolderTAXESFolder
MC00100 (MC Exchange Rate Maintenance)UPR41300 (Payroll Tax Code Setup)

MC40200(MC Currency Setup)UPR41301 (Payroll Tax Status Setup)

MC40300(MC Exchange Table Setup)UPR41302 (Payroll Tax Table Setup)

MC60100(MC Currency Access)UPR41303 (Payroll TaxDate Setup)

MC60200 (MC Exchange Table Access)

PA01501 (Project User Setup)

PDK01000 (PDK Registration)

PDK01500 (PDK SY Company MSTR)

PDK01800 (PDK Palette Master MSTR)

PDK02000 (PDK SY Security Normal MSTR)

PDK02400 (PDK System Password MSTR)

PDK40000 (PDK SY Users Class SETP)

PDK40001 (PDK Users)

PDK40300 (PDK SY Class Normal SETP)

PDK40400 (PDK SY Class Main SETP)

PDK90100(PDK Security)

SY02600 (PDK User Notes MSTR)

SY01400 (User Master)

SY01900 (FinancialsSecurity Master)

SY01990 (Shortcut Bar Master)

SY02000 (Security Restrictions)

SY02400 (System Password Master)

SY02600 (User Notes Master)

SY03500(Registration Master)

SY40300 (Class Restrictions)

SY40400 (Class Master)

SY60100 (User-Company Access)

If using Dynamics Explorer/SmartList, copy all ASI*.* files.

If using Named Printers, copy all STN*.* files.


If a file is not present, just go on to thenext.It usually indicates that part of the programis not set up and is not being used.


Note - Make sure all users are out of Dynamics when the above filesare copied from the old server.


8.If the modified reports and forms dictionaries were stored in the Dynamics data directoryon the server, then the Reports.dic and Forms.dic should be copied from the Dynamicsfolder on the old server to the Dynamics folder on the new server. Make surethe path inthe Dynamics.set located in the Dynamics folder on the workstationispointingto thecorrect location for the dictionaries. To verify this, open the Dynamics.set in anedit modeby right clicking on it and choosing Edit or Open With and open it in Notepad.


9. Afterwards, you should run Check Links (File| Maintenance| Check Links) and reconcilethe years (Utilities|Financial|Reconcile), to verify the integrity of your data.


10. The additional workstations then need to be changed so they look at the data on the newserver. To do this, locate the Dex.ini file in the Dynamics folder on the additional workstationthrough Windows Explorer. Double click on the file to open it. Locate thelinesWorkstation=xxxxx and Pathname=xxxxx. Change these lines to look exactly like the Dex.inifile on the original workstation that was able to get into Dynamics on the new server.


11. After you have saved the changes made to the Dex.ini file, try launching into Dynamics againon the additional workstations.


REFERENCES


1.If using FRx, see Knowledge Base Article 854726 for steps to move FRx to another server.




This article was TechKnowledge Document ID:6409


The issue that is described in the Summary section does not apply to Microsoft Dynamics GP 10.0.