Question
Cognizant Technology Solutions
GB
Last activity: 25 Jan 2022 13:52 EST
Error calling Pega Community REST Service for checking availability of patch releases
After upgrade to Pega 8.6.2 we are observing the the below error in Pega logs after launching the Dev Studio for the first time.
'Error calling Pega Community REST Service for checking availability of patch releases'
Did anyone observe this error in the logs, and please help with the resolution if any?
Accepted Solution
Updated: 25 Jan 2022 13:52 EST
Pegasystems Inc.
GB
@Madhumita_Singh a restart is likely not required.
See:
https://docs-previous.pega.com/pega-services-troubleshooting/when-restart-application-server
You do not need to stop and restart the application server in the following situations:
- When deploying new rules
- When deploying rule-only hotfixes
- After changing the prlogging.xml file You can run the activity Code-RefreshLogConfiguration to process changes at system startup. See this Product Support Community post, Implementing changes to prlogging.xml without restarting.
Pegasystems Inc.
GB
I believe this might be caused by a new function ShowvesionBanner on Dev Studio which is trying to connect community.pega.com through a Final rule of Connect-REST.
Could you try the below?
Set DSS, as below:
Owning Ruleset：Pega-Desktop Setting Purpose：ShowVersionBanner Value：false RuleSet: None
Does that resolve it for you?
Cognizant Technology Solutions
GB
@MarijeSchillern , thanks for replying back.
After adding the DSS, will it require a restart of the server?
Accepted Solution
Updated: 25 Jan 2022 13:52 EST
Pegasystems Inc.
GB
@Madhumita_Singh a restart is likely not required.
See:
https://docs-previous.pega.com/pega-services-troubleshooting/when-restart-application-server
You do not need to stop and restart the application server in the following situations:
- When deploying new rules
- When deploying rule-only hotfixes
- After changing the prlogging.xml file You can run the activity Code-RefreshLogConfiguration to process changes at system startup. See this Product Support Community post, Implementing changes to prlogging.xml without restarting.
Cognizant Technology Solutions
GB
@MarijeSchillern Thanks, it seems to have worked. I have verified the pega logs after adding the above DSS referred in the visibility condition to show the version banner in pzStudioHomeWrapper section and we are not getting the error any longer.
I have added the DSS in our higher environments.