大网数据广告活动
故障转移群集

Can't bring a clustered resource online troubleshooting guidance

· 52CE 我爱测

Provides guidance for when a clustered resource fails to come online in a Windows-based failover cluster

[!div class="nextstepaction"] <a href="https://vsa.services.microsoft.com/v1.0/?partnerId=7d74cf73-5217-4008-833f-87a1a278f2cb&flowId=DMC&initialQuery=31806238" target='_blank'>Try our Virtual Agent</a> - It can help you quickly identify and fix common issues when a resource fails to come online.

This guidance is designed to get you started on troubleshooting issues where clustered resources can't be brought online in a Windows-based cluster environment.

Troubleshooting checklist

  1. When a resource fails to come online, Event ID 1069 is logged on the server that's hosting the resource of concern:

    Error 1069 Microsoft-Windows-FailoverClustering Cluster resource '<Name of the Resource>' of type '<Resource Type>' in clustered role '<Available Storage>' failed.

  2. Check the System event log for the Event ID, and then check if other errors or warnings are logged. For example:

    • If a physical disk resource can't come online, check for disk-related errors or warnings. For example, Event ID 129 (bus reset) or Event ID 153 (IO retried).

    • If a network name resource can't come online, check for DNS-related entries.

    • If an IP address resource can't come online, check for NIC-related events, errors, or warnings.

  3. If nothing except Event ID 1069 is logged, review the cluster log for further troubleshooting. Open an elevated PowerShell prompt and run the following cmdlet:

    Get-ClusterLog -Destination C:\temp
    

    [!NOTE] This cmdlet will generate the cluster logs on all cluster members and copy them to the C:\temp folder on the server where the cmdlet was executed.

  4. Search for strings in the cluster log that might correlate with Event ID 1069:

    [RCM] rcm::RcmResource::HandleFailure
    [RHS] Online for resource
    OnlineThread: Error <Code> bringing resource online.
    [RHS] RhsCall::DeadlockMonitor: Call ONLINERESOURCE
    

    [!NOTE] The placeholder <Code> represents the error code and can differ depending on the issue.

Common support scenarios

Data collection

Before contacting Microsoft Support, you can gather information about the issue.

Prerequisites

  1. TSS must be executed in the context of an account with admin rights on the local system, and EULA must be accepted (once EULA is accepted, TSS won't prompt it again).

  2. We recommend that the local machine uses the RemoteSigned PowerShell execution policy.

Note: In case the current PowerShell execution policy doesn't allow running TSS, the following actions could be taken:

  • Set RemoteSigned for the Process level and run the following cmdlet:

    PS C:\> Set-ExecutionPolicy -scope Process -ExecutionPolicy RemoteSigned

  • Verify if the change has taken effect, run the following cmdlet:

    PS C:\> Get-ExecutionPolicy -List

Since the Process level permissions only apply to the current PowerShell session, once the given PowerShell window in which TSS runs is closed, the assigned permission for the Process level will also go back to the previously configured state.

Gather key information before you contact Microsoft Support

  1. Download TSS and unzip it to the C:\tss_tool folder.

  2. Open an elevated PowerShell prompt and change the directory to the C:\tss_tool folder.

  3. Start the trace by running the cmdlet on the source and destination nodes.

    .\Get-psSDP.ps1
    

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors (upstream author metadata: kaushika-msft). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。