MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Adding a content DB fails

  Asked By: Angie    Date: Jun 21    Category: MOSS    Views: 1634

I have installed MOSS 2007 and am trying to add a SPS 2003 Database to it.
(I backup it from a SQL Server 2000 box and restored it to the SS 2005

When adding the content DB using the UI, I get "Unknown Error" & using
stsadmin gives the following error:

stsadm -o addcontentdb -url http://SJD-aaaabc:43468 -databasename
-databaseserver SPSDBServer

The pre-upgrade scan tool has not yet been run on this database
e Name=ProcessE1_SITE Parent=SPDatabaseServiceInstance. You must run the
rade scan tool before you can continue with the upgrade process. Run the
tool fr
om the following path: C:\Program Files\Common Files\Microsoft Shared\Web

I had ran the pre-config tool on the other box, where I backed up the
database from.



3 Answers Found

Answer #1    Answered By: Dorothy Farmer     Answered On: Jun 21

Looks to me that you have not run the PRESCAN tool on the MOSS server, which
is going to be necessary if you want to restore that V2 database to this

The MOSS Farm is detecting that prescan was never run on this farm, and is
required before any type of upgrade so that the MOSS farm.

Answer #2    Answered By: Jacklyn Burnett     Answered On: Jun 21

How do I run the PRESCAN on the moss  server. When I execute prescan there, I
get this error:

PRESCAN.EXE /all http://mossserver:43468
This program requires Windows SharePoint Services v2.

and I never installed  2003 on the target server. It was a straight 2007
install. I did ran the Prescan on the source 2003 box though, but I would
doubt that doing a backup and restore to the target would carry the prescan

Again, these are 2 different servers and I am using the DB migration to do
the upgrade.

Answer #3    Answered By: Breann Beach     Answered On: Jun 21

This could be something specific to a content  database with a Portal site
collection in it.

But I don't have a definitive answer for you on it. Perhaps someone else on
the list can confirm/deny that for the Portal site collection, you "have" to
rely on a sidebyside migration.

Otherwise, what I would recommend, is if there are team sites in that
database, place them into a different content database, then move it to your
MOSS server, and for the Portal site collection itself, looks like you're
going to need to rely on a side by side for it

You could then move that upgraded database to your Pure MOSS 2007.

Didn't find what you were looking for? Find more on Adding a content DB fails Or get search suggestion and latest updates.