Rank: Newbie
Groups: Member
Joined: 9/9/2014
Posts: 0
|
Everything is working fine locally, but when moving to a server, exceptions are thrown.
Pretty clueless as to what may be the issue here, been getting this error.
I am using DLL version of EO.PDF as (5.0.34.2)
This session is no longer valid. If you wish to reuse the session later, please consider calling GetCookies to retain the session cookies, then reuse these cookies through HtmlToPdfOptions.Cookies with another session. (6)
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: EO.Pdf.Internal.k4: This session is no longer valid. If you wish to reuse the session later, please consider calling GetCookies to retain the session cookies, then reuse these cookies through HtmlToPdfOptions.Cookies with another session. (6)
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:
[k4: This session is no longer valid. If you wish to reuse the session later, please consider calling GetCookies to retain the session cookies, then reuse these cookies through HtmlToPdfOptions.Cookies with another session. (6)]
STO.GenerateLetterandEnclouser.Page_Load(Object sender, EventArgs e) +1019
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35
System.Web.UI.Control.OnLoad(EventArgs e) +91
System.Web.UI.Control.LoadRecursive() +74
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207
Please help me to fix this one,Thanks in advance.
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,088
|
Hi,
This often indicate a deadlock caused by ASP.NET session lock, it can happen if you try to perform a conversion that relies on a request to the same server. For example, consider the following sequence:
A1. Client browser request page1;
A2. The server creates a session and locks that session;
A3. The server runs code associated to page1, for example, Page_Load handler;
A4. After server finishes processing the page, it releases the session lock;
If you try to perform a conversion on step 3 and the Url points to the same server, then the following deadlock can occur:
B1. Step B3 will not finish until the HTML to PDF converter returns;
B2. The converter will not return until your server servers the page you wish to convert to the converter;
B3. Your server will not be able to start serving the page until step A4 occurs;
B4. Step A4 will not occurs until step A3 finishes;
ASPXToPDF has special code to get around this situation. So you can try that and see if it resolves the problem for you.
Thanks!
|