Share via

Not All CRM Source Media is Created Equal

  • Article

Incommunicado...

One of my partners hit a problem the other day when they tried to add a second, load-balanced CRM server to an existing CRM 3.0 environment. After several days and much hair-loss, they still couldn't get this to work and decided to roll-back to the original, single server environment.

Further investigation revealed that the version number of the orignal CRM server installation was v3.0.5300.0, whereas the version number of the second CRM server installation was v3.0.5300.2. The "BuildVersion" table in the CRM database contains a four columns describing the original installation version:

  • MajorVersion = 3
  • MinorVersion = 0
  • BuildNumber = 5300
  • Revision = 0

In this case, if we changed Revision column value to 2 the second CRM server would spring into life, but the first CRM server would fail. After speaking with our support team, it turns out that we have been releasing RTM version refreshes to MSDN Subscriber Downloads and depending on when you download the .ISO image file, you may have v3.0.5300.0, v3.0.5300.1 or v3.0.5300.2.

You can check which version you have by using Notepad to edit the \sql\2.0\versionstamp.sql file on the CRM Server CD and look for the following lines:

set @buildnumber = 5300
set @MajorVersion = 3
set @MinorVersion = 0
set @Revision = 0

Just to put your mind at rest, the version you buy either as a Full Package Product (FPP) or through one of our Volume Licensing programmes (Open, Select or Enterprise Agreement) will always be v3.0.5300.0. This problem only occured because the partner had used their MSDN media when installing the second server, so the lesson here is to make sure you always use the same media each time.

This posting is provided "AS IS" with no warranties, and confers no rights.

Comments

  • Anonymous
    October 26, 2006
    Pink Bubbles Go Ape... As you have probably read here on the CRM product team blog, a refresh of CRM