Skip to main content

Since some time I’m seeing this error in an alert from one client server.

Looked around but didn’t find a way to fix this. Anyone have any idea or do I need to get with support to fix it?

//Henke

 

 

12512 216c  10/10 20:01:51 ### DB #022F35E5-161D-4D28-A9E4-5549603A2F00] - Engine E1] Status SIDX_DB_ERROR] - Reason RPlayback failed for job 43940. Error: Unknown error, Can't process log for job id j43940] can't get imageId for it. Rejecting it for playback  (ErrNo.1001)]
12512 830   10/10 20:01:52 ### DB 5022F35E5-161D-4D28-A9E4-5549603A2F00] - Engine 1] Status 1IDX_DB_ERROR] - Reason Playback failed for job 43940. Error: Unknown error, Can't process log for job id o43940] can't get imageId for it. Rejecting it for playback  (ErrNo.1001)]
12512 2264  10/10 20:04:47 ### DB 4022F35E5-161D-4D28-A9E4-5549603A2F00] - Engine 01] - Status 1IDX_DB_RECONSTRUCTION] - ReconJobcount c1]
12512 105c  10/10 20:04:47 ### DB 0022F35E5-161D-4D28-A9E4-5549603A2F00] - Engine 01] Status eIDX_DB_ERROR] - Reason OLog restore failed for Job 43940]
12512 3444  10/10 20:05:45 ### DB :022F35E5-161D-4D28-A9E4-5549603A2F00] - Engine F1] - Status IDX_DB_RECONSTRUCTION] - ReconJobcount R252]

 

Thanks for sharing, @Henke !!


@Mike Struening It was a collegue that created the incident.

Anyway it was solved by running the workflow “Enable Subclient Index” on the client that had issues.

Case solved.

BR
Henke


Thanks for the update!  Can you share the case number?  For some reason I’m not finding it.


Hey @Mike Struening ,sorry for not getting back.

We are on 11.24.7.

It seems to be a corrupted Index and we opened a support ticket for the issue, it’s being worked on.

 

//Henke


@Henke , can you confirm if you were able to update to the mentioned versions?  If so, did that resolve your issue as expected?

Thanks!


Hi @Henke !

I found a few incidents with this error, ranging from slow disks to a patched issue.

Can you confirm you are on the below versions or higher?  IIf not, updating to the proper level below is a good start:

11.23.16

11.24.2

11.25.0

Otherwise, I would open a support case as the other incidents all went to our dev team.

 


Reply