首页 新闻 搜索 专区 学院

SQL Server (MSSQLSERVER) 服务启动不了,系统日志显示由于下列服务特定错误而终止: 找不到映像文件中指定的资源名。

0
悬赏园豆:50 [已解决问题] 解决于 2020-04-21 11:32

系统日志报错:
SQL Server (MSSQLSERVER) 服务由于下列服务特定错误而终止: 找不到映像文件中指定的资源名。

SQL Server日志文件报错

2020-01-19 09:32:41.96 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)

2020-01-19 09:32:41.96 Server (c) Microsoft Corporation.
2020-01-19 09:32:41.96 Server All rights reserved.
2020-01-19 09:32:41.96 Server Server process ID is 700.
2020-01-19 09:32:41.96 Server System Manufacturer: 'Alibaba Cloud', System Model: 'Alibaba Cloud ECS'.
2020-01-19 09:32:41.96 Server Authentication mode is MIXED.
2020-01-19 09:32:41.96 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2020-01-19 09:32:41.96 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2020-01-19 09:32:41.96 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2020-01-19 09:32:41.96 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2020-01-19 09:32:42.07 服务器 SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2020-01-19 09:32:42.07 服务器 SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2020-01-19 09:32:42.07 服务器 Detected 7918 MB of RAM. This is an informational message; no user action is required.
2020-01-19 09:32:42.07 服务器 Using conventional memory in the memory manager.
2020-01-19 09:32:42.19 服务器 This instance of SQL Server last reported using a process ID of 1640 at 2020/1/19 9:31:36 (local) 2020/1/19 1:31:36 (UTC). This is an informational message only; no user action is required.
2020-01-19 09:32:42.20 服务器 Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2020-01-19 09:32:42.20 服务器 Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2020-01-19 09:32:42.22 spid5s Starting up database 'master'.
2020-01-19 09:32:42.24 spid5s 29 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2020-01-19 09:32:42.26 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2020-01-19 09:32:42.30 Server CLR version v4.0.30319 loaded.
2020-01-19 09:32:42.31 spid5s Resource governor reconfiguration succeeded.
2020-01-19 09:32:42.31 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2020-01-19 09:32:42.31 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2020-01-19 09:32:42.34 spid5s SQL Trace ID 1 was started by login "sa".
2020-01-19 09:32:42.35 spid5s Server name is 'iZhbuqq1d6ox80Z'. This is an informational message only. No user action is required.
2020-01-19 09:32:42.36 服务器 Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319.
2020-01-19 09:32:42.39 spid10s A self-generated certificate was successfully loaded for encryption.
2020-01-19 09:32:42.39 spid10s Server is listening on [ 'any' <ipv6> 1433].
2020-01-19 09:32:42.39 spid10s Server is listening on [ 'any' <ipv4> 1433].
2020-01-19 09:32:42.39 spid10s Server local connection provider is ready to accept connection on [ \.\pipe\SQLLocal\MSSQLSERVER ].
2020-01-19 09:32:42.39 spid10s Server named pipe provider is ready to accept connection on [ \.\pipe\sql\query ].
2020-01-19 09:32:42.39 服务器 Server is listening on [ ::1 <ipv6> 1434].
2020-01-19 09:32:42.39 服务器 Server is listening on [ 127.0.0.1 <ipv4> 1434].
2020-01-19 09:32:42.39 服务器 Dedicated admin connection support was established for listening locally on port 1434.
2020-01-19 09:32:42.39 spid10s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2020-01-19 09:32:42.39 服务器 SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2020-01-19 09:32:42.40 服务器 The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/iZhbuqq1d6ox80Z ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2020-01-19 09:32:42.40 服务器 The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/iZhbuqq1d6ox80Z:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2020-01-19 09:32:42.49 spid11s A new instance of the full-text filter daemon host process has been successfully started.
2020-01-19 09:32:42.58 spid15s Starting up database 'EstarCompetition'.
2020-01-19 09:32:42.58 spid14s Starting up database 'msdb'.
2020-01-19 09:32:42.58 spid6s Starting up database 'mssqlsystemresource'.
2020-01-19 09:32:42.58 spid16s Starting up database 'EstarCompetition_Test'.
2020-01-19 09:32:42.59 spid6s The resource database build version is 11.00.2100. This is an informational message only. No user action is required.
2020-01-19 09:32:42.63 spid6s Starting up database 'model'.
2020-01-19 09:32:42.66 spid6s Clearing tempdb database.
2020-01-19 09:32:42.66 spid6s Error: 5123, Severity: 16, State: 1.
2020-01-19 09:32:42.66 spid6s CREATE FILE encountered operating system error 5(拒绝访问。) while attempting to open or create the physical file 'D:\SqlServerAutomaticBak\DATA'.
2020-01-19 09:32:42.67 spid6s Error: 17204, Severity: 16, State: 1.
2020-01-19 09:32:42.67 spid6s FCB::Open failed: Could not open file D:\SqlServerAutomaticBak\DATA for file number 1. OS error: 5(拒绝访问。).
2020-01-19 09:32:42.67 spid6s Error: 5120, Severity: 16, State: 101.
2020-01-19 09:32:42.67 spid6s Unable to open the physical file "D:\SqlServerAutomaticBak\DATA". Operating system error 5: "5(拒绝访问。)".
2020-01-19 09:32:42.67 spid6s Error: 1802, Severity: 16, State: 4.
2020-01-19 09:32:42.67 spid6s CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2020-01-19 09:32:42.67 spid6s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2020-01-19 09:32:42.67 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2020-01-19 09:32:43.71 spid6s Error: 25725, Severity: 16, State: 1.
2020-01-19 09:32:43.71 spid6s An error occurred while trying to flush all running Extended Event sessions. Some events may be lost.

已经对D:\SqlServerAutomaticBak\DATA添加了everyone完全控制权限和MSSQLSERVER完全控制权限

xiaojunjor的主页 xiaojunjor | 初学一级 | 园豆:108
提问于:2020-01-19 09:35
< >
分享
最佳答案
0

管理员权限运行服务

收获园豆:20
不知道风往哪儿吹 | 小虾三级 |园豆:653 | 2020-01-20 11:59
其他回答(4)
1

用管理员身份打开cmd

收获园豆:10
小小咸鱼YwY | 园豆:1548 (小虾三级) | 2020-01-19 09:39
0

貌似1/2楼说的没有这么简单吧

收获园豆:10
数据酷软件 | 园豆:128 (初学一级) | 2020-01-20 15:04
0

1、建议在win Server版本上安装SQL Server,我安装过这么多次了,没出现过这个问题。。。
2、安装高级版本的SQL Server,这样出现问题的概率比较低。。。

收获园豆:10
lzhdim | 园豆:654 (小虾三级) | 2020-01-24 18:28
0

问题已经解决了,忘记来说一下了
说一下问题产生的原因

临时数据库tempdb占有磁盘空间太大了,我更改了一下位置

更改位置的时候只选择了地址,没有设置文件名,导致了这个错误

使用cmd开启服务,然后重新设置正确的文件地址后解决问题

xiaojunjor | 园豆:108 (初学一级) | 2020-04-21 11:31
清除回答草稿
   您需要登录以后才能回答,未注册用户请先注册