AdError 1005: There was a problem requesting ads from the server. Caused by: Error: 6

[Applixir Team]

Hi,

We've recently started seeing this error across multiple accounts. I'm familiar 1005 having seen it before associated with iOS issues or incorrect URL encoding but this is very different. Here are the details, I will provide a URL to reproduce in a PM if needed but currently I'm looking for any available information regarding 1005: Caused by Error: 6.

1. This is happening on HTML5 IMA SDK

2. We are running on DFP using generated GPT tags with Order/Line Item containing Ad Exchange tag with fallback tags from other ad providers.

3. This error has only occurred on Google Ad Exchange tags

4. The error is reported as follows:

GET https://googleads.g.doubleclick.net/pagead/ads?client=ca-video-pub-86372462…block=1&ged=ve4_td3_tt1_pd3_la3000_er0.0.0.0_vi0.0.528.656_vp0_ts0_eb16747 400

GET https://googleads.g.doubleclick.net/pagead/ads?client=ca-video-pub-86372462…block=1&ged=ve4_td3_tt1_pd3_la3000_er0.0.0.0_vi0.0.528.656_vp0_ts0_eb16747 400

applixir.sdk3.0imb.js:32 AdsLoader error: AdError 1005: There was a problem requesting ads from the server. Caused by: Error: 6

The actual failure occurs in https://imasdk.googleapis.com/js/core/bridge3.355.3_en.html

Thanks,

Applixir Team

[IMA SDK]

Hi,

Thank you for reaching out to us. We were not able to reproduce the behavior that you're seeing with the SDK throwing the error 1005: Caused by Error: 6. Were you able to reproduce the behavior running your ad tag against our VSI? Can you provide the ad tag you were using when you encountered the issue? Please use the "Reply privately to author" option to share the information privately.

Regards,
Arnaud Casame
IMA SDK Team

ref:_00D1U1174p._5001UOEcVS:ref

[Applixir Team]

Hi Arnaud,

I left you a URL to reproduce the error via PM.

Dean

[IMA SDK]

Hi,

Thank you for providing additional insights with regards to the issue. I was not able to reproduce the behavior that you're seeing with the error 1005: Caused by Error: 6 being thrown, the ad was displayed successfully (see screenshot attached). Can you provide the steps to reproduce the behavior that you're seeing? If the issue is only reproducible on your end, can you provide a video recording showing the issue?

Regards,
Arnaud Casame
IMA SDK Team

ref:_00D1U1174p._5001UOEcVS:ref

[Applixir Team]

Hi Arnaud,

This problem is intermittent. Can you try that test URL again?

Thanks,

Applixir team.

[Applixir Team]

I think we've solved this issue. I will leave more information in a day or two when I'm certain.

Thanks,

Applixir team

[Cameron Church]

Hi Applixir

Did you guys confirm your fix?  We're seeing the same issue and wondering if you can share your insights?

CC

[Applixir Team]

No, we are still getting this error.

[Applixir Team]

Btw, if you have a test case that can reproduce this regularly, please post it. It's intermittent and whenever Google tests they don't see it.

On Sunday, December 22, 2019 at 12:56:35 PM UTC-8, Cameron Church wrote:

[Applixir Team]

Hi Arnaud,

We did not solve this problem, it just became harder to reproduce. This error is causing significant problems for our customers and ourselves. I am sending you some additional information regarding this by PM.

Thanks,

Applixir team

[Cameron Church]

You can see our discussion on the matter here https://groups.google.com/forum/#!topic/ima-sdk/IVNsv_uGNOw

What we've learnt is:

1. This is a highly irreproducible error (in controlled setups) because it's happening somewhere along the programmatic chain and only happens when certain conditions are set in a production environment.  Conditions that you can't record from the SDK since they are not made available via it's interface.

2. Although we record the environmental state at the point this error is thrown  each and every time it happens in production in our analytics platform (watchingthat.com) there is no clustering to point to any particular cause at this level so we believe it's somewhere in the configuration layer (ad tag etc) - and this correlates to the description provided by the IMA SDK as to its cause.

3. The SDK is throwing this error but does not provide any context around state at the point it throws the error. Specifically the ad tag that should be the cause of this is not made available.  We have proven in our situation that this is nothing to do with the primary ad tag and is a redirect/wrapper tag.

4. The SDK Support team doesn't have any tooling/ability to further help troubleshoot this - we've been told that there are plans to improve the SDK to provide more of the required context/state at the point of the error being thrown but no time frames are given and things remain quite vague.   The best suggestion they can offer is to run a Charles debug and pray you can replicate it - however see the first point that you need a very specific programmatic instance that makes it all but impossible to replicate.

At this point we've used the data we've collected ourselves to understand what it's not.  We know it's not geographical, and we know it's not device specific.  We also know it's not a content specific issue.  And with our ability to track the timings of the introduction of this error and, over a time series, how it behaves over a 24 hr period we're tracking down changes at the ad server / demand stack to see if we can narrow down configuration changes as candidates.

Hope the above helps.  

[Applixir Team]

Hi Cameron,

I believe I've found the cause of this error. It seems to be caused by various secure/private browsers. This will only reproduce using a standard Google ad tag (AdX or GPT), it will not reproduce with sample tags that don't track. I can reproduce this 100% of the time using Google's own IMA example code. You can most easily reproduce this using Firefox Quantum. First run a test using Firefox in normal mode to verify proper operation. Then run the same test using a Firefox private window and you should get the 1005, error 6 condition.

If you generate a HAR file from the Network tab in Dev Tools and search on 1005 you will get more insights on what is happening.

Dean

[Satyaprakash Mishra]

Hi, 

The same issue getting, below error 

(20:49:34) Ad error: AdError 1005: There was a problem requesting ads from the server. Caused by: Error: 6

Regards,

Satyaprakash Mishra

[IMA SDK]

Hi there,

Thank you for reaching out to us.

Could you please provide the ad tag that you're using so we could investigate the issue on our end? You can share this via "Reply privately to author" option.

With regard to this thread, the issue of 1005 error seems to be with the AdX redirect URL possibly unpublished or being blacklisted instead of the SDK implementation itself, which could be the same case with the issue that you're encountering.

That being said, I would suggest contacting your Google Ad Manager account manager to help you to resolve the issue or you can reach out to the Ad Manager help center for further assistance regarding your concern.

For the complete discussion of this thread, you can check out the link below for your reference:
https://groups.google.com/forum/#!topic/ima-sdk/IVNsv_uGNOw

Regards,
Sherwin Diesta
IMA SDK Team

ref:_00D1U1174p._5001UOEcVS:ref