Upgrade Blocked Sharepoint 2013
- Sharepoint 2013 Upgrade Available
- Upgrade Blocked Sharepoint 2013 Version
- Upgrade Blocked Sharepoint 2013 Email
Per http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx#hwLocServers, support for stretch farm topologies SharePoint 2013 was unsupported. As a result of our continuous efforts to review and update our product performance and capacity boundaries, we are pleased to announce supportability for a
limited set of stretch farm topologies under the definition of distributed topologies. All of these topologies are based on a prerequisite of minimal (< 1ms) latency between components of the farm (see also https://technet.microsoft.com/en-us/library/cc748824(v=office.15).aspx#CfgStretchedFarm).
Topologies that do not meet this definition remain unsupported and are not under consideration for review at this time.
Frequently Asked Questions
On your Windows desktop screen, click Start Administrative Tools SharePoint 2013 Central Administration. Run it as an administrator to have the elevated privileges. You will see the screenshot given below. Central Admin is configured under the categories given above. On the target server, open SharePoint 2013 Management Shell. From the SharePoint 2013 management Shell, execute the following command: Mount-SPContentDatabase -Name DatabaseName -WebApplication URL This command will mount the database and upgrade it to SharePoint 2013. Enter your site and verify that it's working. Step#1 – Attach the SharePoint 2013 content database to the new database server. This step only applies if you are also migrating to a new database server during the SharePoint 2016 migration process. If you are not changing database servers, skip to step#2 as the content database will already be in place and ready to upgrade. Upgrade Blocked The server is blocked from the upgrade. The current server is installed with latest CU and it will remain blocked until all the SP servers in the farm are installed with the same version.
| Q1 | My customer wants to distribute their topology across one or more distinct geographic boundaries (i.e. between cities, states, provinces), is this supported? |
| A1 | No. |
| Q2 | My customer maintains a logical datacenter comprised of one or more physical buildings on a single site. Is this supported? |
| A2 | Yes, providing there is a highly consistent intra-farm latency of <1ms, 99.9% of the time over a period of ten minutes. (Intra-farm latency is commonly defined as the latency between the web front-end and database servers) |
| Q3 | My customer’s latency exceeds 1ms – what can I do to get them to a supported configuration? |
| A3 | See http://technet.microsoft.com/en-us/library/cc263031.aspx for documentation detailing high availability and disaster recovery topologies possible with SharePoint Server 2013. |
Be aware that it will take a couple of weeks till the the SharePoint 2013 article will be updated as it will have to got through official review and approval process.
For SharePoint 2016 see these articles:
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
Sharepoint 2013 Upgrade Available
I did not face any functional issues but was just annoyed by the status warnings.
Upgrade Blocked Sharepoint 2013 Version
Solution
Upgrade Blocked Sharepoint 2013 Email
Restart IIS