This project has moved and is read-only. For the latest updates, please go here.

Getting started with Windows Azure and DotNetNuke

Joe Brinkman has produced an excellent video tutorial about how to deploy DotNetNuke on Windows Azure using this accelerator. You may also want to check this post about the new features of this release.

DotNetNuke Azure Accelerator 6.2 video


Known issues and solutions

After some feedback, some issues has been resolved and some ones need some tips-list in order to clarify possible reasons. If you have an issue like the mentioned here, check this list.

"403 Forbidden" error main reasons

This error means that for one reason, the Azure Web Role has started but can't publish the website contents. The reason for this can be:

  • Check that the SMB worker role has successfully mounted the drive and successfully accomplished other tasks. For this, check the WADSLogTable (i.e. Azure Storage Explorer from
  • Check that the service name has been included in the setting "hostHeaders" on the service configuration file (i.e. ==> hostHeader=";")
  • Check the "/log" subfolder of the Wizard. Perhaps you can find some errors that ocurred when creating the login. The SQL Azure password strength policy is hard. If there are errors, you can open an SSMS session and execute the statements, in order to don't upload again all the packages. I'll modify the wizard in order to advert this issue.
  • Make sure that the setting "driveName" on the service configuration file points to a non-exist or non-currently-in-use-by-another-service VHD file
  • Check that the setting "AcceleratorConnectionString" uses "http" and not "https"
  • For new DNN6 installations, check that the setting "packageContainer" + "package" points to the correct package on storage
  • Currently, changing the drive size on the service configuration file once that has been created is not supported. Set the correct size on the first deployment. For more info about changing the VHD size, see this thread

Note that modifying currently in use settings is not supported at this time. You need to redeploy the service. It's been checked that there is no need to use a certificate to deploy the packages (the certificate is only needed if you use RDP to connect to the instances, something that is really helpful).

"Waiting for Role to start" main reasons

  • Use the latest package included in the Azure Wizard. A previous DNNAzureSMB6.0.cspkg had this bug (see for more info)
  • Make sure that the setting "driveName" on the service configuration file points to a non-exist or non-currently-in-use-by-another-service VHD file
  • The Web Roles should start after no more than 1 minute after the SMB server, so don't wait for a long time after that.
  • I encourage to connect via RDP (see documentation) in order to check that the drive is really mounted and accesible
  • Check the WADSLogTable using a Storage Explorer (i.e. Azure Storage Explorer from for seeying if something was wrong when mounting the drive. This capture shows a log between different deployments of the SMB Server role


Last edited May 29, 2012 at 9:20 PM by davidjrh, version 25


eccountable May 18, 2014 at 8:47 PM 
This is pretty neat and works well. I am impressed with the speed on a 'medium' size instance. I like the idea of separating the app server from the database using a cloud service and SQL database instances. However I have some 3rd party products that I purchased for DNN that are not compatible with this type of deployment in Azure. Is it possible to have an option where we can choose to have DNN and SQL on a single VM?