What does ERROR_AZURE_DRIVE_DEV_PATH_NOT_SET mean?

Answered What does ERROR_AZURE_DRIVE_DEV_PATH_NOT_SET mean?

  • Thursday, April 26, 2012 11:41 AM
     
     

    I am trying to attach a cloud drive on a live VM as described here http://msdn.microsoft.com/en-us/library/gg466226.aspx#bk_Storage but I get the error ERROR_AZURE_DRIVE_DEV_PATH_NOT_SET ?

    What does this mean? I've tripled checked my config at it seems ok.

    I am trying to connect the cloud drive in a Windows Service on a VM Role. I am already checking that the RoleEnvironment.IsAvailable is true so I think Azure is available.

    2012-04-26 12:26:09,360 [6] INFO  VMRoleStartup [(null)] - Starting...
    2012-04-26 12:26:09,422 [7] INFO  VMRoleStartup [(null)] - initialization succeeded
    2012-04-26 12:26:09,454 [7] INFO  VMRoleStartup [(null)] - local cache size 168944
    2012-04-26 12:26:09,454 [7] INFO  VMRoleStartup [(null)] - mounting drive http://me.blob.core.windows.net/mycontainer/drive_1.vhd
    2012-04-26 12:26:09,454 [7] ERROR VMRoleStartup [(null)] - Microsoft.WindowsAzure.StorageClient.CloudDriveException: ERROR_AZURE_DRIVE_DEV_PATH_NOT_SET ---> Microsoft.WindowsAzure.CloudDrive.Interop.InteropCloudDriveException: Exception of type 'Microsoft.WindowsAzure.CloudDrive.Interop.InteropCloudDriveException' was thrown.
       at ThrowIfFailed(UInt32 hr)
       at Microsoft.WindowsAzure.CloudDrive.Interop.InteropCloudDrive.Create(String url, Int64 size, SignatureCallBack sign)
       at Microsoft.WindowsAzure.StorageClient.CloudDrive.Create(Int32 sizeInMB)

All Replies

  • Thursday, April 26, 2012 12:33 PM
     
     Answered
    Can you check this link and see if it helps: http://msdn.microsoft.com/en-us/library/windowsazure/hh708321.aspx

    If this post answers your question, please mark it as an answer. If this post is helpful to you, then vote it as helpful.
    TechyFreak | Mobile Development Resources

    • Marked As Answer by Ian1971 Friday, April 27, 2012 10:10 AM
    •  
  • Thursday, April 26, 2012 3:17 PM
     
     Answered

    Yes this did help. But not straight away.

    First, I discovered that the FixMSI.js script from http://msdn.microsoft.com/en-us/library/gg466226.aspx#bk_Install was failing. For some reason $(BuiltOutputPath) was empty. I did it relative to the $(ProjectDir) instead.

    It then failed with a different error (and much earlier). CloudDriveException 0x80070103 which you have pointed me to the article for.

    Now it attaches ok. The strange thing now is that the device has a warning when the vm starts (but only when hosted in azure), I have to manually go into the vm on azure and update the driver to get it to work. Obviously, this is not ideal. the VM Image itself seems fine when hosted in HyperVisor

    • Marked As Answer by Ian1971 Friday, April 27, 2012 10:10 AM
    •  
  • Friday, April 27, 2012 5:35 AM
    Moderator
     
     

    Hi,

    Try to replace "$(BuiltOutputPath)" to "$(BuildOutputPath)" to see if works.

    Hope this helps. 


    Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact msdnmg@microsoft.com Microsoft One Code Framework

  • Friday, April 27, 2012 10:09 AM
     
     
    Unfortunately that also doesn't work. I am ok for now using project dir, so no biggie. More worrying is the fact that my vm on azure always needs me to fix the wa miniport device even though it was installed ok in hypervisor. Going to raise this as another topic though.