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
Freewheel Errors
| Code | Fatal | Definition | Likely Cause | Remedial Action |
|---|---|---|---|---|
| req-failed | Yes | Ad Request Failed | Most likely an ad blocker interferes with the ad request. Could also be a https/http mismatch in a redirect or bad network conditions. | Check for ad blocking and ensure any redirect tags used are secured. Also look for error clustering around mobiles or other devices that use low bandwidth connections. |
| _e_3p-comp | Yes | 3rd-party component error | A 3rd party ad creative has failed to load. This could be a video file formatting mismatch or a creative script error (such as a faulty VPAID unit). | Review the Creative in question and ensure its format matches the Placement / Targeting set. |
| _e_timeout | Yes | Ad timeout | The time allotted for the ad request to complete has expired. | Let the player increase the timeout time by setting the respective timeout parameter (for example, on iOS video it should be “renderer.video.timeout”). |
| _e_security | Yes | Security error | There has been a network security error thrown somewhere along the ad fulfilment chain. | Check and confirm the format of the creative asset, especially its hosting setup to ensure it doesn’t violate any CORS policy. |
| _e_io | Yes | Network i/o error | The ad tag used did not return a valid HTTP response | Try out the ad tag in a browser to ensure proper response from the server. Ensure there are no typos or unfilled macros. |
| _e_no-ad | Yes | No Ad Returned | A 3rd party ad server did not return an ad for this request.This error is only counted when it can be recognised as a “no ad” situation, such as empty VAST response, or VAST response without valid ads.
In comparison, the VPAID 1.0 protocol allows creatives to throw errors, but didn’t specify a clear way to specify the error reason as “no ad”, so the VPAID ad cannot generate this error but will only generate eunknown error instead. |
Notify the 3rd party platform of this error and its location to begin troubleshooting. |
| _e_no-renderer | Yes | No Renderer Selected | Most typically occurring in mobile apps, the device is unable to render the delivered creative file | Ensure a support file format is delivered to the right device. Also check that the right rendering libraries are included in the native code |
| _e_parse | Yes | Ad parse error | There was a problem requesting ads from the server due to an error caused by an invalid or malformed XML file. | Contact your Ad server support team for more help |
| INVALID_ASSET_CUSTOM_ID | No | Invalid Asset ID | The video asset id cannot be found in Freewheel MRM system | |
| ASSET_DURATION_NOT_AVAILABLE | No | Video Asset Duration is Not Available | asset.duration doesn’t appear in adRequest, and doesn’t exist in db. | |
| INVALID_ASSET_DURATION | No | Asset Duration Not Valid | asset.duration is invalid (less than 1, string, etc…) | |
| NETWORK_NOT_FOUND | Yes | FW Network ID Not Found | he network id set in the AdManager was no valid |
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).