I am using the DNN Community Content management application (version 05.05.00 (653)) on a site hosted by GoDaddy. The site is finally up after installing / uninstalling 3 times. The issue that seems to make it crash is when I'm trying to upload a module that isn't included in the installation, (IE: the Gallery module) .

This latest install seems to relatively stable but it still throws an error whenever I try to upload a module. Unfortunately with the GoDaddy configuration I can't figure out how to set up a debug ... any ideas ??

Gallery 04.03.00 and 04.03.01 RC are known to have a compatibility issue with DotNetNuke 05.05.00 and will throw a duplicate key error when first loading or when adding an album. I am working on a 04.03.02 Beta which will fix that issue and several others.

What other modules have you tried installing?

Are you running under ASP.Net 4.0?

What are the details of the error messages you are seeing either during the install of a module or that you find in the Admin-->Event Viewer following an failed install of a module? Please post the details including the stack trace portion of the error here.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Looked at permissions as you guys indicated and ALL folders seem to have full read/write permissions. After checking this, I attempted a re-install of the gallery module. 4.03 and it has now totally crashed the GoDaddy/DNN site for the 4th time. This is getting frustrating

Server Error in '/pipes' 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>