Question2Replies273Views×Close popoverPraveen Kumar (PraveenK999) AXA ONE-IT AXA ONE-IT IN View Profile PraveenK999 Member since 2015 1 post AXA ONE-IT Posted: November 23, 2016Last activity: November 23, 2016Posted: 23 Nov 2016 2:27 ESTLast activity: 23 Nov 2016 7:38 EST Closed Error: This node is being shut down. You must have shutdown privileges to log in."This useually happens in Pega version 7, due to Quiesce being triggered from SMA.The loga would show following error: This node is being Quiesced. User XX with requestor id (H08F89D5ED7D288085DC77A0F26627C81) does not have Quiesce admin privileges to login.Solution: you must still include either the PegaRULES:HighAvailabilityAdministrator or PegaRULES:HighAvailabilityQuiesceInvestigator user role in a user's access group.OR Go to SMA --> Administration-->High Availability Management --> "Cancel Quiesce"This is a feature which is mainly used for deployment or patch work. 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: 4 years agoPosted: 23 Nov 2016 2:30 EST×Close popoverPraveen Kumar (PraveenK999) AXA ONE-IT AXA ONE-IT IN View ProfilePraveenK999 AXA ONE-IT replied to PraveenK999Also if SMA is not being controlled properly any developer may use SMA wihtout logi, so logs might not tell true story related to the operator ID Posted: 4 years agoPosted: 23 Nov 2016 6:25 EST×Close popoverSantanu Bhattacherjee (Santanu) PEGA Manager CRM - Field Service Pegasystems Inc. IN View ProfileSantanu PEGA replied to PraveenK999Hi To secure SMA you need to do the config at server level. See this article which talks about securing SMA on weblogic .