Answered by:
Has anybody been able to get Azure cloud drive working with VM role adapter?

Question
-
I've been following this walkthrough: http://msdn.microsoft.com/en-us/library/windowsazure/gg466226.aspx
I have version 1.6 of the Windows Azure Integration Components installed on Windows 2008 R2 Enterprise VM.
First, I have not been able to get the role adapter to even start-up using the LocalService account as prescribed in the walkthrough. It seems that even accessing RoleEnvironment.IsAvailable will case this error:
Service cannot be started. System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.
at Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment.Initialize(TimeSpan timeout)
at Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment.get_IsAvailable()
at VMRoleAdapter.RoleAdapter.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
I can get the service to at least start up by running under LocalSystem.
However, when it gets to the call CloudDrive.InitializeCache(), the adapter crashes.
Sunday, May 20, 2012 10:10 PM
Answers
-
The workaround didn't work The only way to resolve the issue is to not use v1.6 at all. v1.4 is the last version of WAIC that actually works. I hope you guys fix the problem in v1.7.
- Edited by atilekt Thursday, May 24, 2012 10:50 PM
- Marked as answer by Allen Chen - MSFT Friday, May 25, 2012 3:05 AM
Thursday, May 24, 2012 10:49 PM
All replies
-
Hi,
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay.
Appreciate your patience.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
Monday, May 21, 2012 10:00 AM -
Hi,
It seems you're not using 1.6 SDK? If you use Reflector to open the 1.6 SDK's Microsoft.WindowsAzure.ServiceRuntime.dll you'll see the callstack is impossible to be what you've seen. Please check that and try the latest SDK to see whether it works.
Also this is a similar thread FYI:
Allen Chen [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
- Edited by Allen Chen - MSFT Tuesday, May 22, 2012 2:49 AM
Tuesday, May 22, 2012 2:41 AM -
I was using the 1.6 SDK--same version as the WAIC that I installed on the VM. The ISO that I mounted to install the WAIC on the VM role came from the v1.6 SDK folder on my development machine.
I will try the workaround suggested in the last message of that thread though.
- Edited by atilekt Tuesday, May 22, 2012 7:22 PM
Tuesday, May 22, 2012 7:21 PM -
>I will try the workaround suggested in the last message of that thread though
Have you resolved this problem?
Allen Chen [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Thursday, May 24, 2012 8:41 AM -
The workaround didn't work The only way to resolve the issue is to not use v1.6 at all. v1.4 is the last version of WAIC that actually works. I hope you guys fix the problem in v1.7.
- Edited by atilekt Thursday, May 24, 2012 10:50 PM
- Marked as answer by Allen Chen - MSFT Friday, May 25, 2012 3:05 AM
Thursday, May 24, 2012 10:49 PM -
Hi Atilekt,
We have reproduced this issue, and it will be fixed in SDK v1.7. There is another workaround, available here: http://msdn.microsoft.com/en-us/library/windowsazure/hh708321.aspx
Wednesday, May 30, 2012 10:06 PM