Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Prescan issues

  Asked By: Dominique    Date: Jun 28    Category: MOSS    Views: 1159

I'm running into some problems with prescan. I ran the prescan /all on the web
front-end server and it completed successfully. After detaching the content
database, and re-attaching it on the MOSS SQL server, I try to use STSADM to add
the content database but it's still indicating that prescan hasn't been run. Am
I missing something?

Share: 

 

11 Answers Found

 
Answer #1    Answered By: Davon Henson     Answered On: Jun 28

IT is my understanding that after you run  the prescan.exe tool on the
content database  you do not have to run the stsadm.exe tool to attach
the content  database. What you can do is extend a portal through
central admin and then when asked to extend a new or existing portal
choose existing portal. Then you point to the content database that
you ran prescan  .exe on. You will need to have attached this database
into SQL server  to point to it. Once you do this sharepoint will know
to upgrade the database and should perform the action of upgrading for
you.
If I am wrong somebody please correct me but this is my
understanding.

 
Answer #2    Answered By: Alisha Itagi     Answered On: Jun 28

If where he is running  stsadm, is a completely different farm, then this
could be why it's detecting that prescan  was never run.

 
Answer #3    Answered By: Judy Pittman     Answered On: Jun 28

The STSADM is on the 2007 farm, yes. My understanding, though, is that the
prescan.exe makes changes to the database  so when I migrate the DB files over to
the new farm, it will know that the scan was run  successfully. Is this true?

 
Answer #4    Answered By: Caleb Gordon     Answered On: Jun 28

I do not believe that it makes changes to the V2 content  databases,
therefore that information would not carry with it. It simply looks for
the prescan  report files, and more than likely writes information to the
V3 configuration database.

 
Answer #5    Answered By: Irving Hurley     Answered On: Jun 28

So, I'm confused. Should I be running  the prescan  from the v3 machine and
targeting the v2 content  database?

 
Answer #6    Answered By: Yvonne Rodriquez     Answered On: Jun 28

I stand corrected on my initial belief (That's why I stated "I believe"
J), that prescan  does in fact update the Content database

 
Answer #7    Answered By: Elisha Abbott     Answered On: Jun 28

prescan.exe only runs against the WSS 2.0 SP2 object model ...you need to
run it (generally) as the very first thing you do to prepare your existing
V2 environment (prior to backing up your V2 databases).

If prescan.exe is not run  or doesn't run successfully, stsadm.exe -o
addcontentdb will complain and won't perform the upgrade.

 
Answer #8    Answered By: Naimish Ranganekar     Answered On: Jun 28

The prescan  utility does update your existing V2 content  databases. It
marks each list as being ready for the upgrade. One outcome of this
change is that every list on the sites you prescan now have a modified
date corresponding to when the scan was run.

You can accomplish a database  migration upgrade through central admin
by creating a new web application. In the settings for your new web
application you can specify what you want the database to be named. If
you enter the name of the content database from V2, it will detect that
the database exists, and perform an in-place upgrade. In order for the
system to not complain about the prescan being run, you need to make
sure that your web application uses the same URL as your V2 top level
site used.

 
Answer #9    Answered By: Caleb Gordon     Answered On: Jun 28

I can confirm that prescan.exe needs to run successfully  (and it does mark
the V2 databases when it does); else when you try to restore and upgrade
with stsadm.exe, stsadm.exe will complain that prescan.exe wasn't run  on the
V2 databases.

 
Answer #10    Answered By: Christie Carlson     Answered On: Jun 28

We successfuly performed a couple content  DB migration but we accomplished
this by running  SQL backup on the content DBs in the V2 farm and then doing
a SQL restore into the V3 farm (vs. detach/attach), then running stsadm.exe
-addcontentdb to add the content DB to an new, empty V3 web application.

Prescan.exe needed to run  successully on the V2 content databases before
running the SQL backup.

 
Answer #11    Answered By: Dorothy Farmer     Answered On: Jun 28

I think I figured out the problem. I was trying to import the content  database
into a web application that already had V3 sites. Once I created a new
application and repeated the process it worked properly. One thing I noticed,
though, is that the custom views I set up on a custom list did not migrate
through. Is this by design?

 
Didn't find what you were looking for? Find more on Prescan issues Or get search suggestion and latest updates.




Tagged: