Does Azure Files have a timeout on established connections?

I have an application deployed in a cloud service, running on multiple Windows Server 2012 R2 virtual machine instances, that uses the Azure Files feature. The Azure Files share is mapped using the net use command, as described in http://blogs.msdn.com/b/windowsazurestorage/archive/2014/05/12/introducing-microsoft-azure-file-service.aspx.

  • e.g. net use z: \\<account name>.file.core.windows.net\<share name> /u:<account name> <account key>

After almost exactly 1 week (1 week, 8 hours later), .NET code that loads files in the share stopped being able to load files, on both virtual machines.

The exception that was occurring was (relevant portion of stack trace shown only):

An unexpected network error occurred. 
System.IO.IOException
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.ReadCore(Byte[] buffer, Int32 offset, Int32 count)
   at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32 count)

Even though the share was still mapped to the drive, I had to remap the share for the application to start accessing the files again. The error was not short lived either, and was occurring repeatedly for 2 days.

Are there any timeouts on already mapped shares that would explain this? Or are there any other explanations for why a previously mapped share would stop working?







  • Edited by Alan.M 7 hours 10 minutes ago
May 20th, 2015 7:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics