SQL Server 2012 R2升级到SQL Server 2016无法正常启动数据库服务解决方案
原定周末把公司的TFS升级到2018，由于TFS 2018需要SQL Server至少是2016以上版本，所以还需要将原来的SQL Server 2012 R2一并升级。今天早上负责的同事告诉我升级失败了。SQL Server 2016的数据库服务无法正常启动。他期间还尝试修复了一次SQL Server 2016，仍然提示无法正常启动数据库服务。错误提示如下：
Action required:
Use the following information to resolve the error, and then try the setup process again. Feature failure reason:
An error occurred during the setup process of the feature. Error details:
§ Error installing SQL Server Database Engine Services Instance Features
The service did not respond to the start or control request in a timely fashion.
Error code: 0x80004005
Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325 to get help on troubleshooting.
Warning details:
§ Missing or unspecified settings that were configured to default values:
Service SID support has been enabled on the service.
给予的帮助不是很大，先打开事件查看器找找有什么错误信息：
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program SQL Server Windows NT - Bit because of this error. Program: SQL Server Windows NT - Bit
File: The error value is listed in the Additional Data section.
User Action
. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
. If the problem persists, restore the file from a backup copy.
. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data
Error value:
Disk type:
错误提示我们可以选择运行一下磁盘检查，凭经验觉得还是再看一次SQL Server 2016的安装日志，Summary内容如下：
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -
Start time: -- ::
End time: -- ::
Requested action: Repair Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for AS: Use the following information to resolve the error, and then try the setup process again. Machine Properties:
Machine name: SQL
Machine processor count:
OS version: Microsoft Windows Server Datacenter (6.2.)
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: Bit
OS clustered: No Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server MSSQL2 MSSQL11.MSSQL2 Database Engine Services Enterprise Edition 11.2.5058.0 No Yes
SQL Server MSSQL2 MSSQL11.MSSQL2 Full-Text and Semantic Extractions for Search Enterprise Edition 11.2.5058.0 No Yes
SQL Server SSMS Enterprise Edition 11.2.5058.0 No Yes
SQL Server Adv_SSMS Enterprise Edition 11.2.5058.0 No Yes
SQL Server MSSQLSERVER MSSQL13.MSSQLSERVER Database Engine Services Enterprise Edition 13.0.1601.5 No Yes
SQL Server MSSQLSERVER MSSQL13.MSSQLSERVER Full-Text and Semantic Extractions for Search Enterprise Edition 13.0.1601.5 No Yes
SQL Server MSSQLSERVER MSAS13.MSSQLSERVER Analysis Services Enterprise Edition 13.0.1601.5 No Yes
SQL Server MSSQLSERVER MSRS13.MSSQLSERVER Reporting Services - Native Enterprise Edition 13.0.1601.5 No Yes Package properties:
Description: Microsoft SQL Server
ProductName: SQL Server
Type: RTM
Version:
SPLevel:
Installation location: I:\x64\setup\
Installation edition: Enterprise User Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASCONFIGDIR: Config
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASTELSVCACCT: NT Service\SSASTELEMETRY
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: Automatic
CLTSTARTUPTYPE:
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\\Setup Bootstrap\Log\20180723_092704\ConfigurationFile.ini
CTLRSTARTUPTYPE:
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
ENU: true
EXTSVCACCOUNT: <empty>
EXTSVCPASSWORD: <empty>
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTROPENLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT: <empty>
ISTELSVCPASSWORD: <empty>
ISTELSVCSTARTUPTYPE:
MRCACHEDIRECTORY:
QUIET: false
QUIETSIMPLE: false
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLTELSVCACCT: NT Service\SQLTELEMETRY
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: Automatic
SUPPRESSPRIVACYSTATEMENTNOTICE: false
UIMODE: Normal
X86: false Configuration file: C:\Program Files\Microsoft SQL Server\\Setup Bootstrap\Log\20180723_092704\ConfigurationFile.ini Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325 Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325 Feature: Reporting Services - Native
Status: Passed Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Analysis Services
Component error code: 0x84BB0001
Error description: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325 Feature: SQL Browser
Status: Passed Feature: SQL Writer
Status: Passed Feature: SQL Client Connectivity
Status: Passed Feature: SQL Client Connectivity SDK
Status: Passed Feature: Setup Support Files
Status: Passed Rules with failures: Global rules: There are no scenario-specific rules. Rules report file: C:\Program Files\Microsoft SQL Server\\Setup Bootstrap\Log\20180723_092704\SystemConfigurationCheck_Report.htm The following warnings were encountered while configuring settings on your SQL Server. These resources / settings were missing or invalid so default values were used in recreating the missing resources. Please review to make sure they don’t require further customization for your applications: Service SID support has been enabled on the service.
大致意思就是数据库服务无法正常启动，更要命的是Error Help Link点击打开后自动回到了微软官网，没有缩小错误范围的价值。于是继续查看Detail.txt，文件内容比较多只把error和exception作为搜索关键字定位，下面只贴出相关信息（期间学习了一下：查看和阅读 SQL Server 安装程序日志文件）：
() -- :: Slp: The configuration failure category of current exception is ConfigurationFailure
() -- :: Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
() -- :: Slp: System.ComponentModel.Win32Exception (0x80004005): The service did not respond to the start or control request in a timely fashion.
() -- :: Slp: at Microsoft.SqlServer.Configuration.Sco.Service.StartService(String[] startParams)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters, Boolean withFailpoint)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.UpgradeSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean fShutdown)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.Upgrade_ConfigRC(Version fromVersion, EffectiveProperties properties, Boolean shutdownRightAway)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.RepairFailedUpgrade(ConfigActionTiming timing, Dictionary` actionData)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.Repair(ConfigActionTiming timing, Dictionary` actionData, PublicConfigurationBase spcb)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.PrivateConfigurationBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, ConfigBaseAction action, Dictionary` actionData, PublicConfigurationBase spcbCurrent)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, ConfigBaseAction action, Dictionary` actionData, PublicConfigurationBase spcbCurrent)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
() -- :: Slp: The following is an exception stack listing the exceptions in outermost to innermost order
() -- :: Slp: Inner exceptions are being indented
() -- :: Slp:
() -- :: Slp: Exception type: System.ComponentModel.Win32Exception
() -- :: Slp: Message:
() -- :: Slp: The service did not respond to the start or control request in a timely fashion.
() -- :: Slp:
() -- :: Slp: HResult : 0x80004005
() -- :: Slp: Error :
() -- :: Slp: Data:
() -- :: Slp: SQL.Setup.FailureCategory = ConfigurationFailure
() -- :: Slp: WatsonConfigActionData = REPAIR@CONFIGRC@SQL_ENGINE_CORE_INST
() -- :: Slp: WatsonExceptionFeatureIdsActionData = System.String[]
() -- :: Slp: Stack:
() -- :: Slp: at Microsoft.SqlServer.Configuration.Sco.Service.StartService(String[] startParams)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters, Boolean withFailpoint)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.UpgradeSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean fShutdown)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.Upgrade_ConfigRC(Version fromVersion, EffectiveProperties properties, Boolean shutdownRightAway)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.RepairFailedUpgrade(ConfigActionTiming timing, Dictionary` actionData)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.Repair(ConfigActionTiming timing, Dictionary` actionData, PublicConfigurationBase spcb)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.PrivateConfigurationBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, ConfigBaseAction action, Dictionary` actionData, PublicConfigurationBase spcbCurrent)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, ConfigBaseAction action, Dictionary` actionData, PublicConfigurationBase spcbCurrent)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
() -- :: Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
() -- :: Slp: Watson Bucket
Original Parameter Values
看了几个错误日志，总之就是围绕启动服务出错。干脆启动SQL Server单机模式碰碰运气。在cmd里输入：
sqlservr.exe -m
运行后，错误提示："The application was unable to start correctly (0xc0000142)"。还是没有得到进一步的进展，我决定运行Procmon分别抓取正常机器和这台错误机器的执行信息，发现区别就在于错误的机器在读取sqltses.ini后便退出了进程。在这之前werfault相关的操作也进入视野，决定用WinDbg看一下相关的hdmp文件。运行WinDbg并输入：
!analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
******************************************************************************* Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqldk.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqldk.dll
GetUrlPageData2 (WinHttp) failed: . KEY_VALUES_STRING: STACKHASH_ANALYSIS: TIMELINE_ANALYSIS: Timeline: !analyze.Start
Name: <blank>
Time: --23T06::.719Z
Diff: mSec Timeline: Dump.Current
Name: <blank>
Time: --23T05::.0Z
Diff: mSec Timeline: Process.Start
Name: <blank>
Time: --23T05::.0Z
Diff: mSec Timeline: OS.Boot
Name: <blank>
Time: --23T02::.0Z
Diff: mSec DUMP_CLASS: DUMP_QUALIFIER: CONTEXT: (.ecxr)
rax= rbx=00000000000000c4 rcx=00000000ffffffff
rdx= rsi=000000000000009d rdi=000007faeafbce48
rip=000007fb0bd831f3 rsp=0000001803fef100 rbp=
r8= r9= r10=
r11=000007faeb398310 r12=000007faeab52ab0 r13=
r14=000007faeab50000 r15=
iopl= nv up ei pl zr na po nc
cs= ss=002b ds=002b es=002b fs= gs=002b efl=
msvcr120!log10+0x313:
000007fb`0bd831f3 c5e173d034 vpsrlq xmm3,xmm0,34h
Resetting default scope FAULTING_IP:
msvcr120!log10+ [f:\dd\vctools\crt\fpw32\tran\amd64\log10.asm @ ]
000007fb`0bd831f3 c5e173d034 vpsrlq xmm3,xmm0,34h EXCEPTION_RECORD: (.exr -)
ExceptionAddress: 000007fb0bd831f3 (msvcr120!log10+0x0000000000000313)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags:
NumberParameters: DEFAULT_BUCKET_ID: ILLEGAL_INSTRUCTION ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. EXCEPTION_CODE_STR: c000001d WATSON_BKT_PROCSTAMP: 5724ae45 WATSON_BKT_PROCVER: 2015.130.1601.5 WATSON_BKT_MODULE: msvcr120.dll WATSON_BKT_MODSTAMP: 56bc00d3 WATSON_BKT_MODOFFSET: 931f3 WATSON_BKT_MODVER: 12.0.40649.5 MODULE_VER_PRODUCT: Microsoft? Visual Studio? BUILD_VERSION_STRING: 6.2.9200.16384 (win8_rtm.-) MODLIST_WITH_TSCHKSUM_HASH: c6a5860b5b55160212c48b9276e6eba3de41b840 MODLIST_SHA1_HASH: 8ff0cba4b013ab435c80aab51efa92ac767733be NTGLOBALFLAG: PROCESS_BAM_CURRENT_THROTTLED: PROCESS_BAM_PREVIOUS_THROTTLED: APPLICATION_VERIFIER_FLAGS: PRODUCT_TYPE: SUITE_MASK: DUMP_FLAGS: d96 DUMP_TYPE: PROCESS_NAME: unknown ANALYSIS_SESSION_HOST: JUNCHU-XPS ANALYSIS_SESSION_TIME: -- ::15.0719 ANALYSIS_VERSION: 10.0.17712.1000 amd64fre THREAD_ATTRIBUTES:
OS_LOCALE: ENU BUGCHECK_STR: ILLEGAL_INSTRUCTION PRIMARY_PROBLEM_CLASS: ILLEGAL_INSTRUCTION PROBLEM_CLASSES: ID: [0n321]
Type: [@APPLICATION_FAULT_STRING]
Class: Primary
Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
BUCKET_ID
Name: Omit
Data: Add
String: [ILLEGAL_INSTRUCTION]
PID: [Unspecified]
TID: [Unspecified]
Frame: [] LAST_CONTROL_TRANSFER: from 000007faeabdb342 to 000007fb0bd831f3 STACK_TEXT:
`03fef100 000007fa`eabdb342 : `000000dd 000007fa`ea7e2679 `7c0b2ebe 000007fb`1906c113 : msvcr120!log10+0x313
`03fef160 000007fb`0bd1276b : `000000c4 ` `0000009d 000007fb`1905a57e : sqltses!InitializeRoundArrays+0x42
`03fef250 000007fa`eab869d6 : ` `03fef8d0 `03fef8d0 000007fa`ea698920 : msvcr120!_initterm+0x3f
`03fef280 000007fa`eab52b72 : ` `03fef670 ` 000007fa`eab52ab0 : sqltses!CRT_INIT+0x1df
`03fef2c0 000007fb`1905b9be : 000007fa`eab50000 `03fef8d0 ` `041551e0 : sqltses!DllMainCRTStartup+0xb6
`03fef300 000007fb`1907b3fc : `04154f10 000007fa`eab50000 `04154e90 `04154df0 : ntdll!LdrpCallInitRoutine+0x3e
`03fef350 000007fb`1907a88b : `04154f10 `04154f01 `03fef400 000007fb`190c9dd0 : ntdll!LdrpInitializeNode+0x192
`03fef450 000007fb`1907e74e : ` ` `03fef4d0 000007fb`1906aa52 : ntdll!LdrpInitializeGraph+0x6f
`03fef490 000007fb`1907e74e : ` `041523b0 `03fef510 ` : ntdll!LdrpInitializeGraph+0x8d
`03fef4d0 000007fb` : ` ` `03fef550 ` : ntdll!LdrpInitializeGraph+0x8d
`03fef510 000007fb` : `03fef8d0 000007fb`19083ce3 ` 000007f7`7d8b8000 : ntdll!LdrpInitializeProcess+0x1a1b
`03fef810 000007fb`1906c1ae : `03fef8d0 ` 000007f7`7d8b8000 ` : ntdll!_LdrpInitialize+0x1565e
`03fef880 ` : ` ` ` ` : ntdll!LdrInitializeThunk+0xe FAILED_INSTRUCTION_ADDRESS:
msvcr120!log10+ [f:\dd\vctools\crt\fpw32\tran\amd64\log10.asm @ ]
000007fb`0bd831f3 c5e173d034 vpsrlq xmm3,xmm0,34h THREAD_SHA1_HASH_MOD_FUNC: 4bb6d88aecf5843ccdb8c6a0528c256becdc603e THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1732d2863928a4e53da11554f7406e3cc67c47dd THREAD_SHA1_HASH_MOD: b5fd421a131c6f1c77c4a87353281934f433e4d5 FOLLOWUP_IP:
msvcr120!log10+ [f:\dd\vctools\crt\fpw32\tran\amd64\log10.asm @ ]
000007fb`0bd831f3 c5e173d034 vpsrlq xmm3,xmm0,34h FAULT_INSTR_CODE: d073e1c5 FAULTING_SOURCE_LINE: f:\dd\vctools\crt\fpw32\tran\amd64\log10.asm FAULTING_SOURCE_FILE: f:\dd\vctools\crt\fpw32\tran\amd64\log10.asm FAULTING_SOURCE_LINE_NUMBER: FAULTING_SOURCE_CODE:
No source found for 'f:\dd\vctools\crt\fpw32\tran\amd64\log10.asm' SYMBOL_STACK_INDEX: SYMBOL_NAME: msvcr120!log10+ FOLLOWUP_NAME: MachineOwner MODULE_NAME: msvcr120 IMAGE_NAME: msvcr120.dll DEBUG_FLR_IMAGE_TIMESTAMP: 56bc00d3 STACK_COMMAND: dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s ; .ecxr ; kb FAILURE_BUCKET_ID: ILLEGAL_INSTRUCTION_c000001d_msvcr120.dll!log10 BUCKET_ID: ILLEGAL_INSTRUCTION_BAD_IP_msvcr120!log10+ FAILURE_EXCEPTION_CODE: c000001d FAILURE_IMAGE_NAME: msvcr120.dll BUCKET_ID_IMAGE_STR: msvcr120.dll FAILURE_MODULE_NAME: msvcr120 BUCKET_ID_MODULE_STR: msvcr120 FAILURE_FUNCTION_NAME: log10 BUCKET_ID_FUNCTION_STR: log10 BUCKET_ID_OFFSET: BUCKET_ID_MODTIMEDATESTAMP: 56bc00d3 BUCKET_ID_MODCHECKSUM: f6c2b BUCKET_ID_MODVER_STR: 12.0.40649.5 BUCKET_ID_PREFIX_STR: ILLEGAL_INSTRUCTION_BAD_IP_ FAILURE_PROBLEM_CLASS: ILLEGAL_INSTRUCTION FAILURE_SYMBOL_NAME: msvcr120.dll!log10 WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/unknown/2015.130.1601.5/5724ae45/msvcr120.dll/12.0.40649.5/56bc00d3/c000001d/000931f3.htm?Retriage=1 TARGET_TIME: --23T05::.000Z OSBUILD: OSSERVICEPACK: SERVICEPACK_NUMBER: OS_REVISION: OSPLATFORM_TYPE: x64 OSNAME: Windows OSEDITION: Windows Server TerminalServer DataCenter SingleUserTS USER_LCID: OSBUILD_TIMESTAMP: -- :: BUILDDATESTAMP_STR: - BUILDLAB_STR: win8_rtm BUILDOSVER_STR: 6.2.9200.16384 ANALYSIS_SESSION_ELAPSED_TIME: 591b ANALYSIS_SOURCE: UM FAILURE_ID_HASH_STRING: um:illegal_instruction_c000001d_msvcr120.dll!log10 FAILURE_ID_HASH: {5866d3bb-feda-328f-6d8f-83f8512752ce} Followup: MachineOwner
---------
初步看了一下是调用msvcr120!log10出现了错误并提示“illegal instruction”，原来是VC 2013的错误，log10应该是数学库提供的函数。于是打开必应输入关键字"vc2013 log10 Illegal Instruction"，果然是VC 2013的bug，下载对应更新包安装重启计算机问题解决。
官方地址：FIX: Programs that are built in Visual C++ 2013 crash with "Illegal Instruction" exception
SQL Server 2012 R2升级到SQL Server 2016无法正常启动数据库服务解决方案的更多相关文章
- SQL Server 2008 R2升级到SQL Server 2012 SP1
1.建议对生产环境对的数据库升级之前做好备份,以防不测. 2.从SQL Server 2008 R2 升级到SQL Server 2012 SP1,需要先安装SQL Server 2008 R2 的S ...
- Windows Server 2008 R2+SQL Server 2014 R2升级到Windows Server 2016+SQL Server 2016
环境: 操作系统:Windows Server 2008 R2 数据库:SQL Server 2014 因SQL Server 2016可以无域创建AlwaysOn集群,集群只剩下单节点也不会挂掉,故 ...
- 在Windows Server 2012 R2中搭建SQL Server 2012故障转移集群
需要说明的是我们搭建的SQL Server故障转移集群(SQL Server Failover Cluster)是可用性集群,而不是负载均衡集群,其目的是为了保证服务的连续性和可用性,而不是为了提高服 ...
- Windows Server 2012 R2 远程桌面自动设置为不允许连接问题解决方案
用“gpedit.msc”调出策略组设置窗口,在策略组界面点击:计算机配置->管理模块->Windows组件->远程桌面服务->远程桌面会话主机->连接->允许用户 ...
- Server 2012 R2 Standard 安装运行PCS7时出现“无法启动此程序，因为计算机中丢失api-ms-win-crt-runtime-l1-1-0.dll”解决方法
网上看到了这篇文章https://www.jianshu.com/p/21f4bb8b5502,根据思路自己尝试,解决了丢失的问题.提示[计算机中丢失api-ms-win-crt-runtime-l1 ...
- Windows Server 2012 R2在线安装.NET Framework3.5
Windows Server 2012 (R2) 默认没有安装 .NET Framework 3.5,但可以通过在线安装或指定备用源路径方式. 之前在这个 在Win Server 2012中安装.NE ...
- Windows Server 2012 R2安装SqlServer 2016
1.系统安装 微软操作系统 Windows Server 2012 R2 官方原版镜像 Windows Server 2012 R2 是由微软公司(Microsoft)设计开发的新一代的服务器专属操作 ...
- Windows Server 2012 R2
Windows Server 2012 R2 历史上的Server有2003 server, 2008 server, 2012 server windows server 2012 r2对计算机的消 ...
- 来宾账户被视为安全威胁，Windows Server 2012 R2禁用Guest账户
转至:https://baijiahao.baidu.com/s?id=1646111224229327621&wfr=spider&for=pc 简单介绍Windows Server ...
随机推荐
- Scala：Object-Oriented Meets Functional
Have the best of both worlds. Construct elegant class hierarchies for maximum code reuse and extensi ...
- cocos2d-x项目创建和打包
1.创建C++的cocos2d-x项目:cocos new test_cpp02 -p com.benmutou.helloWorld -l cpp -d projects C++未编译目录: C++ ...
- CentOS7 下 keepalived 的安装和配置
安装前准备:yum -y install gcc gcc-c++ autoconf automake make yum -y install zlib zlib-devel openssl opens ...
- 64位电脑上启动程序出现丢失MSVCR110.dll的解决办法
启动程序报错如下: 无法启动此程序,因为计算机中丢失MSVCR110.dll.尝试重新安装该程序以解决此问题. 应该很容易就搜索到,缺少这样的dll文件,是没有安装Visual C++ Redistr ...
- [Python设计模式] 第6章 衣服搭配系统——装饰模式
github地址:https://github.com/cheesezh/python_design_patterns 题目 设计一个控制台程序,可以给人搭配嘻哈风格(T恤,垮裤,运动鞋)或白领风格( ...
- BCD码干什么用的？
二进制编码的十进制(Binary Coded Decimal,BCD)数据类型在计算机系统中已经存在很久了.BCD格式经常用于简化对使用十进制数字的设备(比如必须向人显示数字的设备,如时钟和计时器)的 ...
- Spark机器学习(10)：ALS交替最小二乘算法
1. Alternating Least Square ALS(Alternating Least Square),交替最小二乘法.在机器学习中,特指使用最小二乘法的一种协同推荐算法.如下图所示,u表 ...
- windows 系统中的 afd 驱动
afd 的全称是 Ancillary Function Driver for WinSock,是 windows 系统网络部分的核心工具.同 Linux 类似,windows 的 socket 最终也 ...
- gcc下inline的一个问题
今天发现一个问题,与inline有关,也与编译时候是不是优化有关. 大概问题可以用下面的代码来描述: 先写一个libtest1,代码如下 libtest1.h #ifndef LIBTEST_H #d ...
- 移除list中null元素
查询结果为null, list.size()却是1 移除该null元素 totalList.removeAll(Collections.singleton(null));