Skip to main content

Dotnetnuke 05.01.00 Beta – Upgrade Issues 1 – Host->Module Definition page are blank

[PS: As part of consolidation, I am moving all my Dotnetnuke & SharePoint related blog post from http://www.laksha.net/Dotnetnuke.aspx to http://blog.laksha.net.]

I upgraded my website to Dotnetnuke 05.01.00 from Dotnetnuke 04.09.02. Most of the things I tested are working fine. During the upgrade I see few errors but that did not affected the website and are also listed as known issue with Dotnetnuke 05.01.00 Beta (build 266) “Known Issues with Build 266”.

00:00:09.388 -   Executing Script: 05.01.00.SqlDataProvider Error! (see 05.01.00.log for more information)
00:00:25.627 -   Installing Package File DNN-MinimalExtropySkin_01.00.02_Install:  Error!

Dotnetnuke 05.01.00 Beta – Upgrade Issues 1 - After upgrade to Dotnetnuke 05.01.00, contents on the Host->Module Definition page are disappeared.

Below is a screenshot of the Host->Module Definition page.

image 

Interestingly I can modify the URL to http://www.lakshadev.net/tabid/7/ctl/Install/rtab/7/portalid/0/Default.aspx (from http://www.lakshadev.net/tabid/18/portalid/0/Default.aspx) to open the module install modules (install extensions).

image




Comments

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then you do not get

Howto Run Your HTML Static Website Locally In IIS On Windows PC

WHAT & WHY: As a developer many time you may wish if you could run your static HTML website locally on your computer (Windows 7, Windows Vista, Windows XP, Windows 2008). Although with Static website, you could easily download and double click the index.html or home.html file to open and run other pages. But this will not give you the real world senario. For example you will not able to use a path like /images/home-page-banner.jpg. You will have to use a relative paths like ../images/home-page-banner.jpg. Following are very easy steps to do so. These steps are for Static HTML website. I will also post steps for more advance websites that uses ASP, ASP.NET, Dotnetnuke etc and uses database server.   WHAT YOU NEED: 1. IIS Server installed on your local machine 2. FTP username, password to download files form your FTP server 3. Administrative rights on local machine. Many task will display messages requesting Administrative privilege to run the task.    STEPS: 1.

How To Create Virtual Machine Using Existing vmdk file in VMWare Workstation

vmdk file is hard disk of the VMWare virtual machine. There are many scenarios where you may need to create a new virtual machine for an existing vmdk file. This is also an alternate Method to the “ vmx is not a valid virtual machine configuration file – Could not open virtual machine ” issue. Please refer to the previous post “ Could not open virtual machine – vmx is not a valid virtual machine configuration file ” for a full list of possible resolution. This post is to describe one of the solution in more details. How To Create a new virtual machine & attach the existing .vmdk file: 1. Open VMware and select create a new virtual machine with custom (advanced) configuration option. 2. Chose “I will install the operating system later”. and chose “I will install the operating system later”. 3. Select the operating system that matches the operating system in your existing .vldk file. 4. Select a location of the new virtual machine 5. Chose “Use an exis