If you have questions about using mojoPortal, you can post them here.
You may want to first review our site administration documentation to see if your question is answered there.
Hi,
I have a site that is running on mojoPortal running...
mojoPortal 2.3.6.1 MSSQL / ASP.NET Info v4.0.30319 Running in Full Trust / feed-manager 0.0.1.0
I get the above error when I have created a new page (good so far) then added a Feed Manager as the content and I get a server error. Log entry...
------------------------------------------------------------------- 2011-10-10 16:35:33,051 ERROR mojoPortal.Web.Global - 75.83.84.81-en-US - /feed.aspx System.Configuration.ConfigurationErrorsException: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (d:\web\vhosts\seamanmarinesoftware.com\httpdocs\feedmanager\web.config line 701) at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal) at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors) 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) 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 MTConfigUtil.GetCompilationConfig(String vpath) 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, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at mojoPortal.Web.UI.CmsPage.LoadPage() at mojoPortal.Web.UI.CmsPage.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at mojoPortal.Web.mojoBasePage.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.default_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) -------------------------------------------------------------------------------
I went to another of my sites (using mojoportal 2.3.7.0) and it does NOT get the error???
I am going to make a backup of the site, then upgrade mojoPortal to version 2.3.7.0... is there any additional things I should look out for or change after the upgrade? Any thoughts of what would be causing the error?
Hi Phill,
you have a web.config file in your /FeedManager folder that should not be there, mojoPortal does not have a web.config file there.
Hope that helps,
Joe
Hi Joe A,
Of course it doesn't it actually cures what ailed it???? I have no idea how I got a config file in that folder but removing it certainly cured its ailments.
Would there be any great advantage in upgrading to 2.3.7.0 from 2.3.6.1????
Thanks
Yes, the presence of that extra Web.config was the cause of the error, therefore removing it was the fix.
To decide if you want to upgrade, you can read the release notes for versions since version 2.3.6.1.
Best,