March 29, 2002 at 2:20 pm
Anybody have any info on what causes these? Are there any known issues related to Citrix metaframe 1.8?
April 1, 2002 at 6:22 am
First what server pack revision are you running, I believe there was one of the service packs wih something about orphaned connections and I am digging around for.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 1, 2002 at 8:48 am
sql 7 sp3. I think it may have something to do with citrix or a slow server as none of our other clients have this problem.
April 1, 2002 at 9:58 am
Are you sure these are orphaned? Are there still sessions running on Citrix? You can disconnect and your session on Citrix wouls stay open, so your connection would be open. This is as if you were connected from your desktop and had left for the weekend. The spid wouldn't be orphaned, your connection is still open.
Steve Jones
April 1, 2002 at 11:16 am
the user can log out of citrix and their sql session is still there. They seem to have begin and end times(in sql) that are about 5 seconds apart. That is how I can tell which session is active and which is the orphan. The orphans randomly appear throughout the day for most users.
April 1, 2002 at 9:19 pm
Another DBA I work with remarked that he saw this problem with Citrix Metaframe 1.8 at a previous place of employment. There would be sessions still open at 3 AM in the morning, when the Citrix farm was down. They ended up altering several TCP/IP settings based on a Microsoft Knowledge Base article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q120642
We've not seen orphaned sessions in our Citrix Metaframe XP farm, however.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
April 2, 2002 at 9:14 am
There are numerous parameters in that article. Do you know which ones they changed in order to alleviate the problem?
April 2, 2002 at 11:37 am
I believe they altered:
KeepAliveInterval
KeepAliveTime
SessionKeepAlive
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
March 2, 2015 at 6:12 am
have relevant question for this old posting. Goal in my space is to reduce the quantities of this error generated in the log files after night IIS reset:
Exception:
Source: Microsoft.ReportViewer.WebForms
Message: ASP.NET session has expired or could not be found
StackTrace: at Microsoft.Reporting.WebForms.ViewerDataOperation..ctor()
at Microsoft.Reporting.WebForms.SessionKeepAliveOperation..ctor()
at Microsoft.Reporting.WebForms.HttpHandler.GetHandler(String operationType)
at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
If I set the SessionKeepAlive to false just before our nightly IIS resets, and then back to true after the reset, then
(1) will that minimize impact to client experience overall ie cause timeouts only at time of IIS reset?
(2) will users in the middle of actively editing a report in Report Builder loose their changes? Say they started editing a report at 11pm, IIS reset at 11:01pm, and a report in report builder was in the middle of being editted. (what would user experience be?).
Thanks in advance.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply