Well we’ve seen a fair amount of reminiscing in the blogs to date. It’s interesting even to me to hear from the Exchange veterans about the high-flying times back in the 4.0 and 5.5 days. I’m a ...
Updated Jul 01, 2019
Version 2.0
Blog Post
Jason: You're going to have to give us more information about your scenario for us to be able to help out. If you need someone to talk to about the problem, I suggest calling PSS.
Ross: Are you accessing OMA through a URL that looks liks "https://<your server>/oma", or is there something after the '/oma'? If there is something behind the '/oma', the application is going to think that you're trying to access a particular item (eg. an email or meeting request) that you bookmarked from your last session using OMA. Since OMA no longer has information (session state) about what item was matched to the URL you're using, it is letting you know that the session state has been cleared since you last accessed that URL.
Ross: Are you accessing OMA through a URL that looks liks "https://<your server>/oma", or is there something after the '/oma'? If there is something behind the '/oma', the application is going to think that you're trying to access a particular item (eg. an email or meeting request) that you bookmarked from your last session using OMA. Since OMA no longer has information (session state) about what item was matched to the URL you're using, it is letting you know that the session state has been cleared since you last accessed that URL.