I've followed the setup procedures by Bruce Chapman at this link: http://www.dnnsoftware.com/community-blog/cid/154975/moving-a-dnn-install-to-microsoft-azure-websites.

The only change from his procedure is now there's a 'deploy database to Azure' or some such in the flyout menu in SSMS.  So this was used rather than export data tier application.  I needed to clear up some 53 stored procedures using string aliases for columns and install clustered indexes on about 15 or 20 tables.  But other than that the deploy of the database to Azure was fine.

The site content was uploaded rather quickly, web config edits are all correct.  I'm not able to paste images which is a real frustration.  So here goes an attempt to describe a pic in much less than a thousand words.  I get the error 'The page cannot be displayed because an internal server error has occurred.'  I know the content, connection strings and database have to be right because I do get a browser tab with our fav icon in the upper left, by our company name.  Naturally, the fav icon is in web root directory.

The 500 error doc I do get from Azure via FTP doesn't have any data in it.  The hex error code, starting with 0x is all zeros.  There is no statement in the doc what the actual error is.  Here is the text of the 500 error doc.  This is of no help at all.

The implication from emails I get from sales types is if I buy a developer support package for 29.00/mo (which is darn cheap, I'll admit) I'll get answers.  My comeback to them is if the 500 error had data I could solve the problem! :)  And I'd be more inclined to sign up for a support package.

The real conflicting piece of info is in one of the other Azure log files downloaded from FTP.  It shows all contain 200 codes, which mean success.  Which of course does not make sense.

I don't see where paying for support solves anything.  It's Azure's issue as near as I can tell.  If anyone has suggestions, let me know.  I'm not getting anything back from Azure despite several voice and email messages.

Great idea -- here's what I got back.  We're running version 7.2.1:

ERROR: providerPath folder D:\home\site\wwwroot\Providers\DataProviders\SqlDataProvider\ specified for SqlDataProvider does not exist on web server

This sounds like an install snag of some sort.  This path should be on the server.  I don't know that much about the internals of DNN but this should obviously be there.

That doesn't tell me what to do other than reinstall.  I'd rather know why this path isn't there, what caused it to not be created.