On-Premise Streaming - 626, 699 or 620 Errors

Summary

Video playback errors (such as 626, 699 or 620 errors) most commonly occur when a playback device is having difficulty obtaining a license to play the title.  This licensing process takes place when a user selects a movie to view. Sometimes a simple restart of the device and/or browser may resolve this issue. Advanced troubleshooting details can be found below if a restart does not resolve the issue.

Supported Systems

Ensure you are using supported systems which are found in the following link:  

On-Premise Streaming - Supported Systems

626, 699 or 620 Errors for All Titles 

In certain environments, it is common to have strict network rules that can interfere with normal network traffic.  In order for the streaming server to function properly, a number of network endpoints must be reachable. The On-Site Devices Requirements found here (Technical Requirements) must be reachable by the playback device. This information should be brought to the attention of your institution's network administrators as well as the administrators for any managed devices (such as Chromebooks). 

If this is occurring intermittently, it may not be an outright network ban or block. Instead, these kinds of errors can sometimes be caused by something more subtle such as SSL Inspection rules or rules governing JavaScript behavior. 

License server communication can be confirmed by having a user experiencing this issue attempt to reach the appropriate URL for their browser listed below. This will determine if they can indeed reach the license server.

• Apple/Safari & IOS Chrome
  • https://fairplay.swankmp.net/api/v1/license
  • Should display "Fairplay license controller is running"
• Google/Chrome/Firefox/Chromium based browsers
  • https://wvlsmod.swankmp.net/moddrm_proxy
  • Should display "Proxy is proxying!"
• Microsoft/Edge https://pr.swankmp.net/rightsmanager.asmx
  • Should display:
  • 

It might also be helpful to have the user capture an http archive of the error as it occurs.  Instructions on how to do that can be found here - How to capture an http archive (HAR) file

Note: For Customers Using a Swank Cached License Server, your DRM license endpoint would be to your Cached License Server.

699 or 626 Error for Specific Titles

Issue: There is an error that can occur on a MacOS/IOS device when viewing foreign language films that appears to be a 699 or 626 error. When a MacOS or IOS device has a default system language that does not match the default language of the content the Shaka player returns a 699 or 626 error.

Resolution: The issue must be fixed on the Shaka player side by Google. A ticket has been opened with the Shaka Project Team and we are currently waiting for a fix. We have found success using the Google Chrome desktop browser on non-MacOS/IOS devices, but we are still waiting for the root cause to be addressed by the Shaka Project Team.

Update Browser

Issue: Currently supported browsers are Firefox, Chrome, Safari and Edge.  If a browser is too far out of date, the Content Decryption Module (CDM) bundled with the browser may no longer be compatible with our streaming server content. 

Resolution: Please ensure your browser is up to date and try again.  If possible, try an alternate browser.

• Firefox has a Digital Rights Management Content setting that must be enabled. Once this is enabled it might take a minute for the additional DRM component to be installed.
  • 

Browser Plug-Ins

Issue: If your browser is utilizing plug-ins such as ad blockers, these can sometimes interfere with video playback. 

Resolution: Try disabling any browser plug-ins that might be interfering with network connectivity.  If possible, try an alternate browser.

Classroom Presentation Board Playback Issues

Issue: Swank Motion Picture video streams require that the playback devices support Widevine Digital Rights Management (DRM).  Customers have reported that classroom presentation boards listed below may not support the required DRM. 

• Promethean
• Vivi*
• ViewSonic Viewboards
• Newline**

Cause: This can occur when the playback equipment is using the internal Android operating system on the presentation board and DRM is not supported. 

Alternative Solution

We suggest using another device such as a laptop or desktop computer as a streaming source and using the external video input on the equipment to facilitate playback. This should bypass the internal operating system and use the board simply as a monitor. 

If you are using a laptop and the output is still an issue or you are getting an HDCP error, you can change your monitor settings from "mirror" monitors to "extend" monitors and drag the playback window to the external screen. This should allow playback without error. 

How do I Confirm Widevine support for my device?

The simplest way to verify Widevine DRM support on an Android device is to install and run an application called DRM Info (linked below)
https://play.google.com/store/apps/details?id=com.androidfung.drminfo&pcampaignid=web_share
 
Here's a screen shot of what the relevant details look like on an Android phone for example -

 
As you can see in this image, this device supports Widevine Level 1 DRM.  There are three Widevine DRM levels. 

Widevine Level	Security Type	Typical Devices	Max Resolution
L1	Hardware-based (TEE)	Certified Android devices, TVs	Up to 4K
L2	Mixed	Some Android / embedded systems	Usually 720p–1080p
L3	Software-only	PCs, kiosks, touch panels	Usually SD–720p

 
If a device reports L3 support, we still recommend performing a playback test on the device using your Swank streaming portal.  

Brand Specific Feedback
 We have customer feedback below for some brands below, but ultimately your best source of information is going to be the device manufacturer and their support team.

• Vivi: - Users report that video playback works through Vivi Screen Sharing, but not the Play Video feature.
• Newline: Users report that playback works when used with HDMI connected Chromebooks
• Samsung IFP (Interactive Flat Panel): Users report playback directly on a supported browser from the device and direct HDMI connection work. For Wireless screenshare HDCP Issues are presented. Additional details about HDCP issues can be found here: I have a Black/Blank Video with Audio (HDCP Issue)