RecorderStatusService2.asmx returns "Token invalid (20001/2)" even with a freshly created token

MIP
, ,
1

Hi,

I’m trying to retrieve the device status from a Milestone XProtect Recording Server (version 23.2a) using the legacy SOAP service: /RecorderStatusService/RecorderStatusService2.asmx

Here’s my current flow:

  1. I call ServerAPI/ServerCommandService.asmx, and create a new token (the call succeeds).
  2. I use that token together with the device ID I found through /ServerAPI/ServerCommandService.asmx to call /recorderstatusservice/recorderstatusservice2.asmx
  3. The response I get is:
HTTP/1.1 500 Internal Error
 
Server: XProtect Recording Server 23.2a
 
...
 
<soap:Fault>
 
  <soap:Reason>
 
    <soap:Text xml:lang="en">Token invalid</soap:Text>
 
  </soap:Reason>
 
  <detail>
 
    <ErrorNumber>20001</ErrorNumber>
 
    <SubErrorNumber>2</SubErrorNumber>
 
  </detail>
 
</soap:Fault>

I’m using a brand-new token, but the server still rejects it.

The token is sent as part of the SOAP body.

Question:

Can anyone explain what might be wrong with my request, or why I’m getting a “Token invalid (20001/2)” error even with a freshly created token?

2

Hi,

Can you please provide the request that you are sending?

3

Hi, here’s the request I’m sending:

http://{host}:{port}/recorderstatusservice/recorderstatusservice2.asmx

4

Hey,

Just following up, any updates on this?

5

@Rie Kiuchi (Milestone Systems)​ please assist, we have a customer who cannot use our integrated system due to this issue