I have two free subscriptions for windows azure and because I exceeded the limit on the first one, Microsoft closed it down. So I tried to deploy my application from the other subscription, and changed a few settings, and it seems to take a lot longer and the dns name of the depolyed application (in production area) does not seem to work. (I’ve been waiting for about 15 minutes.. in the other subscription it was almost immediate that the link started to work..). Also my webrole seems to be in a state of busy for a very long time..
The application always worked fine and now I’m getting all this trouble just by switching subscription?? I’m getting really frustrated with this especially because I all worked perfectly before. Now I have to ‘waste’ my time getting all the things to work again and I can’t start with anything new. I don’t think this is normal but I can’t seem to find the solution to this either.
edit:
Over half an hour the dns finally started working but this still does not fix the problem with the extreme slow deploying and the busy state of the webrole..
Please study the discussion below to understand why the time to deploy an application could vary between 10-30 minutes:
Is there a way to reduce time between Azure deployment start and role OnStart() code being invoked?
Above details will helped you to get the answer about your statement “.. this still does not fix the problem with the extreme slow deploying and the busy state of the webrole..”..
To add more about that, when your application is deployment phase it goes through several state and in some cases the time taken in one state could be longer then expected and during this time you will see status as “Busy”, “Initializing”, “Starting..” etc and these state actually explain which level you are during your deployment. I hope this helps you to understand the time taken during deployment.