New Install - Error when editing Home page

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
8/4/2008 9:21:26 AM
Gravatar
Total Posts 9

New Install - Error when editing Home page

After a new fresh install, I log on as admin and edit the Home page.  When I save the changes the below error message is displayed.  However, it does appear to save the changes first since reloading the home page shows the changes.  Could there be a setting somewhere that I need to change to prevent this from happening when I edit pages?

My web host is a medium trust, MSSQL 2000, running .Net 2.0 on IIS

Bernie

 

Server Error in '/' Application.
--------------------------------------------------------------------------------

Security Exception
Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

Exception Details: System.Security.SecurityException: That assembly does not allow partially trusted callers.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:


[SecurityException: That assembly does not allow partially trusted callers.]
mojoPortal.Business.SerializationHelper.SerializeToSoap(Object obj) +0
mojoPortal.Business.WebHelpers.IndexWriterTask.QueueTask() +448
mojoPortal.Web.SiteUtils.QueueIndexing() +202
mojoPortal.Web.ContentUI.EditHtml.btnUpdate_Click(Object sender, EventArgs e) +1008
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +105
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +107
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +177
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +7350
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +213
System.Web.UI.Page.ProcessRequest() +86
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
System.Web.UI.Page.ProcessRequest(HttpContext context) +49
ASP.htmledit_aspx.ProcessRequest(HttpContext context) +4
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +358
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

8/4/2008 2:09:39 PM
Gravatar
Total Posts 18439

Re: New Install - Error when editing Home page

Hi,

I've uploaded a new .zip, mojoportal-2-2-6-7-mssqlreleasefiles.zip which has the fix for this. This problem is also discussed in this thread.

Best,

Joe

8/4/2008 2:20:22 PM
Gravatar
Total Posts 9

Re: New Install - Error when editing Home page

Do I need to delete all previous files from the host and upload everything all over again, or is there just a few files that have changed that I can upload?  If at all possible, it would easier to not have to upload 9000+ files again if there's just a few that need it, but can certainly do so if needed.  What is the best way that you recommend?

 

8/4/2008 2:24:34 PM
Gravatar
Total Posts 18439

Re: New Install - Error when editing Home page

You don't need to delete anything, but you can skip a few large folders, ClientScript and Data, but you should upload the rest. I would upload the Setup folder first then the rest except for Data and ClientScript. You can also keep your Web.config file it hasn't changed. You should delete DotNetOpenId.dll from the bin folder of the download package so you don't upload it since it has to be deleted for medium trust.

After you finish uploading, download your Web.config and upload it again, this is just to recycle the application by changing the timestamp on the file.

Hope it helps,

Joe

You must sign in to post in the forums. This thread is closed to new posts.