One of my client was unable to install SQL Server 2014 on a Windows 2012 Cluster. They were using mount points with below the structure. Let us learn about installation error. Setup said it cannot create a file when that file already exists.
- M:\Data_MP
- M:\Log_MP
- M:\System_MP
- M:\Temp_MP
- M:\Backup_MP
Over here, M was 10GB local drive, Data_MP is a SAN disk mounted in the root drive. As we can see they have configured disks from the SAN as mount points. The validation is getting successful, but the SQL installation is failing with below error.
Error description: The resource ‘Cluster Disk 1’ could not be moved from cluster group ‘Available Storage’ to cluster group ‘SQL Server (MSQLSERVER)’. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 183. Description: Cannot create a file when that file already exists
When I looked at the Detail.txt file for more details, the message is same.
WORKAROUND/SOLUTION
There are two workarounds which I found for them
- Pre-create a Windows Cluster group/Role in Cluster and add the disks to that group before starting the setup. During the setup wizard, choose this group for SQL to be installed.
- Mount the mount points in a folder instead of Root drive like below
- M:\UserDB_Data\Data_MP
- M:\UserDB_Log\Log_MP
- M:\SystemDB\System_MP
- M:\TempDB\Temp_MP
- M:\Backup\Backup_MP
Over here, M was 10GB local drive, UserDB_Data is a folder inside M and Data_MP is SAN disk mounted inside folder.
Hope this would help someone in the world!
Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.
2 Comments. Leave new
Excellent workaround
Thanks a lot, It worked properly, even without mount the mount points in a folder instead of Root drive.