Background
SharePoint 2013 was installed and updated with patches that give you the version 15.0.4433.1506. After all the server install is complete, you will notice that the Servers in the Farm displayes “Upgrade Available”, as well as following warning “To get more detailed information about the local upgrade status, run: stsadm.exe -o localupgradestatus”
When you follow above steps or look up the Upgrade Status screens on the Central administration, everything looks good, yet the farm status continues to show, Upgrade Available.
Issue
I did not face any functional issues but was just annoyed by the status warnings.
Solution
Restart IIS
Technorati Tags: SharePoint 2013
Posts
8 comments:
Hello,
Did you install only a single Sharepoint server or a Sharepoint server farm with two or more nodes? Did the issue occur only on one server or every installed server?
Also I would like to ask you, have you run the following command on the Sharepoint server?
(get-spserver $env:computername).NeedsUpgrade
And if so, did you receive an output of "False" or "True"?
Thank you in advance.
Hello Buddha,
This was a Single Server Farm.
I ran the STSADM -o localupgradestatus which I believe might be your PowerShell command equivalent.
The output was 0 (False)
-Rajesh
Hi Rajesh,
I have same situation i SP2010 Farm and i ran following command "psconfig -cmd upgrade -inplace b2b -wait". and noticed status as "No Action Required". but status changed to "Upgrade Available" within a day. Any thoughts on this.?please suggest.
Hi Nazakath,
The Upgrade available means that there is a newer CU/SP available at the SharePoint Updates page that the one installed on your farm. Simply check what is the version of your farm and compare with the latest available version.
You have option to install the latest updates.
-Rajesh
I am receiving the same message despite having the latest version (15.0.4675.1000 as of 2/6). (get-spserver).NeedsUpgrade returns one of the servers as False with the others as true.
kenyadoit,
Ensure you had ran the Configuration Wizard on all of your servers one by one. You ight be missing the Config Wizard run on the server in question.
HTH
-Rajesh
I ran the command on all of the servers in the farm and rebooted and am still experiencing the issue. this is preventing me from installing the Reporting Services Add in for Sharepoint
Ok here's what I did and what happened and you wouldn't believe it:
After looking through the event logs we noticed an error stating the logging database was in an availability group which is why psconfig would not work. After taking the database out of the group we were able to run psconfig. This apparently occurs occasionally after deploying updates. If you have a clustered environment, take the logging database out of the DAG before running psconfig and make sure backups are not running.
Post a Comment