Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 2 of 2

Thread: ML/64 encrypted Ticket Error

  1. 08-16-2011, 07:17 AM #1
    mohanrh is offline Member
    Join Date
    Jul 2009
    Posts
    78

    Exclamation ML/64 encrypted Ticket Error

    We are using aspdotnetstorefront ML/64 version 8.0 for our main ecommerce site. Occasionally, some of our users complain that they are unable to logon to the site and the site keeps them redirecting to the main page every time they login. I traced it to the error in formsauthentication.decrypt method during authentication and it mainly happens on IE and usually due to a corrupted cookie. The error is
    ------------------------------------------------------------------------------
    Exception message: Invalid value for 'encryptedTicket' parameter.

    Stack trace: at System.Web.Security.FormsAuthentication.Decrypt(St ring encryptedTicket)
    at AspDotNetStorefront.Global.rBU0jjPAT(Object , EventArgs )
    ---------------------------------------------------------------------------------
    Usually clearing the cookie makes this issue go away. But is there a way to solve this issue without having the user manually deleting the cookie? This is really causing problem to our users and I am looking for a solution at the earliest. Any help in this regard is greatly appreciated.

    Mohan
  2. 09-21-2011, 01:50 PM #2
    mohanrh is offline Member
    Join Date
    Jul 2009
    Posts
    78

    Default Encrypted Ticket Error

    Is there a way to fix " Invalid value for 'encryptedTicket' parameter" error on IE. Even just clearing cookies does not solve the issue. Apparently, physically deleting the cookie finally solves the problem. It would be very helpful if someone could suggest a programmatic solution to this issue.