error installing extra small package

Mar 17, 2013 at 12:25 AM
Tried a number of times on fresh installs & get the following
  • Install DotNetNuke: Error: The remote server returned an error: (404) Not Found.
    Upload failed!
Mar 17, 2013 at 6:41 AM
Disregard,

Ive worked out that provided cloud service & storage are created as new during running the accelerator, deployment will work.

Wont work if you create new cloud service & storage via dashboard, first.

Hope someone finds this helpful.
Coordinator
Mar 18, 2013 at 4:05 PM
Really weird. The accelerator creates the cloud service and storage accounts just on the second wizard step before going further...or...which "Deployment Type" did you choose on the first step? Are you talking about the manual deployment?
Apr 12, 2013 at 5:05 AM
Edited Apr 13, 2013 at 6:47 AM
Same Error, Try second time for version, firstly by remove all services in Azure portal, clean.

Using DNN Azure Accelerate Wizard (6.4 RTM), I encountered the same error. environment as follow

Windows 8 Pro --> Desktop
Subscription --> Windows Azure Cloud Essentials
Location --> Southeast Asia
Virtual; Network Setting --> Unchecked
SSL Settings --> Unchecked
Accelerator Deployment Package --> DNN Azure Single and Small 6.4
                                                          DNN Community Edition 07.00.05 (Latest)
Checked Auto-install

First four steps/tasks Completed successfully

Deploy the package Creating deployment...
                                        Running (DNNAzure_IN_0: Initializ...
                                        Running (DNNAzure_IN_0: Busy)...

Error Message

Upload Failed !

-
  • Deploy the package Completed
  • Install DotNetNuke: Error: The remote Server returned an error : (404) Not Found.
    Upload Failed !
Just wonder what need to be done in order to correct the error.
By the way, it is possible to deploy "Professional Edition"?
Thanks for advise.
Apr 13, 2013 at 6:53 AM
Edited Apr 13, 2013 at 6:56 AM
Today try using version 6.3 to install DNN 07.00.05 CE is OK.

By the way, how to get the Professional Edition Pkg Customer URL instead of Community Edition (CE). I had downloaded "DotNetNuke_Professional_07.00.05_Install.zip" to my local PC C:\

Also I can't find Virtual Network Settings inform on Azure Connect, just do not know where to get the activation token for Azure Connect.

Thanks for advise and Have a Nice Weekend.
Jun 6, 2013 at 7:07 PM
We see this same error with v6.4 quite often. It usually requires us to quite the accelerator app and start again. Is there any resolve to this?
Thanks.
Coordinator
Jun 6, 2013 at 8:15 PM
I believe that I answered via e-mail and for some reason the answers did not appear here. Here some pending answers:
  • To install PE edition, you must upload the install package to a public internet location. Specify that URL by selecting "Custom package" in the packages selection step
  • To get a Virtual Network token, you must go to the Old Azure portal (is not available yet on the current management portal). You can Access the Old portal here: https://windows.azure.com
  • The problems around the 404 error seems to be related to the way of how the drive is being mapped in the 6.4 package. Take a look to this workitem for more info: https://dnnazureaccelerator.codeplex.com/workitem/1291. This item has high priority.
Regards,

David
Jun 6, 2013 at 8:26 PM
Thanks for the update David. Is there anything we can do to resolve the 404 error or do we need to wait for an update?
Jun 6, 2013 at 8:30 PM
When I go to https://windows.azure.com, I get automatically redirected to https://manage.windowsazure.com/

Doesn't seem to be anyway to get to the old portal.
Coordinator
Jun 6, 2013 at 9:00 PM
For the 404 error, if it is the error I mention in the issue you will need to wait for the update. Note that in the error I mention, the site is really available after about a minute and you can browse it. If you can't another issue could happen and I will be happy to assist. Please, download https://azurestorageexplorer.codeplex.com/ and look for any error in the WADLogsTable.

About accesing the old portal, I have verified that is still redirecting me to the old portal (perhaps because my Live Id is not an Office 365 Live Id or similar). In any case, you can select going to the Old portal by clicking on the top-right menu on the new portal (first option after clicking in your Live Id address).