Recorder error: (GetSequences) Internal error - Server unreachable. Reason: ProtocolError - , 0 - 0

I got the following error when trying to read the sequences of a set of camera in a loop.

Recorder error: (GetSequences) Internal error - Server unreachable. Reason: ProtocolError - , 0 - 0

Attached with the code snippet of my function, which iterate a list of camera Item and add their respective sequence(s) into a collection.

For instance, the ListOfSeqSource consists of three camera items.

Sometimes one or two out of them are able to retrieve from the VMS,

but never all of them.

The second code snippet shows how the error is capture by registering to the Environment manager.

            //ListOfSeqSource is list of item : List<item> with Kind == Camera
            ListOfSeqSource.RemoveAll(x => x.FQID.Kind != Kind.Camera);
 
            foreach (var seqSource in ListOfSeqSource)
            {
                List<object> ListOfSeqDataInOneSource = new List<object>();
                    var thisSeqDataSource = new SequenceDataSource(seqSource);
 
                    ListOfSeqDataInOneSource = thisSeqDataSource.GetData(
                             DateTime.Now,
                                new TimeSpan(30, 0, 0, 0), //read all data from 30 days before
                                10, //10 files max
                                new TimeSpan(0),
                                0);
 
                    if (ListOfSeqDataInOneSource.Count == 0) continue;
 
                    //Add result into collection
                    _viewModel.AllSequenceCollection.AddRange(ListOfSeqDataInOneSource);
                }
            }
 EnvironmentManager.Instance.RegisterReceiver(RecorderErrorHandler,
                new MessageIdFilter(MessageId.Control.RecorderErrorIndication));
 
 private object RecorderErrorHandler(Message message, FQID receiver, FQID sender)
        {
            RecorderErrorIndicationData data = message.Data as RecorderErrorIndicationData;
 
            string errMsg =
                "Recorder error: (" + data.Command + ") " +
                data.ErrorText + ", " + data.RecorderWebInterfaceErrorCode +
                " - " + data.PtzErrorDetail;
            App.CctvLogger.Error(errMsg);
 
            new ConfirmationMessageBox(ButtonLayout.OK, "Recorder Error", errMsg).ShowDialog();
 
            return null;
        }

Thanks.

I tried to reproduce the behavior but for me your code works perfectly every time.

A note of caution: Asking for 30 days of sequences could be an operation that takes a long time, it will potentially take many seconds, at one point the request could time out. I am unsure if this is effectively what the error says.

Do you get the responses you get fast?

When it fails is it on cameras with no or very little recorded video?

What XProtect product and version is the server?

Thanks for the reply, I tried reduced it to 7 days with 10 files max problem remained.

Yes, the error responded within 1 second after the .GetData(..) is called.

Camera which failed has no recorded video.

We are running XProtect Management Client 2017 R3, XProtect Corporate 2017 R3 Pilot, Milestone Xprotect Smart Wall.

Is there any reason(s) or document(s) I can refer to regarding why this error is thrown?

I had an idea that I then just needed to test with a camera with no recording but I cannot reproduce even if I have this.

Maybe you should check if this old server has been patched (https://supportcommunity.milestonesys.com/s/article/XProtect-2017-R3-Cumulative-Patch-Installers?language=en_US)

If you look into the recording server debug logs ([C:\ProgramData\Milestone\XProtect](file:C:/ProgramData/Milestone/XProtect) Recording Server\Logs) something might reveal.

PS. I find it strange that you say you have a pilot that old, if you have the need for pilot work please make sure you use the newest XProtect version.

Thanks for the reply again.

When I try to locate the recording server debug logs directory, it

cannot be found (as shown in the photo below).

The XProtect version is provided by our vendor, it has been working all the while until recently, and we are trying to figure out what happened.

Meanwhile, we are checking whether the it is patched or not, thanks.