Skip to main content
NetApp Knowledge Base

Azure connected object store unavailable due to "Not found"

  1. Last updated
  2. Save as PDF
Views:
76
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • Microsoft Azure
  • FabricPool

Issue

  • Azure connected object store becomes unavailable
  • When this occurs the following logs may be seen: 

EMS: 
Sun Feb 05 15:42:39 +0000 [cluster-01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "fp1" from node bedb0a81-40e1-11ec-9e9f-d039ea3acfe9. Reason: Not found.

SKTRACE: 
2026-03-24T02:13:51Z 2129383265410774 [16:0] OSC_ERR:  populateErrorResponse:825 Unknown error code from provider: AccountNotFound

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.