Skip to main content
NetApp Knowledge Base

E-series AutoSupport could not be delivered

Last Updated:

Applies to

NetApp E-Series 


AutoSupport failed message error bundle file not available

Priority:CRITICAL, ASUP Message Type:Daily Schedule, ASUP Task Type:AOD Trigger Query, Status:FAILED, Storage Array:, SAID:6D039EA0002BD3390000000060700331, Thread ID:668,069, Delivery Method:HTTPS, Sequence Number:793, Delivery, AutoSupport Decompressed Size:N/A, Total Collection Time:N/A, Message:AutoSupport message bundle file not available.

Looking into web-server-trace-log log Daily AutoSupport ASUP starts and completes successfully and delivered

INFO [SMMonitorTask-1944] trace [] [requestId=0, deviceId=N/A] Array CSB collection is starting, file: /msw_data/data/monitor/supportdata/draft/BUNDLE.Daily.6D039EA0002BD3390000000060700331.1650183424859/BUNDLE.Daily.6D039EA0002BD3390000000060700331.1650183424859.7z

INFO [SMMonitorTask-1532] trace [] [requestId=0, deviceId=N/A] Connecting to HTTPS server:, IP

INFO [SMMonitorTask-1944] trace [] [requestId=0, deviceId=N/A] ASUP task complete, task: AUTO_SUPPORT_COLLECTION, source: AUTO_SUPPORT_DAILY_SCHEDULE, status: SUCCESS

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.