Problem with local Azure deployment

I'm trying to run a WebRole on my local machine via Compute Emulator. My Compute Emulator and Storage Emulator is running fine. When I hit F5 in VS2010, I can see the action in Compute Emulator. But after a while, I get an exception in VS2010;

  Microsoft.WindowsAzure.Hosts.Worker.RuntimeEnvironmentException was unhandled
  Message=Unable to load the runtime environment: could not get hosting environment settings
  Source=WaWorkerHost
  StackTrace:
       at Microsoft.WindowsAzure.Hosts.Worker.Parameters..ctor()
       at Microsoft.WindowsAzure.Hosts.Worker.Loader.Main(String[] args)
  InnerException: 

Then Roles in Compute Emulator begins to shutdown. VS2010 launches the browser with IP and port but no luck, it's not running of course.

I don't think this is a coding error because I live the same problem even in an empty out-of-the-box Azure project and a single Web Role on it.

I've searched the net but no i开发者_如何学Cnfo about this error. Actually if you search exactly for "RuntimeEnvironmentException" Google returns zero result. Using the description words also does not make any sense.

Anyone have an idea?

Thanks, Ali

Sorry for not responding earlier but I was still working on the issue. Then a Microsoft guy from Turkey office figured it out. There is a problem with localization on developer machines. In development environment computers, in "Region and Languages", set "Format" to "English (United States)" and "Current Location" to "United States". After setting these, Azure emulator is working flawlessly. They said this is a known issue and they're preparing a report about this. I hope this will be resolved in next releases.

Hope this helps to anyone who live same problem. And thanks everyone who tried to help...

Ali

I've had a similar issue where the compute emulator just fails to load my web role and nothing ever responds. It seems to happen to me when I hibernate my laptop a few times while the compute emulator is running. Even shutting the emulator down and restarting it doesn't seem to help.

Best solution I've found is to reboot. Definitely not elegant (and a bit of a pain in the butt), but it's worked for me every time.

Not sure if this helps or not. Good luck.