I have tried to install DNN several times and the results have always been "iffy" to say the least. I finally got one earlier version (4.X) running but the install routine would commony flake out ten or twenty times before it finally decided to do it. I didn't make any changes in settings at any time. I just kept trying the install and it would fail and fail and fail, and then suddenly it would decide to work. I uninstalled and then reinstalled just to make sure I wasn't crazy and I eventually determined that I had done everything right -- it was just DNN that decided not to run the install for ten or twenty times before it decided to do it.
That was not a happy experience. I guess I am from the old school that expects software to have consistent results. You would think that by Version 5.0 somebody would have straightened out the many install problems.
So now I am trying again on DNN 5.1 (saw the notes on the web about "DON'T INSTALL DNN 5.0"). I am on Vista with SQL Server 2005 and I am trying to connect it up to a database in SQL 2005. The problems seem to occur when you want to connect to your own database instead of just blindly accepting all the defaults.
Before anyone asks, yes, I read the instructions (in fact, I read at least ten different versions of the instructions). Yes, I followed them carefully, and no, I don't need any particular instructions on any point because I have been doing similar things for a long time. So it isn't problem that was covered anywhere by the instructions.
After following the instructions carefully, the final step of trying to bring up the install wizard in the browser only results in the following error message:
Anybody got any clue what is causing this?
I should add, when I tried getting answers on previous occassions, there simply weren't any. Doesn't the DNN company support this public version at all? Why are they on version 5.0 and still have a flaky install?
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.
Source Error:
Line 80: </system.webServer>
Line 81: <system.web>
Line 82: <machineKey validationKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902" decryptionKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC" decryption="3DES" validation="SHA1" />
Line 83: <!-- HttpModules for Common Functionality -->
Line 84: <httpModules>
|
Source File: C:\DotNetNuke\web.config Line: 82
Server Error in '/' Application.
Configuration Error