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 Thursday, May 21, 2015 12:08 AM

Hi,

please check for the orphaned network adapters in the VM and remove them manually. After that reboot the VM once. Check if the issue persists even after that.

To find the network adapters, open up Device Manager, selected View > Show hidden devices and then expanded Network adapters.

Regards,
Manu

• Proposed as answer by Nagamalar NagarajanMicrosoft contingent staff, Moderator Monday, May 25, 2015 6:45 AM

Hi Alan,

Orphaned Network Adapters are hidden/ghost network adapters.
To view them you would have to type "set DEVMGR_SHOW_NONPRESENT_DEVICES =1"in command prompt and run the command.
Start devmgmt.msc from run.
In Device Manager, choose "View/Show hidden devices".
Under Network Adapters, you would see the Orphaned Network Devices.

One of the reasons for Orphaned Network Adapters could be if a network share or connection is not truncated completely.
However it wouldn't be possible to isolate the reason for orphaned network adapter or if this is because of Azure files or Windows Server unless the issue recurs and we are able to obtain a Trace or reproduce the issue.

Regards,
Malar.

• Marked as answer by Nagamalar NagarajanMicrosoft contingent staff, Moderator Thursday, May 28, 2015 10:13 AM