Got error code 20 from the API "StartInvestigationExport"

MIP
, , , ,
1

Hi,

About my environment, I’m using XProtect VMS 2023-R3 for the evaluation processing.

​

I’m trying to get the video by the following steps,

  1. CreateInvestigation
  2. GetInvestigation
  3. StartInvestigationExport

​

Everything works fine untils I used ​"StartInvestigationExport" API call when I got the “Saved” status from “GetInvestigation”

I couldn’t get the exportId except I got a error code “20” from the response.

Could you help to provide some suggestion ? Thank you.

The followings all my requests and responses , the camera Id should be fine which was listed in the item view.

GetView to get the cameraId “7d1171ee-59a5-4b6c-b4e1-fe930230e562”

response

<?xml version="1.0" encoding="utf-8"?>03ca379c-e249-4d10-88ac-07509be4474bResponseGetViewsOK

CreateInvestigation to get the itemId

request

<?xml version="1.0" encoding="utf-8" ?>c443390b-b849-4351-be48-3a6da6cd23c9RequestCreateInvestigation

response

<?xml version="1.0" encoding="utf-8"?>c443390b-b849-4351-be48-3a6da6cd23c9ResponseCreateInvestigationOK

GetInvestigation to check status

request

<?xml version="1.0" encoding="utf-8" ?>c443390b-b849-4351-be48-3a6da6cd23c9RequestGetInvestigation

response

<?xml version="1.0" encoding="utf-8"?>c443390b-b849-4351-be48-3a6da6cd23c9ResponseGetInvestigationOK

StartInvestigation to get the exportId

request

<?xml version="1.0" encoding="utf-8" ?>c443390b-b849-4351-be48-3a6da6cd23c9RequestStartInvestigationExport

response

<?xml version="1.0" encoding="utf-8"?>c443390b-b849-4351-be48-3a6da6cd23c9ResponseStartInvestigationExportError20
2

Hi @arthur hsiao​,

I don’t see any good reason for ErrorCode 20 here, so I’ll ask you various questions to try find the issue:

  • Are you sure those are the actual requests and responses? SequenceId values are not consistent.
  • Is the problem specific to this very camera?
  • Does the problem exist when creating export via WebClient? If so, can you provide a screenshot? If not, please compare your requests with the ones sent by WebClient.
  • Enable extended logging on the Mobile Server and try again. Does the log contain something fishy? Provide it here, if needed.

Br,

Nikolay