locked
Configuration Failed during a Windows Update RRS feed

  • Question

  • Unable to connect to an internal SharePoint site (on Server2003) after some Updates were applied overnight.  SharePoint 3.0 (not sure of SP, cannot get into management).  Following updates were applied:  980773, 976765, 979909, 976769v2, 982381, 978695, 982666, 975562, 980195, 979907, 979482, 979559, 980218.

    The Web Server Externsions "Updates.log" file shows following:

    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoStartWindowsService(String serviceName)
       at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()
       at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
       at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision()
       at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
       at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.EnableAndProvisionSearchNTService()
    [SPManager] [ERROR] [6/9/2010 3:09:21 AM]: Upgrade [SPSearchDatabase Name=WSS_Search_WEB01 Parent=SPDatabaseServiceInstance Name=Microsoft##SSEE] failed.
    [SPManager] [ERROR] [6/9/2010 3:09:21 AM]: The service did not start due to a logon failure
    [SPManager] [ERROR] [6/9/2010 3:09:21 AM]: Cannot start service SPSearch on computer '.'.

    I try to start the "SharePoint Service Search" service and get the error: Could not start the Windows SharePoint service Search service on Local computer.  Error 1069: The service did not start due to a logon failure.

    I have reset the password for the domain account used for "Log on" for this service, but still receive the same error when starting the service.  Same for the SQLAgent$SHAREPOINT service.  I'm unable to get into SharePoint 3.0 Central Administration.  Get "Service Unavailable" in IE.

    NOt sure what else to try.  Thanks for all ideas.

    Wednesday, June 9, 2010 6:02 PM

Answers

  • Actually, I was able to solve it this afternoon.  TracyP had me heading in the right direction, but it took two extra switches on the command: psconfig -cmd upgrade -inplace b2b.  I added the -wait -force switches to that command (found in other threads/forums), and users were immediately able to log in with no trouble.

    Entire command: psconfig -cmd upgrade -inplace b2b -wait -force

    R

    Monday, June 14, 2010 10:28 PM
  • That's a relief, Romseye! I'm glad it's up and running for you and glad I could pitch in.

    Tracy

    • Marked as answer by Romseye Thursday, January 20, 2011 11:29 PM
    Tuesday, June 15, 2010 10:08 PM

All replies

  • 1.  Run the following STSADM operations to stop and start the SPWebService:

            stsadm -o provisonservice -action stop -servicetype "" -servicename ""

            stsadm -o provisionservice -action start -servicetype "" -servicename ""

    2.  Instantiate the upgrade by executing psconfig.exe

            psconfig –cmd upgrade –inplace b2b –wait –force

     

    Wednesday, June 9, 2010 6:28 PM
  • Should have mentioned I tried that previously, including a reboot, and still no luck.  Tried it again, still no luck.  Getting:

     

    The webpage cannot be found

     HTTP 404
     

    Most likely causes:

    • There might be a typing error in the address.
    • If you clicked on a link, it may be out of date.

    The webpage cannot be found

     HTTP 404
     

    Most likely causes:

    • There might be a typing error in the address.
    • If you clicked on a link, it may be out of date.

    Get Event 5586 also...

    Unknown SQL Exception 33002 occured. Additional error information from SQL Server is included below.

    Access to module dbo.proc_GetRunnableWorkItems is blocked because the signature is not valid.

    Wednesday, June 9, 2010 6:49 PM
  • did you run all the above commands???  did they complete successfully?
    Wednesday, June 9, 2010 8:41 PM
  • Yes.  All completed "successfully".

    I restared the server again and these events are listed:

    Event Type: Error
    Event Source: Windows SharePoint Services 3 Search
    Event Category: Gatherer
    Event ID: 2424
    Date:  6/9/2010
    Time:  4:20:02 PM
    User:  N/A
    Computer: <SERVER NAME>
    Description:
    The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

    Context: Application 'Search', Catalog 'index file on the search server Search'

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Information
    Event Source: MSSQL$MICROSOFT##SSEE
    Event Category: (2)
    Event ID: 2803
    Date:  6/9/2010
    Time:  4:20:03 PM
    User:  N/A
    Computer: <SERVER NAME>
    Description:
    The description for Event ID ( 2803 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 1, Object Plans.
    Data:
    0000: f3 0a 00 00 0a 00 00 00   ó.......
    0008: 16 00 00 00 57 00 45 00   ....W.E.
    0010: 42 00 30 00 31 00 5c 00   B.0.1.\.
    0018: 4d 00 49 00 43 00 52 00   M.I.C.R.
    0020: 4f 00 53 00 4f 00 46 00   O.S.O.F.
    0028: 54 00 23 00 23 00 53 00   T.#.#.S.
    0030: 53 00 45 00 45 00 00 00   S.E.E...
    0038: 07 00 00 00 6d 00 61 00   ....m.a.
    0040: 73 00 74 00 65 00 72 00   s.t.e.r.
    0048: 00 00                     ..     

    Event Type: Information
    Event Source: MSSQL$MICROSOFT##SSEE
    Event Category: (2)
    Event ID: 2803
    Date:  6/9/2010
    Time:  4:20:03 PM
    User:  N/A
    Computer: <SERVER NAME>
    Description:
    The description for Event ID ( 2803 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 1, SQL Plans.
    Data:
    0000: f3 0a 00 00 0a 00 00 00   ó.......
    0008: 16 00 00 00 57 00 45 00   ....W.E.
    0010: 42 00 30 00 31 00 5c 00   B.0.1.\.
    0018: 4d 00 49 00 43 00 52 00   M.I.C.R.
    0020: 4f 00 53 00 4f 00 46 00   O.S.O.F.
    0028: 54 00 23 00 23 00 53 00   T.#.#.S.
    0030: 53 00 45 00 45 00 00 00   S.E.E...
    0038: 07 00 00 00 6d 00 61 00   ....m.a.
    0040: 73 00 74 00 65 00 72 00   s.t.e.r.
    0048: 00 00                     ..     

    Event Type: Information
    Event Source: MSSQL$MICROSOFT##SSEE
    Event Category: (2)
    Event ID: 2803
    Date:  6/9/2010
    Time:  4:20:03 PM
    User:  N/A
    Computer: <SERVER NAME>
    Description:
    The description for Event ID ( 2803 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 1, Bound Trees.
    Data:
    0000: f3 0a 00 00 0a 00 00 00   ó.......
    0008: 16 00 00 00 57 00 45 00   ....W.E.
    0010: 42 00 30 00 31 00 5c 00   B.0.1.\.
    0018: 4d 00 49 00 43 00 52 00   M.I.C.R.
    0020: 4f 00 53 00 4f 00 46 00   O.S.O.F.
    0028: 54 00 23 00 23 00 53 00   T.#.#.S.
    0030: 53 00 45 00 45 00 00 00   S.E.E...
    0038: 07 00 00 00 6d 00 61 00   ....m.a.
    0040: 73 00 74 00 65 00 72 00   s.t.e.r.
    0048: 00 00                     ..     

    Event Type: Information
    Event Source: MSSQL$MICROSOFT##SSEE
    Event Category: (2)
    Event ID: 17137
    Date:  6/9/2010
    Time:  4:20:07 PM
    User:  NT AUTHORITY\NETWORK SERVICE
    Computer: <SERVER NAME>
    Description:
    The description for Event ID ( 17137 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: WSS_Content.
    Data:
    0000: f1 42 00 00 0a 00 00 00   ñB......
    0008: 16 00 00 00 57 00 45 00   ....W.E.
    0010: 42 00 30 00 31 00 5c 00   B.0.1.\.
    0018: 4d 00 49 00 43 00 52 00   M.I.C.R.
    0020: 4f 00 53 00 4f 00 46 00   O.S.O.F.
    0028: 54 00 23 00 23 00 53 00   T.#.#.S.
    0030: 53 00 45 00 45 00 00 00   S.E.E...
    0038: 07 00 00 00 6d 00 61 00   ....m.a.
    0040: 73 00 74 00 65 00 72 00   s.t.e.r.
    0048: 00 00                     ..     

    Event Type: Information
    Event Source: MSSQL$MICROSOFT##SSEE
    Event Category: (2)
    Event ID: 3455
    Date:  6/9/2010
    Time:  4:20:10 PM
    User:  NT AUTHORITY\NETWORK SERVICE
    Computer: <SERVER NAME>
    Description:
    The description for Event ID ( 3455 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: WSS_Content, 5, 100, 0.
    Data:
    0000: 7f 0d 00 00 0a 00 00 00   .......
    0008: 16 00 00 00 57 00 45 00   ....W.E.
    0010: 42 00 30 00 31 00 5c 00   B.0.1.\.
    0018: 4d 00 49 00 43 00 52 00   M.I.C.R.
    0020: 4f 00 53 00 4f 00 46 00   O.S.O.F.
    0028: 54 00 23 00 23 00 53 00   T.#.#.S.
    0030: 53 00 45 00 45 00 00 00   S.E.E...
    0038: 07 00 00 00 6d 00 61 00   ....m.a.
    0040: 73 00 74 00 65 00 72 00   s.t.e.r.
    0048: 00 00                     ..     

    Event Type: Error
    Event Source: MSSQL$MICROSOFT##SSEE
    Event Category: (2)
    Event ID: 33002
    Date:  6/9/2010
    Time:  4:20:10 PM
    User:  NT AUTHORITY\NETWORK SERVICE
    Computer: <SERVER NAME>
    Description:
    The description for Event ID ( 33002 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: module, dbo.proc_GetCurrent.
    Data:
    0000: ea 80 00 00 10 00 00 00   ê€......
    0008: 16 00 00 00 57 00 45 00   ....W.E.
    0010: 42 00 30 00 31 00 5c 00   B.0.1.\.
    0018: 4d 00 49 00 43 00 52 00   M.I.C.R.
    0020: 4f 00 53 00 4f 00 46 00   O.S.O.F.
    0028: 54 00 23 00 23 00 53 00   T.#.#.S.
    0030: 53 00 45 00 45 00 00 00   S.E.E...
    0038: 0c 00 00 00 57 00 53 00   ....W.S.
    0040: 53 00 5f 00 43 00 6f 00   S._.C.o.
    0048: 6e 00 74 00 65 00 6e 00   n.t.e.n.
    0050: 74 00 00 00               t...   

    Event Type: Error
    Event Source: Windows SharePoint Services 3
    Event Category: Database
    Event ID: 5586
    Date:  6/9/2010
    Time:  4:20:10 PM
    User:  N/A
    Computer: <SERVER NAME>
    Description:
    Unknown SQL Exception 33002 occured. Additional error information from SQL Server is included below.

    Access to module dbo.proc_GetCurrent is blocked because the signature is not valid.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Error
    Event Source: Windows SharePoint Services 3 Search
    Event Category: Gatherer
    Event ID: 2424
    Date:  6/9/2010
    Time:  4:20:10 PM
    User:  N/A
    Computer: <SERVER NAME>
    Description:
    The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

    Context: Application 'Search', Catalog 'index file on the search server Search'

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Error
    Event Source: MSSQL$MICROSOFT##SSEE
    Event Category: (2)
    Event ID: 33002
    Date:  6/9/2010
    Time:  4:20:33 PM
    User:  NT AUTHORITY\NETWORK SERVICE
    Computer: <SERVER NAME>
    Description:
    The description for Event ID ( 33002 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: module, dbo.proc_GetRunnableWorkItems.
    Data:
    0000: ea 80 00 00 10 00 00 00   ê€......
    0008: 16 00 00 00 57 00 45 00   ....W.E.
    0010: 42 00 30 00 31 00 5c 00   B.0.1.\.
    0018: 4d 00 49 00 43 00 52 00   M.I.C.R.
    0020: 4f 00 53 00 4f 00 46 00   O.S.O.F.
    0028: 54 00 23 00 23 00 53 00   T.#.#.S.
    0030: 53 00 45 00 45 00 00 00   S.E.E...
    0038: 0c 00 00 00 57 00 53 00   ....W.S.
    0040: 53 00 5f 00 43 00 6f 00   S._.C.o.
    0048: 6e 00 74 00 65 00 6e 00   n.t.e.n.
    0050: 74 00 00 00               t...   

     

    Wednesday, June 9, 2010 9:20 PM
  • Also, in the System event log, notice these two:

    Event Type: Warning
    Event Source: W3SVC
    Event Category: None
    Event ID: 1057
    Date:  6/9/2010
    Time:  4:05:33 PM
    User:  N/A
    Computer: <SERVER NAME>
    Description:
    The identity of application pool 'SharePoint Central Administration v3' is invalid, so the World Wide Web Publishing Service can not create a worker process to serve the application pool.  Therefore, the application pool has been disabled.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Error
    Event Source: W3SVC
    Event Category: None
    Event ID: 1059
    Date:  6/9/2010
    Time:  4:05:33 PM
    User:  N/A
    Computer: <SERVER NAME>
    Description:
    A failure was encountered while launching the process serving application pool 'SharePoint Central Administration v3'. The application pool has been disabled.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Thanks for all help.

    Wednesday, June 9, 2010 10:21 PM
  • Romseye,

    I had a very similar problem after last night's updates, though I'm using Sharepoint 3.0 on Small Business Server 2008.

    In case it helps you, here's what finally worked for me:

    - In Central Administration/Operations/Services on Server/Windows Sharepoint Services Search Settings, I changed the Service Account and the Content Access Account to the built-in Administrator account (i.e. [short domain name]\Administrator).

    - Rebooted (twice) and ran SharePoint Products and Technologies Configuration Wizard from another account with administrator privileges.

    The wizard had failed repeatedly on earlier attempts, but after the Central Administration changes and the reboots, it finally ran all the way through and indicated that the configuration/installation had succeeded.

    Access to Companyweb was then restored on the server and clients.

    Good luck with it.

    J

     

    Thursday, June 10, 2010 1:12 AM
  • Hi Romseye,

    When you say 'SharePoint can't get into Management' do you mean that you can't browse Central Administration, or the site (or possibly both)? Also, what account is running your Search Service -- is it a local account such as NT Authority\Network Service (if so, add this account as a local Admin and test running PSCONFIG again)? What Service Pack are you at for SharePoint? (You can find this out by locating your OWSSVR.dll, and checking it's version. In C:\Windows\Assembly, you should also check your SharePoint dlls for the version listed.) Also, I want to verify that you're running only WSS 3.0 on this machine.

    Login as the account running your Central Administration Application pool, if it is a domain account. Otherwise, login as a member of the local administrator's group and run the PSCONFIG wizard for me. Let's see if it runs through successfully. If not, remain logged in as the same account as you:

    1. Open a command prompt (via Start > Run > cmd).
    2. Change directory to <system drive>\Program Files\Common Files\Microsoft Shared\web server extensions\12\Bin.
    3. Run the command (without the quotes) "psconfig -cmd upgrade -inplace b2b".

    This may take some time to run to completion.

    To help assure we have correct access, you should also follow: http://support.microsoft.com/kb/934838/en-us - How to change service accounts and service account passwords in SharePoint Server 2007 and in Windows SharePoint Services 3.0. Update your account passwords and try to launch the site.

    Also, you might want to download the SQL Management Studio Express and check the state of your database (for instance, if you can't browse the site itself, is your Content database listing 'Suspect').

    To download SQL Server Management Studio Express go here:

    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796

    To connect to the Database Engine, use:  .\MSSQL$MICROSOFT##SSEE or <servername>\MSSQL$MICROSOFT##SSEE

    As ever, don't change anything in the databases or stored procedures you see directly, as the referential integrity of your SharePoint databases would be compromised. But do check for Suspect databases, or other helpful information under the Management > SQL Server Logs tree.

     

    • Edited by Tracyp - MSFT Thursday, June 10, 2010 5:53 PM Extra step!
    Thursday, June 10, 2010 3:04 PM
  • Ok, answers to your questions...

    1.  Can't run SharePoint 3.0 Central Administration.  Get IE window stating "Service Unavailable"
    2.  Search Service is a domain account with a password I have reset to something I know from previous admin's pwd.  It is a member of the local Administrators group.  Not Network Service.  I have tried Network Service, no difference.
    3.  OWSSVR.DLL version is 12.0.6535.5003.
    4.  As for dlls in C:\Windows\Assembly folder,  versions range from 1.0.5000.0 to 12.0.0.0.  Some of the dlls seem to have duplicates though.  For example, I've got w System.Xml files, 1.0.5000.0 & 2.0.0.0.  NOt sure if that is normal.
    5. Output from PSCONFIG after logging in as local account WSS_SVC_SHAREPOINT, which is the account that runs the Search Service:

    C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>psco
    nfig -cmd upgrade -inplace b2b
    SharePoint Products and Technologies Configuration Wizard version 12.0.6500.5000
    Copyright (C) Microsoft Corporation 2005. All rights reserved.

    Performing configuration task 1 of 4
    Initializing SharePoint Products and Technologies upgrade...

    Successfully initialized SharePoint Products and Technologies upgrade.

    Performing configuration task 2 of 4
    Initiating the upgrade sequence...

    Successfully initiated the upgrade sequence.

    Performing configuration task 3 of 4
    Upgrading SharePoint Products and Technologies...

    Failed to upgrade SharePoint Products and Technologies.

    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfig
    urationTaskException was thrown.  Additional exception information: The upgrade
    command is invalid or a failure has been encountered.
    Failed to upgrade SharePoint Products and Technologies.

    Total number of configuration settings run: 3
    Total number of successful configuration settings: 2
    Total number of unsuccessful configuration settings: 1
    Successfully stopped the configuration of SharePoint Products and Technologies.
    Configuration of SharePoint Products and Technologies failed.  Configuration mus
    t be performed before you use SharePoint Products and Technologies.  For further
     details, see the diagnostic log located at C:\Program Files\Common Files\Micros
    oft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_6_10_2010_15_23_29_523_9
    40382235.log and the application event log.

    Interesting.  This worked ok yesterday when logged in as a domain admin.  Three pertinent events from App log:

    Event Type: Error
    Event Source: Windows SharePoint Services 3
    Event Category: Timer
    Event ID: 6398
    Date:  6/10/2010
    Time:  3:25:57 PM
    User:  N/A
    Computer: WEB01
    Description:
    The Execute method of job definition Microsoft.SharePoint.Administration.SPUpgradeJobDefinition (ID bf1e1325-a349-4269-b2e1-6ae039be7a38) threw an exception. More information is included below.

    Upgrade completed with errors.  Review the upgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log.  The number of errors and warnings is listed at the end of the upgrade log file.

    Event Type: Error
    Event Source: SharePoint Products and Technologies Configuration Wizard
    Event Category: None
    Event ID: 104
    Date:  6/10/2010
    Time:  3:26:03 PM
    User:  N/A
    Computer: WEB01
    Description:
    Failed to upgrade SharePoint Products and Technologies.
    Failed to upgrade SharePoint Products and Technologies.  Further information regarding this failure can be found at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log.
    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: The upgrade command is invalid or a failure has been encountered.
    Failed to upgrade SharePoint Products and Technologies.
    Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

    Event Type: Error
    Event Source: SharePoint Products and Technologies Configuration Wizard
    Event Category: None
    Event ID: 100
    Date:  6/10/2010
    Time:  3:26:03 PM
    User:  N/A
    Computer: WEB01
    Description:
    Configuration of SharePoint Products and Technologies failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_6_10_2010_15_23_29_523_940382235.log, fix the problem, and run this configuration wizard again.

    The first ERR in the PSCDiagnostics_6_10_2010_15_23_29_523_940382235.log log is: 
    06/10/2010 15:26:03  5  ERR            The B2B upgrader timer job failed.


    The second ERR is:
    06/10/2010 15:26:03  5  ERR            Task upgrade has failed with a PostSetupConfigurationTaskException An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: The upgrade command is invalid or a failure has been encountered.
    Failed to upgrade SharePoint Products and Technologies.


    The third is:
    06/10/2010 15:26:03  5  ERR              Task upgrade has failed

    The fourth is:
    06/10/2010 15:26:03  1  ERR          Task upgrade SharePoint Products and Technologies failed, so stopping execution of the engine

    The fifth is:
    06/10/2010 15:26:03  1  ERR          Failed to upgrade SharePoint Products and Technologies.
    Failed to upgrade SharePoint Products and Technologies.  Further information regarding this failure can be found at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log.
    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: The upgrade command is invalid or a failure has been encountered.
    Failed to upgrade SharePoint Products and Technologies.
    Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

    The sixth is:
    06/10/2010 15:26:03  1  ERR          One or more configuration tasks has failed or some tasks were not run

    The seventh is:
    06/10/2010 15:26:03  1  ERR        One or more configuration tasks has failed to execute

    The eigth is:
    06/10/2010 15:26:03  1  ERR          Configuration of SharePoint Products and Technologies failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_6_10_2010_15_23_29_523_940382235.log, fix the problem, and run this configuration wizard again.

    The last is:
    06/10/2010 15:26:03  1  ERR      Post setup configuration was not run successfully when using the command line task driver module

    6. Started SQL Management Studio Express and got the following error windows when starting: (<server name>\MICROSOFT@@SSEE, and Windows Authentication)

    Error Window 1:

    TITLE: Connect to Server
    ------------------------------

    Cannot connect to <SERVERNAME>\MICROSOFT##SSEE.

    ------------------------------
    ADDITIONAL INFORMATION:

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

    ------------------------------
    BUTTONS:

    OK
    ------------------------------

    Pasting the "Details:"

    ------------------------------
    Program Location:

       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
       at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

    Click the Cancel button and get...

    No Server Connection in the Summary pane of Studio Express window.

    I'll now follow the steps in article 934838.  I've done this before, but won't hurt to try again.  Will update results in new reply.

    Thanks for your help so far.

    Thursday, June 10, 2010 9:00 PM
  • Hi Josh.  Thx for the ideas.  Unfortunately, I cannot get into Central Administration, as I get Service Unavailable error in IE.  I just noticed the server is running IE 7, so will upgrade to 8.0 to check for differences.  Thanks.
    Thursday, June 10, 2010 9:02 PM
  • Oh, checked the System Event log and see these two events:

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7038
    Date:  6/10/2010
    Time:  3:25:56 PM
    User:  N/A
    Computer: WEB01
    Description:
    The SPSearch service was unable to log on as kytn\wss_svc_sharepoint with the currently configured password due to the following error:
    Logon failure: unknown user name or bad password.

    To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7000
    Date:  6/10/2010
    Time:  3:25:56 PM
    User:  N/A
    Computer: WEB01
    Description:
    The Windows SharePoint Services Search service failed to start due to the following error:
    The service did not start due to a logon failure.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    I had reset this password yesterday becuase I did not know the previous password before I started here.  It did reset correctly, cause I am able to log in to the server ok.  Weird.

    Thursday, June 10, 2010 9:05 PM
  • 1.  UPdating password for the account used by the Central Administration application pool:

    C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa
    dm -o updatefarmcredentials -userlogin <servername>\wss_svc_sharepoint -password testpwd

    To ensure that all credential caches in IIS have updated, you must run the comma
    nd "IISRESET /NOFORCE" on all servers in the farm.  This should be done after al
    l credential updates have been completed.
    Operation completed successfully.

    C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>iisr
    eset /noforce

    Attempting stop...
    Internet services successfully stopped
    Attempting start...
    Internet services successfully restarted

    2.  Verify that the Administration Application Pool Credential Deployment job definition is no longer displayed on the Timer Job Definitions page:

    Clicked Start/Administrative Tools, SharePoint 3.0 Central Administration, and bam!  Central Admin actually came up this time!!!  Whew!  Seeing progress here!  It is not shown in the list!

    Ok.  Question about the next steps (3 through 5) 
    1.  Do I need to perform these user account password resets?
    2.  How do I determine the account used by Web applications on the server farm?  (Identity tab in Properties of Application Pool SharePoint - 80?)

    Thanks!  Starting to feel better.  :)

    Thursday, June 10, 2010 9:27 PM
  • Ok.  Question about the next steps in article 934838 (3 through 5) 
    1.  Regarding the user account password resets, do I need to do this?
    2.  How can I determine the current account name for each the account roles?  (e.g., updatefarmcredentials, updateaccountpassword, spsearch -farmserviceaccount, & spsearch -farmcontentaccessaccount)

    3.  Whare are the typical accounts associated with each of the above account roles?
    4.  Which are set by SharePoint when installed, and which by the user who created the SharePoint site?

    Related problem:  When I try logging into a document share from a workstation using the wss_svc_sharepoint created for the Search Service account, I am unable to do so.  Get the following:

    You are not authorized to view this page

    You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept.

    HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration.
    Internet Information Services (IIS)

    Should I be able to log in using this account?

    Friday, June 11, 2010 3:10 PM
  • Hi again, Romseye,

    I'm glad you're starting to feel better (that's the goal!) -- I hope we can keep heading in that direction, for sure!

    Regarding your 'You are not authorized to view this page', was this account able to view the document library beforehand? I also want to confirm whether you've walked all the way through the password change KB article yet.

    Regarding where to find the accounts in the steps below (for the password change) you'd need to go to Central Administration > Operations > Services on Server > Windows SharePoint Services Search Service Settings. The radio buttons on this page will allow you to focus on different parts of your farm. You can choose Custom and then click Search. 'Service Account' corresponds to step 4, and 'Content Access Account' corresponds to step 5. In stand-alone mode, the first accounts in the KB would be set by the installation as it rolls out. However, when you start the Search service in Central Administration, you set the Default Content Access account and the Search Service account, yourself.

    (4) Update the password for the account that is used to run the Windows SharePoint Services Help Search service. To do this, type the following line at a command prompt on every server on the server farm, and then press ENTER:
    stsadm.exe -o spsearch -farmserviceaccount DomainName\UserName -farmservicepassword NewPassword

    (5) Update the password for the default content access account that is used by the Windows SharePoint Services Help Search service. To do this, type the following line at a command prompt on every server on the server farm, and then press ENTER:
    stsadm.exe -o spsearch -farmcontentaccessaccount DomainName\UserName -farmcontentaccesspassword NewPassword

    Assuming that WSS_SVC_SharePoint is used for all accounts, it will appear as both the accounts listed here too, and we should password reset both and check permissions again.

    Regarding your first question, it's a pretty unusual thing to run only portions of the password change KB (unless you only have WSS v3, at which point, you skip directions referring to SharePoint Server 2007). The KB article helps refresh the passwords and get them all on the same page.

    Thanks!

    • Edited by Tracyp - MSFT Friday, June 11, 2010 6:15 PM Added more complete information!
    Friday, June 11, 2010 6:05 PM
  • Thanks.  Answers...

    Not sure if this account was able to log in before as I never knew the account existed before yesterday.  I've recently inherited this network.

    Ok, went through resetting account password for each step.  The Search Service service is now running successfully.  I did another “IISRESET /NOFORCE”, and then tried connecting as one of my users from my workstation, and still unable to log in.  Connecting to following URL: http://<servername>/treasury/forms/allitems.aspx.  Get the “Connect to <server.domain.net>” window, enter <domain>\user1, and their password, and window comes right back.  After 3<sup>rd</sup> try, get following error:

    You are not authorized to view this page

    You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept.

    I now need to understand how to get my users access to the site.  I was hoping things would be normal after all that. The Windows Internal Database (Microsoft$$SSEE) service is set to "Manual" and logs in as "Network Service"  All ther other SharePoint services log in with the WSS_SVC_SHAREPOINT account.
    Appreciate your help.

    Friday, June 11, 2010 7:53 PM
  • I have a similar problem with Dynamics Business Portal. Which runs on WSS.
    I can get into the SharePoint 3.0 Central Administration site but I cannot get into Business Portal.
    I am getting the same error in my Applications logs.
    This happed after patches were installed.
    Fortunatly this server is a VM and I was able to reinstall a snapshot pre patches.

    Is there any idea what patch caused the problem and why?

    Have any of the solutions posted above worked for you?

    Van

    Monday, June 14, 2010 4:27 PM
  • Unfortunately, I have too little experience with SharePoint, otherwise I might have been able to resolve this by now.  I believe it is just a matter of setting the correct permissions for users to be allowed access to the site.  I'm guessing whatever happened blasted their credentials away, yet recreating regular user permissions for the site is not allowing them to connect.  (Or I'm missing something due to lack of knowledge still.)  Sorry I cannot be of more help.

    R

    Monday, June 14, 2010 6:54 PM
  • Actually, I was able to solve it this afternoon.  TracyP had me heading in the right direction, but it took two extra switches on the command: psconfig -cmd upgrade -inplace b2b.  I added the -wait -force switches to that command (found in other threads/forums), and users were immediately able to log in with no trouble.

    Entire command: psconfig -cmd upgrade -inplace b2b -wait -force

    R

    Monday, June 14, 2010 10:28 PM
  • That's a relief, Romseye! I'm glad it's up and running for you and glad I could pitch in.

    Tracy

    • Marked as answer by Romseye Thursday, January 20, 2011 11:29 PM
    Tuesday, June 15, 2010 10:08 PM
  • I also saw this today.

     

    I resolved it by editing my HOSTS file. The Office Search service had put an entry in there for some reason.

     

    IPV6IP Servername  #Put here by Office Search Service

     

    I deleted the entry and everything went back to normal

    Tuesday, August 17, 2010 7:31 PM