I am getting the following message at the top of the contentpain (sic) but ONLY when logged in as Host or Admin. Id o not get this message if  I am not logged in or am logged in as any other user.

An error has occurred.
Could Not Load Container: /WannaSki/Portals/_default/Containers/DNN-Blue/Image Header - White Background.ascx

This happens on all pages which have content - except it does not happen to any new pages I now add. Obviously I've pushed the wrong button somewhere, or the database has been screwed up.

I am not alone because someone else had the same:

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/13439/scope/posts/Default.aspx

Like that guy I am running 4.0.2 and sql 2005.

Any suggestions?

BTW, the following physical path does exist:

c:\web\WannaSki/Portals\_default\Containers\DNN-Blue\Image Header - White Background.ascx

But I do not know about a virtual one. Here is the message from the log file.

ModuleId: -1
ModuleDefId: -1
FriendlyName:
ModuleControlSource:
AssemblyVersion: 04.00.02
Method: System.Web.UI.Util.CheckVirtualFileExists
FileName:
FileLineNumber: 0
FileColumnNumber: 0
PortalID: 0
PortalName: WannaSki
UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Home
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
ExceptionGUID: e95a18a4-7f97-4b98-9069-afb1a46b306a
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: Unhandled error loading module.
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled error loading module. ---> System.Web.HttpException: The file '/WannaSki/Portals/_default/Containers/DNN-Blue/Image Header - White Background.ascx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(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.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.LoadContainer(String ContainerPath, Control objPane) --- End of inner exception stack trace ---
StackTrace:
Source:
Server Name: COTTER-4B

Curiouser and Curiouser - To quote Alice

So when we start off everything is blue - except for the red error messages.

Under Admin I change Admin and Portals, Skins and Containers to Green. Suddenly everything's green (skins & containers) except for the one or more containers in each window stays blue. All containers in other panes are green. Note that I did NOT ask for anything to be propagated to all other pages. I created and added each page individually and added each module. I did NOT set the individual page or modules colours - ie I wanted them all to be the same.

Then the really odd one. I went to the blog page and there are 5 blog containers, 3 blue and 2 green. These were obviously all added at the same time as I added the blog module. I certainly did not alter the individual colours of 2 of the containers.

So I open up the settings of a blue container in the contentpane and module container shows the Host radiobutton is set, and the module container is  (not specified.)  - I'm not sure if angle brackets screw things up - lets find out ... <not specified>

I click the site radio button, do not change the (not specified) dropdown. When I 'update' the container turns green. The 'could not find' message has gone away .  I return to the settings and the radio button has been reset to Host.

I go through the whole site setting each module by clicking site and all the messages have gone away.

I then go back to site settings and return the site and host to blue and everything is hunky dory, back where it should be. So Ireckon I had a screwed database, and I'm slightly worried it is still screwed. My Gallery module has stopped working - but that may be something else.

There seems to a define time point. I suspect modules I edited after that point were OK, and earlier ones weren't - but I cannot prove it, or even be certain. I suspect there is some sequence of something that cause this, as someone else had the identical problem. And I do not thing it is easily reproducible. Worst type of bug, intermittent ones.

Paul

I know its prolly a bit late - I've just started using DNN

I solved this problem on my site just by selecting the "Site" option instead of "Host".  I left the drop-down box as "<Not Specified>".

I would like to know why the drop-down box only contains the standard DNN containers with the "Host" option, yet it shows all my custom containers with the "Site" option?