故障转移时,无法使SQL Server资源联机在群集节点上。 [英] Can't bring the SQL Server resource online On Cluster Node when fail over .
问题描述
我可以' t使SQL Server资源联机上网 节点2在节点1上正常工作。
我可以看到事件日志中的以下错误。
来自源MSSQLSERVER的事件ID 19019的描述不能是找到。引发此事件的组件未安装在本地计算机上,或者安装已损坏。您可以在本地计算机上安装或修复
组件。
The description for Event ID 19019 from source MSSQLSERVER cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the
component on the local computer.
如果事件源自另一台计算机,则必须随事件一起保存显示信息。
事件中包含以下信息:
[sqsrvres] OnlineThread:错误2使资源联机。
SQL错误: -
SQL Error :-
-d E :\ MSSQL10_50.MSSQLSERVER \ MSSQL \DATA \ master.mdf
-e E:\ MSSQL10_50.MSSQLSERVER \ MSSQL \Log \ERRORLOG
-l E:\ MSSQL10_50.MSSQLSERVER \ MSSQL \ DATA \ mastlog.ldf
2019-02-23 11:19:08.88 Server     SQL Server从正常的优先级基础(= 7)开始。这仅是一条信息性消息。无需用户操作。
2019-02-23 11:19:08.88服务器    检测到16个CPU。这是一条情报信息;无需用户操作。
2019-02-23 11:19:08.88 Server    已启用大量页面扩展。
2019-02-23 11:19:08.88 Server    大页面粒度:2097152
2019-02-23 11:19:08.93 Server    无法使用大页面扩展:无法分配32MB
2019-02-23 11:19:08.93 Server    无法使用大页面扩展:无法分配32MB
2019-02-23 11:19:08.94 Server    无法使用大页面扩展:无法分配32MB
2019-02-23 11:19:09.06 Server    使用锁定页面缓冲池。
2019-02-23 11:19:09.27 Server    使用动态锁定分配。 每个节点初始分配2500个锁定块和5000个锁定所有者块。 这只是一条信息性消息。 无需用户操作。
2019-02-23 11:19:09.27 Server    锁定分区已启用。 这仅是一条信息性消息。无需用户操作。
2019-02-23 11:19:09.30 Server    节点配置:节点0:CPU掩码:0x000000000000ff00:0活动CPU掩码:0x000000000000ff00:0。此消息提供此计算机的NUMA配置的说明。这是一条信息性消息
。无需用户操作。
2019-02-23 11:19:09.30 Server    节点配置:节点1:CPU掩码:0x00000000000000ff:0活动CPU掩码:0x00000000000000ff:0。此消息提供此计算机的NUMA配置的说明。这是一条信息性消息
。无需用户操作。
2019-02-23 11:19:09.35 spid9s    启动数据库'master'。
2019-02-23 11:19:09.43 spid9s    恢复正在数据库'master'中写入检查点(1)。这仅是一条信息性消息。无需用户操作。
2019-02-23 11:19:09.50 spid9s    数据库'master'的CHECKDB在2018-01-30 00:04:22.590(当地时间)完成且没有错误。这只是一条信息性消息;无需用户操作。
2019-02-23 11:19:09.53 spid9s    资源调控器重新配置成功。
2019-02-23 11:19:09.53 spid9s     SQL Server Audit正在启动审核。这是一条情报信息。无需用户操作。
2019-02-23 11:19:09.53 spid9s     SQL Server Audit已启动审核。这是一条情报信息。无需用户操作。
2019-02-23 11:19:09.53 spid9s     FILESTREAM:有效级别= 0,配置级别= 0,文件系统访问共享名称='MSSQLSERVER'。
$
2019-02-23 11:19:09.56 spid9s     SQL跟踪ID 1由登录"sa"启动。
2019-02-23 11:19:09.57 spid9s    启动数据库'mssqlsystemresource'。
2019-02-23 11:19:09.58 spid9s    资源数据库构建版本为10.50.6000。这仅是一条信息性消息。无需用户操作。
2019-02-23 11:19:09.88 spid9s    服务器名称为"1V01"。这仅是一条信息性消息。无需用户操作。
2019-02-23 11:19:09.88 spid9s    运行服务器的本地节点的NETBIOS名称是"NodeA"。这仅是一条信息性消息。无需用户操作。
2019-02-23 11:19:09.88 spid12s   启动数据库'模型'。
2019-02-23 11:19:10.05 Server    已成功加载自生成的证书以进行加密。
2019-02-23 11:19:10.09 spid12s   CHECKDB数据库'model'在2016-06-17 02:01:06.790(当地时间)完成且没有错误。这只是一条信息性消息;无需用户操作。
2019-02-23 11:19:10.10 spid12s   清除tempdb数据库。
2019-02-23 11:19:10.17 Server &NBSP; &NBSP;服务器正在监听[10.10.10.1< ipv4> 1433]。
2019-02-23 11:19:10.17服务器 &NBSP; &NBSP;服务器本地连接提供程序已准备好接受[\\.\pipe\SQLLocal \ MSSQLSERVER]上的连接。
2019-02-23 11:19:10.17 Server &NBSP; &NBSP;服务器命名管道提供程序已准备好接受[\\.\pipe\ $$ \ V01 \sql\query]上的连接。
2019-02-23 11:19 :10.27 spid12s &NBSP; 启动数据库'tempdb'。
2019-02-23 11:19:10.33 spid15s &NBSP; 已成功启动全文过滤器守护程序主机进程的新实例。
2019-02-23 11:19:10.35 spid16s &NBSP; Service Broker协议传输已禁用或未配置。
2019-02-23 11:19:10.35 spid16s &NBSP; 数据库镜像协议传输已禁用或未配置。
2019-02-23 11:19:10.35 spid16s &NBSP; Service Broker经理已经开始。
-d E:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e E:\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l E:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2019-02-23 11:19:08.88 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-02-23 11:19:08.88 Server Detected 16 CPUs. This is an informational message; no user action is required.
2019-02-23 11:19:08.88 Server Large Page Extensions enabled.
2019-02-23 11:19:08.88 Server Large Page Granularity: 2097152
2019-02-23 11:19:08.93 Server Cannot use Large Page Extensions: Failed to allocate 32MB
2019-02-23 11:19:08.93 Server Cannot use Large Page Extensions: Failed to allocate 32MB
2019-02-23 11:19:08.94 Server Cannot use Large Page Extensions: Failed to allocate 32MB
2019-02-23 11:19:09.06 Server Using locked pages for buffer pool.
2019-02-23 11:19:09.27 Server 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.
2019-02-23 11:19:09.27 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2019-02-23 11:19:09.30 Server Node configuration: node 0: CPU mask: 0x000000000000ff00:0 Active CPU mask: 0x000000000000ff00:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2019-02-23 11:19:09.30 Server Node configuration: node 1: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2019-02-23 11:19:09.35 spid9s Starting up database 'master'.
2019-02-23 11:19:09.43 spid9s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2019-02-23 11:19:09.50 spid9s CHECKDB for database 'master' finished without errors on 2018-01-30 00:04:22.590 (local time). This is an informational message only; no user action is required.
2019-02-23 11:19:09.53 spid9s Resource governor reconfiguration succeeded.
2019-02-23 11:19:09.53 spid9s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-02-23 11:19:09.53 spid9s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-02-23 11:19:09.53 spid9s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2019-02-23 11:19:09.56 spid9s SQL Trace ID 1 was started by login "sa".
2019-02-23 11:19:09.57 spid9s Starting up database 'mssqlsystemresource'.
2019-02-23 11:19:09.58 spid9s The resource database build version is 10.50.6000. This is an informational message only. No user action is required.
2019-02-23 11:19:09.88 spid9s Server name is '1V01'. This is an informational message only. No user action is required.
2019-02-23 11:19:09.88 spid9s The NETBIOS name of the local node that is running the server is 'NodeA'. This is an informational message only. No user action is required.
2019-02-23 11:19:09.88 spid12s Starting up database 'model'.
2019-02-23 11:19:10.05 Server A self-generated certificate was successfully loaded for encryption.
2019-02-23 11:19:10.09 spid12s CHECKDB for database 'model' finished without errors on 2016-06-17 02:01:06.790 (local time). This is an informational message only; no user action is required.
2019-02-23 11:19:10.10 spid12s Clearing tempdb database.
2019-02-23 11:19:10.17 Server Server is listening on [ 10.10.10.1 <ipv4> 1433].
2019-02-23 11:19:10.17 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2019-02-23 11:19:10.17 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\V01\sql\query ].
2019-02-23 11:19:10.27 spid12s Starting up database 'tempdb'.
2019-02-23 11:19:10.33 spid15s A new instance of the full-text filter daemon host process has been successfully started.
2019-02-23 11:19:10.35 spid16s The Service Broker protocol transport is disabled or not configured.
2019-02-23 11:19:10.35 spid16s The Database Mirroring protocol transport is disabled or not configured.
2019-02-23 11:19:10.35 spid16s Service Broker manager has started.
2019-02-23 11:19:12.32 Server &NBSP; &NBSP; SQL Server网络接口库无法注册SQL Server服务的服务主体名称(SPN)。错误:0x202b,状态:15。未注册SPN可能导致集成身份验证
回退到NTLM而不是Kerberos。这是一条情报信息。只有在身份验证策略要求Kerberos身份验证时才需要采取进一步措施。
2019-02-23 11:19:12.32 Server &NBSP; &NBSP; SQL Server现在已准备好进行客户端连接。这是一条情报信息;无需用户操作。
2019-02-23 11:19:23.84 spid52 &NBSP; &NBSP;配置选项'show advanced options'从0更改为1.运行RECONFIGURE语句进行安装。
2019-02-23 11:19:23.84 spid52 &NBSP; &NBSP; FILESTREAM:有效级别= 0,配置级别= 0,文件系统访问共享名称='MSSQLSERVER'。
$
2019-02-23 11:19:23.84 spid52 &NBSP; &NBSP;配置选项'Agent XPs'从0更改为1.运行RECONFIGURE语句进行安装。
2019-02-23 11:19:23.84 spid52 &NBSP; &NBSP; FILESTREAM:有效级别= 0,配置级别= 0,文件系统访问共享名称='MSSQLSERVER'。
$
2019-02-23 11:19:23.85 spid52 &NBSP; &NBSP;配置选项'show advanced options'从1更改为0.运行RECONFIGURE语句进行安装。
2019-02-23 11:19:23.85 spid52 &NBSP; &NBSP; FILESTREAM:有效级别= 0,配置级别= 0,文件系统访问共享名称='MSSQLSERVER'。
$
2019-02-23 11:19:24.15 spid52 &NBSP; &NBSP;试图将库'xpsqlbot.dll'加载到内存中。这仅是一条信息性消息。无需用户操作。
2019-02-23 11:19:24.16 spid52 &NBSP; &NBSP;使用'xpsqlbot.dll'版本'2009.100.1600'执行扩展存储过程'xp_qv'。这只是一条信息性消息;无需用户操作。
2019-02-23 11:19:24.27 spid52 &NBSP; &NBSP;试图将库'xpstar.dll'加载到内存中。这仅是一条信息性消息。无需用户操作。
2019-02-23 11:19:24.28 spid52 &NBSP; &NBSP;使用'xpstar.dll'版本'2009.100.1600'执行扩展存储过程'xp_instance_regread'。这只是一条信息性消息;无需用户操作。
2019-02-23 11:19:24.32 spid52 &NBSP; &NBSP;试图将库'xplog70.dll'加载到内存中。这仅是一条信息性消息。无需用户操作。
2019-02-23 11:19:24.33 spid52 &NBSP; &NBSP;使用'xplog70.dll'版本'2009.100.6000'执行扩展存储过程'xp_msver'。这只是一条信息性消息;无需用户操作。
2019-02-23 11:27:24.29 spid53 &NBSP; &NBSP;配置选项'show advanced options'从0更改为1.运行RECONFIGURE语句进行安装。
2019-02-23 11:27:24.29 spid53 &NBSP; &NBSP; FILESTREAM:有效级别= 0,配置级别= 0,文件系统访问共享名称='MSSQLSERVER'。
$
2019-02-23 11:27:24.29 spid53 &NBSP; &NBSP;配置选项'Agent XPs'从1更改为0.运行RECONFIGURE语句进行安装。
2019-02-23 11:27:24.29 spid53 &NBSP; &NBSP; FILESTREAM:有效级别= 0,配置级别= 0,文件系统访问共享名称='MSSQLSERVER'。
$
2019-02-23 11:27:24.30 spid53 &NBSP; &NBSP;配置选项'show advanced options'从1更改为0.运行RECONFIGURE语句进行安装。
2019-02-23 11:27:24.30 spid53 &NBSP; &NBSP; FILESTREAM:有效级别= 0,配置级别= 0,文件系统访问共享名称='MSSQLSERVER'。
$
2019-02-23 11:27:26.29 spid16s &NBSP; Service Broker经理已经关闭。
2019-02-23 11:27:26.39 spid9s &NBSP; &NBSP; SQL Server正在终止以响应来自服务控制管理器的"停止"请求。这仅是一条信息性消息。无需用户操作。
2019-02-23 11:27:26.39 spid9s &NBSP; &NBSP;由于服务器关闭,SQL Trace已停止。跟踪ID ='1'。这只是一条信息性消息;不需要用户操作。
2019-02-23 11:19:12.32 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x202b, state: 15. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2019-02-23 11:19:12.32 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-02-23 11:19:23.84 spid52 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2019-02-23 11:19:23.84 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2019-02-23 11:19:23.84 spid52 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2019-02-23 11:19:23.84 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2019-02-23 11:19:23.85 spid52 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2019-02-23 11:19:23.85 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2019-02-23 11:19:24.15 spid52 Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2019-02-23 11:19:24.16 spid52 Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2019-02-23 11:19:24.27 spid52 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2019-02-23 11:19:24.28 spid52 Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2019-02-23 11:19:24.32 spid52 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2019-02-23 11:19:24.33 spid52 Using 'xplog70.dll' version '2009.100.6000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2019-02-23 11:27:24.29 spid53 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2019-02-23 11:27:24.29 spid53 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2019-02-23 11:27:24.29 spid53 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
2019-02-23 11:27:24.29 spid53 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2019-02-23 11:27:24.30 spid53 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2019-02-23 11:27:24.30 spid53 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2019-02-23 11:27:26.29 spid16s Service Broker manager has shut down.
2019-02-23 11:27:26.39 spid9s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2019-02-23 11:27:26.39 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
你可以帮我解决这个问题。
Could you Please help me on this issue.
推荐答案
我怀疑你有在第二个节点中的配置管理器中创建的别名,该别名指向错误的SQL或配置不正确。
I suspect you have an alias created in you configuration manager in 2nd node that is either pointing to wrong SQL or configured incorrectly.
检查是否创建了任何别名。打开SQL Server配置管理器 - > "SQL Native Client XX配置(32位)"和"SQL Native Client XX配置"和"SQL Native Client XX配置"。 - >别名。纠正或删除它,然后尝试故障转移。
Check if there are any Aliases created. Open SQL Server configuration manager -> "SQL Native Client XX Configuration (32 bit)" and "SQL Native Client XX Configuration" -> Aliases. Correct it or remove it and then try failing over.
这篇关于故障转移时,无法使SQL Server资源联机在群集节点上。的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!