Answered by:
Microsoft Dynamics CRM 4.0 Setup Updates.

Question
-
-- Poor english below:Hi, I have an issue with the Setup Updates when installing Microsoft Dynamics CRM 4.0Windows Server 2003 R2 on Microsoft Virtual Server 2005 RC2. English OS.Installing Microsoft Dynamics CRM 4.0 i386 from MSDN ISOs.Tested both English and French versions.I don't want to have Internet access on that virtual server so I downloaded the Setup Updates from the Microsoft download site. (I need to provide a package that doesn't rely on MS download site...)I renamed the setup updates package for "server_i386_patchupdate16092008.msp"Created config_patch_update.xml that looks like:<CRMSetup><Server><Patch update="true">server_i386_patchupdate16092008.msp</Patch></Server></CRMSetup>Then I launch the Installation Wizard with this command:setupserver.exe /config config_patch_update.xmlAnd this is the error I get all the time:13:36:23| Info| === Setup bootstrap logging started 2008-09-16 13:36:23 ===13:36:23| Info| Bootstrap version: 4.0.7333.3.13:36:23| Info| User: Administrator.13:36:23| Info| Invoked with command line: setupserver.exe /config config_patch_update.xml13:36:23| Info| Running C:\Installation\Microsoft\CRM\4.0\server\i386\setupserver.exe13:36:23| Info| Loading bootstrap library C:\Installation\Microsoft\CRM\4.0\server\i386\ServerSetup.dll13:36:23| Info| Microsoft Dynamics CRM is not currently installed.13:36:23| Info| Closing bootstrap library C:\Installation\Microsoft\CRM\4.0\server\i386\ServerSetup.dll13:36:23| Info| Beginning to parse configuration file 'C:\Installation\Microsoft\CRM\4.0\server\i386\config_patch_update.xml'13:36:23| Info| Found product element: server13:36:23| Info| Found patch element13:36:23| Info| Update=true13:36:23| Info| Patch File Location override: server_i386_patchupdate16092008.msp13:36:23| Info| End of patch element13:36:35| Info| Patchfile target Product code: {8DD75D83-D4A1-43AE-80C4-28480F69E419}13:36:35| Info| Patchfile target version: 4.0.7333.11313:36:35| Info| Patchfile target language: 103613:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {E43FF076-9593-40C9-8238-7AF0E2D74F69}13:36:35| Info| Patchfile target version: 4.0.7333.11313:36:35| Info| Patchfile target language: 104313:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {BC8DD950-8100-42F4-9EA9-26FCD41690AF}13:36:35| Info| Patchfile target version: 4.0.7333.313:36:35| Info| Patchfile target language: 103313:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {57C27990-DD20-4838-9437-7F3A1365D519}13:36:35| Info| Patchfile target version: 4.0.7333.11313:36:35| Info| Patchfile target language: 308213:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {E6EB47D7-FCE5-46D0-AFB3-3F8EB4D6B938}13:36:35| Info| Patchfile target version: 4.0.7333.13113:36:35| Info| Patchfile target language: 205213:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {86FB9CBA-51B4-441C-AA76-4DC3C18E3FF7}13:36:35| Info| Patchfile target version: 4.0.7333.12713:36:35| Info| Patchfile target language: 103013:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {1CC98634-EEAE-4C41-85DF-DA5008CBC079}13:36:35| Info| Patchfile target version: 4.0.7333.14513:36:35| Info| Patchfile target language: 104013:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {3173A4EF-2C61-4739-BB6C-3952376C1724}13:36:35| Info| Patchfile target version: 4.0.7333.12713:36:35| Info| Patchfile target language: 103513:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {8795A8F1-61F1-419C-B3E6-86012F4C3009}13:36:35| Info| Patchfile target version: 4.0.7333.14513:36:35| Info| Patchfile target language: 105313:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {9FEE72CD-F3E9-44BB-A16B-2811E4A75414}13:36:35| Info| Patchfile target version: 4.0.7333.11313:36:35| Info| Patchfile target language: 103113:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {DA6CC5FC-1A49-4E46-BB45-81E71F9A9390}13:36:35| Info| Patchfile target version: 4.0.7333.13813:36:35| Info| Patchfile target language: 104113:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {9489E48A-7E07-4057-8E7F-F48FFA9DAA7E}13:36:35| Info| Patchfile target version: 4.0.7333.14913:36:35| Info| Patchfile target language: 104613:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {EE872419-A88F-4FBA-AD6C-AE8C9C0B56B1}13:36:35| Info| Patchfile target version: 4.0.7333.16213:36:35| Info| Patchfile target language: 102913:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {C9E828D4-C025-4DFD-8CE2-477FFAB10664}13:36:35| Info| Patchfile target version: 4.0.7333.17213:36:35| Info| Patchfile target language: 103813:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {B60FC945-151F-4633-90E9-DDF4F4440D10}13:36:35| Info| Patchfile target version: 4.0.7333.16013:36:35| Info| Patchfile target language: 104513:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {0B41D9B2-0285-42E6-884B-079ACAF702F7}13:36:35| Info| Patchfile target version: 4.0.7333.15213:36:35| Info| Patchfile target language: 104913:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {8A50C6B4-F97B-4BEC-9329-D52D85CC8E19}13:36:35| Info| Patchfile target version: 4.0.7333.17613:36:35| Info| Patchfile target language: 103713:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {8B3DBB7E-4D40-4AE1-93FD-962FEA039096}13:36:35| Info| Patchfile target version: 4.0.7333.18013:36:35| Info| Patchfile target language: 103213:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {129C62EB-4939-483D-A5FF-6A781E8F1BF7}13:36:35| Info| Patchfile target version: 4.0.7333.15113:36:35| Info| Patchfile target language: 104413:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {A7D62638-DF9E-4B60-ACB8-6E79ADC0F0B1}13:36:35| Info| Patchfile target version: 4.0.7333.15113:36:35| Info| Patchfile target language: 207013:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {34CE1A6E-1DA6-497F-83AE-6407C6627B21}13:36:35| Info| Patchfile target version: 4.0.7333.16213:36:35| Info| Patchfile target language: 105513:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {48A86E9C-5CC9-41CA-9AAA-B016C05B87FD}13:36:35| Info| Patchfile target version: 4.0.7333.16913:36:35| Info| Patchfile target language: 102813:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {27B3C9D0-5B5B-47FB-9F48-470EAD315B9D}13:36:35| Info| Patchfile target version: 4.0.7333.17613:36:35| Info| Patchfile target language: 307613:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {E491353F-FAEC-4C03-8955-E0311EB4D9BD}13:36:35| Info| Patchfile target version: 4.0.7333.17613:36:35| Info| Patchfile target language: 104213:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:35| Info| Patchfile target Product code: {93561220-1B10-48F9-9C38-73F91B74CE6F}13:36:35| Info| Patchfile target version: 4.0.7333.17613:36:35| Info| Patchfile target language: 102513:36:35| Info| Patchfile target upgrade code: {20EA1269-CD24-459C-B8D7-E227D70386D9}13:36:37| Info| Patchfile passed validation checks.13:37:27| Info| Copying installer files to local directory:13:37:27| Info| Package: C:\Installation\Microsoft\CRM\4.0\server\i386\Server.msi, Options: ADDLOCAL="Installer" INSTALLDIR="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSCRM_{2ACA7B0F-613C-4A47-A7EC-EE34283C5881}" TARGETDIR="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSCRM_{2ACA7B0F-613C-4A47-A7EC-EE34283C5881}" ALLOWRUN=1 PATCH="server_i386_patchupdate16092008.msp"13:37:39| Error| Error 1635 reported by MsiInstallProduct13:37:39| Error| Setup cannot proceed because an error occured while copying installer files to the local system: Impossible d'ouvrir ce package correctif. Vérifiez que le package correctif existe et que vous pouvez y accéder, ou contactez le revendeur de l'application afin de vérifier que c'est un package correctif Windows Installer valide. (setup.cpp:CCrmSetup::CopyInstallerFiles:385).13:38:11| Error| Setup cannot proceed because an error occured while copying installer files to the local system: Impossible d'ouvrir ce package correctif. Vérifiez que le package correctif existe et que vous pouvez y accéder, ou contactez le revendeur de l'application afin de vérifier que c'est un package correctif Windows Installer valide. , Error, OK13:38:11| Info| InputResult: OK13:38:12| Info| Copying installer files to local directory:13:38:12| Info| Package: C:\Installation\Microsoft\CRM\4.0\server\i386\Server.msi, Options: ADDLOCAL="Installer" INSTALLDIR="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSCRM_{B1264369-C085-4A16-A4F2-4BEF169BA716}" TARGETDIR="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSCRM_{B1264369-C085-4A16-A4F2-4BEF169BA716}" ALLOWRUN=1 PATCH="server_i386_patchupdate16092008.msp"13:38:24| Error| Error 1635 reported by MsiInstallProduct13:38:24| Error| Setup cannot proceed because an error occured while copying installer files to the local system: Impossible d'ouvrir ce package correctif. Vérifiez que le package correctif existe et que vous pouvez y accéder, ou contactez le revendeur de l'application afin de vérifier que c'est un package correctif Windows Installer valide. (setup.cpp:CCrmSetup::CopyInstallerFiles:385).13:38:27| Error| Setup cannot proceed because an error occured while copying installer files to the local system: Impossible d'ouvrir ce package correctif. Vérifiez que le package correctif existe et que vous pouvez y accéder, ou contactez le revendeur de l'application afin de vérifier que c'est un package correctif Windows Installer valide. , Error, OK13:38:27| Info| InputResult: OK13:38:29| Info| Do you really want to cancel out of Setup?, Question, Yes|No13:38:29| Info| InputResult: Yes13:38:29| Info| === Setup bootstrap logging ended 2008-09-16 13:38:29 ==="Impossible d'ouvrir ce package correctif. Vérifiez que le package correctif existe et que vous pouvez y accéder, ou contactez le revendeur de l'application afin de vérifier que c'est un package correctif Windows Installer valide" That means something like: Impossible to open the update package. Verify that the update package exists and that you can access it, or contact the application provider to get a valid Windows Installer update package.I have the exact same issue installing it in English.Any ideas would be great!Maxime FortierTuesday, September 30, 2008 3:42 PM
Answers
-
To anyone else coming across this issue, the solution is to specify the full path to the update (msp) file in the configuration xml.
Good luck to everyone!
Eran- Marked as answer by MaximeFortier Friday, June 19, 2009 5:18 PM
Wednesday, June 3, 2009 6:30 AM
All replies
-
Hi,
It's a little difficult to understand your setup. But i will provide an input assuming that you are trying to setup a new CRM server with update without a net connection. By looking at the error i feel that the issue here is when the CRM setup tries to copy the files the setup dont have accuss to your directroy. So first thing make sure that u run the setup with a domain admin account.
Following contains a sample scrip file that i created to install. Hope this will help you. I have explained the important options
<CRMSetup>
<Server><Patch update="true">C:\server_i386.msp</Patch> (This is where u define the update. Make sure ur setup acc have write permisions to this directory)<LicenseKey>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</LicenseKey><SqlServer>LocalHost</SqlServer><Database create="true" /><Reporting URL="http://CRMV4:808/ReportServer" /><OrganizationCollation>Latin1_General_CI_AI</OrganizationCollation><basecurrency isocurrencycode="USD" currencyname="US Dollar" currencysymbol="$" /><Organization>FGH</Organization><OrganizationUniqueName>FGH</OrganizationUniqueName><OU>OU=CRMSystemUsers,DC=FGH,DC=com</OU> (This is the AD OU where the setup creates the user groups)<WebsiteUrl create="true" /><InstallDir>c:\Program Files\Microsoft CRM</InstallDir> (Install dir, the setup should have rights to this too)<CrmServiceAccount type="NetworkService"> (service account for the CRM services)<ServiceAccountLogin /><ServiceAccountPassword /></CrmServiceAccount><SQM optin="false" /><Email><IncomingExchangeServer name="localhost" /></Email></Server></CRMSetup>Let us know this helps
Thanks
samapthperera
- Proposed as answer by Juan Solares Thursday, June 4, 2009 6:39 PM
Friday, October 17, 2008 7:08 AM -
Thanks for your reply!"you are trying to setup a new CRM server with update without a net connection"
- This is exactly what I am trying to do.
"Make sure that u run the setup with a domain admin account."
- I ran setup with a DA Account
Monday, October 20, 2008 3:27 PM -
To anyone else coming across this issue, the solution is to specify the full path to the update (msp) file in the configuration xml.
Good luck to everyone!
Eran- Marked as answer by MaximeFortier Friday, June 19, 2009 5:18 PM
Wednesday, June 3, 2009 6:30 AM -
Hi,
So strange... i was having this type of error when running crm setup after updating the setup files:
13:38:12| Info| Copying installer files to local directory:13:38:12| Info| Package: C:\Installation\Microsoft\CRM\4.0\server\i386\Server.msi, Options: ADDLOCAL="Installer" INSTALLDIR="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSCRM_{B1264369-C085-4A16-A4F2-4BEF169BA716}" TARGETDIR="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSCRM_{B1264369-C085-4A16-A4F2-4BEF169BA716}" ALLOWRUN=1 PATCH="server_i386_patchupdate16092008.msp"13:38:24| Error| Error 1635 reported by MsiInstallProduct13:38:24| Error| Setup cannot proceed because an error occured while copying installer files to the local system
I then closed the installer, and run it again and it worked this time. Just amazing. :)
Regards,
Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.comWednesday, July 21, 2010 9:21 PM