Hello,

I was trying to run the 4.0 version and found a couple of issues.

I am running it right from the IDE. The first error I get it in the file config.vb line 156

Dim xmlMachineKey As XmlNode = xmlConfig.SelectSingleNode("configuration/system.web/machineKey")

This is always returning NOTHING so I have to wrap the next chunk of codelike this:

If xmlMachineKey IsNot Nothing Then

xmlMachineKey.Attributes("validationKey").InnerText = validationKey

xmlMachineKey.Attributes("decryptionKey").InnerText = decryptionKey

End If

That did not work either, so I then forced the xmlMachineKey to read the node like so:

Dim xmlMachineKey As XmlNode = xmlConfig.ChildNodes(0).ChildNodes(4).ChildNodes(0)

now xmlMachineKey is not nothing and is reading the correct values.

When I run DNN now, it goes into an infinite loop and redirections.

Any ideas are very appreciated.

netguy wrote:

Hello,

I was trying to run the 4.0 version and found a couple of issues.
I am running it right from the IDE. The first error I get it in the file config.vb line 156

   Dim xmlMachineKey As XmlNode = xmlConfig.SelectSingleNode("configuration/system.web/machineKey")

This is always returning NOTHING so I have to wrap the next chunk of codelike this:

   If xmlMachineKey IsNot Nothing Then
      xmlMachineKey.Attributes("validationKey").InnerText = validationKey
      xmlMachineKey.Attributes("decryptionKey").InnerText = decryptionKey
   End If

That did not work either, so I then forced the xmlMachineKey to read the node like so:

   Dim xmlMachineKey As XmlNode = xmlConfig.ChildNodes(0).ChildNodes(4).ChildNodes(0)

now xmlMachineKey is not nothing and is reading the correct values.

When I run DNN now, it goes into an infinite loop and redirections.

Any ideas are very appreciated.

I tried this, and although xmlMachineKey was initialized (not nothing), it did not seem to be a reference to the appropriate key, and still got an exception when attempting to write to the attributes. I am using most likely a later version than you, dnn 4.0.2, but I would think the developer config file has not changed much. but it is not reading the correct values.

Have you or anyone else experienced this, and if so found a solution?

System Configuration:

Windows XP Pro SP2 + All Latest Patches
Visual Studio 2005 Pro (not-beta)
SQL 2005 Developer

Installed DotNetNuke 4.02 to C:\Data\Projects\DotNetNuke4_4.0.2...

2 hours later... I renamed the DotNetNuke directory, removing the dots from the path, thinking there may be some security setting preventing paths with dots, with no luck. I just restarted the debug session, and it bombs out in exactly the same manor as described earlier in this thread/message.

 

Yah, I am evaluating moving to DNN from Rainbow.  I have to say DNN doesn't have 1/1,000,000 the organization Rainbow Portal has.

I'd like to see a post if anyone knows an answer.  I have this same exact problem.

The issue with DNN is

GIVE ME A SQL SCRIPT TO INSTALL THE DATBASE AND SETUP THE APP

The app's code should not be used to install itself.  It loops because it is writing to it's own web.config, which is not a good idea.   I can't believe this made it out the door at DNN...   I know I have it set up right.  Clearly there is something wrong if so many other people today have the same issue.

 

I'm have the exact same problem

 

Anyone from core found a fix yet?

BTW, error message displayed by DNN leads you down the wrong path.

Tom

You probably have something invalid in your web.config file.   Basically, you have to step through the code and find out.   What is valid is written to the web.config, which causes .NET to think the application is starting anew.   So it will keep looping and failing at the same problem.

For me, I think it turned out to be an invalid web.config file. For what it's worth, I started with the development web.config file. To really fix the problem, I re-extracted the source (which forced me to have to reset permissions on DNN4's directory, and started with the Release.config, modifying only the debug attribute and the SQLConnectionString values.

Then, for grins & giggles, I figured I would change the template used by DNN to the corporate web site template, but that blew up as only the default dotnetnuke template is included with the source.

I am happy to report that it is now comfortably humming along with no apparent issues. Thanks for the tips!!