Question
Midland Credit management
IN
Last activity: 12 Mar 2025 14:35 EDT
SRS storage reported the following error while purging
We are cloud , recently to switch over to 24.2 we cloned our environment and index search was not working and when we tried indexing we got the following issue :
SRS storage reported the following error while purging previously indexed instances of 'Data-Admin-Operator-ID': Unable to purge data in the storage, HTTP status code: 403 Forbidden, response body: {"message":"Forbidden","_links":{"self":{"href":"/fdb1a042-b166-40ec-bf43-3e5e7d102927/all-data","templated":false}},"_embedded":{"errors":[{"message":"Forbidden","_links":{},"_embedded":{}}]}}, entity name: Data-Admin-Operator-ID
Any idea how can this be resolved ?
Accepted Solution
Updated: 12 Mar 2025 14:35 EDT
Pegasystems Inc.
GB
@NitinB17212478 please could you have a look at a recently-published support document:
Search fails in data class in Search and Reporting Service
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
The error you are encountering, which indicates a 403 Forbidden status, suggests that there may be an authentication issue or insufficient permissions related to the SRS (Search and Reporting Service) when attempting to purge previously indexed instances. Here are some steps you can take to resolve this issue:
@NitinB17212478 please could you have a look at a recently-published support document:
Search fails in data class in Search and Reporting Service
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
The error you are encountering, which indicates a 403 Forbidden status, suggests that there may be an authentication issue or insufficient permissions related to the SRS (Search and Reporting Service) when attempting to purge previously indexed instances. Here are some steps you can take to resolve this issue:
- Check Permissions: Ensure that the user account you are using has the necessary permissions to perform purging operations on the SRS.
- Review Logs: Check the logs for both Infinity and SRS to identify the specific reason for the 403 response. This may provide more context on what is being blocked.
- Dynamic System Settings: Consider applying additional settings using available dynamic system settings to manage indexing and purging operations effectively.
- Contact Support: If the issue persists, it may be beneficial to reach out to Pega support for further assistance, as they can provide more tailored guidance based on your specific environment and configuration.