<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>
<blockquote type="cite"><span style="font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 10px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); float: none; display: inline !important;">So
is it possible the issue is the client's cookie and a clear of said cookie might resolve this?</span></blockquote>
</div>
<br>
<div>If the hunch is right, there's no session that matches whatever cookie is getting sent. That could be the cookie, that could be the web browser, that could be...</div>
<div><br>
</div>
<div>The SP just looks at the cookies set in the inbound HTTP request and attempts to associate them with a session that it's maintaining.</div>
<div><br>
</div>
<div>The easiest way is to play it yourself and witness everything. If you can't replicate the behavior, you'll have a hardr time tracking it down.</div>
</body>
</html>