Sign in
 
HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery
TechCenter >
> 
> 
Prescan.exe on SPS 2003 not running

Answered Prescan.exe on SPS 2003 not running

  • Tuesday, January 19, 2010 1:42 PM
     
     
    Sign In to Vote
    0
    Hi all,

    when we run the Prescan on my SPS 2003 ( SPack 3) i get an error where the prescan doesnt run. when i check the upgradelog file, i get the below mentioned error message

    01/19/2010 17:52:33 Error: You cannot use Local System or Local Service as the application pool identity for Windows SharePoint Services. Please change the application pool identity on virtual server http://abc:153.

    Kindly post your comments and suggestions as to what should i do so that the prescan runs on the server.

    Thanks

    Nez
    • Edited by Mike Walsh FIN Tuesday, January 19, 2010 1:45 PM SPS 2003 added to Title
    •  
     

All Replies

  • Tuesday, January 19, 2010 2:18 PM
     
     
    Sign In to Vote
    0
    Hi there,

    You will need to change the identity to a domain user account instead of using local service / system accounts concerning the application pool for http://abc:153 in IIS

    1: Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
    2: Click the plus sign next to your server name.
    3: Click the plus sign next to Web Sites.
    4: Right-click the website relevant to http://abc153, and then click Properties.
    5: Click the Home Directory tab.
    6: Make a note of the application pool name in the Application pool box, and then click Cancel.
    7: Click the plus sign next to Application Pools.
    8: Right-click the application pool that needs to be updated, and then click Properties.
    9: In the "Application Pool ID" Properties dialog box, click the Identity tab.
    10: Under Application pool identity, verify that Configurable is selected, and then in the User name box, type the new account to use.
    11: In the Password box, type the password for the new account, and then click OK.
    12: After you have reset the application pool identity, you must restart IIS. To restart IIS, run iisreset on the command line.

    There's more information on this here:
    http://support.microsoft.com/kb/837813

    Hope this helps

    Cheers

    Geoff
     
  • Tuesday, January 19, 2010 3:03 PM
     
     
    Sign In to Vote
    0
    Hi Goeff, Thanks for the reply, even i was thinking of doing the same, but as the site is up and running i feared whether chaging the App Pool identity username might affect the site. I just wanted to know what rights and permissions the domain user should have which will be added in the app pool identity. Thanks Nez
     
  • Tuesday, January 19, 2010 6:31 PM
     
     
    Sign In to Vote
    0
    Hi,

    The user account for the application pool must have the standard rights in order to run an application pool, and must have rights to read and write to the SQL Server databases for the portal.

    The following rights are required for the application pool identity:

    Must be a member of the IIS_WPG, SPS_WPG, and STS_WPG groups on the web server. Must be a Db_owner on these databases; portal site _SITE database, _SERV database, _PROF database, and for the configuration database (by default, this is SPS01_Config_db)

    Suggest you also read this:
    http://support.microsoft.com/kb/832770

    Hope this answers

    Cheers

    Geoff
     
  • Wednesday, January 20, 2010 1:43 PM
     
     
    Sign In to Vote
    0
    Hi Geoff,

    I did as you recomemmended, but again the prescan din start. the log file threw this error.

    01/20/2010 18:12:35 Error: Cannot determine server status for virtual server: http://abc
    01/20/2010 18:12:35 Microsoft.SharePoint.SPException: The virtual server that is referenced here is not in the config database. ---> System.Runtime.InteropServices.COMException (0x81070552): The virtual server that is referenced here is not in the config database.
       at Microsoft.SharePoint.Library.SPRequestInternalClass.GetVirtualServerProperty(Int32 lIISInstanceID, Boolean bInXMLFormat, String bstrName, String& pbstrValue, Int64& plVersion)
       at Microsoft.SharePoint.Library.a.a(Int32 A_0, Boolean A_1, String A_2, String& A_3, Int64& A_4)

    Please suggest.

    Thanks
    Anis
     
  • Wednesday, January 20, 2010 2:03 PM
     
     Answered
    Sign In to Vote
    0
    Hi,

    Check that the virtual server is extended:
    1. Start SharePoint Portal Server Central Administration.
    2. On the SharePoint Portal Server Central Administration page, in the Portal Site and Virtual Server Configuration area, click Extend an existing virtual server from the Virtual Server List page .
    3. On the Virtual Server List page, in the list of virtual servers, verify that Extend appears next to the name of the virtual server that you unextended
    More information is given in this article:
    http://support.microsoft.com/kb/827850

    Then check KB hotfixes http://support.microsoft.com/default.aspx?scid=KB;%5bLN%5d;918742 and http://support.microsoft.com/kb/918744 will help you identify and remove orphaned objects.  Ensure you can get to (http://abc) from the web front-end server prior to running PRESCAN.  If the portal does not render from the web front-end, check the host header entries in IIS for abc and make sure it exists in addition to a mapping in the servers hosts table.

    Cheers

    Geoff
     
  • Thursday, January 21, 2010 6:48 AM
     
     
    Sign In to Vote
    0
    Hi geoff, I went to the central admin and check. there infront of the web server its showing upgrade insted of extend. Does it needs to be upgraded?? Nez
     
  • Thursday, January 21, 2010 7:11 AM
     
     
    Sign In to Vote
    0
    Hi,

    There is a hotfix that addresses this issue here:

    http://support.microsoft.com/kb/907308

    Cheers

    Geoff
     
  • Friday, January 29, 2010 3:34 AM
     
     
    Sign In to Vote
    0

    Hi Anis,

     

    Do you want to perform in-place upgrade?

     

    Does the http://abc exist in your WSS v2 server?

     

    If not, go into the V2 central administration page and  unextend the site  http://abc. After that run the prescan tool again and check the effect.

     

    If the steps above can’t resolve your issue, you can try the following suggestions:

     

    - Uninstall v2 and v3.

    - Restore the content database from previous backup.

    - Install WSS v2 with SP2 by creating new config DB.

    - Add the content database and make sure the site is up and running.

    - Install V3 with do not upgrade at this time.

    - Run prescan tool.

    - Create a web application.

    - Add the content DB using the command stsadm -o addcontentdb -url <urlname> -databasename <databasename> and then browse to the site.

     

    Hope this helps.

     

    Rock Wang

    Rock Wang– MSFT