Ad Errors and Warnings Reference (Web Player)

JWP is excited to help you monetize your content. With that being said, the complex nature of video advertising means that ad-related errors will happen from time to time. We hope that this list of error codes provides some insight into possible reasons that you are seeing these errors. We also have included possible solutions that may lead you to being able to resolve the issue.

If you are still seeing ad-related issue after trying any applicable solutions, we highly recommend contacting your ad provider for further troubleshooting. This is because the player is primarily making the ad request using the URL you embed in the player and it is the responsibility of the ad provider to respond with a VAST-compatible response that the player can then display to your viewers. If they determine that they believe the issue is with the player, please open a case with our Support Team.

Ad client specifications

Errors often happen because ad tags or creatives are out of spec with either VAST or Google IMA. For this reason, we encourage publishers to refer to the respective specifications for the ad client they are using below:

Ad errors and warnings

1xxxx: VAST general errors
2xxxx: IMA errors
5xxxx: VAST VPAID errors
6xxxx: JWP ad errors
7xxxx: JWP ad warnings

VAST general errors

VAST Error Code	JW Error Code	Error	Possible Causes	Possible Solutions
`100`	`10100`	XML parsing error	VAST supplied is not a valid XML document. URL supplied does not resolve to a valid XML document. Perhaps a CORS issue.	Check the CORS headers of the domain hosting the XML to make sure they are configured to allow the domain of the page access.
`101`	`10101`	VAST schema validation error	The VAST validates as XML, but does not validate per the VAST schema. This could due to missing mandatory elements/attributes, or combinations of elements/attributes that are not permissible.	When working with third-party networks, the fill-rate can be less than 100%. If so, this is an expected error. For example, if the third-party expects to fill 60% of the time, you should expect 40% errors. You can check to ensure that the error rate is in line with the fill-rate of the third-party network. Some ad providers use empty VAST 3.0 responses to show that they have received the request but do not wish to fill it.
`102`	`10102`	VAST version of response not supported	Bidder did not respect the VAST version(s) in the bid request. Exchange is sending the wrong VAST version(s) in the bid request. The VAST does not contain the version. This could also be considered a schema validation issue.	JWP 8 does not provide support for VAST 1.0 ads.
`301`	`10301`	Timeout of VAST URI provided in Wrapper element, or of VAST URI provided in a subsequent Wrapper element	Invalid URI Unreachable or request timeout for URI Security or other exceptions related to requesting a VAST URI This can be caused by requesting a secure (HTTPS) resource on a non-secure (HTTP) page	Check that the VAST URI is valid and reachable Check whether this occurs more on mobile devices Check whether or not issue is reproducible on a non-secure (HTTP) version of your page The timeout is configurable for using the creativeTimeout and requestTimeout configuration options. However, increasing the timeout could potentially negatively affect user experience
`303`	`10303`	No ads VAST response after one or more Wrappers. Also includes the number of empty VAST responses from fallback.	No Ad element in VAST document after following wrappers	When working with third-party networks, the fill-rate can be less than 100%. If so, this is an expected error. For example, if the third-party expects to fill 60% of the time, you should expect 40% errors. You can check to ensure that the error rate is in line with the fill-rate of the third-party network.
`400`	`10400`	General linear error. Video player is unable to display the linear ad.	MediaFile is not a valid video file of the specified format	Check to see if MediaFile’s format is valid and supported Does the MediaFile’s URI actually return a video asset?
`401`	`10401`	File not found. Unable to find Linear/MediaFile from URI	URI of Linear/MediaFile is not valid	Does the Linear/MediaFile’s URI actually return a valid asset?
`402`	`10402`	Timeout of MediaFile URI	Issue with CDN server Timeout (in milliseconds) when loading a video ad media file. If loading takes longer than this timeout, the ad playback is canceled Can be caused by low bandwidth, or poor website implementation with competing requests that delay the loading of the media file Can occur when a video auto-plays in a mobile environment, since it should be click-to-play (there are some exceptions)	The timeout is configurable for using the creativeTimeout and requestTimeout configuration options. However, increasing the timeout could potentially negatively affect user experience
`403`	`10403`	Could not find MediaFile that is supported by this video player, based on the attributes of the MediaFile element.	Bidder did not respect the MIME types in the bid request Exchange did not send the correct MIME types This may indicate that the wrong creative type attempted to play. For example, a Flash creative attempted to play on a mobile device or a browser that does not support Flash. Ad is inline but no compatible media file is found. Generally, if the player reaches a point where it sees no MediaFiles in the array of mediafiles considered eligible.	Reach out to your ad provider to request only HTML5-compatible creatives.
`405`	`10405`	Problem displaying MediaFile	CORS issue on CDN server Unsupported codecs Mismatch between MIME type and video file type Unsupported delivery method
`408`	`10408`	Conditional ad rejected	This is not so much an error as it is expected when the `conditionaladoptout` configuration option is enabled and a conditional ad is found.
`502`	`10502`	Unable to fetch NonLinearAds/NonLinear resource	Issue with CDN server
`900`	`10900`	Undefined error	This error is usually fired when the error does not match the criteria of any of the other errors.
`1000`	`11000`	VMAP schema error	The VPAID validates as XML, but does not validate per the VPAID schema. This could due to missing mandatory elements/attributes, or combinations of elements/attributes that are not permissible.	When working with third-party networks, the fill-rate can be less than 100%. If so, this is an expected error. For example, if the third-party expects to fill 60% of the time, you should expect 40% errors. You can check to ensure that the error rate is in line with the fill-rate of the third-party network. Some ad providers use empty VAST 3.0 responses to show that they have received the request but do not wish to fill it.
`1002`	`11002`	VMAP parsing error	This error can be fired when the error does not match the criteria of any of the other VMAP-related errors.
`1007`	`11007`	Ad response document retrieval timeout	Issue with CDN server Timeout (in milliseconds) when loading an ad response. If loading takes longer than this timeout, the ad playback is canceled. Can be caused by low bandwidth, or poor website implementation with competing requests that delay the loading of the ad response.	The timeout is configurable for using the creativeTimeout and requestTimeout configuration options. However, increasing the timeout could potentially negatively affect user experience.
`1008`	`11008`	Ad response document retrieval error	CDN responsed with an error code.

VAST VPAID errors

VAST Error Code	JW Error Code	Error	Possible Causes	Possible Solutions
`100`	`50100`	VPAID parsing error	VAST supplied is not a valid XML document. URL supplied does not resolve to a valid XML document. Perhaps a CORS issue.	Check on the CORS headers of the domain hosting the XML to make sure they are properly configured to allow the domain of the page access.
`400`	`50400`	VPAID general linear error	MediaFile is not a valid video file of the specified format.	Check to see if MediaFile’s format is valid and supported. Does the MediaFile’s URI actually return a video asset?
`401`	`50401`	VPAID file not found	URI of Linear/MediaFile is not valid.	Does the Linear/MediaFile’s URI actually return a valid asset?
`402`	`50402`	VPAID playback timed out	Issue with CDN server. Timeout (in milliseconds) when loading a VPAID ad. If loading takes longer than this timeout, the ad playback is canceled. Can be caused by low bandwidth, or poor website implementation with competing requests that delay the loading of the VPAID ad.	The timeout is configurable for using the creativeTimeout and requestTimeout configuration options. However, increasing the timeout could potentially negatively affect user experience.
`405`	`50405`	VPAID file could not be played
`900`	`50004`	VPAID ad request reached a timeout	Issue with CDN server. Timeout (in milliseconds) when loading a VPAID ad. If loading takes longer than this timeout, the ad playback is canceled. Can be caused by low bandwidth, or poor website implementation with competing requests that delay the loading of the VPAID ad.	The timeout is configurable for using the creativeTimeout and requestTimeout configuration options. However, increasing the timeout could potentially negatively affect user experience.
`901`	`50901`	VPAID general error	This is a general error that may be fired for a number of reasons due to the fact that VPAID ads often do not provide the player with a lot of information about errors.
`901`	`51901`	VPAID general error	VPAID creative fired a JavaScript exception that prevented successful playback. This can be, but is not limited to, syntax errors within the VPAID's JavaScript.	Reach out to your ad provider.

IMA errors

IMA Error Code	JW Error Code	Error	Possible Causes	Possible Solutions
-	`20000`	IMA SDK download failed	Ad blocker caused the IMA SDK not to download
`100`	`20100`	VAST_MALFORMED_RESPONSE The ad response was not recognized as a valid VAST ad.	VAST supplied is not a valid XML document. URL supplied does not resolve to a valid XML document. Perhaps a CORS issue.	Check on the CORS headers of the domain hosting the XML to make sure they are properly configured to allow the domain of the page access.
`101`	`20101`	VAST_SCHEMA_VALIDATION_ERROR	The VAST validates as XML, but does not validate per the VAST schema. This could due to missing mandatory elements/attributes, or combinations of elements/attributes that are not permissible.	When working with third-party networks, the fill-rate can be less than 100%. If so, this is an expected error. For example, if the third-party expects to fill 60% of the time, you should expect 40% errors. You can check to ensure that the error rate is in line with the fill-rate of the third-party network. Some ad providers use empty VAST 3.0 responses to show that they have received the request but do not wish to fill it.
`102`	`20102`	VAST_UNSUPPORTED_VERSION	Bidder did not respect the VAST version(s) in the bid request. Exchange is sending the wrong VAST version(s) in the bid request.	JWP 8 does not provide support for VAST 1.0 ads.
`200`	`20200`	VAST_TRAFFICKING_ERROR	The player received an ad type that it was not expecting and/or cannot display.
`201`	`20201`	VAST_UNEXPECTED_LINEARITY	Ad linearity is different from what the video player is expecting.
`202`	`20202`	VAST_UNEXPECTED_DURATION_ERROR	VAST duration is different from the actual media file duration.
`300`	`20300`	VAST_WRAPPER_ERROR	General VAST wrapper error.
`301`	`20301`	VAST_LOAD_TIMEOUT	Invalid URI Unreachable or request timeout for URI Security or other exceptions related to requesting a VAST URI. This can be caused by requesting a secure (HTTPS) resource on a non-secure (HTTP) page.	Check that the VAST URI is valid and reachable. Check whether this occurs more on mobile devices. Check whether or not issue is reproducible on a non-secure (HTTP) version of your page. The timeout is configurable for using the creativeTimeout and requestTimeout configuration options. However, increasing the timeout could potentially negatively affect user experience.
`302`	`20302`	VAST_TOO_MANY_REDIRECTS	The maximum number of VAST wrapper redirects has been reached.
`303`	`20303`	VAST_NO_ADS_AFTER_WRAPPER	No Ad element in VAST document after following wrappers.	When working with third-party networks, the fill-rate can be less than 100%. If so, this is an expected error. For example, if the third-party expects to fill 60% of the time, you should expect 40% errors. You can check to ensure that the error rate is in line with the fill-rate of the third-party network.
`400`	`20400`	VIDEO_PLAY_ERROR	MediaFile is not a valid video file of the specified format.	Check to see if MediaFile’s format is valid and supported. Does the MediaFile’s URI actually return a video asset?
`402`	`20402`	VAST_MEDIA_LOAD_TIMEOUT	Issue with CDN server. Timeout (in milliseconds) when loading a video ad media file. If loading takes longer than this timeout, the ad playback is canceled. Can be caused by low bandwidth, or poor website implementation with competing requests that delay the loading of the media file. Can occur when a video auto-plays in a mobile environment, since it should be click-to-play (there are some exceptions).	The timeout is configurable for using the creativeTimeout and requestTimeout configuration options. However, increasing the timeout could potentially negatively affect user experience.
`403`	`20403`	VAST_LINEAR_ASSET_MISMATCH	Bidder did not respect the MIME types in the bid request. Exchange did not send the correct MIME types. This may indicate that the wrong creative type attempted to play. For example, a Flash creative attempted to play on a mobile device or a browser that does not support Flash. Ad is inline but no compatible media file is found. Generally, if the player reaches a point where it sees no MediaFiles in the array of mediafiles considered eligible.	Reach out to your ad provider to request only HTML5-compatible creatives.
`405`	`20405`	VAST_PROBLEM_DISPLAYING_MEDIA_FILE	CORS issue on CDN server. Unsupported codecs. Mismatch between MIME type and video file type. Unsupported delivery method.
`500`	`20500`	OVERLAY_AD_PLAYING_FAILED	An overlay ad failed to render.
`501`	`20501`	NONLINEAR_DIMENSIONS_ERROR	Unable to display NonLinear ad because creative dimensions do not align with creative display area (i.e. creative dimension too large).
`502`	`20502`	OVERLAY_AD_LOADING_FAILED	Issue with CDN server
`503`	`20503`	VAST_NONLINEAR_ASSET_MISMATCH	Assets were found in the VAST ad response for nonlinear ad, but none of them matched the video player's capabilities.
`602`	`20602`	COMPANION_REQUIRED_ERROR	Unable to display one or more required companions. The master ad is discarded since the required companions could not be displayed.
`603`	`20603`	COMPANION_AD_LOADING_FAILED	A companion ad failed to load or render.
`900`	`20900`	UNKNOWN_ERROR	An unexpected error occurred and the cause is not known. Refer to the inner error for more information. This error is usually fired when the error does not match the criteria of any of the other errors.
`901`	`20901`	VPAID_ERROR	A VPAID error occurred. Refer to the inner error for more information.
`1005`	`21005`	FAILED_TO_REQUEST_ADS	There was a problem requesting ads from the server.
`1007`	`21007`	VAST_ASSET_NOT_FOUND	No assets were found in the VAST ad response. Issue with CDN server. Timeout (in milliseconds) when loading an ad response. If loading takes longer than this timeout, the ad playback is canceled. Can be caused by low bandwidth, or poor website implementation with competing requests that delay the loading of the ad response.	The timeout is configurable for using the creativeTimeout and requestTimeout configuration options. However, increasing the timeout could potentially negatively affect user experience.
`1009`	`21009`	VAST_EMPTY_RESPONSE	Empty VAST response	When working with third-party networks, the fill-rate can be less than 100%. If so, this is an expected error. For example, if the third-party expects to fill 60% of the time, you should expect 40% errors. You can check to ensure that the error rate is in line with the fill-rate of the third-party network.
`1010`	`21010`	UNKNOWN_AD_RESPONSE	The ad response was not understood and cannot be parsed.
`1011`	`21011`	UNSUPPORTED_LOCALE	The language specified in the setLocale configuration option does not match any of the two-letter ISO 639-1 country codes.
`1012`	`21012`	ADS_REQUEST_NETWORK_ERROR	Issue with the CDN server.
`1013`	`21013`	INVALID_AD_TAG	The encoding of the ad tag URL is incorrect.	Check the encoding of special characters in the URL of your ad tag.
`1020`	`21020`	STREAM_INITIALIZATION_FAILED	The stream that contains server-side ad insertion fails to play.	Contact your streaming provider.
`1021`	`21021`	ASSET_FALLBACK_FAILED	The ad provider did not return a valid ad using the fallback.	Contact your ad provider.
`1101`	`21101`	INVALID_ARGUMENTS	You probably will not see this error when using JWP.
`1105`	`21105`	INVALID_ADX_EXTENSION	An invalid AdX extension was found.
`1205`	`21205`	AUTOPLAY_DISALLOWED	The viewer’s autoplay settings in their browser prevented the ad from autoplaying.	Configure your player to be click-to-play.

JWP ad errors

VAST Error Code	JW Error Code	Error	Possible Causes	Possible Solutions
`900`	`60001`	Empty VAST response	No Ad element in VAST document after following wrappers.	When working with third-party networks, the fill-rate can be less than 100%. If so, this is an expected error. For example, if the third-party expects to fill 60% of the time, you should expect 40% errors. You can check to ensure that the error rate is in line with the fill-rate of the third-party network. Some ad providers use empty VAST 3.0 responses to show that they have received the request but do not wish to fill it.
-	`60002`	Ad limit reached	The amount of ad impressions your account has generated in the calendar month exceeds the specified limit.	Contact your JWP sales representative for more details or for upgrade options.
-	`60003`	Ad blocker	The viewer has an ad blocker app or extension installed for their browser.
-	`60004`	Tag download timeout	Issue with CDN server. Timeout (in milliseconds) when loading a VPAID ad response. If loading takes longer than this timeout, the ad playback is canceled. Can be caused by low bandwidth, or poor website implementation with competing requests that delay the loading of the VPAID ad response.	The timeout is configurable for using the creativeTimeout and requestTimeout configuration options. However, increasing the timeout could potentially negatively affect user experience.
`1002`	`60005`	Empty VMAP response	No Ad element in VAST document after following wrappers.	When working with third-party networks, the fill-rate can be less than 100%. If so, this is an expected error. For example, if the third-party expects to fill 60% of the time, you should expect 40% errors. You can check to ensure that the error rate is in line with the fill-rate of the third-party network. Some ad providers use empty VAST 3.0 responses to show that they have received the request but do not wish to fill it.
`900`	`60006`	Ad tag failed to download	An ad tag failed to download, but not inside of a wrapper.
`900`	`60007`	Failed to play because of an unsupported operating system.	An ad tag failed to play because of an unsupported operating system.
-	`60008`	Bidding plugin is unavailable	The bidding plugin was unavailable when the ad was requested.	Might be resolved in a later attempt.
-	`60009`	Not entitled for Player Bidding	Your account is not entitled for Player Bidding.	Contact your JWP sales representative for more details or for upgrade options.
-	`60900`	Unknown error

JWP ad warnings

VAST Error Code	JW Error Code	Error	Possible Causes	Possible Solutions
`1002`	`70001`	Tracking events are missing `breakStart`, `breakEnd`, or error for `AdBreak`	VMAP does not contain tracking events for the ad break. The ad will still play but there will not be pings sent for the events missing from the tracking events.	Contact your ad provider.