Manually running PSCONFIG is required after installing SharePoint Foundation 2010 Updates
Question
-
Microsoft SharePoint Foundation 2010 Service Pack 1 (SP1) was recently released through Microsoft Update. On a default installation, Windows SBS 2011 Standard administrators should be able to see it in the SBS Console and would need to approve it for installation before it is offered for installation on the server.
Since SharePoint Foundation 2010, patching SharePoint is a two-step process. The updated binaries are first installed and then PSCONFIG must be completed to update the SharePoint databases.
Without completing PSCONFIG, you might experience unexpected SharePoint search failures and all backups may stop working on the affected server.The Following errors may be found in the server application log:
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation Search
Event ID: 70
Task Category: Gatherer
Level: Error
User: CONTOSO\spsearch
Computer: CONTOSO-SERVER.contoso.local
Description:
The mount operation for the gatherer application 37ad8233-57f1-47b1-873e-6a91d0f1bc36 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.Log Name: Application
Source: Microsoft-Windows-Backup
Event ID: 521
Level: Error
User: SYSTEM
Description:
The backup operation that started at '?2011?-?07?-?06T02:12:07.198000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.You can also run the following commands to determine if you need to complete the update process with PSCONFIG:
- Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
- Once the shell opens, type the following command followed by enter:
(get-spserver $env:computername).NeedsUpgrade
If the result of this command is True, then you need to complete the steps below. If the result is False then no further action is needed, if you are encountering similar events the cause will most likely not be resolved by the following steps.
To complete the SharePoint service pack process you need to follow the same steps that were previously posted on the Official SBS Blog regarding the necessity to complete PSCONFIG after a SharePoint update. Here are the steps from the article:
In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:
1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeaturesNote: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.
For additional information on SharePoint Foundation 2010 patching mechanism, please see the following TechNet article:
http://technet.microsoft.com/en-us/library/ff806326.aspx
- Edited by Fang Xie Thursday, July 7, 2011 2:51 AM
- Changed type Susan BradleyMVP Friday, March 30, 2012 6:36 PM Change to ? to flag as answer
- Edited by Susan BradleyMVP Friday, March 30, 2012 6:38 PM Edited title to indicate all updates need a psconfig
Answers
All replies
-
I'm still receiving the message updating my psconfig databases when logging in to my terminal server with same policies...
Have updated the sharepoint manually:
1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeaturesThis step has succeeded!
After that I restart all services sharepoint e.d. / IIS and readed the blog;'
http://blogs.technet.com/b/sbs/ says it has to do with manual scheduler task:
Note: this message will only be cleared after the issue is resolved and the schedule task runs again that night. If needed, you can re-run the scheduled task in Task Manager, under Microsoft\Windows\Windows Small Business Server 2011 Standard.
The task writes a log called WSSPsconfigurationNotification.log in C:\Program Files\Windows Small Business Server\logs.
We also have the more traditional console alert, if configured, an email will be sent when this alert is detected.
Have run the task manually, still exist the same message error when logging in to my network! Anyone experience the same problems?
Thanks in advantage,
Array01
-
i have been struggling with the sharepoint security up date on SBS 2008. I have run the psconfig as shown in KB944267. The psconfig on 2008 is run from the %\12\bin instead of what the %14\bin for 2010. There is no 14 folder. I am having a terrible time with this and wondered if I need to use the longer command line that has been stated in here, and whether it will work from the %\12\bin folder. The command I am running is:
psconfig -cmd upgrade -inplace b2b -wait -force
results are as follows:
-
in SBS 2008 you are to also do the following before the psconfig:
net stop MSSQL$MICROSOFT##SSEE
net start MSSQL$MICROSOFT##SSEE
Then the psconfig listed in my last post. After that to rerun the Sharepoint Products and Technologies Configuration Wizard. After doing all of this I get the following Errors:
-
My application event log shows the following errors:
-
Microsoft SharePoint Foundation 2010 Service Pack 1 (SP1) was recently released through Microsoft Update. On a default installation, Windows SBS 2011 Standard administrators should be able to see it in the SBS Console and would need to approve it for installation before it is offered for installation on the server.
Since SharePoint Foundation 2010, patching SharePoint is a two-step process. The updated binaries are first installed and then PSCONFIG must be completed to update the SharePoint databases.
Without completing PSCONFIG, you might experience unexpected SharePoint search failures and all backups may stop working on the affected server.The Following errors may be found in the server application log:
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation Search
Event ID: 70
Task Category: Gatherer
Level: Error
User: CONTOSO\spsearch
Computer: CONTOSO-SERVER.contoso.local
Description:
The mount operation for the gatherer application 37ad8233-57f1-47b1-873e-6a91d0f1bc36 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.Log Name: Application
Source: Microsoft-Windows-Backup
Event ID: 521
Level: Error
User: SYSTEM
Description:
The backup operation that started at '?2011?-?07?-?06T02:12:07.198000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.You can also run the following commands to determine if you need to complete the update process with PSCONFIG:
- Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
- Once the shell opens, type the following command followed by enter:
(get-spserver $env:computername).NeedsUpgrade
If the result of this command is True, then you need to complete the steps below. If the result is False then no further action is needed, if you are encountering similar events the cause will most likely not be resolved by the following steps.
To complete the SharePoint service pack process you need to follow the same steps that were previously posted on the Official SBS Blog regarding the necessity to complete PSCONFIG after a SharePoint update. Here are the steps from the article:
In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:
1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeaturesNote: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.
For additional information on SharePoint Foundation 2010 patching mechanism, please see the following TechNet article:
Thank's a lot for this article!
Martin
-
Microsoft SharePoint Foundation 2010 Service Pack 1 (SP1) was recently released through Microsoft Update. On a default installation, Windows SBS 2011 Standard administrators should be able to see it in the SBS Console and would need to approve it for installation before it is offered for installation on the server.
Since SharePoint Foundation 2010, patching SharePoint is a two-step process. The updated binaries are first installed and then PSCONFIG must be completed to update the SharePoint databases.
Without completing PSCONFIG, you might experience unexpected SharePoint search failures and all backups may stop working on the affected server.The Following errors may be found in the server application log:
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation Search
Event ID: 70
Task Category: Gatherer
Level: Error
User: CONTOSO\spsearch
Computer: CONTOSO-SERVER.contoso.local
Description:
The mount operation for the gatherer application 37ad8233-57f1-47b1-873e-6a91d0f1bc36 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.Log Name: Application
Source: Microsoft-Windows-Backup
Event ID: 521
Level: Error
User: SYSTEM
Description:
The backup operation that started at '?2011?-?07?-?06T02:12:07.198000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.You can also run the following commands to determine if you need to complete the update process with PSCONFIG:
- Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
- Once the shell opens, type the following command followed by enter:
(get-spserver $env:computername).NeedsUpgrade
If the result of this command is True, then you need to complete the steps below. If the result is False then no further action is needed, if you are encountering similar events the cause will most likely not be resolved by the following steps.
To complete the SharePoint service pack process you need to follow the same steps that were previously posted on the Official SBS Blog regarding the necessity to complete PSCONFIG after a SharePoint update. Here are the steps from the article:
In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:
1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeaturesNote: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.
For additional information on SharePoint Foundation 2010 patching mechanism, please see the following TechNet article:
http://technet.microsoft.com/en-us/library/ff806326.aspx
After SP1 installation I face similar problems (before everything was fine).
Now Exchangeserver is not running anymore and remote acces is not possible.
(get-spserver $env:computername).NeedsUpgrade not working because my server name is "name-server" . Returning argument no server with the name "-server"
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures. Not working. Returning error IIS must be installed and running. I checked, and it is.
These errors cost me two day's allready. Software is running on a brand new HP-350P Gen8 server.
Hope anybody can be of assistance.
