DotNetNuke error

**RFH Reseller: Jaro** · 29th November 2007, 11:31 AM

One of my DNN 4.x sites gives the following error when I click on one of the menu-items in the 'Admin' in 'Host' menu (i.e. Site Settings, File Manager, ...):

Code:

Error: File Manager is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: D:\website.com\wwwroot\web\Admin\Files\filemanager.ascx(691): error BC30560: 'controls_sectionheadcontrol_ascx' is ambiguous in the namespace 'ASP'. ---> System.Web.HttpCompileException: D:\website.com\wwwroot\web\Admin\Files\filemanager.ascx(691): error BC30560: 'controls_sectionheadcontrol_ascx' is ambiguous in the namespace 'ASP'. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

Not all items have this problem (i.e. User Accounts works).
The last thing I did was edit one of the pages (about week ago), logged out and logged in this morning after which the error occurred. So, there's no obvious cause, as far as I can tell.

Any ideas?

Thanks,
J.

**Tanzy** · 29th November 2007, 10:41 PM

Google is your friend on this one. It looks like an issue with a file, not what you did. I have 2 suggestions to try

1. Edit the web.config file and resave it. (You only need to put a space in it somewhere). This will force your website application to restart.

2. Change the website to not have ASP.Net (what ever version). Then enable ASP.Net (whatever version). With a bit of luck this will force the removal of any temp asp.net compiled files on the server.

Hoper this helps. If you need more info do a google search on BC30560: and you will see that it is something to go with temp files on the server. I'm hoping one of these 2 methods will sort it out. Otherwise, you will need to raise a help call.

Ken

**RFH Reseller: Jaro** · 30th November 2007, 07:02 AM

Thanks Tanzy. Tried both and it didn't solve the problem.

I hope Warren can help me out; I'll log a call.

**Tanzy** · 30th November 2007, 04:47 PM

Sorry to hear that they did not resolve your problem. As I say, it was a hope that it would work. I'm sure Warren will be able to sort it via a supprot ticket though.

**RFH Reseller: Jaro** · 30th November 2007, 05:00 PM

I just opened the ticket.

Meanwhile I selected and installed an other CMS next to DNN (it's a small site, so this took only a couple of hours).

I really like DNN, but these unexpected errors (this is not the first time I run into 'unexpected behaviour' of DNN/.NET) bring me doubt. It makes me wonder whether DNN is actually suited for 'professional' use...

**RFH Reseller: smorgo** · 30th November 2007, 07:38 PM

Curiously, I tried to upload a document to my DNN site half an hour ago and got the same error but for controls_moduleauditcontrol_ascx.

I just flipped back to copy the message and paste it here and now it's working!

Maybe something cache related?

**Tanzy** · 30th November 2007, 07:40 PM

I have been using DNN for a number of years now and have not had this issue. I've also tried a number of other portals and find that DNN is the best .net one in my view.

The advantage of DNN I also find is that if there is not a module that does what I want, I can code one myself with a fair bit of ease.

As to its sutability for professional use, there are a number of corporations that are using it.

Right I'm going now, as it is begining to sound like I'm a DNN evangalist

**RFH Reseller: Jaro** · 1st December 2007, 08:28 AM

Warren cleared the 'Temporary ASP.NET Files cache' and now the problem is solved. As predicted (by Tanzy).

And, thanks for showing met the light!

Now we're on the subject...

is there an (easy) way to keep a DNN site running? So it won't take half a minute or so to startup when someone first visits the site (especially for new sites, which attract only a few visitors per hour, this is painful)? Preferably not using an external site for sending 'keep alives'.