SharePoint 2013 RTM升级失败

最新推荐文章于 2021-01-30 00:29:59 发布

计算机器

最新推荐文章于 2021-01-30 00:29:59 发布

阅读量1.3k

点赞数

分类专栏： SharePoint 研究

本文链接：https://blog.csdn.net/shrenk/article/details/39093683

版权

SharePoint 研究专栏收录该内容

86 篇文章 1 订阅

订阅专栏

今天想把一个老的环境升级一下，这个环境是SharePoint 2013 server RTM，准备先升级到SP1，于是下载了SP1的安装包“officeserversp2013sp1-kb2817429-fullfile-x64-en-us.exe”，在server上运行，结果出错了，错误信息就是安装失败：“The installation of this package failed”

还好是在虚拟机中，于是回滚到RTM的状态，查了一下微软的文档才发现，升级RTM的时候，必须先安装March 2013 PU:

"Note:
The Server packages for the Feb 2013 CU are contained in the March 2013 PU and will be mandatory requirementfor installing subsequent SharePoint 2013 cumulative updates!!! "

相关信息和下载地址请参考文章：点击打开链接

但是问题是，当我下载March 2013 PU安装的时候，还是同样的失败信息。于是又安装了March 2013 PU和RTM之间的两个升级包，之后才能成功的安装March 2013 PU。安装March 2013 CU之后，运行配置向导失败，log中显示的错误信息是：

Exception: System.ServiceModel.ServerTooBusyException: The HTTP service located at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc is unavailable.  This could be because the service is too busy or because no endpoint was found listening at the specified address. Please ensure that the address is correct and try accessing the service again later. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   --- End of inner exception stack trace ---
    ... ...

竟然提示SecurityTokenServiceApplication/securitytoken.svc不可用，于是查看了一下applicaiton pool，果然SecurityTokenServiceApplicationPool停了，启动之后重新运行配置向导，成功完成升级。完成升级之后的SharePoint 2013 build number是15.0.4481.1005

然后直接安装SP1升级包，成功安装，完成了升级。

这次升级也总结了一个经验，就是在运行配置向导之前，要检查一下SharePoint的Application Pool或者SharePoint的站点是否是运行的。如果是停止的状态，要检查一下World Wide Publishing Service（W3SVC）是否是运行着的。