Errors after upgrade from 2.3.1.3 to 2.3.1.9

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

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.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
11/17/2009 11:16:14 AM
dsumra
Gravatar
Total Posts 11
View Posts

Errors after upgrade from 2.3.1.3 to 2.3.1.9

Hi,

I recently upgraded from version 2.3.1.3 to 2.3.1.9. After this upgrade when I try to delete an history page I get an error page with following message

" We're sorry but a server error has occurred while trying to process your request.

The error has been logged and will be reviewed by our staff as soon as possible. It is possible that the error was just a momentary hiccup and you may wish to use the back button and try again or go back to the home page."

Please help.

11/17/2009 11:21:33 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Errors after upgrade from 2.3.1.3 to 2.3.1.9

Hi,

I recommend upgrade to version 2.3.2.9

Best,

Joe

11/17/2009 12:07:08 PM
dsumra
Gravatar
Total Posts 11
View Posts

Re: Errors after upgrade from 2.3.1.3 to 2.3.1.9

Hello Joe,

Thank you for your quick response.

I upgraded it to the latest version i.e. 2.3.2.9 as you suggested but the problem still persist. I still get the error page when I try to delete an history page.

 

Regards,

Deepak

11/17/2009 1:31:51 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Errors after upgrade from 2.3.1.3 to 2.3.1.9

Hi,

1. Go to Administration > System Log

2. Clear the log to get rid of all existing errors in the log

3. Go cause the error by deleting history

4. Go back to the log and copy the full stack trace and error message for the last error at the bottom of the log and paste it here in the forums so I can see it.

Please don't post the entire contents of a huge log, that is why I ask you to first clear the log, so we can eliminate all the other errors in there first.

Best,

Joe

11/17/2009 2:00:36 PM
dsumra
Gravatar
Total Posts 11
View Posts

Re: Errors after upgrade from 2.3.1.3 to 2.3.1.9

Hello Joe,

I changed "customerror" setting to "Off" and tried deleting the history page. An error page with following details came up:

 

"Server Error in '/' Application.

Collection is read-only.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NotSupportedException: Collection is read-only.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

 

Stack Trace:

[NotSupportedException: Collection is read-only.]

System.Collections.Specialized.NameValueCollection.Set(String name, String value) +5259386

System.Web.HttpHeaderCollection.SynchronizeHeader(String name, String value) +32

System.Web.HttpRequest.SynchronizeHeader(String name, String value) +44

System.Web.Hosting.IIS7WorkerRequest.GetHeaderChanges(HttpContext ctx, Boolean forRequest) +611

System.Web.Hosting.IIS7WorkerRequest.SynchronizeVariables(HttpContext context) +52

System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +477"

11/17/2009 2:14:20 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Errors after upgrade from 2.3.1.3 to 2.3.1.9

Hi,

You may think this error was a result of upgrade but I do not think so. This error is not pointing to any mojoportal code, it is pointing to ASP.NET runtime code and there is no mojoportal code that touches the http header collection.

I believe you have some 3rd party isapi module probably an url rewriter installed that is not compatible with IIS 7 or else not compatible with IIS 7 in integrated pipeline mode.

You "may" be able to solve it by changing the app pool for mojoPortal to a "Classic" app pool rather than the default "Integrated" app pool.

Probably the best solution is to uninstall this isapi filter and use the free url rewrite module that is now available for IIS 7.

Search for the Web Platform Installer, install it and you will see that it can install the free url rewriter module.

Hope it helps,

Joe

11/17/2009 2:24:28 PM
dsumra
Gravatar
Total Posts 11
View Posts

Re: Errors after upgrade from 2.3.1.3 to 2.3.1.9

Hello Joe,

Sorry I missed your previous reply.

I did as you suggested. I did not get any system errors in System error log but I get warnings in Application error log. Details of warning are as follows:

--------------------------------------------------------------------------------------------------------

- System

- Provider

[ Name] ASP.NET 2.0.50727.0

- EventID 1309

[ Qualifiers] 32768

Level 3

Task 3

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2009-11-17T20:09:24.000Z

EventRecordID 22850

Channel Application

Computer ******

Security

- EventData

3005

An unhandled exception has occurred.

11/17/2009 3:09:24 PM

11/17/2009 8:09:24 PM

736eb31b9ec140968807d0b465047be0

32

3

0

/LM/W3SVC/7/ROOT-2-129029609941209540

Full

/

5048

w3wp.exe

NT AUTHORITY\NETWORK SERVICE

NotSupportedException

Collection is read-only.

http://mojo.com/HtmlEdit.aspx?mid=26&pageid=21

/HtmlEdit.aspx

True

Forms

NT AUTHORITY\NETWORK SERVICE

6

NT AUTHORITY\NETWORK SERVICE

False

at System.Collections.Specialized.NameValueCollection.Set(String name, String value) at System.Web.HttpHeaderCollection.SynchronizeHeader(String name, String value) at System.Web.HttpRequest.SynchronizeHeader(String name, String value) at System.Web.Hosting.IIS7WorkerRequest.GetHeaderChanges(HttpContext ctx, Boolean forRequest) at System.Web.Hosting.IIS7WorkerRequest.SynchronizeVariables(HttpContext context) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)

-------------------------------------------------------------------------------------------------------

I removed IP, Hostname and Site details from the event details for security reasons.

 

Thanks and Regards,

Deepak

11/17/2009 2:31:50 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Errors after upgrade from 2.3.1.3 to 2.3.1.9

Still the error in the log shows a stack trace pointing only to asp.net runtime code not to mojoPortal code. This error is not originating in mojoPortal code or it would point to mojoPortal code in the stack trace.

As I said previously I believe you have a third party isapi filter installed on the server causing this error. Something in your stack is writing to the http headers before it gets to any mojoportal code.

Hope it helps,

Joe

11/18/2009 8:05:19 AM
dsumra
Gravatar
Total Posts 11
View Posts

Re: Errors after upgrade from 2.3.1.3 to 2.3.1.9

Hello Joe,

I configured back the older version i.e. 2.3.1.3 and I did not get the error when I deleted the history.

I made no changes in the IIS configuration. Just for your information I am using Windows Server 2008 standard and Microsoft SQL Server 2008.

 

Regards,

Deepak

 

 

 

11/18/2009 8:26:47 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Errors after upgrade from 2.3.1.3 to 2.3.1.9

Hi,

I googled some fragments of this error and found this in the telerik forums

http://www.telerik.com/community/forums/aspnet-ajax/upload/iis7-instructions-incorrect.aspx

It seems to indicate that this can happen if IIS is not configured to allow custom httpmodules registered in Web.config.

When you upgraded to the new version of mojoPortal did you try to keep your old Web.config file? You should always use the new one.

I would try changing the app pool between a Classic app pool and an Integrated app pool and see if it makes a difference.

I would also try commenting out all references to NeatUpload in Web.config or use the Medium Trust instructions to disable NeatUpload and see if it solves the problem.

Hope it helps,

Joe

11/18/2009 9:19:02 AM
dsumra
Gravatar
Total Posts 11
View Posts

Re: Errors after upgrade from 2.3.1.3 to 2.3.1.9

Hello Joe,

I followed Medium Trust instructions as you suggested and made the following changes:

# Rename Web.config file to Web.fulltrust.config

# Rename Web.mediumtrust.config to Web.config

 

I can delete the history pages now without errors.

Thank you for your quick response and resolution to the problem.

 

Best Regards,

Deepak

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