SharePoint 2013累积更新-内部版本号未更改 [英] SharePoint 2013 Cumulative Updates - No Change in Build Number

查看:60
本文介绍了SharePoint 2013累积更新-内部版本号未更改的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

任何帮助将不胜感激.我们在更新开发SharePoint 2013服务器场的2018年3月CU时遇到问题. (环境:Windows 2012 Server,SQL 2012和SP 2013)

Any help will be appreciated. We have an issue in updating Mar 2018 CU on development SharePoint 2013 Farm. (Environment: Windows 2012 Server, SQL 2012 and SP 2013)

当前内部版本号: 15.0.4701.1000;                                           构建 尝试更新:   15.0.5015.1000

Current Build Number : 15.0.4701.1000;                                          Build Trying to Update  :  ​15.0.5015.1000

从https://support.microsoft.com/en-us/help/4018302&hl=zh_CN下载了KB4018302和安装时出现的问题

Downloaded KB4018302 from https://support.microsoft.com/en-us/help/4018302  and an issue while installing

问题#1:消息"在系统上找不到产品的预期版本"安装累积更新时.

Issue#1 : Message "The expected version of the product was not found on the system " when installing Cumulative Update.

按照以下说明执行安装,

Installation is stated after executing as below,

运行>> ubersrv2013-kb4018302-fullfile-x64-glb.exe PACKAGE.BYPASS.DETECTION.CHECK = 1

Run >> ubersrv2013-kb4018302-fullfile-x64-glb.exe PACKAGE.BYPASS.DETECTION.CHECK=1

问题2::添加旁路检查后,安装运行了几个小时,但未打开任何配置向导,但从命令行提前运行了psconfig.第4步中的第4步退出,出现以下错误

Issue #2: Installation ran for couple of hours after adding bypass check but no configuration wizard is opened but went a ahead ran psconfig from command line. Step 4 of 4 exited with below error

引发了类型为Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException的异常.其他异常信息:发生了更新冲突,您必须重试此操作.对象SPUpgradeSession Name = Upgrade-20180507-100057-953 由XXXX \ sp_setup在计算机SPServer01上的PSCONFIG(5168)进程中更新.查看跟踪日志以获取有关冲突的更多信息.

An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20180507-100057-953 was updated by XXXX\sp_setup, in the PSCONFIG (5168) process, on machine SPServer01. View the tracing log for more information about the conflict.

紧随其后的文章并再次启动PCONFIG,

Followed below article and started PCONFIG again,

https://blogs.technet.microsoft.com/balasm/2012/05/17/configuration-wizard-failed-an-update-conflict-has-occurred-and-you-must-re-try-this -action/

https://blogs.technet.microsoft.com/balasm/2012/05/17/configuration-wizard-failed-an-update-conflict-has-occurred-and-you-must-re-try-this-action/

此时间配置已完成,但内部版本号未更改.看起来农场上没有安装任何东西.

This time configuration is completed but no change in build number. Looks like nothing installed on farm. 

感谢您的帮助和/或任何建议.

Appreciate for your help and / or any suggestions.

致谢

Arkay

谢谢

推荐答案

从不使用BYPASS.您需要解决无法找到正确版本的消息.这可能表明您从未将SP1应用于SharePoint 2013(及相关产品,如果适用).
Never use BYPASS. You need to resolve the message that it wasn't able to find the proper version. This likely indicates you never applied SP1 to SharePoint 2013 (and associated products, if applicable).


这篇关于SharePoint 2013累积更新-内部版本号未更改的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆