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

DotNetNuke Azure Accelerator Install Video

Jul 4, 2011 at 1:19 PM

Hello,
Is there a video that shows the required steps for installation of DNN on Azure?
I have tried the steps described on http://dnnazureaccelerator.codeplex.com/ but received, HTTP 403 error.
What i;ve done is as follows:
1) downloaded DNN Azure Accelerator, extracted, and run exe file with admin priviliges
2) created sql azure also permitted access to from 0.0.0.0 to 254.254.254.254 so that everyone can access it. of course this was for testing purposes :-) i tested the connection from the install app and it was successfully connected.
3) created blob storage, got access keys
4) executed the installation application and it has produced the following output which states the install was successfull. (this output will be pasted at the end of the message)
5) created hosted service
6) wheni try to access to the site i got "http 403 error"


does anyone have any idea about what might have gone wrong?
regards,
ZAM


Additional info: the output from the installation log.

Settings loaded from service configuration file: 'C:\temp\DNNAzureAccelerator\ServiceConfiguration.cscfg'
Setting Environment Variables
 AcceleratorConnectionString : DefaultEndpointsProtocol=https;AccountName=dotnetnuke1;AccountKey=paHVkIQ72JjG0oOXMaGkmzlTKrGZUwV+XeMiwPMvGqVChjpAK9/Y0gu69gzELav2+yjyA6r9zmYOb/LcogmQhw==
 DefaultEndpointsProtocol : https
 AccountName : dotnetnuke1
 AccountKey : paHVkIQ72JjG0oOXMaGkmzlTKrGZUwV+XeMiwPMvGqVChjpAK9/Y0gu69gzELav2+yjyA6r9zmYOb/LcogmQhw
 DatabaseConnectionString : Server=tcp:sb9c9r2zxx.database.windows.net;Database=dnn1;User ID=alenmalhasoglu@sb9c9r2zxx;Password=P@ssw0rd@;dbUser=dnn1;dbPassword=P@ssw0rd@;Trusted_Connection=False;Encrypt=True;
 Server : tcp:sb9c9r2zxx.database.windows.net
 Database : dnn1
 User ID : alenmalhasoglu@sb9c9r2zxx
 Password : P@ssw0rd@
 dbUser : dnn1
 dbPassword : P@ssw0rd@
 Trusted_Connection : False
 Encrypt : True
 AcceleratorDrivePageBlobUri : azure-accelerator-drives/dotnetnuke.vhd
 AcceleratorContainerSyncUri : wa-accelerator-apps
================================================
  Rapid Provisioning of SQL Azure for DotNetNuke Community.
================================================
-- ENVIRONMENT SETTINGS --
 SQL Server Con:   tcp:sb9c9r2zxx.database.windows.net 
 SQL Server Admin: alenmalhasoglu@sb9c9r2zxx
 SQL Server:       sb9c9r2zxx
 SQL Database:     dnn1
 Admin User:       alenmalhasoglu
 Admin Password:   P@ssw0rd@
 DotNetNuke User:     dnn1
 DotNetNuke Password: P@ssw0rd@
 Accelerator container Sync Uri: wa-accelerator-apps
 Drive Page Blob Uri: azure-accelerator-drives/dotnetnuke.vhd
-- DATABASE: CREATING --
-- DATABASE: VERIFYING --
Database Verified: dnn1
Login Verified: dnn1
-- DATABASE: SETTING SECURITY --
-- DATABASE: DEPLOYING SCHEMA --
-- DATABASE: DEFAULT DATA INITIALIZATION --
-- STORAGE: UPLOADING SERVICE CONFIGURATION --
Settings loaded from service configuration file: 'C:\temp\DNNAzureAccelerator\ServiceConfiguration.cscfg'
Uploading file to storage...
Source:  'C:\temp\DNNAzureAccelerator\bin\ServiceConfiguration.cscfg'
Target:  'https://dotnetnuke1.blob.core.windows.net/wa-accelerator-apps/ServiceConfiguration.cscfg'
Upload completed!
-- STORAGE: UPLOADING SOLUTION ENGINE --
Settings loaded from service configuration file: 'C:\temp\DNNAzureAccelerator\ServiceConfiguration.cscfg'
Uploading file to storage...
Source:  'C:\temp\DNNAzureAccelerator\Packed\DNNAzureSMB.cspkg'
Target:  'https://dotnetnuke1.blob.core.windows.net/wa-accelerator-apps/DNNAzureSMB.cspkg'
Upload completed!
-- STORAGE: UPLOADING CLOUD DRIVE --
Settings loaded from service configuration file: 'C:\temp\DNNAzureAccelerator\ServiceConfiguration.cscfg'
Uploading file to storage...
Source:  'C:\temp\DNNAzureAccelerator\Packed\DotNetNuke.vhd'
Target:  'https://dotnetnuke1.blob.core.windows.net/azure-accelerator-drives/dotnetnuke.vhd'
Total size of upload:  256 Mb
   4 of 256 Mb ( 1.56 % )
   8 of 256 Mb ( 3.12 % )
  12 of 256 Mb ( 4.69 % )
  16 of 256 Mb ( 6.25 % )
  20 of 256 Mb ( 7.81 % )
  24 of 256 Mb ( 9.37 % )
  28 of 256 Mb ( 10.94 % )
  32 of 256 Mb ( 12.50 % )
  36 of 256 Mb ( 14.06 % )
  40 of 256 Mb ( 15.62 % )
  44 of 256 Mb ( 17.19 % )
  48 of 256 Mb ( 18.75 % )
  52 of 256 Mb ( 20.31 % )
  56 of 256 Mb ( 21.87 % )
  60 of 256 Mb ( 23.44 % )
  64 of 256 Mb ( 25.00 % )
  68 of 256 Mb ( 26.56 % )
  72 of 256 Mb ( 28.12 % )
  76 of 256 Mb ( 29.69 % )
  80 of 256 Mb ( 31.25 % )
  84 of 256 Mb ( 32.81 % )
  88 of 256 Mb ( 34.37 % )
  92 of 256 Mb ( 35.94 % )
  96 of 256 Mb ( 37.50 % )
 100 of 256 Mb ( 39.06 % )
 104 of 256 Mb ( 40.62 % )
 108 of 256 Mb ( 42.19 % )
 112 of 256 Mb ( 43.75 % )
 116 of 256 Mb ( 45.31 % )
 120 of 256 Mb ( 46.87 % )
 124 of 256 Mb ( 48.44 % )
 128 of 256 Mb ( 50.00 % )
 132 of 256 Mb ( 51.56 % )
 136 of 256 Mb ( 53.12 % )
 140 of 256 Mb ( 54.69 % )
 144 of 256 Mb ( 56.25 % )
 148 of 256 Mb ( 57.81 % )
 152 of 256 Mb ( 59.37 % )
 156 of 256 Mb ( 60.94 % )
 160 of 256 Mb ( 62.50 % )
 164 of 256 Mb ( 64.06 % )
 168 of 256 Mb ( 65.62 % )
 172 of 256 Mb ( 67.19 % )
 176 of 256 Mb ( 68.75 % )
 180 of 256 Mb ( 70.31 % )
 184 of 256 Mb ( 71.87 % )
 188 of 256 Mb ( 73.44 % )
 192 of 256 Mb ( 75.00 % )
 196 of 256 Mb ( 76.56 % )
 200 of 256 Mb ( 78.12 % )
 204 of 256 Mb ( 79.69 % )
 208 of 256 Mb ( 81.25 % )
 212 of 256 Mb ( 82.81 % )
 216 of 256 Mb ( 84.37 % )
 220 of 256 Mb ( 85.94 % )
 224 of 256 Mb ( 87.50 % )
 228 of 256 Mb ( 89.06 % )
 232 of 256 Mb ( 90.62 % )
 236 of 256 Mb ( 92.19 % )
 240 of 256 Mb ( 93.75 % )
 244 of 256 Mb ( 95.31 % )
 248 of 256 Mb ( 96.87 % )
 252 of 256 Mb ( 98.44 % )
 256 of 256 Mb ( 100.00 % )
Blob successfully uploaded.
Snapshot created:  'https://dotnetnuke1.blob.core.windows.net/azure-accelerator-drives/dotnetnuke.vhd?snapshot=2011-07-04T10%3A16%3A51.3634814Z'
Upload completed!
==============================================
 Deployment Complete
 Return to the Azure management interface and
 provision a new staging service. The solution
 package and service configuration file have
 already been uploaded to Azure. The provision-
 ing tools will allow you to select these 
 existing files from Azure storage services
 instead of uploading from your local system.
==============================================



Jul 5, 2011 at 4:35 PM

I received similar results. I'm trying to upload to a small instance that is part of my MSDN subscription. This looks like it creates two instances which I'm not sure is the difference or where my error is starting. Is there any recommendations for which azure plan runs best with this version?

Jul 6, 2011 at 11:24 AM

Hello Bruce,

After posting this question i have tried several different approaches to deploy DNN Azure Accelerator. Finally i managed to deploy and run it properly on Windows Azure. 

The missing bit was the "certificate". When you run the DNN Azure Accelerator wizard, it does

  • create the db
  • upload the azure package, and configuration files
  • upload VHD drive file which will be used as CloudDrive

After above steps you should go to your Azure management page and create a hosted service to deploy your already uploaded package. That that time if you forget to

associate a certificate to your hosted service, the error that i have experienced happens. If you add the cert to the hosted service deployment, everything works fine.

Re your question about suggestion about the deployment, i have managed to deploy DNN Azure Accelerator to "two small sized servers" one is for SMB, and the other is for DNNAzure. I haven't tried to deploy to an

ExtraSmall Sized servers, but it may work if you do the proper configuration.

regards,

Alen Ziver Malhasoglu

 

Jul 6, 2011 at 1:21 PM
Edited Jul 6, 2011 at 1:35 PM

Hi,

I'll investigate the Alen's comment because the certificate should only be needed if you have configured RDP access to the instances. Certainly, in all my actual deployments I've a management certificate configured in order to enable RDP, but I believe that I had removed the certificate requeriments from the SMB package.

A HTTP 403 Error (Forbidden), should mean that the DNN Azure web role deployment wasn't successfull, and the server is publishing the "Default website" (that is empty), not the "DotNetNuke website" that is created on the fly. The reasons for this can vary, but the principal casuistic that I've observed is that the SMB server could not mount the VHD drive, and after 15 minutes the webrole goes online serving the "Default website". Please, check the WADLogsTable for more info (the SMB server writes a lot of info there while this process) and tell me if you see any error.

An important thing, is that the "AcceleratorConnectionString" needs to have "DefaultProtocol=http" (not https) in the SMB Server section of the ServiceConfiguration.cscfg, because https is not supported by the CloudDrive APIs.

@Bruce, I confirm that you can use any plan available. There is no limits on creating DNN instances in Windows Azure while you have an active account.

  

Effective 
before Dec. 10th 2009

Effective  
after Dec. 10th 2009

Effective 
after Jan. 4th 2010

  

Token (CTP)

Token (CTP)

Token (non-billing country)

Paying subscription

Deployment Slots

2

2

2

2

Hosted Services

1

1

20

20

Roles per  
deployment

5

5

5

5

Instances per Role

2

2

no limit

no limit

VM CPU Cores

no limit

8

8

20

Storage Accounts

2

2

5

5

Jul 6, 2011 at 1:31 PM

Thank you for the response David,

Can you please post the result of your experiment, so that thread followers will learn if cert requirements exists or not?

cheers,

Alen

Jul 6, 2011 at 1:42 PM

Alen, I've updated the previous response after thinking about the "403 error" could you check the WADLogsTable for more info?

Thanks again.

Jul 6, 2011 at 2:59 PM

Thanks Alen, I'll give that shot as I had a certificate on my hosted instance, but did not associate it with this role.

 

@David, David, please bare with me as I'm farily new with messing with Azure. I have an account that is just for playing. don't want to really spend any extra money until I'm convinced my ideas will work. isn't each instance considered a server on Azure? I only have one as part of my MSDN subscription and don't want ot bring up another one right now since I'm just playing with some ideas and I want to see it run on Azure before I go too far. Looks like the wizard creates two instances, which means I'm going to get charged for one of them( I think). The SingleExtraSmall config creates an Extra small instance which is not what i want either as I doubt DNN will run with that little bit of memory well at least without driving me crazy. What would I need to do to just get a small instance up and running? Sorry for the newbie questions. I'm not new with DNN at all and have setup thousands of isntalls, but this one seems to be kicking my butt to get it working.

 

tia

Bruce

Jul 6, 2011 at 3:48 PM

@Bruce,

If you have already uploaded the VHD and created the SQL Azure database with the SMB wizard, you are very close to the solution that you need. The steps should be:

  1. Download the Source Package and open it on Visual Studio 2010
  2. You will see two service projects. Select the DNNAzureSingle service and change its configuration to use a Small instance.
  3. Right-click the service and select "Publish..." (this should be a good moment to configure RDP also) and write the package to your local disk
  4. You will see your "DNNAzureSingle and Small" package and a Service Configuration file. Change the settings of the configuration file for similar entries on the actual SMB published version
  5. Deploy the service with this new package and configuration file instead of the SMB version. You will have a minimum of 1 DNNAzure instance that will mount the VHD and publish its contents. The next ones will connect to the first instance for publishing the contents.I

I'm really seeying that a video or more visual documentation is needed. Need a little bit of time for it :) If you have any problem with the steps, don't hesitate to contact me.

Regards,

David Rodriguez

 

 

 

Jul 11, 2011 at 11:02 AM
Edited Jul 11, 2011 at 11:04 AM

Hi David,

I’m also trying to deploy DotNetNuke in Azure. But I’m getting “403 - Forbidden: Access is denied” error.

Please find the below Logs for your reference. I don’t see any error in log. So assuming the web role is deployed successfully.

Information: Diagnostics Setup complete

Information: Mounting cloud drive - Begin

Information: Mounting cloud drive - Accesing acount info

Information: Mounting cloud drive - Locating VHD container:azure-accelerator-drives

Information: Mounting cloud drive - Creating VHD container if not exists

Information: Mounting cloud drive - Get drive Name

Information: Mounting cloud drive - Local cache initialization

Information: Creating user account for sharing

Information: Enable SMB traffic through the firewall

Information: Share the drive

Information: Modify web.config settings

Information: Exiting SMB Server OnStart

Information: SMBServer entry point called

Any help is highly appreciated.
Thanks,
Vinay TC

Jul 11, 2011 at 11:14 AM

@tcvinay, Have you tried the solution that @Alen talked about? (add the certificate to the service). I haven't had time to reproduce the error in order to verify what is the problem, but your Log looks like the SMB server is starting perfectly.

Thanks,

David Rodriguez

Jul 12, 2011 at 5:56 AM

Hi David,

I was not able to find any certificate whic i could add while creating the hosted service.

Can you/Alen let me know which certificate to use? and where I could find teh certificate?

Thanks,

Vinay TC

Jul 12, 2011 at 9:02 AM

Hi Vinay,

 

have a look at the following thread please:

http://dnnazureaccelerator.codeplex.com/discussions/263563

 

regards,

Alen

Aug 5, 2011 at 9:23 AM

How to (tutorial) deploy DNN to Azure here http://www.squidoo.com/publishing-dotnetnuke-6-0-to-windows-azure

Aug 15, 2011 at 5:29 PM

After two successfull deployments, I've built a list about the main reasons of the 403 error. Check the "Documentation" page to see the list and tell me if one of them fix your problem. (http://dnnazureaccelerator.codeplex.com/documentation)

Thanks for feedback