Error upgrading CRM3.0 -> CRM4.0

All replies

• 

  

  0

  Sign in to vote

  Hi,

   

  Does your testing server and live server on the same domain? If so, it can't be used the same configuration file.

  You need to change the <Organization> tag, because the installation will look for the database which indicated by the Active Directory organizational name

   

  Regards,

  Jim

  Thursday, January 24, 2008 3:20 PM

  Moderator
• 

  

  0

  Sign in to vote

  Probably you allready tried an installation of Microsoft CRM 4.0 The installation created the database MSCRM_CONFIG.

  You should delete this database in SQL DataManagment studio. If you allready deleted this database in SQL Managment studio , you should also delete or move those two files :

  D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSCRM_CONFIG.mdf

  D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSCRM_CONFIG_log.ldf

   

  Regards

  Tomaz

  Thursday, January 24, 2008 5:04 PM
• 

  

  0

  Sign in to vote

   It means already exists, if you

   

  I'm thinking that where you are deploying to a web farm with a shared SQL database. you need to create the database first, and then deploy each of the CRM (web) servers with a <Database create="false" update="true/> option.

   

  for that you use some command line tools

   

  http://blogs.msdn.com/crm/archive/2008/01/18/multi-tenancy-in-crm-4.aspx

  Install Microsoft Dynamics CRM Server

  The following command will install Microsoft Dynamics CRM Server:

   

  SetupServer.exe [/Q] [/InstallAlways] [/L [drive:][[path] logfilename.log]] [/config [drive:] [[path] configfilename.xml]]

   

  SetupServer.exe for Microsoft Dynamics CRM Server is located in the root of the Microsoft Dynamics CRM Server installation disk or download-files location.

  Parameters

  None

  Used without parameters, Setup will install with all display screens.

   

  /Q

  Quiet mode installation. This parameter requires a configuration file in XML format. The /config parameter contains the name of the XML configuration file. No dialog boxes or error messages will appear on the display screen. To capture error message information, include the log file parameter (/L).

  /InstallAlways

  This parameter forces Setup to ignore the installation state and operate in install mode. When you use this parameter, Setup will try to install on a server where Microsoft Dynamics CRM is already installed.

  /QR

  Requires a configuration file in XML format specified by the /config parameter. Displays installation progress bars and all error messages.

  /L [drive:][[path] logfilename.log]]

  Creates a log file of installation activity. You can specify the file name of the log file and where to put it. If you do not specify a name or location, a log file will be created in the Drive:\Documents and Settings\\UserName\Application Data\Microsoft\MSCRM\Logs folder, where UserName is the account name of the user running Setup. The following options are available:

  /LV  Log verbose.

  /L*   Log all information except verbose.

  /L*V Log all information including verbose.

  /config [drive:] [[path] configfilename.xml]]

  The /config parameter uses the specified XML configuration file to provide Setup with the additional information to complete installation successfully. An example XML configuration file is discussed in the following section.

   

  Best Regards,

  Imran

   

  http://microsoftcrm3.blogspot.com

   

   

   

  Thursday, January 24, 2008 5:05 PM

  Moderator
• 

  

  0

  Sign in to vote

  Tomaž Vodušek wrote:

  Probably you allready tried an installation of Microsoft CRM 4.0 The installation created the database MSCRM_CONFIG. You should delete this database in SQL DataManagment studio. If you allready deleted this database in SQL Managment studio , you should also delete or move those two files : D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSCRM_CONFIG.mdf D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSCRM_CONFIG_log.ldf   Regards Tomaz

   

   

  This was the correct solution for me. I had done one upgrade attempt, but without using the command-line tool/xml configuration. I did detach the database before the upgrade attempt, but it still finds the MSCRM_CONFIG files if they're in the same directory. So I just moved them(hate deleting stuff untill I'm 110% sure), and the upgrade was successfull. CRM 4.0 is up and running

   

  Using the command-line tool and the xml configuration file is really the way to do this. Thanks for taking time to help me out guys, I really appreciate that. I was really stuck/blind, but the answer came pretty quick after posting it.

   

  Thanks guys for all your help.

  Frode Magnussen

  Friday, January 25, 2008 3:12 PM