SMB File Share Storage Failover Cluster "path is not valid folder path"

I am having an issue that I am scratching my head over. So I have setup a 3 node Hyper-V host cluster that I am attempting to use SMB File Share storage for the shared storage medium. I have been trying to migrate a virtual machine from one of the nodes
local storage into the file share using System Center VMM 2012 R2 with UR5 however I keep getting the message "The specified path is not a valid folder path on node2.domain.com" for the storage that VMM automatically selects for placement of files
from the migration. However what is odd is to the same file share for storage I can do a new deployment of a virtual machine to the same cluster with the same shares; I can also delete a virtual machine from the share fine; the file share for the virtual machine
I library I am deploying machines from is the same server as the file shares for the cluster that I am deploying to so maybe that is why that succeeds; if I try to move the recently deployed VM from one file share to another for storage same error comes up.
The three nodes all reference the same file server, which is just one file server for the storage, and the shares were created in VMM and as such the file share permissions were setup by VMM so they should be sufficient. I have also attempted this with both
delegation of CIFS and without through AD (trust to specified computers with CIFS, Hyper-V Replica and Microsoft Virtual Console Service via Kerberos only).
I am stumped as to what to check next or how to get this working and would appreciate any guidance anyone can give towards a resolution for this problem.

Jeff,
Thanks for reporting this.
There's an known issue with UR5 that VMM gives wrong error when deploying a HAVM onto a SMB share. In that situation, VMM complains "Invalid folder path".
To confirm you are hitting the same issue, would you kindly let me know:
1. Are you trying to migrate a HighlyAvailable VM onto the SMB share?
2. On UI of "Migrate Storage Wizard", if you click "Browse", do you see the target file share showing up in "Select Destination Folder" dialog?
3. By "the three nodes all reference the same file server", I assume you added the target file share onto the list of File Share Storage thru the cluster's properties UI. If so, please go to the UI and check whether the access status shows
green there.
4. By "local storage", do you mean "local disk"? Or a shared LUN from any array? I assume it's not "available storage" or "CSV" of the cluster. Please double confirm.
Note: If we are sure hitting the known issue, I will later re-direct you to a hotfix. But let's make sure it is the issue first.
Look forward to your reply.

Similar Messages

File Monitor - Not working properly on SMB file share

The "File Monitor" does not trigger on SMB file share, i think this might be a bug.
I have tried the same "File Monitor" on a windows share, and it works like intended. However, when I use the same runbook on a Solaris SMB share, it does not trigger properly. It triggers when I delete or rename a file, but not any thing else (like
create, changed, etc) I have turned all the triggers on just to see what actually makes it trigger...
I'm using specified authentication (domain user and password)
The SMB folder is shared on a Solaris (SunOS 5.10).
Can anyone confirm that they also have this problem?
Is there a patch to fix this? Thanks.

Can someone please verify that they also have this problem?
Thanks.

Flat file connection: The file name "\server\share\path\file.txt" specified in the connection was not valid

I'm trying to execute a SSIS package via SQL agent with a flat file source - however it fails with Code: 0xC001401E The file name "\server\share\path\file.txt" specified in the connection was not valid.
It appears that the problem is with the rights of the user that's running the package (it's a proxy account). If I use a higher-privelege account (domain admin) to run the package it completes successfully. But this is not a long-term solution, and I can't
see a reason why the user doesn't have rights to the file. The effective permissions of the file and parent folder both give the user full control. The user has full control over the share as well. The user can access the file (copy, etc) outside the SSIS
package.
Running the package manually via DTExec gives me the same error - I've tried 32 and 64bit versions with the same result. But running as a domain admin works correctly every time.
I feel like I've been beating my head against a brick wall on this one... Is there some sort of magic permissions, file or otherwise, that are required to use a flat file target in an SSIS package?

Hi Rossco150,
I have tried to reproduce the issue in my test environment (Windows Server 2012 R2 + SQL Server 2008 R2), however, everything goes well with the permission settings as you mentioned. In my test, the permissions of the folders are set as follows:
\\ServerName\Temp --- Read
\\ServerName\Temp\Source --- No access
\\ServerName\Temp\Source\Flat Files --- Full control
I suspect that your permission settings on the folders are not absolutely as you said above. Could you double check the permission settings on each level of the folder hierarchy? In addition, check the “Execute as user” information from job history to make
sure the job was running in the proxy security context indeed. Which version of SSIS are you using? If possible, I suggest that you install the latest Service Pack for you SQL Server or even install the latest CU patch.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

Selecting VHDx as storage for File Server Role (Failover Cluster 2012 R2)

Is it possible to select an already existing (offline) VHD or VHDX as storage when creating the "File Server" role? Reason I want to do that is because I already have a file server setup as a virtual machine and causing issues so my company
decided to make the change towards a File Server role.
Thank you
David

Hi David,
Do you mean you configured it to file server failover cluster via "High Availability Wizard" ?
I think you need to choose a shared volume between two nodes to achieve high availability .
Please refer to following link :
http://technet.microsoft.com/en-us/library/cc731844(v=WS.10).aspx
If you do not select a shared volume , I think there is no difference than sharing a mounted VHDX file on a standalone file server .
I would suggest to copy these files to CSV and share them .
Hope it helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Powershell: Set Access Based Enumeration on share in Failover Cluster

Hi guys,
I'm facing the following problem. Below you see my script to create a shared folder. (My folder share is visible in failover cluster manager, underneath clustergroup TESTSTO01.)
Now I need to enable Access Based Enumeration on this share. Has anyone a clue how to do that in powershell? (Version 2).
I also need to make sure that the files and programs are not available offline.
Thanks in advance!
$SHARE_READ = 1179817 # 100100000000010101001
$SHARE_CHANGE = 1245631 # 100110000000100010110
$SHARE_FULL = 2032127 # 111110000000111111111
$SHARE_NONE = 1 # 000000000000000000001
$ACETYPE_ACCESS_ALLOWED = 0
$ACETYPE_ACCESS_DENIED = 1
$ACETYPE_SYSTEM_AUDIT = 2
$ACEFLAG_INHERIT_ACE = 2
$ACEFLAG_NO_PROPAGATE_INHERIT_ACE = 4
$ACEFLAG_INHERIT_ONLY_ACE = 8
$ACEFLAG_INHERITED_ACE = 16
$ACEFLAG_VALID_INHERIT_FLAGS = 31
$ACEFLAG_SUCCESSFUL_ACCESS = 64
$ACEFLAG_FAILED_ACCESS = 128
# New Trustee
function New-Trustee($Domain, $User)
$Trustee = ([WMIClass]"\\TESTSTO01\root\cimv2:Win32_Trustee").CreateInstance()
   $Trustee.Domain = $Domain
   $Trustee.Name = $User
   if ($User -eq "Administrators")
{$Trustee.SID = @(1, 2, 0, 0, 0, 0, 0, 5, 32, 0, 0, 0,32,2,0,0)}
else
{$Trustee.SID = @(1, 1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0)}
   return $Trustee
# New ACE
function New-ACE($Domain, $User, $Access, $Type, $Flags)
$ACE = ([WMIClass]"\\TESTSTO01\root\cimv2:Win32_ACE").CreateInstance()
   $ACE.AccessMask = $Access
   $ACE.AceFlags = $Flags
   $ACE.AceType = $Type
   $ACE.Trustee = New-Trustee $Domain $User
   return $ACE
# Get SD
function Get-SD
$sd = ([WMIClass]"\\TESTSTO01\root\cimv2:Win32_SecurityDescriptor").CreateInstance()
$ACE1 = New-ACE -Domain $null -User "Everyone" -Access $SHARE_CHANGE -Type $ACETYPE_ACCESS_ALLOWED -Flags $ACEFLAG_INHERIT_ACE
$ACE2 = New-ACE -Domain $null -User "Administrators" -Access $SHARE_FULL -Type $ACETYPE_ACCESS_ALLOWED -Flags $ACEFLAG_INHERIT_ACE
[System.Management.ManagementObject[]] $DACL = $ACE1, $ACE2
$sd.DACL =$DACL
return $sd
# Create-Share
function Create-Share($ShareName, $Path, $Comment,$Access)
   $checkShare = (Get-WmiObject Win32_Share -Filter "Name='$ShareName'")
   if ($checkShare -ne $null) {
   # "Share exists and will now be deteted!!!"
   get-WmiObject Win32_Share -Filter "Name='$ShareName'" | foreach-object { $_.Delete() }
   $wmishare = [WMIClass] "\\TESTSTO01\ROOT\CIMV2:Win32_Share"
$Access = Get-SD
   $R = $wmishare.Create($Path,$Sharename,0,$null,$Comment,"", $Access)
   if ($R.ReturnValue -ne 0) {
   Write-Error "Error while creating share: " + $R.ReturnValue
   exit
   # Write-Host "Share has been created."
# Create first share with permissons **********************************
$ShareName = "$Company$"
$Path = "$Driveletter" + ":\$Company"
$Comment = ""
$Domain = $Null
Create-Share $ShareName $Path $Comment $Access

Unable to find type [CmdletBinding(SupportsShouldProcess=$TRUE)]: make sure tha
t the assembly containing this type is loaded.
At C:\Script Nathalie\Everyware2.ps1:294 char:45
+ [CmdletBinding(SupportsShouldProcess=$TRUE)] <<<<
   + CategoryInfo : InvalidOperation: (CmdletBinding(S...dProcess=$T
   RUE):String) [], RuntimeException
   + FullyQualifiedErrorId : TypeNotFound
The term 'param' is not recognized as the name of a cmdlet, function, script fi
le, or operable program. Check the spelling of the name, or if a path was inclu
ded, verify that the path is correct and try again.
At C:\Script Nathalie\Everyware2.ps1:295 char:6
+ param <<<< (
   + CategoryInfo : ObjectNotFound: (param:String) [], CommandNotFou
   ndException
   + FullyQualifiedErrorId : CommandNotFoundException
The term 'begin' is not recognized as the name of a cmdlet, function, script fi
le, or operable program. Check the spelling of the name, or if a path was inclu
ded, verify that the path is correct and try again.
At C:\Script Nathalie\Everyware2.ps1:304 char:6
+ begin <<<< {
   + CategoryInfo : ObjectNotFound: (begin:String) [], CommandNotFou
   ndException
   + FullyQualifiedErrorId : CommandNotFoundException
Get-Process : Cannot evaluate parameter 'Name' because its argument is specifie
d as a script block and there is no input. A script block cannot be evaluated w
ithout input.
At C:\Script Nathalie\Everyware2.ps1:331 char:8
+ process <<<< {
   + CategoryInfo : MetadataError: (:) [Get-Process], ParameterBindi
   ngException
   + FullyQualifiedErrorId : ScriptBlockArgumentNoInput,Microsoft.PowerShell.
   Commands.GetProcessCommand
The term 'end' is not recognized as the name of a cmdlet, function, script file
, or operable program. Check the spelling of the name, or if a path was include
d, verify that the path is correct and try again.
At C:\Script Nathalie\Everyware2.ps1:345 char:4
+ end <<<< {
   + CategoryInfo : ObjectNotFound: (end:String) [], CommandNotFound
   Exception
   + FullyQualifiedErrorId : CommandNotFoundException
The term 'set-shareABE' is not recognized as the name of a cmdlet, function, sc
ript file, or operable program. Check the spelling of the name, or if a path wa
s included, verify that the path is correct and try again.
At C:\Script Nathalie\Everyware2.ps1:348 char:13
+ set-shareABE <<<< TESTSTO01 $Company$ -Enable
   + CategoryInfo : ObjectNotFound: (set-shareABE:String) [], Comman
   dNotFoundException
   + FullyQualifiedErrorId : CommandNotFoundException

Migrating single file server to failover cluster file server

Hi,
Currently we have one file server which is our Domain controller also. File Server data stored in SAN storage lun. Users home folders also resides at file server.Now we want to create 2 node failover cluster file server.
Questions:
1)Can we assign same storage lun to failover cluster?
2)Do we need to assign all permissions and storage quota again?
What is the best option to achieve this goal.

Hi,
if you attach the same LUN to the failover cluster the NTFS permission (security tab) are retained because they are stored in the LUN itself
Share permission are lost because they are stored in the registry of the file server. If you have few share with a simple share permission structure, simply recreate them in the cluster. If you have a lot of shares and complex permission tree, you have to
export registry hives related to lanmanserver\shares

Windows 2003 File Share 4 node Cluster: Does Cluster Resources need to be brought offline prior removing / unmapping any LUN's from SAN end?

Hello All,
Recently, on a 4 node Windows 2003 File Share Cluster, we encountered a problem where when trying to remove few shares (that were no longer in use) directly from SAN end crashed the entire Cluster (i.e., other shares also lost their SAN connectivity). I
suppose the Cluster resources need to be brought offline prior removing it from SAN but I've been advised that these shares were not the root and instead a 'mount point' created within the share; and hence there is no need of bringing down any Cluster resources
offline.
Please can someone comment on the above and provide me detailed steps as to how we go about reclaiming SAN space from specific shares on a W2003 Cluster?
p.s., let me know if you need any additional information.
Thanks in advance.

Hi Alex,
The problem started when SAN Support reclaimed few storage LUNs by unmapping them from our clustered file servers. When they reclaimed the unused LUNs, other SAN drives which were there also disappeared causing the unavailability of file shares.
Internet access is not enabled on these servers. Servers in question are running 64-bit Windows Server 2003 Sp2. This is a four node file share cluster. When the unsued LUN's were pulled, the entire Cluster lost its SAN connectivity. Windows cluster service
was not starting on any of the cluster nodes. To resolve the problem all the four cluster nodes were rebooted after which cluster service started on all the cluster nodes and resources came online.
Some of the events at the time of problem occurrence were,
Event ID     : 57
Raw Event ID : 57
Record Nr.   : 25424072
Category     : None
Source       : Ftdisk
Type         : Warning
Generated    : 19.07.2014 10:49:46
Written      : 19.07.2014 10:49:46
Machine      : ********
Message      : The system failed to flush data to the transaction log.
Corruption may occur.
Event ID     : 1209
Raw Event ID : 1209
Record Nr.   : 25424002
Category     : None
Source       : ClusDisk
Type         : Error
Generated    : 19.07.2014 10:49:10
Written      : 19.07.2014 10:49:10
Machine      : ***********
Message      : Cluster service is requesting a bus reset for device
\Device\ClusDisk0.
Event ID     : 15
Raw Event ID : 15
Record Nr.   : 25412958
Category     : None
Source       : Disk
Type         : Error
Generated    : 11.07.2014 10:54:53
Written      : 11.07.2014 10:54:53
Machine      : *************
Message      : The device, \Device\Harddisk46\DR48, is not ready for access yet.
Let me know if you need any additional info, many thanks.

Unable to see the file share content via UNC path

I have run a cmd command to modify the NTFS permissions on a few home directories.
That command has helped me to remove all from the ACL of shared folders; and add domain admins into it.
I am an admin on that Windows server. Now, whenever I try to access any home directory via UNC path; it doesn't displays the files and folders in it. But, if I go to the server and try to open the particular home directory from there...first it gives me
a prompt that I currently do not have access on folder and then gives me an option to click on continue and then I can access the files and folders within the directory.
I am also able to see the files and folders in the directory via UNC path after doing the above steps.
Can somebody help me understand what I did wrong here and how can this be resolved now?

Sorry, am added into local administratir group. But, NTFS permissions shows that I have only "read" and "change" permissions (I have checked this from effective permissions).
The ACL of folder shows only "Domain Admins" have full access and I am not a part of AD group "Domain Admins". I think this is the root cause of the issue.
I am running below mentioned command to give myself full access on the file shares without making any changes to the current ACL of all shared folders. However, it is not working and not even throwing any error message.
for /f %i in (u:\users.txt) do cacls \\hdfile01\users$\%i /C /G "AMadm":F
users.txt contains 'cn'. Another thing to notice here is that if I just keep one ID in .txt file and then run my command; it is working. But its not running for all users in loop.
Can somebody please help.

SL and SMB file shares gives 'file already in use' errors

Hi all,
I'm posting a question which has been asked here before but not answered.
We have several Mac users accessing files on a SMB share running on a Windows 2003 Server.
Everything worked fine for years until they upgraded to Snow Leopard, then they started experiencing errors when saving changes to an already-created file; they are thrown the error "Could not save <filename> because the file is already in use or was left open" - however it is clearly not open and nobody else has accessed it from the share.
There seems to be a lot of allusions made to this problem and I've seen hints that it was supposed to have been fixed in 10.6.3 - but we're still experiencing it and it's driving our users nuts!
Any help would be greatly appreciated.

I have similar problems with my new MacPros loaded with SL 10.6.4. Every time when the next network user want to open the file the 1st user opened (closed already), it keeps saying the file is in use.

Shared folders (Windows file shares) show access denied and do not prompt for credentials

Scenario:
Like other admins, I log on and work as a 'standard user' (usera) with no admin rights anywhere in the domain, to perform admin tasks I have another account (userb) which I authenticate with as and when required. userb has been allocated/delegated permissions
as required.
Problem:
When trying to connect to shared folders on servers (2008 R2) using a UNC patch via Windows Explorer (Win 7 Ent.), I see an access denied error and do not get an option to supply alternative credentials.
If I try to connect to the admin shares on the same server (\\server\C$ or \\server\e$) I get an access denied message AND get prompted for credentials. I supply my admin account and gain access as expected.
If I check share and storage management when attempting to connect, I see that Windows is trying to connect me to each share as usera (which has no access). I understand why I get access denied at this point, but not why it can't just prompt me to supply an
account that does have access. When trying the admin shares I also see the usera account, but I get a prompt to supply a user who does have access.
Share permissions on the folders are for example 'Everyone' Full Control. NTFS permissions are 'userb' has modify (read, execute, list, traverse etc) via a 'Server Admins' AD Universal security group.
Note: If I do a NET USE from CMD and use the /USER switch, I can access the shares fine. But this is not great for accessing shared folders on the fly from various computers.
How can I get the other shares on the server to prompt me, rather than just say access denied?
Many thanks.

Try to disable guest user from the server
If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY
suggestion in a test environment before implementing!

Unable to share calendars - This sharing message is not valid - Outlook 2013 Exchange 2007

Running Exchange 2007 latest and greatest service pack and rollup with Outlook 2013 fully patched. When users attempt to share their calendar, the recipient receives an email that says "This sharing message is not valid. All action buttons have been
disabled" and "(Sender not verified) - Calendar".
We're not using IMAP or POP. Was working in the past and stopped working.

Hi,
Is Exchange account the default account in Outlook?
Does this issue occur on all users? (If no, please try to recreate problematic user’s profile to check this issue)
Please check the following setting:
Open AD users and computers.
Right-click on problematic user to properties.
Under General tab, check if the E-mail field is right.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

10.9.2 Mavericks and can no longer connect to our SMB file share on the network.

Smb was working under 10.9.1. Now smb and usning the finder I get "connection failed". Both of my NAS are not out when i am using my mac book pro thru the wifi connection. Is any one else have the same problem?

Same story here - smb:// worked under 10.9.1, but the Update 10.9.2 broke it.
Some facts:
Mac Book Pro Retina 2012
Network connection is over WLAN (The connection is very stable and no issues else where)
The issue seems to be caused when there are larger files (> 500MB) in the share
smb:// works for shares with lots of folders but only small files in them
smb:// and cifs:// are both almost unusable
smb:// shows a blank screen for ages- Finder will eventually hang up
cifs:// will connect fast (wow!), but the connection is very unstable for larger files
The funny part is, that Mavericks (pre 10.9.2) was the first OS X which fixed most SMB issues of its predecessor. (SMB2 was somwhat slow, but quite usable) Now, I can not really use my Mac to work...
Moral of the story, I think I will switch to Ubuntu 14 when it is released in April - it should support HDPI Displays.

Unable to save over existing photoshop cs6 file using smb file share

The issue has been noted in 10.7 and 10.8. As a test, SMB did the same thing running from OSX Server but worked fine using AFP on OSX Server. The shared directory being used is on Windows Server 2008 R2.

if you can't trash them after restarting the computer and they are not locked use cocktail to trash them.

Windows Server 2012 , File Share, need to create CNAME but not working

I'm doing a file server migration for an old Netapp and I'm moving all the data to a Windows Server 2012 Standard System. I need to be able to have 3+ cnames for the system so I don't impact existing clients. I have read the below
articles and none of them are working.
Currently I'm getting the following error
"The Mapped Network drive could not be created because the following error occurred"
"The target account name is incorrect"
So I have tried the following without any luck, and these fixes below are supposed to work on Window 2008R2, but they don't on Server 2012
1) use DisableStrictNameChecking registry value
2) use netdom to create another hostname that is bound to the server, netdom computername (mysystem) /Add (newsystemname)
3) I used setspn to create an alternative name for the system
4) tried disabling SMB3
Any help on this would be greatly appreciated, I'm sure this is possible just down know now.
Jason

Why don't you just go into DNS and create multiple records for the same IP address?
Or, if you like trying more complicated paths, install DFS and use its distributed naming capability. It can have many, many different names.
.:|:.:|:. tim

Failover Cluster Manager is not performing failback of VM's

I have a 2 node Hyper-V Cluster setup in my environment. Currently I have 8 VM's with 4 on each Hyper-V server.
Each VM is setup to failback immediately tot he most preferred owner, however I have not seen this occur as of yet.
Both Hyper-V servers rebooted this morning at about the same time. Looking at all the VM's they are currently all on the opposite host that I prefer them to be on. In the General tab I have the preferred host checked that the VM should reside on.
Is there any reason the VM's aren't failing back to their preferred host?

There are two settings, you need to set the preferred owners as well as the failback policy. See this KB article:
http://support.microsoft.com/kb/197047
Thanks!
Elden
The Failback policy is to immediately allow failback.
The Maximum failures in specified period was set to 1 and period was set to 6 hours (default). I changed it to 5 maximum failures in 2 hours.
I tested by taking a node offline and then back online and all the VM's went back to their preferred node.
However, the issue I had was when both nodes went offline and came back up they didn't seem to go back to their preferred node.

SMB File Share Storage Failover Cluster "path is not valid folder path"

Similar Messages

Maybe you are looking for