Frequently asked questions about the Windows Installer .msp files for Microsoft Dynamics GP

Overview

Q1: What is an .MSP file?

A1: An .MSP file is a Windows Installer patch file that includes updates to an application that was installed with Windows Installer.

Q2: Why is Microsoft Dynamics GP now using .MSP files?

A2: An .MSP file must be used to patch any application installed with Windows Installer. Microsoft Dynamics GP now uses Windows Installer and must be patched with an .MSP file.

Q3: Are all .MSP files inclusive?

A3: Yes. All .MSP files include all hot fixes, service packs, tax update, and payroll year end updates that were previously released.

Q4: Is there a current list of all .MSP files released for Microsoft Dynamics GP 9.0 and later versions?

A4: Yes. Visit one of the following Microsoft Web sites depending on whether you are a partner or a customer.

Microsoft Dynamics GP 9.0
Partner and Customer Microsoft Dynamics GP 10.0

Partner Customer Q5: What is the difference between installing an .MSP file and installing a Microsoft Business Solutions - Great Plains 8.0 service pack?

A5: The Microsoft Business Solutions - Great Plains 8.0 installation used Install Shield. Therefore, all service packs were an .exe file that used Install Shield for the installation. Microsoft Dynamics GP 9.0 and later versions uses Windows Installer to install the application. Therefore, all service packs, hotfixes, tax updates, and payroll year end updates must be installed with an .MSP file. The Microsoft Business Solutions - Great Plains 8.0 service packs required the user to run the Perform Special Upgrade process on the computer that was running Microsoft SQL Server. Microsoft Dynamics GP users no longer have to run the Perform Special Upgrade process. When you install an .MSP file on the server, the users have to start Utilities and mark each company database for an update. This process is similar to running an update from Microsoft Business Solutions - Great Plains 8.0 to Microsoft Dynamics GP 9.0. This process may take several minutes for each database.

Installation

Q1: Is there a preinstall checklist that I can follow before I install a service pack or a hotfix?

A1: Yes. Use the following service pack or hotfix preinstall checklist:

1. Verify that you are logged in as a domain administrator. This step eliminates any permissions issues to where the package or the installation file is located.
2. Run Windows Updates, and verify that you have all critical updates downloaded and installed.
3. Verify that you have Microsoft Windows Installer 3.1 installed. To do this, open the Add or Remove Programs item in Control Panel.
   
   For more information about how to obtain Windows Installer 3.1, click the following article number to view the article in the Microsoft Knowledge Base:
   893803 Windows Installer 3.1 v2 (3.1.4000.2435) is available
    
4. Make sure that the Microsoft .NET Framework 1.1 is installed and up-to-date. Update the .NET Framework through Windows Update. Verify that the updates are installed by looking for "Microsoft .NET Framework 1.1" in the Add/Remove Programs item in Control Panel.
5. Update the Windows Scripts for Windows XP. This step is not automatically performed through Windows Update. However, you can follow this step by visiting one of the following Microsoft Web sites:
   Windows Script 5.7 for Windows XP
   http://www.microsoft.com/download/details.aspx?familyid=47809025-D896-482E-A0D6-524E7E844D81
   
   Windows Script 5.7 for Windows Server 2003
   http://www.microsoft.com/download/details.aspx?familyid=F00CB8C0-32E9-411D-A896-F2CD5EF21EB4
6. Copy the .msp file to the local hard disk drive. Do not install the update over the network.

Q2: Does the user have to have specific rights on the workstation where the .MSP file has to be installed?

A2: Yes. The user must be a Power User or an Administrator on the workstation where the .MSP file is installed. If the user is not a Power User or an Administrator, the user receives the following error message: Q3: Are there special steps to install a service pack or a hotfix on a Windows Vista-based, Windows Server 2008, or Windows 7 computer?

A3: Use one of the following methods:

• Temporarily disable User Account Control (UAC). To do this, follow these steps:
  1. Turn off User Account Control (UAC).
     For more information, click the following article number to view the article in the Microsoft Knowledge Base:
     929908 Description of the Windows Vista versions that are supported together with Microsoft Dynamics GP
      
  2. Double-click the .msp file to install.
• Use UAC. To do this, follow these steps:
  1. Open the Command Prompt window as a user who has administrative permissions on the local computer. This command is located in the Accessories group. To do this, right-click the
     Command Prompt shortcut, and then click Run as administrator.
  2. Copy the path file to the root folder of drive C.
  3. Type the following command, and then press ENTER:
     cd c:\
  4. Type the following command, and then press ENTER to install the patch file:
     Msiexec /p c:\PatchFile /l*v C:\MSPErrorlog.txt
     Note PatchFile represents the name of the service pack or the hotfix that you are installing.

Q4: Can I run the .MSP file and copy the .CNK files out of the Microsoft Dynamics GP folder and then install these .CNK files at other client workstations?


A4: No. The .CNK files cannot be copied from the Microsoft Dynamics GP folder. Windows Installer tracks the addition of all .MSP files. If only the .CNK files were copied and installed, Windows Installer does not know which products were patched. There are also more files then the .CNK files that get patched. Copying only the .CNK files would cause additional problems if a user ran a repair on the Microsoft Dynamics GP installation.

Q5: Why is it required to start Utilities and update the company databases after installing an .MSP file on the server?


A5: In Microsoft Business Solutions - Great Plains 8.0, users ran the Perform Special Upgrade process when we released changes to database objects in the service packs. Microsoft Dynamics GP users must mark each company for an update in Utilities. This will make the appropriate database object changes for each database.

Q6: How long will the Utilities process for updating my company databases take?


A6: The update process may take several minutes for each company database depending on the size of the database.

Q7: Do I have to start Utilities at each client workstation after the .MSP file is installed?


A7: Yes. After the .MSP file is installed on the server, the user will be prompted to run Utilities at each client workstation.

Q8: Can I easily roll out an .MSP file to my clients?


A8: Yes. After the .MSP file is installed on the server, you can use the Automatic Client Updates feature to roll out the patch to all clients. See Chapter 5 in the SystemAdminGuide.pdf on the Release 9.0 Volume 1 CD-ROM under Documentation or on the Microsoft Dynamics GP 10.0 and later DVD.

Q9: If I do not install the .MSP on one client, will that cause issues?


A9: After the .MSP file is installed on the server, the database version has been updated for that patch. If a client workstation does not have the .MSP file installed, the version information will not match. That client will receive an error message that the version does not match and will not be able to log on.

Q10: Can third-party products use an .MSP file to install service packs?


A10: Yes. Third-party product can also use the Automatic Client Updates Feature to install the .MSP files automatically. Refer to Chapter 5 in the SystemAdminGuide.pdf on the Release 9.0 Volume 1 CD-ROM under Documentation.

Q11: Can I install the .MSP file on a client workstation first before installing the .MSP file on the server?


A11: Yes. However, the client will not be able to login to any company database until the .MSP file has been installed on the server. Utilities must also be started on the server to update all company databases.

Q12: Can I create an installation package (install template) from the Microsoft Dynamics GP CD or DVD that includes the .MSP service packs?


A12: At this time, the service packs cannot be included within the installation package file. However, you can set up an Automatic Client Update to automate the installation for the .MSP service packs. Refer to Chapter 5 in the SystemAdminGuide.pdf on the Release 9.0 Volume 1 CD-ROM under Documentation or on the Microsoft Dynamics GP 10.0 and later DVD.

Q13: If I have a test server that has multiple installations of Microsoft Dynamics GP 9.0 or later versions, will the .MSP installation patch all the installations?


A13: Yes. If you run the .MSP installation, all Microsoft Dynamics GP installations will be patched. If you want to patch only one Microsoft Dynamics GP installation, follow these steps:

1. Click Start, click Run, type regedit, and then click
   OK.
2. Locate and then click the following registry subkey:
   Microsoft Dynamics GP 9.0
   32-bit enironment
   HKEY_LOCAL_MACHINE\Software\Microsoft\Business Solutions\Great Plains
   
   64-bit environment HKEY_LOCAL_MACHINE\Software\wow6432Node\Microsoft\Business Solutions\Great Plains
   Microsoft Dynamics GP 10.0 and later versions
   32-bit environment
   HKEY_LOCAL_MACHINE\Software\Microsoft\Business Solutions\Great Plains\1033
   
   64-bit environment
   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Business Solutions\Great Plains\1033
3. Expand the folder for the instance of Microsoft Dynamics GP you want to patch.
   
   Note The DEFAULT folder is for the default installation. The Inst01 folder is for the second instance of Microsoft Dynamics GP. For example, if you want to patch the second installation, expand the Inst01 folder.
4. Click the SETUP folder, double-click the Product Code, and then copy the code.
5. Exit Registry Editor.
6. Click Start, and then click
   Run.
7. To install the .MSP file, type the following, and then click OK:
   C:\updatename.msp /n {E979C594-95F9-4E3A-985D-A1DFDF403227}
   Note Replace "C:\updatename.msp" with the path to the .MSP file and the name of the .MSP patch file. Replace "{E979C594-95F9-4E3A-985D-A1DFDF403227}" with the Product Code the you copied in step 4.

Troubleshooting

Q1: Is there a list of common error messages that may appear when running Windows Installer .MSP files?

A1: Yes. Visit the following Microsoft Web site to view an article that describes the error messages that may be generated when you install .MSP files: Q2: Why am I being prompted to insert the Microsoft Dynamics GP 9.0 CD when I am installing a service pack for Microsoft Dynamics GP 9.0? A2: This error message may indicate potential issues with the current install of Microsoft Dynamics GP 9.0 on this computer. Insert the Microsoft Dynamics GP 9.0 to continue the service pack installation. If the installation does not continue, remove Microsoft Dynamics GP 9.0 from this computer. Then, reinstall Microsoft Dynamics GP 9.0, and then install the latest service pack.

Q3: Why do I receive the following error message when I am installing a service pack for Microsoft Dynamics GP 9.0? A3: If you have only one installation of Microsoft Dynamics GP 9.0, this error message may indicate potential issues with the current installation of Microsoft Dynamics GP 9.0 on this computer. To resolve the problem, follow these steps:

1. Click Start, click Control Panel, and then double-click Add or Remove Programs.
2. In the Currently installed programs list, click Microsoft Dynamics GP 9.0, and then click
   Change.
3. Run a repair on the Microsoft Dynamics GP 9.0 installation.

If the problem is not resolved, remove Microsoft Dynamics GP 9.0 on this computer. Then, reinstall Microsoft Dynamics GP 9.0, and then install the latest service pack again. If you have multiple installations of Microsoft Dynamics GP 9.0 on your computer and you are installing an .MSP update that is older then other .MSP files that have been installed, you will receive the error message. For example, if you have installed Service Pack 1 and you are now installing the 2005 Payroll Year End Update .MSP file, you may receive the error message. If you would like to patch an installation with an older .MSP file, follow the steps in the answer to question 17 to manually patch only one installation.

Note All .MSP files include all the previous .MSP file fixes.

Q4: Why do I receive the following error message when I am installing a service pack for Microsoft Dynamics GP? A4: This error may occur if the workstation is not restarted after you are prompted to restart.

1. Restart the workstation, and then start Microsoft Dynamics GP again.
2. Rename the Dex.dic file in the Microsoft Dynamics GP folder, and then run the msp patch installation again.

This error may occur when you attempt to start Microsoft Dynamics GP if the DEX.DIC is not at the correct build.

1. Please browse to the Microsoft Dynamics GP Code folder on the server (the default path is C:\Program Files\Microsoft Dynamics\GP) and rename the current DEX.DIC to DEXOLD.DIC.
2. Open Control Panel, click
   Add/Remove Programs and click Microsoft Dynamics GP 9.0 or Microsoft Dynamics GP 10.0 and click
   Change.
3. In the ‘Program Maintenance’ window select the
   Repair option.
4. Start Microsoft Dynamics GP by double clicking on the
   Microsoft Dynamics GP icon to verify the error is resolved.

Q5: When I try to install a service pack for Microsoft Dynamics GP 9.0, I receive the following error message: When I browse to the GreatPlains.msi file on the installation CD, I receive the same error message. What is the problem?

A5: This problem occurs if the path to the original GreatPlains.msi file was changed or if the file was moved. You must correct the registry entry for the path of the GreatPlains.msi file. To do this, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

1. Click Start, click Run, type regedit, and then click
   OK.
2. On the File menu, click
   Export.
3. In the File name box, type
   registry backup, click All under
   Export Range, and then click Save.
4. Press CTRL+F, type GreatPlains.msi, and then click Find Next. A registry subkey that resembles the following will be returned:
   HKEY_CLASSES_ROOT\Installer\Products\495C979E9F59A3E489D51AFDFD042372\SourceList
5. Right-click LastUsedSource, and then click
   Modify.
6. Replace the current path with the path to the GreatPlains.msi file on the Microsoft Dynamics GP 9.0 installation CD. For example, if the CD is in the D drive, the Value data information is as follows:
   D:\Bin\
7. Click OK, and then exit Registry Editor.
8. Retry the installation of the service pack.
   
   Note If you have multiple instances of Microsoft Dynamics GP installed, you may have to repeat these steps to fix any other instances of the GreatPlains.msi file.

Q6: When I install a service pack, the following error appears: The error code is 2755. What is causing this error?

A6: This error occurs for either of the following reasons.

• The service pack or the hotfix is not physically on the same drive partition as the Microsoft Dynamics GP application folder. For example, the service pack file exists on the C drive and the Microsoft Dynamics GP folder is on the D drive. To resolve this problem, download and then run the service pack file or the hotfix file on the same physical drive as the Microsoft Dynamics GP directory.
• The service pack or the hotfix is installed from a network location. To resolve this problem if the service pack or the hotfix is on a network share, copy this file locally to the workstation, and then install the file.

Q7: When I try to uninstall Microsoft Dynamics GP 9.0, I receive the following error message:
 

How can I resolve this?

A7: When you uninstall the Microsoft Dynamics GP program, the GreatPlains.msi file is accessed. If this file cannot be found, you receive this error message. To resolve this issue, copy the GreatPlains.msi file from the Microsoft Dynamics GP installation CD to the location that is displayed in the error message. The GreatPlains.msi file is located in the Bin folder on the Microsoft Dynamics GP installation CD. After you copy the file, try to uninstall Microsoft Dynamics GP again. In this example, you copy the GreatPlains.msi file to following location:
Q8. When you try to apply a service pack or hotfix for either Microsoft Dynamics GP on a Windows Vista computer, the following error is given:
 
A8: This error message is occuring because of the User Access Control (UAC) in Windows Vista. Use one of the following methods to resolve the issue:

• Run the installation of the service pack or hotfix as an Administrator. To do this, right-click the file, on the shortcut menu, click
  Run As Administrator, and then continue through the isntallation of the service pack or hotfix.
• Disable User Access Control. To do this, follow these steps:
  1. In Control Panel, click Add or remove user accounts.
  2. Click the user account that you are logging into the computer as, and then click Go to the main User Accounts Page.
  3. Click Change security settings, clear the Use User Account Control (UAC) to help protect your computer option, and then click OK.
  4. Restart the computer when you are prompted.
  5. Install by double-clicking the installation file.
  6. As soon as the installation has finished, reset the changes that you made in steps 1-4 to enable UAC.