Question1Replies1764Views×Close popoversri vishnu prabhu (srivishnu) CAPGEMINI CAPGEMINI IN View ProfileSend Message srivishnu Member since 2016 28 posts CAPGEMINI Posted: May 5, 2017Last activity: May 7, 2017Posted: 5 May 2017 5:27 EDTLast activity: 7 May 2017 22:02 EDT Closed Unable to restore passivated requestor; error in authorization activation (no legacy context found)Hi Team,We installed below mentioned hot fixes in our application.HFIX-33066- Unauthorized Access Issue HFIX-23815- Live UI Button missing HFIX-32457- Authentication IssueAfter that we have seen some slowness in the application.We found log file2017-05-05 00:27:42,346 [ES PassivationDaemon] [ STANDARD] [ ] [ ] ( mgmt.base.NodeRequestorMgt) ERROR - Passivation Daemon; Requestor: HDDFBEB4DBAB6646BA6CA522B490E0B77 encountered error during passivation; will re-enqueue com.pega.pegarules.pub.PRRuntimeException: Unable to restore passivated requestor; error in authorization activation (no legacy context found)Let us why this exception getting displayed.Thanks in advanceRegards,Vishnu***Updated by moderator: Lochan to update Categories*** System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post, learn more×Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 3 years agoPosted: 5 May 2017 5:40 EDT×Close popoverBasavaraj Kadakol (BASAVARAJ) PEGA Technical Manager Pegasystems Inc. IN View ProfileSend MessageBASAVARAJ PEGA replied to srivishnuHi Vishnu, Do you have SAML SSO configured the exception could be due to the activation during re-authentication of a timed out session. Please check if there are any configuration issues as SAML SSO.