Installing MOSS 2007 RTM on a farm running MOSS 2007 Beta2 TR

Tomorrow sometime Microsoft will release Office SharePoint Server 2007 for download at the Microsoft Download Center. Check out this post to find all of the details on downloading. In anticipation of the flood of demand for help on migrating away from TR and onto RTM I have decided to release so updated instructions a little early. Yes, Microsoft will publish the “official” instructions tomorrow I just thought you might appreciate a version with screen shots. And yes step 5 really says to uninstall MOSS. J It will be ok. Of course I never do something like this without doing a backup first. See this link for backup and restore guidance.


Let the fun begin!!!


For Microsoft’s version of this instructions check out Joel’s post.


  1. Note which server is hosting SharePoint Central Administration and confirm that there are no pending or failed backup/restore or upgrade timer jobs.
    1. Go to SharePoint Central Administration
    2. Click the Operations Tab
    3. From Global Configuration click Timer Job Definitions
    4. Delete any failed or pending jobs referencing backup/restore, or upgrade. You may not have any of these but you need to check.
  2. Write down some information about all of your servers in the farm
    1. Make a list of every server that host SharePoint Central Administration. You may skip this step if you have a single server install.
      1. Go to SharePoint Central Administration
      2. Click the Operations Tab
      3. Click Services on server
      4. Now click the Custom radio button
      5. Look to the Central Administration service and see if it is started. If yes then record the server name as hosting Central Admin

      6. Now click Server name above and on the drop down select Change server. Repeat these steps checking each server in your farm.

    2. Make a list of each servers role
      1. Click Start > Run
      2. Type regedit.exe and press OK
      3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\ServerRole and record the value.
      4. Repeat these steps for each server with MOSS installed
    3. Discover if you used a standard or enterprise key
      1. Go to SharePoint Central Administration
      2. Click the Operations Tab
      3. From Upgrade and Migration click Enable Enterprise Features. If you have the screen below then you used the Enterprise key. If you used the Enterprise key then you must use the Enterprise key when you enter the a key while installing the RTM bits. If you don’t have the screen below then you used the Standard key to do your install and you may use either the Standard or Enterprise key when you install the RTM bits.

  3. Backup the 12.0 hive from the registry. Warning: If you are unfamiliar with the registry proceed with caution as you can damage your system. For more information on editing the registry see KB322756.
    1. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0
    2. Right Click on 12.0 and click Export

    3. Provide a filename, choose a safe location for the backup file and click save.
  4. Now edit the registry key by renaming the dsn key
    1. Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB\dsn]
    2. Right click on dsn and click rename

    3. Enter dsn2 and click off the key making the change permanent

    4. Close the registry editor.
  5. Purge the old configuration wizard logs
    1. Open windows explorer
    2. Navigate to c:\program files\common files\Microsoft shared\web server extensions\12\logs
    3. Delete all files that are psc*.log (These are just an example you may have more or less.)

  6. Check to see if you have installed any language packs and uninstall them.
    1. Open Control Panel
    2. Click add/remove programs
    3. If you have any language packs uninstall them at this time.
  7. The next step is to uninstall MOSS Beta2 Technical Refresh. This will uninstall MOSS completely from your machine but will not delete any of your data.
    1. Open Control Panel
    2. Click add/remove programs
    3. Scroll down to Microsoft Office SharePoint Server 2007 (Beta) and click Remove
    4. At the “Are you sure you want to remove Microsoft Office SharePoint Server 2007 (Beta) from your Machine?” message click Yes.
    5. At the warning message asking if you want to uninstall now click Ok.
    6. When the uninstall is complete click Close.
  8. Reboot your server
  9. If you have more than one MOSS server repeat steps 6 – 8 for all servers in the farm. The order does not matter and you can do all of the servers at the same time or individually.
  10. Now that all servers have had MOSS uninstalled from them and have been rebooted you need to install MOSS 2007 RTM. You will perform the following steps on one server at a time. Start with the web front end server that previously hosted Central Admin (noted in step 2a above) and then you may do all additional servers in any order. Perform only on one server at a time. If any server fails resolve the issue before continuing to the next server.
    1. Run setup.exe from the RTM installation folder.
    2. Enter your product key and click continue. Be sure that use the proper key based on your findings from step 2c above.
      1. SharePoint Server Standard Trial: XJMKW-8T7PR-76XT6-RTC8G-VVWCQ
      2. SharePoint Server Enterprise Trial: F2JBW-4PDJC-HKXTJ-YCKRP-T2J9D
    3. Read the Microsoft Software License Terms, check the box beside I accept and click Continue.
    4. At the choose the installation you want click the Advanced button.
    5. At this server type screen you should choose the appropriate option for you. Also, if you would like to use a non-default installation folder then you will need to click the File Location tab and specify the directory of your choice. You recorded the server type in step 2 b above.
    6. De-Select the box for running the Configuration Wizard and click Close.
    7. Now install any necessary language packs on the server. Instructions found here.
  11. Once all servers have been installed return to your original web front end server which will host SharePoint Central Administration.
    1. Click Start > All Programs > Microsoft Office Server > SharePoint Configuration and Technologies Configuration Wizard.
    2. Click Next at the Welcome screen.
    3. At the warning message click Yes.
    4. At the Completing SharePoint screen you should see your database and database server listed. Click Next.
    5. You will see a warning message reminding you to install MOSS on all servers in your farm before proceeding. Ignore this warning message and click Ok

    6. You may notice this message while configuration wizard is running. It is safe to ignore.

    7. At the Configuration Successful screen click Finish.
  12. Now find out what your servers search topology is.
    1. Go to SharePoint Central Administration
    2. Click the Operations Tab
    3. From Topologies and Services click Services on Server
    4. If the Office SharePoint Server Search is stopped go to step 13
    5. If the Office SharePoint Server Search is started from the command line on this server you need to run the command stsadm -o osearch -action start (Make sure you navigate to the 12\bin directory as shown in the screen shot).

                  


  1. Return to the Services on Server page and click Office SharePoint Server Search to go to the settings screen

  2. If the box to the left of Use this server for indexing content is checked your server is a Index server. Now perform the sub steps. If it is not enabled skip to step h.
    1. Click Start > Run
    2. Type regedit.exe and press OK
    3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\{Application GUID} For each key that you find with this pattern do the following
      1. Set the default key to On
      2. Create a new subkey named Gathering Manager
      3. Under Gathering Manager create a DWORD value named UseClustering and set it to 0.
    4. Now open a command prompt.
    5. Run the command net stop osearch
    6. Run the command net start osearch

    7. Run iisreset on every server in your farm.
  3. If the box to the left of Use this server for serving search queries is checked your server is a Query server

  1. Now for the tricky part. If you are on a single server install then you can skip all of this. Perform the following steps only on servers that is either an Index server or a Query server but not both. So if the server had both boxes in step 12 f do not perform these steps. If the server had neither box checked in step 12 f checked do not perform these steps. If the server only had 1 box checked continue.
    1. For every server that only has the Query role
      1. Go to SharePoint Central Administration
      2. Click the Operations Tab
      3. From Topologies and Services click Services on Server
      4. On the Office SharePoint Server Service click stop
      5. Wait for the status to change to Stopped
      6. Repeat these steps for any other server with the Query only role
    2. For every server that has only the Index role
      1. Now open a command prompt.
      2. Run the command net stop osearch
      3. Run the command net start osearch

      4. Wait 5 minutes
    3. Now once all servers are complete you can continue
      1. Go back to each of the servers you stopped in 13 a
      2. Go to SharePoint Central Administration
      3. Click the Operations Tab
      4. From Topologies and Services click Services on Server
      5. Click start on the Office SharePoint Server Search service
      6. Wait on each server to complete initializing before moving to the next
        1. To ensure that the server has initialized navigate to the SSP and click search settings
        2. Check that the propagation status is Idle
  2. More than likely your search scopes are missing. To correct this problem
    1. Open the home page of your portal in your browser
    2. Right click on the search tab and chose Copy Shortcut
    3. Click Site Actions> Site Settings > Modify all site settings
    4. Under Site Collection Administration click Search Settings
    5. Click Use custom scopes and then paste in the URL you copied in step b and click OK.

         

  3. Now that all of SharePoint is upgraded and you have confirmed search is working you need to install the latest release of the Microsoft .NET Framework 3.0 on all servers in your farm.
    1. Open control panel
    2. Click Add or Remove Programs
    3. Find Microsoft .NET Framework 3.0 in the list and click Remove
    4. Install the latest release you just downloaded.

Shane – SharePoint Help


42 thoughts on “Installing MOSS 2007 RTM on a farm running MOSS 2007 Beta2 TR”

  1. You da bomb Shane, thanks for publishing this!

    Also, since I didn’t fill out a smile sheet consider this a 10…really enjoyed you and Mike and the fun you made the class in Denver. Great value exchange.

    Best for the holidays and hope you survive the next few weeks. Enjoy marriage!!

  2. Please write down under which account your services are running and set these back before starting the wizard. The system account does not have priviledges to finished this job. Your wizard will hang at configuration step 8.

  3. I have B2TR installed on the server. I do not have any sites that I needed. Could you please point out any resources to on how I can unstall B2TR and clean install MOSS 2007?

  4. on section 12.2.3….about registry update on “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Applications\{GUID}”, i noticed that joel’s guide (so as the one from technet) used “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\{Application GUID}”…..does it matter?

  5. Tried to upgrade our internal testsite (luckily not our web-presence site!)

    My installation did not comply to the

    Note:  

    The server type of a computer is located in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\ServerRole registry subkey. The values are singleserver for Basic installations, and either WFE (commonly referred to as “Web front end”) or Complete (commonly referred to as “application server”) for Advanced (farm) installations.

    The value of our ServerRole subkey is: APPLICATION

    After 11.3, I get the Connect to a Server Farm Screen.

    Selecting Yes, I want to connect … <Next>

    I get to the Specify Configuration Database Settings – all fields are empty.

    Filling out the Database server field and clicking Retrieve Database Names fills out the Database name and Username correctly.

    After 11.4 the wizard stops at step 2/8.

    The configuration wizard was not able to succeed “could’nt connect to config.db” – though I used same account and pw as in my B2TR-installation – the installation was able to see the database – and I can see the database tables in SQL Server Management Studio runas this account.

    I suspect my upgrade to B2TR maybe is incomplete?

    Best regards

    Erik Bo

  6. Well, I got to step 12 number 6 and my upgrade failed.  The logs state:  This database is from a pre-release version of SharePoint Products and Technologies that cannot be upgraded.

    I thought this doc was to help me upgrade from Beta 2 to RTM?  Has anyone else run across this one?

  7. Thanks Shane!! Seems to have worked like a charm for me. One thing… I did not have .NET Framework 3.0 installed when I was running Beta 2TR. As such, at Step 10, I was forced to install .NET Framework 3.0 before I could proceed with the install of MOSS 2007 RTM. I assume that this means that I can skip your last step since I have already installed the most current version of .NET Framework 3.0?

    Thanks again for the detailed instructions.

  8. I was running WSS Beta 3. Upgraded to new RC Office Sharepoint Services 3.0 and found that it is the crippled copy. No Excel Services.
    I uninstalled and tried new install of MOSS 2007 Trial. Fails with instruction to uninstall previous version Sharepoint. I don’t know what else to uninstall. I’m not concerned with data as this was a sandbox platform.
    Do I need to uninstall all of Office 2007 Beta?

  9. I am getting the following error and it is keeping me from accessing anything including the Central Administrator. I have followed all of the steps and get this everytime when I try to connect to an existing farm. I can create a new farm with no problems.

    The schema version (3.0.146.0) of the database SharePoint_AdminContent_46cdd693-3a02-4b54-9f01-85f40d8e045a on xx-sql\xx_2005_SE_2 is not consistent with the expected database schema version (3.0.149.0) on xxxxx-xxxx. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match.

    Any help on this is appreciated.

    Thanks,
    Eric

  10. Hello Shane,

    I am getting an error whenever I open “<site collection>” -> Site Settings -> Workflows page.

    The error is “Failed to find the XML file at location ’12\Template\Features\IPFSDocumentConversion\feature.xml’. This error is being generated after I had upgraded from Beta2TR to RTM. Is it possible for you to help me?

    Thanks & Regards,

    Kumar

  11. When I am trying to upgrade my Beta 2TR to RTM, I am getting this error.

    “This database is from a pre-release version of SharePoint Products and Technologies that cannot be upgraded.”

    Can anyone help me to fix this.

    Thanks,
    Mubarak

  12. In step 12, I don’t see “Office SharePoint Server Search” in my services… I did an advanced installation of the Enterprise edition as a web front end. Everything’s on a single development machine, but I had to do an advanced install to use my SQL 2000 instead of installing a superfluous 2005 express. Where do I go to enable or assign that service to my

  13. That is because you did the web front end install which does not install the search piece on your server. You need to redo the install and this time choose advanced and then complete. Sorry.

  14. Hi Shane-

    Hi-

    I am not able to open the central admin, everytime I try I receive the below error on the evntvwr – Application Log

    The schema version (3.0.149.0) of the database *** on ****is not consistent with the expected database schema version (3.0.150.0) on ***. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match.

    Is there a solution for this?

    Thanks!!!

  15. Hi there, i am new to sharepoint. I have the same problem as above , i donot have Indexer service running and when i go to Operations-> Services on server there is no Office sharepoint search service. and all the radio buttons on the page are disbled. I have logged in as system account.

    There was a server before running the search service but that server no more exist as it got virus and is disconnected. Please help.

    If i go to application management and check for the services enabled. Office sharepoint search says “Not enabled” as there are no Indexers.

    Please help!!!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>