Exporting (troubleshooting)
The export may have been created on a computer with a 64 bit Windows operating system, and you are using a 32 bit operating system.
To resolve the issue, try one or more of the following:
- Open the SmartClient-Player.exe file on a 64-bit Windows computer.
- Open the export with a 32-bit version of XProtect Smart Client. To do this, follow these steps:
- Open this link: https://www.milestonesys.com/downloads/.
- Select Product, for example XProtect Corporate, Version, and Language.
- Click XProtect Smart Client 32-bit to download the application.
- When installed, go to the export folder and open the Client Files folder.
- Double-click the Exported Project.scp file. The XProtect Smart Client – Player should open, and you can play back the video.
- Ask the person who provided the export to create a new export using a 32-bit XProtect Smart Client.
- Ask the person who provided the export to create a new export using a different export format, for example AVI or MKV.
You may also experience this issue if the export was created using a different encryption algorithm than the current version of your XProtect Smart Client. See also .
Error messages and warnings
Your current XProtect VMS system uses AES-256 for encrypting exported video data to comply with the FIPS 140-2A U.S. government standard that defines the critical security parameters that vendors must use for encryption before selling the software or hardware to U.S. government agencies. security standard. However, the system which was used to create the export uses a different encryption standard.
To resolve the issue, do one of the following:
- Re-export the video data using an upgraded version of XProtect Smart Client. The version must be equal to or newer than your current version
- Though Milestone recommends always using the latest version of XProtect Smart Client, you can open the export using an older version of XProtect Smart Client in offline mode
- Open the export on a computer where FIPS mode is disabled. See also https://docs.microsoft.com/en-us/windows/security/threat-protection/fips-140-validation#using-windows-in-a-fips-140-2-approved-mode-of-operation
Milestone recommends that you password-protect your data. To do this, select the Encrypt with password check box in the Export window.
No tampering key is included in the video export. Either the tampering key was removed or the video export was created using a stand-alone third-party application based on the MIP SDKIncident defined on surveillance system to trigger an alarm in XProtect Smart Client. If your organization uses the feature, triggered alarms are displayed in views that contain alarm lists or maps. 2020 R2 or older. If the tampering key is missing, there is no way of verifying the authenticity of the video project file.
To resolve the issue, do one or more of the following:
- Request a new video export and make sure the tampering key is included
- Re-export the video data using a third-party application which is based on MIP SDK 2020 R3 or later