PARTNERS - Please join us for our upcoming webinar:
Leveraging Intelligent Recommendations for Operational Transformation.
AMS Partners click HERE | EMEA/APJ Partners click HERE

Error in RunAllAnalyticsJob: connnection proxy not usable after transaction completion

yogesh2
Regular Contributor
Regular Contributor

What is the cause of this error? 

Analytics show records in dry run but I am not able to run using "Run Now" and get below error when I try to run the analytics via RunAllAnalyticsJob

yogesh2_1-1719295281360.png

 

10 REPLIES 10

rushikeshvartak
All-Star
All-Star

Elastic search index is corrupted. Please create new report with different name maybe append  1 in end


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

Is there a way to repair the index?

I deleted and re-created the report with same name (we don't want to append 1 unnecessarily) and still got same error.

You need to rename report. as index already exists on elastic search.

Add underscore/hyphen in name.

You can raise saviynt support ticket to delete elastic search index deletion


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

Manu269
All-Star
All-Star

@yogesh2 we faced similar case in past. Ended up opening an FD ticket with Saviynt Ops. They consulted their devops for resolution.

Regards
Manish Kumar
If the response answered your query, please Accept As Solution and Kudos
.

Dhiraj_Yadav_1
New Contributor III
New Contributor III

Hi @yogesh2 ,

Were you able to fix this issue?

Thanks,

Dhiraj Yadav

This was fixed 'automagically' during a product upgrade (to version 24.7)

We still have a ticket open with Saviynt support on this and they are saying they did not make any changes so even they are not sure how this got fixed for us. We are awaiting RCA and will let you know, I suggest you create a ticket as well as this seems to be recurrent issue.

Dhiraj_Yadav_1
New Contributor III
New Contributor III

Hi @Manu269 ,

May I know what was the solution provided the Saviynt Devops team.

Thanks,

Dhiraj

Manu269
All-Star
All-Star

We did not get much details regarding resolution, but was resolved by devops. Raise a ticket with saviynt ops please

Regards
Manish Kumar
If the response answered your query, please Accept As Solution and Kudos
.

@Manu269  Is this is a known issue? We are also facing the same.

@PratithShetty I doubt this could be. I suggest try opening a ticket with saviynt operation and they would clarify.

Regards
Manish Kumar
If the response answered your query, please Accept As Solution and Kudos
.