Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Mangesh Walhe (Mangesh Walhe) Senior System Architect
Pegasystems Inc.
JP
Mangesh Walhe Member since 2018 15 posts
Posted: Sep 26, 2018
Last activity: Sep 28, 2018
Posted: 26 Sep 2018 2:56 EDT
Last activity: 28 Sep 2018 2:16 EDT
Closed
Solved

Failure in RoboticsApiHelper.GetRobotProfile after robot registration

Facing an issue while connecting from Platform to RPA. Registration is successful, but it fails immediately after that when it tries acquiring the 'Profile information' from Pega Platform server. Has anyone come across such problem?

Pega Platform version is 7.4 and Robotics version is 8.0.1088.0

Following is the log snippet (can not share the whole log just yet.):

INFO | 2018-09-25 17:04:28,583 | 1 | 1 | 8064 | STA | Robotics | | | RoboticsApiHelper.RegisterRobot - Robot registration started. Robot Name: <VM Name>, Workgroup: <WkGroup Name>, Authentication Mode: 'Basic'.
INFO | 2018-09-25 17:04:29,071 | 1 | 1 | 8064 | STA | Robotics | | | RoboticsApiHelper.RegisterRobot - Robot registration succeeded.
ERROR | 2018-09-25 17:04:29,279 | 1 | 1 | 8064 | STA | Robotics | | | RoboticsApiHelper.GetRobotProfile - Get robot profile failed. Robot Name: <VM Name>, Status Code: 'NotFound'.
ERROR | 2018-09-25 17:04:29,284 | 1 | 1 | 8064 | STA | Robotics | | | Error requesting data from Pega. http://<Host>:<port>/.../api/v1/data/D_pxRobotProfile
ERROR | 2018-09-25 17:04:29,285 | 1 | 1 | 8064 | STA | Robotics | | | Code: NotFound(404), Content: {
"pxObjClass":"Pega-API-Data"
,"errors":[
{
"ID":"Pega_API_017"
,"message":"指定されたパラメータ ID でデータ ページが見つかりません"
,"pxObjClass":"Pega-API-Error"
}
]
}

Show More

Facing an issue while connecting from Platform to RPA. Registration is successful, but it fails immediately after that when it tries acquiring the 'Profile information' from Pega Platform server. Has anyone come across such problem?

Pega Platform version is 7.4 and Robotics version is 8.0.1088.0

Following is the log snippet (can not share the whole log just yet.):

INFO | 2018-09-25 17:04:28,583 | 1 | 1 | 8064 | STA | Robotics | | | RoboticsApiHelper.RegisterRobot - Robot registration started. Robot Name: <VM Name>, Workgroup: <WkGroup Name>, Authentication Mode: 'Basic'.
INFO | 2018-09-25 17:04:29,071 | 1 | 1 | 8064 | STA | Robotics | | | RoboticsApiHelper.RegisterRobot - Robot registration succeeded.
ERROR | 2018-09-25 17:04:29,279 | 1 | 1 | 8064 | STA | Robotics | | | RoboticsApiHelper.GetRobotProfile - Get robot profile failed. Robot Name: <VM Name>, Status Code: 'NotFound'.
ERROR | 2018-09-25 17:04:29,284 | 1 | 1 | 8064 | STA | Robotics | | | Error requesting data from Pega. http://<Host>:<port>/.../api/v1/data/D_pxRobotProfile
ERROR | 2018-09-25 17:04:29,285 | 1 | 1 | 8064 | STA | Robotics | | | Code: NotFound(404), Content: {
"pxObjClass":"Pega-API-Data"
,"errors":[
{
"ID":"Pega_API_017"
,"message":"指定されたパラメータ ID でデータ ページが見つかりません"
,"pxObjClass":"Pega-API-Error"
}
]
}

ERROR | 2018-09-25 17:04:29,285 | 1 | 1 | 8064 | STA | Robotics | | | RoboticsService.RegisterRobot - Unable to acquire RobotInfo.
INFO | 2018-09-25 17:04:29,309 | 1 | 1 | 8064 | STA | Robotics | | | RoboticsApiHelper.RobotSignOff - Robot sign off started. Robot name: <VM Name>.
ERROR | 2018-09-25 17:04:29,472 | 1 | 1 | 8064 | STA | Robotics | | | RoboticsApiHelper.RobotSignOff - Robot sign off failed.

The runtime shuts down after the above log.


Show Less
To see attachments, please log in.
Robotic Process Automation

  • Toshiro Sasaki

Accepted Solution

Posted: 6 years ago
Posted: 28 Sep 2018 2:16 EDT
Mangesh Walhe (Mangesh Walhe) Senior System Architect
Pegasystems Inc.
JP

The problem has been resolved.

After checking the sequence of events after registration, we concluded that problem must be in authentication/access group evaluation. Checked Dynamic System settings followed by the 2 decision tables

  1. pyGetWorkGroupForRobotByRequestorOperatorID and
  2. pyGetAccessGroupForRobotByWorkGroup

Since the above were alright, we checked the Workgroup value assigned to the Operator ID instance corresponding to the Robot. Found that, someone had by mistake changed it to the value due to which it won't pass through the decision table conditions.

It is working fine now after restoring the value with a valid one. 

Thank you everyone for all the support.

To see attachments, please log in.
Posted: 6 years ago
Posted: 27 Sep 2018 23:16 EDT
Andrew Grondin (grona) GCS Solutions Engineer I
Pegasystems Inc.
US

Text translates to "The data page can not be found with the specified parameter ID". 

Is that url the one you're actually using or is it just an example string?

To see attachments, please log in.

Accepted Solution

Posted: 6 years ago
Posted: 28 Sep 2018 2:16 EDT
Mangesh Walhe (Mangesh Walhe) Senior System Architect
Pegasystems Inc.
JP

The problem has been resolved.

After checking the sequence of events after registration, we concluded that problem must be in authentication/access group evaluation. Checked Dynamic System settings followed by the 2 decision tables

  1. pyGetWorkGroupForRobotByRequestorOperatorID and
  2. pyGetAccessGroupForRobotByWorkGroup

Since the above were alright, we checked the Workgroup value assigned to the Operator ID instance corresponding to the Robot. Found that, someone had by mistake changed it to the value due to which it won't pass through the decision table conditions.

It is working fine now after restoring the value with a valid one. 

Thank you everyone for all the support.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice