Question3Replies1415Views ManjunathaM6763 Member since 2017 6 posts ING Vysya Bank Ltd Posted: 2 years agoLast activity: 2 years 8 months ago Closed Unable to restore passivated requestor; error in authorization activationHi Team,Any idea on what this error could be. We are not able to stop the requestor(H28A64B69EC82CE3B9C9EFC85F26CB88A) as well from SMA.2018-01-26 15:22:06,821 [ES PassivationDaemon] [ STANDARD] [ ] [ ] ( mgmt.base.NodeRequestorMgt) ERROR - Passivation Daemon; Requestor: H28A64B69EC82CE3B9C9EFC85F26CB88A encountered error during passivation; will re-enqueuecom.pega.pegarules.pub.PRRuntimeException: Unable to restore passivated requestor; error in authorization activation (no legacy context found)***Edited by Moderator Marissa to update categories*** System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post 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: 2 years agoManjunathaM6763 ING Vysya Bank Ltd replied to ManjunathaM6763Any help on this would be appreciated. Posted: 2 years agoInakolluH VCE replied to ManjunathaM6763Hi , Below Pdn article might help in your case. Please check the configurations as specified in the pdn article: https://pdn.pega.com/community/product-support/question/unable-restore-… Posted: 2 years agoManjunathaM6763 ING Vysya Bank Ltd replied to InakolluHHi Thanks for your response. I did check that post but that didn't help me. we are not using SSO in our implementation.