Hi Everyone
Previously: I had a working 05.04.02 installation that I attempted to upgrade to 05.06.00. That upgrade did not work, and since that path had started at 04.04.01 I decided to start new. The key killer was dbo.Tabs table updates which did not complete correctly and therefore removed the HOST menu options (story for another day). I was NOT able to resolve this issue by using Management Studio.
Today's problem is a new fresh installation on SQL Server 2005, ASP .NET 4.0 and Windows Server 2008 R2.
Using a the fresh installation DNN web application, the error on the "Install Optional Module" page is
Error Installing Module(s): Telerik (05.06.00).
It's interesting that Telerik installation was another problem in the upgrade from 05.04.02 to 05.06.00. Like many people, I took the DLLs from the Install version and used FTP to put them into the bin (I agree that this patch is a workaround and there is no way for people to verify if moving a DLL will actually work well). In today's story, the DLLs from the install and the bin are identical (as you would expect from a fresh installation).
I have decided to NOT wait for an answer to this problem, but instead go back to the 05.05 series (latest) and start from there. I will continue to go back until I have a latest series version level that works on a fresh (new) installation. I find it useful to leave these specific technical comments in the forum since need to know that their issue has been encountered before (technical wiki mentality).
I also have general safe advice for people doing a DNN upgrade. In addition to archiving the files and the database, I would NOT recommend going forward with any version update which produces errors. At this point I am not convinced that the upgrades from the 05 series has been performing sufficient prerequisite database consistency checks before completing a process. In other words, the upgrade path should not just act, in the sense of making new changes, but at each stage should be checking for database consistency (especially dbo.Tabs which is a key table for administrative access) before attempting a new update. The mentality comes from the database world, where a transaction cannot complete unless all the related steps complete successfully (and if it does not complete, the process should roll back to where you were at the beginning). My perception is that the 05 series updates to now have been moving forward and assuming that people will fix errors if and when they occur (whether in the file structure, as with missing files, or in the database as with partially complete T-SQL statements -- and my proof is the evidence of 05 series upgrade failures posted to this forum). Based on the forum traffic, there is no particular version of DNN which I could recommend because this software is inherently offered as a trial-and-error solution, so proceed at your own risk.
FYI -- When i look at the website directly, I get the following nominal error:
Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>
|
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>
|