Hi Folks,

              * I had migrated SP 2007 to SP 2010 with out using PreScan.exe and every thing had gone Smoothly like slicing mango with sharp knife .

              * Now i have task to Migrate SP 2003 to SP 2010 and I am able to migrate from SP 2003 to SP 2010 via SP 2007 ,But loosing all my site content .Here firstly when i migrated  SP 2003 to SP 2007 it is showing me as I have 1 site but when I c the site there is nothing data existed

              * I came to knew i.e I need to run PreScan.Exe when I run the Prescan.exe it is showing me info as below image .Can any one tell me what should I do to solve the issue shown below as  Prescan.exe :Requires Windows SharePoint Service v2

                  

Hi Siddiqali,

in WSS3 and SP2007 you would want to use stsadm -o preupgradecheck

The preupgradecheck operation calls the core execution engine and runs detection routines. The preupgradecheck operation runs in default mode without any parameters, will detect each rule file in the rule file directory (that is, "%commonserverfiles%/Microsoft Shared/web server extenstions/12/config/preupgradecheck"), and then execute each of them sequentially. A subset of rules files can be specified using the localonly parameter.

Reference http://technet.microsoft.com/en-us/library/dd793605(v=office.12)

-Ivan

Hi Ivan,

            Thanks for your response,Sorry to late reply as here Saturday and Sunday.If possible provide me stsadm to run prescan.exe with example .Hope you reply me

       

Hi Siddiqali,

I did you run will create from the BIN folder or if you have added the path C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN to your environment variables path you can run stsadm and psconfig fropm any dos prompt..

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN\stsadm -o preupgradecheck will create and HTML report for you with a lot of information about each webapp, sitecollection, feature etc...

-Ivan

HI Ivan,

            Thanks for you reply.I request you to tell me how can i use  your mention commanf "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN\stsadm -o preupgradecheck" for single web application ,I have used the command and got the below issues.Hope you reply me

   

 

Hi,

A better way to look at the results is by using the HTML output and the log files to give you the results you are looming for. As rules are processed during the pre-upgrade scanning, the results from each rule are written to an XML log file and a text log file. These log files are written to the %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS directory and use the following naming convention, where a random number is used to differentiate between possible simultaneous attempts to run the pre-upgrade command:

• PreUpgradeCheck_YYYYMMDD-hhmmss-millisecond-random-number.XML

• PreUpgradeCheck_YYYYMMDD-hhmmss-millisecond-random-number.LOG

Both of the preceding log files contain the following information:

• The checks that were run.

• The issues that were found.

• A description of how to fix the detected issue or a link to a KB article that pertains to the issue.

After the scan is finished, the XML results are transformed to HTML format that can be viewed as a page in the default Web browser. The file-naming convention for the transformed XML is PreUpgradeCheck_YYYYMMDD-hhmmss-millisecond-random-number.HTM. The result of this conversion is an HTML page that you can view in your Web browser.

I havent tried to only perform the check on a single webapp. However, you should run PreScan.Exe in your SP2003 environment prior to upgrade, I believe running prescan was a prerequisite anyway?

-Ivan

... like slicing mango with sharp knife .

Slicing mango's with a sharp knife goes smoothly, until you hit the kernel that's hiding inside ;-)