GRPC error: Received unexpected EOS on empty DATA frame from server

[Daan Groot]

Hi,

When querying ad_group_ad_asset_view we sometimes get back the following error: INTERNAL: Received unexpected EOS on empty DATA frame from server.

This seems to happen when the request has been running for an hour. Therefore, we thought this was a time-out and we increased the time-out to 4 hours. Unfortunately, this did not make a difference, we are still getting errors.

Some more details:

• We are on version 9
• We use the java client
• We use  SearchStream requests
• Full query: "SELECT\n" +
  " asset.id,\n" +
  " asset.text_asset.text,\n" +
  " ad_group.id,\n" +
  " ad_group_ad.ad.id,\n" +
  " ad_group_ad.ad.responsive_search_ad.headlines\n" +
  "FROM\n" +
  " ad_group_ad_asset_view\n" +
  "WHERE\n" +
  " campaign.status != 'REMOVED' AND\n" +
  " ad_group.status != 'REMOVED' AND\n" +
  " ad_group_ad.status != 'REMOVED' AND\n" +
  " ad_group_ad.ad.type = 'RESPONSIVE_SEARCH_AD' AND\n" +
  " ad_group_ad_asset_view.enabled = true AND\n" +
  " ad_group_ad_asset_view.field_type = 'HEADLINE'"
• Full java stack trace: Caused by: com.google.api.gax.rpc.InternalException: io.grpc.StatusRuntimeException: INTERNAL: Received unexpected EOS on empty DATA frame from server
      at com.google.api.gax.rpc.ApiExceptionFactory.createException(ApiExceptionFactory.java:67)
      at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:72)
      at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:60)
      at com.google.api.gax.grpc.ExceptionResponseObserver.onErrorImpl(ExceptionResponseObserver.java:82)
      at com.google.api.gax.rpc.StateCheckingResponseObserver.onError(StateCheckingResponseObserver.java:86)
      at com.google.api.gax.grpc.GrpcDirectStreamController$ResponseObserverAdapter.onClose(GrpcDirectStreamController.java:149)
      at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
      at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
      at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
      at com.google.ads.googleads.lib.logging.LoggingInterceptor$1$1.onClose(LoggingInterceptor.java:113)
      at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:463)
      at io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:427)
      at io.grpc.internal.DelayedClientCall$DelayedListener.onClose(DelayedClientCall.java:460)
      at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:557)
      at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:69)
      at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:738)
      at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:717)
      at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
      at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133)
      ... 3 more

We hope you can give us more insights on why this is happening. Thanks!

Best,

Daan Groot

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out.

To investigate the issue further, could you please provide the complete request and response logs, with the request-id?

If you haven't yet, logging can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link. Please reply via privately author option.

Thanks,

Nirmita Google Ads API Team

ref:_00D1U1174p._5004Q2arOmu:ref

[Google Ads API Forum Advisor]

Hi Dan,

Replying over here since I saw your issue on the Java client library issues list, but this looks like an API issue that's not specific to that client library.

For some reason, I'm having a hard time finding the request with ID amJbGo5ALKnf_ihJ5CMvvg in our logs. Could you click Reply privately to author on this message and send me the following so I can try to locate that request?

• The customer_id of the request
• The date and time of the request, including the time zone
• The login-customer-id of the request, if set

Also, please let me know in that message if you have attempted to retry the failed request in these cases, and if so, whether the retries succeeded.

Thanks,
Josh, Google Ads API Team
 

ref:_00D1U1174p._5004Q2arOmu:ref

[Daan Groot]

Hi Josh,

Have you received my private message?

Best,

Daan

Op donderdag 16 juni 2022 om 20:22:58 UTC+2 schreef adsapi: