Certain Users unable to access site unless they delete history

[frank@omnica.co.uk]

Hi

We have a recurring issue were certain users cannot access the webstore (.NET error page appears). We think it is related to another post <a href="http://forums.aspdotnetstorefront.com/showthread.php?31647-ML-64-encrypted-Ticket-Error&highlight=ML%2F64+encrypted+Ticket+Error">ML/64 encrypted Ticket Error</a>

The suggestion here is to clear the cookie which makes the this issue goes away. Indeed our users have cleared their history as a short term fix for the problem. Is there a way to perhaps rename the authentication cookie which will force everyone to login again and perhaps fix the issue? Or, is there another way to approach. The error we think that is responsible is shown below:

Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.


Is impersonating: False
Stack trace: at AspDotNetStorefront.Global.oAxw6cgXp(Object , EventArgs )
at AspDotNetStorefront.Global.Application_Authenticat eRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep. System.Web.HttpApplication.IExecutionStep.Execute( )
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean& completedSynchronously)


Many thanks for any help provided

Frank

[danrawk]

hey frank!
just curious if you were able to track this down to resolution? having a similar behavior. feels like a cookie issue but i can't duplicate it to track down the error code.

resetting/erasing cookies in maintenance seems to fix, as does deleting browser cookies, but that's not a long term fix.

dan

Hi

We have a recurring issue were certain users cannot access the webstore (.NET error page appears). We think it is related to another post <a href="http://forums.aspdotnetstorefront.com/showthread.php?31647-ML-64-encrypted-Ticket-Error&highlight=ML%2F64+encrypted+Ticket+Error">ML/64 encrypted Ticket Error</a>

The suggestion here is to clear the cookie which makes the this issue goes away. Indeed our users have cleared their history as a short term fix for the problem. Is there a way to perhaps rename the authentication cookie which will force everyone to login again and perhaps fix the issue? Or, is there another way to approach. The error we think that is responsible is shown below:

Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.


Is impersonating: False
Stack trace: at AspDotNetStorefront.Global.oAxw6cgXp(Object , EventArgs )
at AspDotNetStorefront.Global.Application_Authenticat eRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep. System.Web.HttpApplication.IExecutionStep.Execute( )
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean& completedSynchronously)


Many thanks for any help provided

Frank

[jsimacek]

There is another thread on this already, but see fix at: http://manual.aspdotnetstorefront.co...r-10-ie10.aspx