Learn More





Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Azure Setup IssuesAzure Setup Issues
New Post
5/14/2016 5:54 PM

I've followed the setup procedures by Bruce Chapman at this link:

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.

HTTP Error 500.0 - Internal Server Error

The page cannot be displayed because an internal server error has occurred.

Most likely causes:

  • IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. Thanks ... this may well be the generic situation.  But I need more info and the error form has none.
  • IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
  • Note, the fav icon is showing up and the company name is also, in the browser tab.  Since this is displaying the web config file is being located and the connection strings are working
  • IIS was not able to process configuration for the Web site or application. not applicable, it is.
  • The authenticated user does not have permission to use this DLL. we're not even that far yet :)
  • The request is mapped to a managed handler but the .NET Extensibility Feature is not installed. Have no idea what this refers to ... but I think it's not relevant to this issue.

Things you can try:

  • Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
  • Check the event logs to see if any additional information was logged.
  • Verify the permissions for the DLL.
  • Install the .NET Extensibility feature if the request is mapped to a managed handler.
  • Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

Detailed Error Information:

Module    RequestFilter
Notification    BeginRequest
Handler    ExtensionlessUrl-Integrated-4.0
Error Code    0x00000000-- all zeros, no useable error code given.
Requested URL    http://abetterfundraiser:80/
Physical Path    D:\home\site\wwwroot
Logon Method    Not yet determined
Logon User    Not yet determined

More Information:

This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.Thanks, Azure ... but could you be more specific ...

View more information »

Microsoft Knowledge Base Articles: Naturally there are no articles because there is no error data to parse by which relevant KB articles can be found. :)

New Post
5/17/2016 11:51 AM
If you try to navigate to http://SITE/install/install.aspx do you get any details there on an error, or connection problem?

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee Software Solutions DotNetNuke Module Development, Upgrades and consulting. a chat room for DotNetNuke discussions
New Post
5/17/2016 8:46 PM

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.


New Post
5/17/2016 9:21 PM

Here is input from visual studio.  This is from the eventlog.xml file.  I've verified the connection string against the publish settings file.  It's correct. Of course I can't just put those here. :)

I think I'm on the right track now.

        Cannot open database "abetterA8SBWgIv3" requested by the login. The login failed.
        Login failed for user 'DTSTest'.
        at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal&amp; connection)
        at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal&amp; connection)
        at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal&amp; connection)
        at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
        at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
        at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
        at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
        at System.Data.SqlClient.SqlConnection.Open()
        at PetaPoco.Database.OpenSharedConnection()
        at PetaPoco.Database.Execute(String sql, Object[] args)
        at DotNetNuke.Data.PetaPoco.PetaPocoHelper.ExecuteNonQuery(String connectionString, CommandType type, Int32 timeout, String sql, Object[] args)
        at DotNetNuke.Data.DataProvider.PurgeLog()
        at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.PurgeLogBuffer()
        at DotNetNuke.Common.Initialize.LogEnd()
        at DotNetNuke.Web.Common.Internal.DotNetNukeHttpApplication.Application_End(Object sender, EventArgs eventArgs)


HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Azure Setup IssuesAzure Setup Issues

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out