Aug 17, 2011 at 12:21 PM
Edited Aug 17, 2011 at 12:22 PM
If you experience a timeout on any wizard step of the official DNN installation assistant, check that the three Azure components, the Azure service, the Azure storage and the SQL Azure server use the same Datacenter (try to use an affinity group for that).
If you don't use the same affinity group, perhaps you will deploy the components between different datacenters around the world if you don't take care of that. This means a latency increase during installation and use of the services, and of course, invoicing
of the in/out bandwith inside your own application!!
If this is your case, create an affinity group and re-create all the components using the same affinity group.
A tip for re-creating a VHD image contents and a new SQL Azure database after a stuck installation is:
- Stop the service and wait for the completion of the stopping process
- Delete the VHD blob using a storage tool
- Delete the SQL Azure database using the Azure Management Console
- Create a new blank SQL Azure database using the Azure Console
- Start the service.
After this, the wizard will be resetted to the initial state. You will be prompted for a database user during installation. If you don't want to use the admin database user, create an database user (check the /sql/createuser.sql file that is inside the DNN
Azure Wizard package for more information).
Hope this helps.