Question
Accenture Inc
PH
Last activity: 10 Mar 2025 6:08 EDT
There has been an issue; please consult your system administrator -- Error during login
It displays this error when I ty to login using my developer operator.
Error
There has been an issue; please consult your system administrator I checked the logs and it has these errors
Accepted Solution
Updated: 10 Mar 2025 4:19 EDT
Accenture Inc
PH
Hi, this issue has been resolved. Rootcause: The operator has a rule in private edit which was causing the error in the logs. Resolution: I logged in using another developer operator and deleted the instance of the private edited rule from the original operator’s ruleset. After that specific rule has been deleted, I was able to log back in again. Thank you everyone for your help.
Pegasystems Inc.
GB
The error message you're seeing, along with the log entries you provided, points to a few specific issues with your operator configuration that we can troubleshoot.
The error messages "Role is not specified" and "Exception caught while evaluating data transform" typically indicate problems with your operator's access group configuration or role assignments. Here are some steps you can take to resolve this issue:
The error message you're seeing, along with the log entries you provided, points to a few specific issues with your operator configuration that we can troubleshoot.
The error messages "Role is not specified" and "Exception caught while evaluating data transform" typically indicate problems with your operator's access group configuration or role assignments. Here are some steps you can take to resolve this issue:
Troubleshooting Steps
- Check your operator's access group settings:
- Log in as an administrator (if you have access to another working account)
- Navigate to Dev Studio > Operator ID
- Search for your developer operator
- Verify that your operator is associated with the correct access group
- Make sure the access group is properly selected as the default
- Verify roles in the access group:
- Open the access group associated with your developer operator
- Check if all necessary roles are assigned to this access group
- Look specifically for any deprecated portals like "SysAdminDD" and remove them
- Ensure you have the required developer roles such as "PegaRULES:Developer" assigned
- Revalidate and save the access group:
- After making any necessary changes to the access group, perform a "Revalidate and Save"
- This will refresh the role assignments and clear any inconsistencies
- Investigate data transform issues:
- If the above steps don't resolve the issue, there might be a problem with a data transform
- Check the PegaRULES.log file for more detailed information about the failing data transform
- Look for any custom authentication or operator provisioning data transforms that might be causing the error
If you continue to experience issues after trying these steps, please provide additional details from your PegaRULES.log file, especially any entries around the time of the login attempt, as this could help identify the specific data transform that's failing.
References: Troubleshooting mobile app misconfiguration and authentication issues Managing user access with access groups Troubleshooting a Pega Platform application
Accenture Inc
PH
@MarijeSchillern I tried setting different access groups to my operator but got the same error during login. All the other operators in these access groups work just fine. Any other possible cause?
Updated: 6 Mar 2025 2:15 EST
Maantic Inc
IN
Looks like an issue with your access group. Either there is no role specified or the role that is added does not actually exist.
Eclantiqx
IN
Hi @TuesdayMayC,
login with the other operator
and check is there any differences with that operator then change if you have observed any changes then try to login again
Go to Records -> Organization-> OperatorID
Open your Operator
In Security Tab Verify Is Disable check box selected, If selected uncheck that and save
Now try to login
Otherwise clear the cache and try again once
Hope it works
Thanks
Regards
Raja
Eclantiqx
IN
Hi @TuesdayMayC,
Did your issue solved?
Please post here solved or not solved?
If solved, How?
Thanks
Regards
Raja
Eclantiqx
IN
Accepted Solution
Updated: 10 Mar 2025 4:19 EDT
Accenture Inc
PH
Hi, this issue has been resolved. Rootcause: The operator has a rule in private edit which was causing the error in the logs. Resolution: I logged in using another developer operator and deleted the instance of the private edited rule from the original operator’s ruleset. After that specific rule has been deleted, I was able to log back in again. Thank you everyone for your help.
Eclantiqx
IN
Hi @TuesdayMayC,
Thank you for posting the solution for solving the issue
I have one doubt, in the exception, you mentioned
Error
There has been an issue; please consult your system administrator I checked the logs and it has these errors
Exception cause while using Data transform
Role is not specified
How you solve the Role and Data transform issues
Could you please reply for the above issues, how you solved
Thanks
Regards
Raja