If the client is updated, but the component libraries are corrupted or outdated, the API calls made by the UI may not align with the SDK's internal state machine. The SDK may interpret a playback request as an invalid session and return an exclusive lock error.
: If your NVR is only set to record the "Main Stream" but your SmartPSS playback setting is defaulted to "Sub Stream" (Extra Stream), it will return an error because the data doesn't exist. : In the Playback menu, manually toggle between Main Stream Sub Stream to see if one loads. 3. Check for Account Permissions
To resolve this error, users should follow a logical progression from software resets to hardware configuration: If the client is updated, but the component
The following procedures are recommended in order of complexity.
If you are using the latest version (e.g., V2.x) and it fails, consider trying an older, more stable version, or vice-versa. 3. Check User Permissions (No Right to Operate) : In the Playback menu, manually toggle between
If you are still seeing this error, I can help you dig deeper. Please let me know: What is the of your NVR/DVR?
The Windows operating system blocks the dhnetsdk.dll script layer from building localized playback cache data if the application lacks administrative read and write paths. If you are using the latest version (e
Elias started to turn around, but the screen flashed one last time. "Playback Started."