MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

My MOSS 2007 Upgrade Story & Solution

  Asked By: Parvesh    Date: Apr 30    Category: MOSS    Views: 2284

I've been posting messages left and right as I sort through the upgrade
process. The bottom line is that it's not be fun, or in any manner

After opening a ticket with Microsoft and then telling them I want our
money back, an interesting solution to my dozen or so failed attempts to
upgrade SPS 2003 to MOSS 2007.

The primary error I was seeing was:

"System.Data.SqlClient.SqlException: Violation of UNIQUE KEY constraint
'IX_DataServicePropMap_ServerIDPropName'. Cannot insert duplicate key in
object 'dbo.DataServicePropMap'. The statement has been terminated."

Both the In-Place upgrade and the Gradual Upgrade would fail, and the
PreScan would not show any errors!

It turns out that a custom field was inserted in the PROFILE DB by
either an aftermarket template pack OR an over zealous admin attempting
to get LDAP to work with SPS 2003.

The solution, and keep in mind I'm a MOSS 2007 Noob, was to install MOSS
2007 without upgrading, then create a new SSP, then add an additional
web application, delete the associated database for the new web
application, and insert the SITEDB for SPS 2003 site using STSADM.EXE
(which upgrades things on the fly).

a. Install the MOSS2007 on the same server are your SPS2003
1. Options: Do not Upgrade at this time, but use Server
Type as Complete

b. When the installation of binaries completes uncheck the option
"Run the Configuration Wizard"

c. Run the Prescan.exe program from the command-line:
1. CD C:\Program Files\Common files\Microsoft Shared\web
server extensions\12\bin
2. Type "prescan /c preupgradescanconfig.xml /all"

d. Checking the Prescan Log and search for the word "Error"

e. Run the Configuration Wizard

f. Create a New Farm
1. (This essentially means "create new Config DB")

g. After creating a New Farm Successfully > Browse to the Central
admin Page.

h. Central Administration > Operations > Services on Server > Start
the "Office SharePoint Server Search"
1. Configure all the Parameters

i. Browse to the "Shared Services Administrator" Link in the Quick

j. Create a new SSP (Use a new Web Application to host the SSP site
and also the MySite."

k. Once the above two procedures are complete, browse to the
SharePoint Central Administration > Application management > Create
a New Web Application.
1. Create this Web Application with a Dummy Database.

l. Browse to the SharePoint Central Administration > Application
management > Content Database and Delete the Database from the newly
created Web Application.

m. Browse to the SharePoint Central administrator (SPS2003).
1. Delete the SharePoint from the Portal Site (without
Deleting the Content DB's)

n. After the SharePoint has been removed from the SharePoint 2003
1. open a command prompt and change the directory to
c:\program files\common files\Microsoft shared\web server
2. Run the command "Stsadm -o addcontentdb -url http://<New
Web Application URL> -databasename <_SiteDB Name of the SPS2003>

o. Perform an IISreset and browse to the site associtated with the
additional web application you created (i.e. <server name>:12345) and
check if it works ok.

Of course, you'll need to uninstall SPS 2003, and then move your web app
for the upgraded SITEDB to port 80...



No Answers Found. Be the First, To Post Answer.

Didn't find what you were looking for? Find more on My MOSS 2007 Upgrade Story & Solution Or get search suggestion and latest updates.