Browse Video Advertising Error Codes
Error Codes – Index
100 – 102: VAST XML Document Errors
200 – 203: VAST Creative File Errors
300 – 303: VAST Ad Request Errors
400 – 410: VAST Linear Tag Errors
500 – 503: VAST Non-Linear Tag Errors
600 – 604: VAST Companion Ad Errors
900 – 901: VPAID Errors
Brightcove Player Ad Errors
JWPlayer Ad Errors
1005 – 2048: IMA3 SDK Errors
Freewheel Errors
VAST Linear Tag Errors
| Code | Fatal | Definition | Likely Cause | Remedial Action |
|---|---|---|---|---|
| 400 / 400:20400 | Yes | General linear error | This can be caused when a video player is unable to display the linear ad. It may occur when the MediaFile is not a valid video file of the specified format, or because the browser restricted autoplay with sound, or another unknown reason | Publisher – Check for player issues, enable your player to detect for restricted autoplay, or alert the buyer Buyer – Ensure that the VAST response returns a valid creative |
| 401 | Yes | MediaFile not found | This can be caused when a file cannot be found from a MediaFile URI | Publisher – Ensure that all MediaFiles in the response return a valid video asset. If not, alert the buyer Buyer -Ensure that the VAST response returns a valid creative |
| 402 / 402:20402 | No | Timeout of MediaFile URI | This can be caused by a problem fetching or playing the MediaFile, and could be any of the following:
|
Publisher – Increase the timeout limit of your player Buyer – Ensure that any CDN-hosted creatives are returned within the specified media timeout |
| 403 | Yes | Could not find MediaFile that is supported by this video player, based on the attributes of the MediaFile element | This can be caused by a VAST response that declares unsupported MIME types for all available MediaFiles. For example:
|
Publisher – Ensure that the creative format or technology requested is supported by the video player’s device and platform. For example, VPAID creatives should not be requested from mobile apps Buyer – Ensure that all returned creatives respect the video format in the bid request |
| 405 | Yes | Problem displaying MediaFile | This can be caused when a faulty creative is returned due to a mismatch between the MIME type and the video file type, a CORS configuration on the creative’s CDN, transcoding-related reason such as an unsupported codec, or unsupported delivery method | Publisher – Alert the buyer Buyer – Ensure that all creative MIME types and CDN configurations are accurate |
| 406 | No | Missing required mezzanine file | This can be caused a VAST response is returned without a required mezzanine file. Publishers with server-side ad implementations (SSAI) often require mezzanine files, which are raw high-quality video files for ad-stitching, or to generate video files of appropriate quality (VAST 4) | Publisher – Alert the buyer Buyer – Ensure that a mezzanine file is included in your response when required by the publisher |
| 407 | Yes | Mezzanine file downloaded for the first time | This can be caused when the mezzanine file is downloaded for the first time, so no ad is served. It can also occur when an ad insertion is missed because the creative is being transcoded. It continues to occur until the creative is available for insertion (VAST 4) | No action required |
| 408 | Yes | Ad rejected in VAST response | This can be caused when the ad returned in the VAST response is rejected | Publisher – Alert the buyer Buyer – Ensure that only approved creatives are returned in your VAST response, or that any advertisers or agencies hosting the creatives are aware of rejections |
| 409 | Yes | Interactive unit in the InteractiveCreativeFile node was not executed | This can be caused when a creative defined in the InteractiveCreativeFile node does not execute | Publisher – Alert the buyer Buyer – Ensure that any interactive creatives returned in your response successfully play when requested |
| 410 | Yes | Verification unit in the Verification node was not executed | This can be caused when the code referenced in the AdVerification node does not execute (VAST 4) | Publisher – Alert the buyer Buyer – Ensure that the verification code referenced in the response is correctly implemented according to the verification vendor |
Error severity levels:
Non-Fatal – An error is triggered but the video ad request is not interrupted and a video ad is successfully served.
Fatal – An error is triggered and the video ad request is stopped, preventing an ad being played. This is either followed by video content playback or a new ad request being triggered (depending on player configuration).