Detected RavenDB index errors, please start maintenance mode and resolve the following issues:
Index [SagaDetailsIndex] error: Could not properly write to index SagaDetailsIndex (Action: Failed to reduce index: SagaDetailsIndex (id: 21) 2 single step keys and 0 multi step keys. Skipping this batch (it won’t be reduced), Doc: , At: 7/18/2022 11:41:19 AM)
Index [SagaDetailsIndex] error: Could not properly write to index SagaDetailsIndex (Action: Failed to reduce index: SagaDetailsIndex (id: 21) 17 single step keys and 0 multi step keys. Skipping this batch (it won’t be reduced), Doc: , At: 7/18/2022 11:41:50 AM)
Index [SagaDetailsIndex] error: Could not properly write to index SagaDetailsIndex (Action: Failed to reduce index: SagaDetailsIndex (id: 21) 20 single step keys and 0 multi step keys. Skipping this batch (it won’t be reduced), Doc: , At: 10/18/2022 2:29:33 PM)
I want to be sure that installing the Raven DB Management Studio on our server that I wasn’t going to have a problem with it overwriting libraries or otherwise interfering with NServiceBus functionality.
There is no effective backup to restore should this cause an issue.
If I can install it on my local machine for instance and manage the indices from there, that would be better.
I also wanted to be sure that fixing this issue would help NServiceBus perform well. “If it ain’t broke, don’t fix it.”
When you bring service control into maintenance mode (2nd link from Ramon’s response) you will be able to open Raven’s Management Studio so there is no need to install anything.
I know this is an older discussion, but the current documentation still doesn’t explain this well. There is an animation that attempts to illustrate it, but it stops short.
I too was thinking I was going to have to install/copy over an executable from the RavenDB project. I suggest/request you update the maint. mode document to list the steps out more explicitly, perhaps the animation as well.