Session Ended (Error 3002) RRS feed

  • Question

  • I'm trying to rollout Forefront Identity Manager to my company. I have it installed on three servers : SQL, Portal and Web.

    Everything is setup and seems to be working correctly, except for one issue.

    When I open a browser and navigate to the registration page, I get the first page, click next and immediately get "Session ended. Return to the home page to start again (Error 3002)". If I click to go back to the first page it then works correctly.

    Every user trying this after me wont have the same problem.

    I then browse to the password reset webpage. Again I get the first page, but after entering my credentials I get the Session Ended page again. Once again if i click to go back to the first page, everything then works, and all other users trying this after me work fine.

    It seems to be the very first person to try one of the web pages gets the error, and then everything works. (not just my account, any test account i try first) I'm not sure how long it takes to fail again, as it's not in live environment yet, but when I try it a few days later I'm back to this "first attempt will fail" problem.

    Does anyone have any ideas?

    • Edited by Neurozzzzz Thursday, March 26, 2015 12:47 PM
    Thursday, March 26, 2015 12:46 PM

All replies

  • I'm having the exact same issue...did you ever find a solution?

    My assumption is that it's being cause by the App Pool recycling, which I hope means will be less of an issue when I move it to production and more people are using it. I've thought about trying a higher timeout value on the recycle, or even using a "keep-alive" like script to prevent it from recycling all together, but I'm not sure if just hitting the page is enough, as it never seems to throw the error message until after entering in a username and hitting submit.

    Digging a little further, in the web.config for the Reset Portal (located here: C:\Program Files\Microsoft Forefront Identity Manager\2010\Password Reset Portal), there is a "SessionTimeoutInMinutes" attribute. That seems pretty promising for editing to solve/mitigate this issue. I'm going to try that out and report back.

    • Edited by sunmorgus Wednesday, December 2, 2015 12:54 PM
    Wednesday, December 2, 2015 12:46 PM
  • Hi Sunmorgus,

    Issue got resolved after increasing the Session TimeoutInminutes?

    Let me know as I am getting the same error but I am getting error in production servers.

    Monday, December 5, 2016 1:35 PM