After we've applied the latest patch (which should fix issues with datastore upgrade) we can't start any job since then.
Saw this due to the fact last night no job had been executed. we're running 8.0.2.200 P20240910)
The job is started, but then after a while we get the message "Job was unable to start within the configured timeout"
https://imgur.com/oC2sJ62
![Image]()
https://imgur.com/eNr64l7
![Image]()
All jobs then have the status 'Queued'
I assume this is related to a job which is stalled for 300h, Case #07410790
The Veeam.Archive.Proxy log gives the following entry, which I presume hold the other jobs to be started / queued...
Saw this due to the fact last night no job had been executed. we're running 8.0.2.200 P20240910)
The job is started, but then after a while we get the message "Job was unable to start within the configured timeout"
https://imgur.com/oC2sJ62

https://imgur.com/eNr64l7

All jobs then have the status 'Queued'
I assume this is related to a job which is stalled for 300h, Case #07410790
The Veeam.Archive.Proxy log gives the following entry, which I presume hold the other jobs to be started / queued...
Code:
18.09.2024 10:48:09.728] 350 (1) Warning: Double message processing was detected. Message stream sequence: 93183 (key: UserMailboxResolvedEvent_17d15cf3-af0d-4f1f-8db6-518949af29c7_ab5afe5d-a68d-4d75-9e79-10d5b0b45491). Processed sequence top: 93187. Processing skipped[18.09.2024 10:48:09.728] 350 (1) Warning: Double message processing was detected. Message stream sequence: 93184 (key: UserMailboxResolvedEvent_17d15cf3-af0d-4f1f-8db6-518949af29c7_2b66ff2b-507e-4125-81be-d5290dd795ab). Processed sequence top: 93187. Processing skipped[18.09.2024 10:48:09.728] 350 (1) Warning: Double message processing was detected. Message stream sequence: 93185 (key: UserMailboxResolvedEvent_17d15cf3-af0d-4f1f-8db6-518949af29c7_ba914a6a-d577-41ea-8854-e79a32488505). Processed sequence top: 93187. Processing skippedStatistics: Posted by kristofpoppe — Sep 18, 2024 8:46 am









