This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 83%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EG%3C/text%3E%3C/svg%3E)
I am using the SDK to connect to an Azure Data Lake Service Gen2 via an IAM Role Assignment using an app registration in Azure AD. The application is able to create the DataLakeFileSystemClient object okay, but when the application then tries to use that to create the DataLakeDirectoryClient object, I keep getting a System.AggregateException error: "The specified filesystem does not exist".
The DataLakeServiceClient uses accountname, clientid, clientsecret, and clientTennantID to initialize itself. I've checked that the app registration account is set up with the proper role assignment of Storage Blob Data Contributor (or Storage Blob Data Owner) for the various containers I've tried, but I keep getting this same exception from the different containers and different app registration accounts that I've tried. Is there a data lake setting that I have not enabled?
Thanks for any insights.
An Azure service that provides an enterprise-wide hyper-scale repository for big data analytic workloads and is integrated with Azure Blob Storage.
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
I think I found the issue. The following line 40 was commented out in the program.cs file.
//CreateFileSystem(_dataLakeServiceClient).Wait();
Uncommenting this out addressed that error.
@glennox125 Glad to know that the issue is resolved. Thanks for the update! Appreciate for sharing the steps which helped you, this would certainly benefit other community members.
I think I found the issue. The following line 40 was commented out in the program.cs file.
//CreateFileSystem(_dataLakeServiceClient).Wait();
Uncommenting this out addressed that error.
@glennox125 Glad to know that the issue is resolved. Thanks for sharing the steps which fixed the issue! which could be beneficial for other community members reading this thread.