Posted wrong error.

These 2 errors seem to be filling my log viewer and are always together.

????

AssemblyVersion: 03.02.02
Method: System.Web.HttpCookieCollection.Remove
FileName:
FileLineNumber: 0
FileColumnNumber: 0
PortalID: 0
PortalName: BRIT intranet
UserID: 16
UserName: BRITAFE\tbiggin
ActiveTabID: 56
ActiveTabName: Documents(BMS)
AbsoluteURL: /DotNetNuke/DesktopModules/Bring2mind/DMX/Download.aspx
AbsoluteURLReferrer: http://cilr/dotnetnuke/Do...ryId/23/Default.aspx
ExceptionGUID: d1deb6e6-381c-445c-9265-95f2c4163e33
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: Unhandled Error:
Message: System.Exception: Unhandled Error: ---> System.Web.HttpException: Server cannot modify cookies after HTTP headers have been sent. at System.Web.HttpCookieCollection.Remove(String name) at Microsoft.ScalableHosting.Security.Roles.DeleteCookie() at Microsoft.ScalableHosting.Security.RoleManagerModule.OnLeave(Object source, EventArgs eventArgs) at System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---
StackTrace:
Source:
Server Name: CILR

ModuleId: -1
ModuleDefId: -1
FriendlyName:
ModuleControlSource:
AssemblyVersion: 03.02.02
Method: System.Threading.Thread.AbortInternal
FileName:
FileLineNumber: 0
FileColumnNumber: 0
PortalID: 0
PortalName: BRIT intranet
UserID: 16
UserName: BRITAFE\tbiggin
ActiveTabID: 56
ActiveTabName: Documents(BMS)
AbsoluteURL: /DotNetNuke/Default.aspx
AbsoluteURLReferrer: http://cilr/dotnetnuke/Do...ryId/23/Default.aspx
ExceptionGUID: 539af38e-d50a-4b28-82ff-0e4faaace3a5
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: Unhandled Error Adding Module to ContentPane
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Thread.AbortInternal() at System.Threading.Thread.Abort(Object stateInfo) at System.Web.HttpResponse.End() at System.Web.HttpResponse.Redirect(String url, Boolean endResponse) at System.Web.HttpResponse.Redirect(String url) at Bring2mind.DNN.Modules.DMX.Dispatch.MyInitialize() at Bring2mind.DNN.Modules.DMX.Dispatch.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.UserControl.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---
StackTrace:
Source:
Server Name: CILR

Any ideas??

Peter M

Hi Peter,
The System.Threading.Thread.AbortInternal is familiar. It occurs when a page redirects and effctively cuts off the rest of the page being sent to the client. I'm pretty sure all redirect statements in DMX follow the guideline Me.Response.Redirect(someurl, True), where the true stands for 'endResponse' which is what it should do or else cookies would be set after this and that would lead to the dreaded 'Server cannot modify cookies after HTTP headers have been sent' error. It appears in your version (which version is this by the way) some old statements still exist.
Peter

FYI

We noticed this forum when looking for a similar error.

 

Server cannot modify cookies after HTTP headers have been sent.
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.Web.HttpException: Server cannot modify cookies after HTTP headers have been sent.

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. 

Turned out the issue was with the host / schedule process not purging logs correctly. We have blogged about the solution here:

http://www.interactiveweb...ders-have-been-sent/

Hope it helps someone else!