Sebastian,

Yes, since I am working off a live site (I unfortunately done have a development area for this site). What I did was make an immediate backup of the SQL Database and all the website files. I downloaded the web files backup to my local machine, applied the update to the files locally, and uploaded the new files to the website. (The reason I did it that way is that using FTP to uploaded the files individually as a batch just took forever, was faster to do it this way). After the upload, I navigated to the site which kicked off the upgrade process.

---

Ben Santiago, MCP Certified & A+ Certified
Programmer Analyst
(SQL, FoxPro, VB, VB.Net, Java, HTML, ASP, JSP, VBS, Cognos ReportNet)

"does you web.config contain a "location" node -there is a known issue where this causes web.config merges to fail, which looks like it may be your issue."

Found this quote on another forum. I did have the location node to prevent child inheritance for virtual directory applications. When I commented out the tag the install ran without errors.

Hope this helps.

The location tag was added by me. It should not be part of any DNN instillation. We installed our DNN on the root of the site. When a department needed an application to run along side DNN, we put it in a virtuale directory. The application was inheriting all of the settings from the DNN web.config file so we added the location tag with the attribute "inheritInChildApplications=false". The only reason I found it was I was doing a line by line comparison of a newly installed DNN web.config with my current one. After gettng the upgrade to work on our test site l can no longer log-in with any account but that is for another post.

Good luck on finding you problem. It has to be someting that was added to the web.config file that is causing the problem.