SBS 2008 migration

Small Business Server migration from 2003 to 2008

Recent attempt to do a migration from SBS 2003 to SBS 2008 shows that official guide from Microsoft is not enough.

Below are some issues that came up during migration and how they were solved.

Issue #1
SBS 2008 wasn’t able to connect to source server during installation in migration mode.
Everything looked like it’s not using the right NIC, however after connecting cable to another NIC we started getting an error message saying that source server is not ready for migration.

It appeared that NICs were not enabled at all, so the solution is to press Shift+F10.
This gives a command promt. Type control to open Control Panel and adjust networks settings there, enable NIC. Installation continues after with no issues.

Issue #2
The next issue we had to deal with is an error message during Public folder migration, saying “The token supplied to the function is invalid 80090308

The solution is to remove SSL certificate from IIS:

  • Click Start, point to Programs, click Administrative Tools, and then click Internet Services Manager.
  • Click your server, and then expand the Web site that contains the Exadmin virtual root (the default Web site is “Default Web Site”).
  • Right-click Exadmin, and then click Properties.
  • Click the Directory Security tab.
  • Under Secure Communications, click Edit.
  • Click to clear the “Require secure channel (SSL)” check box. If
  • “Require 128-bit encryption” is shaded, click to select “Require secure
  • channel (SSL)”, click to clear “Require 128-bit encryption”, and then click
  • to clear the “Require secure channel (SSL)” check box again.
  • Click OK two times.
  • Restart Exchange System Manager.”

Issue #3
“Microsoft.SharePoint.SPException: User cannot be found” when trying to change Site Collection administrator for Oldcompanyweb.

The reason for this error is wrong user ID for Site Owner. To fix the error, go through dbo.Webs and dbo.Sites tables in SQL Management Studio and replace user IDs to correct Administrator IS from dbo.UserInfo table.

Issue #4
stsadm import and export command that Microsoft recommends to use for moving data from oldcompanyweb to companyweb doesn’t overwrite contents of companyweb.

Therefore at least there will be a greeting message from SBS server on the home page after importing content into companyweb as well as dates and owners of pages will be replaced.

We’ve user stsadm backup and restore commands with overwrite option which worked fine:
Stsadm -o backup -url http://oldcompanyweb -filename c:oldcompanyweb.bak
Stsadm -o restore -url http://companyweb -filename c:oldcompanyweb.bak -overwrite

Issue #5
Companyweb and SharePoint Central Admin not accessible after installing updates.

It took longer to find the solution than to fix the issue itself:

  • Open the Services snap-in and Restart the Windows Internal Database service.
  • Run the following command from an elevated command prompt (if the command fails, note the error and run the command again, in some occasions due to some timing considerations, it might have to be run multiple times before it works, we would suggest trying it 2 or 3 times):
    C:Program FilesCommon FilesMicrosoft SharedWeb server extensions12BINpsconfig -cmd upgrade -inplace b2b -wait -force
  • The command may take a long time to run. If it completes successfully, SharePoint Central Admin and Companyweb should work (confirm IIS services are running, bindings are correct, etc.)
  • After the psconfig completes, check the following:
  • If SharePoint Central Admin works but Companyweb does not, check the bindings for the web site in IIS, we’ve seen some cases where they are missing.

Issue #6
If you decide to install KB934525 patch, make sure you do post installation tasks. For some reason this wasn’t mentioned in the documentation for this patch:

Post-installation information

After you apply this hotfix package, you must run the SharePoint Products and Technologies Configuration Wizard.

To do this, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.

Important Because of a problem with the hotfix installation, you must not run the SharePoint Products and Technologies Configuration Wizard to complete the installation if you are running a Windows SharePoint Services stand-alone installation that uses the Windows Internal Database Engine. Instead, you must use the Psconfig.exe command-line utility. To do this, follow these steps:
Click Start, click Run, type cmd in the Open box, and then click OK.
Change to the following directory:
system driveProgram FilesCommon FilesMicrosoft SharedWeb Server Extensions12Bin
Run the following command:
psconfig -cmd upgrade -inplace b2b
If you ran the SharePoint Products and Technologies Configuration Wizard, you may experience a long delay, and the wizard may not be completed successfully.

Alternatively, the configuration process may be unsuccessful, and you may receive the following error messages:
Configuration Failed
An exception of type System.Data.SQLClient.SQLException was thrown. Additional exception information access to module dbo.proc_MSS_GetConfigurationProperty is blocked because the signature is not valid.

Additionally, the following event may be logged in the Application log:

Event ID: 5586
Source: Windows SharePoint Services 3
Unknown SQL Exception 33002 occured.
Additional error information from SQL Server is included below.
Access to module dbo.proc_MSS_GetConfigurationProperty is blocked because the signature is not valid.

If you experience these issues, use the Psconfig.exe command to manually complete the installation of the hotfix.

Somehow, more than half of issues are related to Sharepoint. That’s probably just a coincidence, however 🙂