Question

Unable to check platform REST service due to the HTTP response code of 500 indicated a server error - RMS configuration.

Hi Team,

Please find the error message below while trying to Configure Applications Environment & Release Details (on Release Management Server)

Step Status Info

Trying to save an invalid page: ** ** Unable to check platform REST service due to the HTTP response code of 500 indicated a server error. The response data may contain a reason. // The body of the service's response, which is set up for mapping in the Connector rule, was empty for this service call.
Trying to save an invalid page: page is not valid

Please help.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

November 10, 2017 - 3:35pm

Hi,

Please find the error messages below.

User ID: ppydi 
2017-11-10 14:51:00,136 [.130.231-8407-exec-1] [TABTHREAD0] [                    ] [    PegaPRESTO:07.20] ( rd.queryexec.SqlQueryExecutor) ERROR 10.100.130.231|10.103.195.86 ppydi - An error occured on executing the query for the report definition - There was a problem getting a list: code: 6263 SQLState: S0001 Message: Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option. 
2017-11-10 14:51:00,141 [.130.231-8407-exec-1] [TABTHREAD0] [                    ] [    PegaPRESTO:07.20] ( rd.queryexec.SqlQueryExecutor) ERROR 10.100.130.231|10.103.195.86 ppydi - Query: SELECT "PC0"."tyIsSourceMachine" AS "tyIsSourceMachine" , "PC0"."tyEnvironmentName" AS "tyEnvironmentName" , "PC0"."tyEnvironmentType" AS "tyEnvironmentType" , PEGA_DATA.pr_read_from_stream('.tyProtocol', "PC0".pzInsKey, "PC0".pzPVStream) AS "tyProtocol" , "PC0"."tyHostname" AS "tyHostname" , "PC0"."tyPort" AS "tyPort" , "PC0"."tyContextroot" AS "tyContextroot" , "PC0"."tyLeadOperatorID" AS "tyLeadOperatorID" , "PC0"."pyID" AS "pyID" , "PC0"."pzInsKey" AS "pzInsKey" , "PC0"."pxCoverInsKey" AS "pxCoverInsKey" , "PC0"."tyApplicationName" AS "tyApplicationName" , "PC0"."pyStatusWork" AS "pyStatusWork" , "PC0"."pxCreateDateTime" AS "pxCreateDateTime" FROM PEGA_DATA.pc_pegarmf_work "PC0" WHERE  ( "PC0"."pxCoverInsKey" = ?  AND  UPPER("PC0"."pyStatusWork") NOT LIKE ?   )  AND "PC0"."pxObjClass" = ?  ORDER BY 14 ASC 
2017-11-10 15:01:31,222 [130.231-8407-exec-18] [  STANDARD] [                    ] [    PegaPRESTO:07.20] (  rd.resolve.SqlReportResolver) ERROR 10.100.130.231|10.103.195.86 ppydi - An error occured during resolving the report definition - One of the join conditions involving the following unoptimized property is not allowed, since it can severely degrade performance: Deploy.tyTargetEnvironmentInsKey in class PRESTO-work-EnvironmentSync. Revise the join conditions or optimize the property. 
2017-11-10 15:01:31,249 [130.231-8407-exec-18] [  STANDARD] [                    ] [    PegaPRESTO:07.20] (  rd.resolve.SqlReportResolver) ERROR 10.100.130.231|10.103.195.86 ppydi - An error occured during resolving the report definition - One of the join conditions involving the following unoptimized property is not allowed, since it can severely degrade performance: Deploy.tyTargetEnvironmentInsKey in class PRESTO-work-EnvironmentSync. Revise the join conditions or optimize the property. 
2017-11-10 15:01:31,428 [130.231-8407-exec-18] [  STANDARD] [                    ] [    PegaPRESTO:07.20] (lve.SetQueryValidationResolver) WARN  10.100.130.231|10.103.195.86 ppydi - Union not applied because properties[tyInstanceType] are not optimized in PRESTO-work-BranchReview 
2017-11-10 15:01:31,506 [130.231-8407-exec-18] [  STANDARD] [                    ] [    PegaPRESTO:07.20] (lve.SetQueryValidationResolver) WARN  10.100.130.231|10.103.195.86 ppydi - Union not applied because properties[tyInstanceType] are not optimized in PRESTO-work-BranchReview 
 

Recommendations from PEGA : 

"To resolve this issue, connect to the Microsoft SQL Server using a SQL Client as the database administrator and issue the following command:

sp_configure 'clr enabled', 1 "

 

We cannot implement the above mentioned setting in our database.Please provide us the alternate solutions.

 

 

Pega
November 13, 2017 - 4:00am

Hi Pradeep,

We are looking into the issue. Let you know once we debug it.

Regards,

Chinmaya Hegde

November 13, 2017 - 10:04am
Response to ChinmayaNH

Thank you.
Please let us know if you need a SR to be opened as well.

Regards,
Pradeep Pydi.

November 13, 2017 - 10:19am
Response to PradeepChowdaryP

Hi Pradeep,

This is a component in PDN Exchange, so SR would not help here. 

We will try to provide the fix by the end of next week.

Alternatively, you can as well try to fix it, probably it needs the property to be exposed/optimized.

November 16, 2017 - 12:33pm
Response to ChaitraKamaraju

In addition to the following property (tyTargetEnvironmentInsKey),we have optimized the tyInstanceType as well.Even then we are still facing the same REST service error.

PFA's for the logs.