Event 1801 is logged when you add a file share to a continuously available Windows Server 2012 cluster

View products that this article applies to.

Symptoms

When you create a file share on a clustered Windows Server 2012 file server that has the Continuously Available property enabled, the following event is logged:

Source: Microsoft-Windows-SmbServer

Event ID: 1801
Description:
CA failure - Failed to set continuously available property on a new or existing file share as Resume Key filter is not started.

Additionally, the following event may be logged in the ResumeKeyFilter log:

Source: Microsoft-Windows-ResumeKeyFilter

Event ID: 1008

Description:
The filter failed to attach to a volume because the volume supports short names but the filter does not support short names.

Note Event ID 1008 is logged on the cluster node in a traditional file server cluster when the resource group is online. In a scale-out file server cluster, this event is logged on the Cluster Shared Volume (CSV) coordinator node.

↑ Back to the top

Cause

This issue occurs because the file system of the file share that is being added supports short (8.3) file names. However, continuously available file shares do not support short file names.

↑ Back to the top

Resolution

If you use applications that depend on short file names, you cannot use the Continuously Available feature. For more information about the Continuously Available feature, click the following article number to view the article in the Microsoft Knowledge Base:

2709568 New SMB 3.0 features in the Windows Server 2012 file server

If you do not use applications that depend on short file names, disable support for short file names before you enable the Continuously Available property.

How to disable and remove short file names

Note Cluster shared volumes must have a drive letter assigned before you run these commands. To assign a drive letter to a cluster shared volume, go to the "How to assign a drive letter to a volume" section.

To determine whether short file names are enabled, run the following command:
Fsutil 8dot3name query <volume path>
The output shows the global and per-volume settings.
To disable short file name creation on a specific volume, run the following command:
Fsutil 8dot3name set <volume path> 1
To remove short file names from a specific volume, run the following command:
Fsutil 8dot3name strip <volume path>
Note We recommend that you remove the existing short file names from the volume before you enable the Continuously Available property.

Warning If youpermanently remove short file names and do not change the registry keys that point to the short file names, unexpected application failures may occur. These failures include the inability to uninstall an application. We recommend that you first back up your directory or volume before you try to remove short file names.

For more information about the Fsutil8dot3name commands, go to the following Microsoft TechNet website:

More information about the Fsutil 8dot3name commands

How to assign a drive letter to a volume

To assign a drive letter to a volume, follow these steps:

Run Mountvol.exe without parameters to determine the volume name of the cluster shared volume.
Assign a drive letter by using the volume name value that you obtain in step 1. To do this, run the following command:
Mountvol.exe <drive letter>: <volume name>
After you disable short file name creation, remove the mount point. To do this, run the following command:
Mountvol.exe <drive letter>: /D

↑ Back to the top

More Information

For more information about the SMB Transparent Failover feature, go to the following Microsoft website:

Introduction to the SMB Transparent Failover feature

For more information about application compatibility and API support for SMB 3.0, for the Cluster Shared Volume file system, and for the Resilient file system, go to the following Microsoft website:

General information about application compatibility and API support for SMB 3.0, for the Cluster Shared Volume file system, and for the Resilient file system

For more information about file management functions in SMB 3.0, go to the following Microsoft website:

More information about file management functions in SMB 3.0

↑ Back to the top