SharePoint 2007: The Definitive Guide

Common Issues

This section reviews some of the common issues that come up while upgrading.

Known Issues for Preupgrade Scanning

We'll start with the known issues for preupgrade scanning.

Upgrade is blocked if you use "localhost" as your server name

Using "localhost" as your server name can cause many issues in your environment and is not recommended. If you are using "localhost" as your server name, when you run the preupgrade scan tool, this issue is logged and the upgrade cannot proceed. You must rename the server computer and then run an operation in prescan before you continue with the upgrade. Follow these steps to rename your server and fix the issue for the preupgrade scan tool:

1. Back up the configuration database.

2. From the command line, change to the following path: %windir%\Program Files\ Common Files\Microsoft Shared\Web Server Extensions\12\bin. Then run the following command to change the server name in the configuration database:

   	stsadm.exe -o setconfigdb -databaseserver <Server Name> -connect
   

   Warning

   If you are using the database migration path to upgrade, this operation will not resolve the issue, because you are upgrading to a different configuration database. Instead, you must use a script to fix this issue in the content databases directly.

From the command line, change to the following path: %windir%\Program Files\ Common Files\Microsoft Shared\Web Server Extensions\12\bin. Then run the following command to clear the issue for the preupgrade scan tool:

 Prescan /fixlocalhost ...