 |
|
|
Joined: 11/21/2005
Posts: 201
|
|
|
DotNetNuke 4.0.3; Windows Server 2003 running SQL Server 2005 Express
An error has occurred.
Could Not Load Container: /DotNetNuke/Portals/_default/Containers/DNN-Blue/Image Header - Color Background.ascx
When logged into the portal as a user (even as Admin or Host), I'm getting this error, displaying at the top of the LeftPane and/or the ContentPane - when displaying a page where there is at least one container in one or both of those panes. If there is a container in any other pane, the error does not appear above those panes. This error does not happen when NOT logged in, such as when browsing annonymously. Below the error, the containers in the LeftPane and ContentPane display OK. Any ideas on how to remedy this?
If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
|
| |
|
|
 | |
|
|
Joined: 11/21/2005
Posts: 201
|
|
|
On the Home page load, I sometimes get a more detailed error message. But for a two-week old DNN user, it isn't clear to me what's gone wrong. Any possible solutions? Thank you...
 |
Could Not Load Container: /DotNetNuke/Portals/_default/Containers/DNN-Blue/Image Header - Color Background.ascx
DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled error loading module. ---> System.Configuration.ConfigurationErrorsException: The element 'buildProviders' cannot be defined below the application level. (C:\DotNetNuke\web.config line 72) at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult) at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject) at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject) at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission) at System.Configuration.BaseConfigurationRecord.GetSection(String configKey) at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName) at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index) at System.Web.Configuration.RuntimeConfig.get_Compilation() at System.Web.Compilation.BuildManager.IsBatchEnabledForDirectory(VirtualPath virtualDir) 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.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 --- |
If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
|
| |
|
|
| |
|
|
|
you need to add the root folder of your installation (/dotnetnuke) as web site or virtual directory in IIS settings.
|
| |
|
|
| |
|
|
Joined: 11/21/2005
Posts: 201
|
|
|
Thank you for the pointer, but I'm not exactly sure where to change IIS Settings (I'm fairly new to DNN and IIS). I tried the following:
Web Sites [folder] > MySite (highlight and right-click) > Properties > Home Directory [tab] > Local Path: C:\DotNetNuke (which points to my DNN 4.0.3 installation)
Application Name: Create [button] : DotNetNuke; Execute Permissions: Scripts Only
I want the default DNN portal to come up when browsing to mydomain.com, and it does with this configuration above, but still my Admin and Host users get the errors described above. Funny that only the Admin and Host users get the errors; no other users, or annonymous users, get the error.
When I re-create a Virtual Directory (Application Name) 'DotNetNuke' under mydomain.com, and point the Virtual Directory to C:\DotNetNuke, then I can browse to mydomain.com/dotnetnuke as Admin and Host and login without errors. That's great, but I want my default portal to come up when browsing to mydomain.com alone. Do you know how I can do that, while leaving the Virtual Directory active?
If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
|
| |
|
|
| |
|
|
Joined: 11/21/2005
Posts: 201
|
|
|
It turns out I was trying to push my first-DNN-install-created-portal to do too much. And when I changed the way I was configuring DNN, the errors disappeared.
I was trying to get the first-DNN-install-created-portal (which I'll call "core portal" for short) to be accessible not only from the URL it was orginally installed and configured to resolve to (www.mydomain.com/dotnetnuke), but also to resolve to a simple URL (a web root URL, that is www.mydomain.com). Messing with IIS settings but mostly trying to have DotNetNuke resolve aliases for both the example URL's above, led me to get the errors above when attempting to access the core portal. I could reach the core portal via either URL above, but when I logged into the portal as either Admin or Host by way of the simple URL, I would get the errors. If I accessed the portal via the alias to my DotNetNuke application (www.mydomain.com/dotnetnuke), then I got no errors logged in as Admin or Host. Strange thing was that if I logged into either URL as any user OTHER than Admin or Host, no errors occured.
Once I stopped trying to configure IIS and DNN in a way that would never properly resolve, the errors went away. Basically, I created a Parent portal and left my Core portal alone. If you need it, there's more about this in another post:
http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/108/threadid/42564/scope/posts/Default.aspx
Tikkune
If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
|
| |
|
|
| |