08-25-2009 05:44 AM
Solved! Go to Solution.
08-31-2009 04:19 PM
That message is being reported from the file system, I don't know why after reboot it should report that for that fileshare should report its write protected. SQL server data may report no problem becuase whatever is causing fileshare to fault, has passed by the time SQL server tries to write to the volume.
I suppose you could try to find out by just onlining the MountV and then trying to browse the folder from the local server before you share it, but you might have to be quick to try and create a file before the problem condition passes.
I suggest you have the cluster apply the workaround you are doing manually (retry online). In the properties for the FileShare agent (right click FileShare, View -> Properties View) select ShowAllAttributes, look for OnlineRetryLimit and set to 1. This will retry the online operation which based on your experience should allow the resource online. Set this higher if needed.
James.
08-25-2009 02:58 PM
With this one, as you can try to online again and it is successful with no further action suggests some kind of timing issue for the online. Check that you have the FileShare linked to the correct MountV.
Usually FileShare fails to online due to a permsissions issue, path incorrect, or some other configuration issue that needs to be resolved before online will work. Any file system issue will fault the MountV, not the FileShare.
The reason it is faulting should be logged in the application event log. Test the online and then look in that log for "AgentFramework" and you will see a message in the form of:
FileShare:<name>:online:Failed to open folder <some_folder_name> [X:Y]
where X and Y are numbers.
Use the second number and from command line "net helpmsg Y" and hopefully this will give you the reason why.
James
08-26-2009 04:29 AM
08-31-2009 01:03 PM
08-31-2009 04:19 PM
That message is being reported from the file system, I don't know why after reboot it should report that for that fileshare should report its write protected. SQL server data may report no problem becuase whatever is causing fileshare to fault, has passed by the time SQL server tries to write to the volume.
I suppose you could try to find out by just onlining the MountV and then trying to browse the folder from the local server before you share it, but you might have to be quick to try and create a file before the problem condition passes.
I suggest you have the cluster apply the workaround you are doing manually (retry online). In the properties for the FileShare agent (right click FileShare, View -> Properties View) select ShowAllAttributes, look for OnlineRetryLimit and set to 1. This will retry the online operation which based on your experience should allow the resource online. Set this higher if needed.
James.
09-01-2009 04:51 AM