Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

PrevPrev Go to previous topic
NextNext Go to next topic
Forums Document Exchange Lite Installation and Activation Issues
Last Post 08/28/2006 10:29 PM by  Ryan Garcia
Unhandled Error Adding Module to BottomPane
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Ryan Garcia
New Member
New Member
Posts:16


--
08/26/2006 3:36 AM

    Peter,

    The exception below is generated everytime someone opens a document.  I just upgraded our DMX version to 03.04.06 from 03.02.01 hoping that it would go away.  But it did not.  I did not get any errors running the module install over the existing one.

    This is our production server running on DNN 3.2.2.

    Do you have any resolution to this?

    Please help.

    Ryan

    ==================
    ModuleId    : -1
    ModuleDefId: -1
    FriendlyName:
    ModuleControlSource:
    AssemblyVersion: 03.02.02
    Method: System.Threading.Thread.AbortInternal
    FileName:
    FileLineNumber: 0
    FileColumnNumber: 0
    PortalID: 9
    PortalName: Leyte Mudslide Response
    UserID: -1
    UserName:
    ActiveTabID: 339
    ActiveTabName: Document Exchange
    AbsoluteURL: /Default.aspx
    AbsoluteURLReferrer: http://www1.apan-info.net...ult.aspx?EntryId=588
    ExceptionGUID: 0e8fa33c-46a6-4afd-bd84-64a73a7f4b17
    DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
    InnerException: Unhandled Error Adding Module to BottomPane
    Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to BottomPane ---> 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 Bring2mind.DNN.Modules.DMX.Dispatch.MyInitialize() at Bring2mind.DNN.Modules.DMX.Dispatch.a(Object A_0, EventArgs A_1) 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: WWW1
    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    08/26/2006 5:51 PM
    Ryan,
    There is a lot of chat on various (asp.net) forums about this. For reasons unknown to me IIS considers branching out to another page as an error. The behavior, however, is totally wanted and should not trigger any error handling. Unfortunately DNN, by default, logs this error as well so it clogs up the log. You can opt to no longer log this kind of error.
    Just to continue on your specific installation: are you saying it produces a red triangle and stops all execution? Or is this just something you see in the log? If the former, then it is something I've not seen before. I can only imagine that IIS refuses to accept this behavior. What OS/IIS version/trust level are you running?
    Peter
    Ryan Garcia
    New Member
    New Member
    Posts:16


    --
    08/28/2006 10:29 PM
    Thank you for responding.

    This one just clogs up the logs table and does not affect Documents Exchange. I'll figure DNN out on how to not log this error anymore...

    Thanks.

    Ryan
    You are not authorized to post a reply.

    Forums Document Exchange Lite Installation and Activation Issues
    © 2024 Bring2mind Terms Of UsePrivacy Statement