# Fabric lakehouse ingest - error Import Metadata

**URL:** <https://community.timextender.com/t/fabric-lakehouse-ingest-error-import-metadata/1737>\
**Category:** Ingest\
**Tags:** migrated\
**Created:** [March 7, 2025, 12:00am UTC](https://community.timextender.com/t/fabric-lakehouse-ingest-error-import-metadata/1737 "2025-03-07T00:00:00Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![PieterQ](https://community.timextender.com/letter_avatar_proxy/v4/letter/p/4da419/32.png) [@PieterQ](https://community.timextender.com/u/PieterQ)\
**Post date:** [March 7, 2025, 12:00am UTC](https://community.timextender.com/t/fabric-lakehouse-ingest-error-import-metadata/1737/1 "2025-03-07T00:00:00Z")

</div>

Hi Everyone,

We want to use Fabric lakehouse as ingest layer, and did the setup according to this article:

[docs.timextender.com/latest/ingest/fabric-lakehouse-ingest-instance-storage-public-preview/](https://docs.timextender.com/latest/ingest/fabric-lakehouse-ingest-instance-storage-public-preview/)

We are running TimeXtender version 6898.1

We created the lakehouse form Fabric, not by using the ‘Create Storage; option from TDI.

When we test the connection in TDI, everything looks fine:

 ![](https://community.timextender.com/uploads/default/original/2X/b/b2c50ba7693963246e59fdc7c90e37c7c1ec98b3.webp)

However, the metadata import task fails with following error:

_The execution failed with error:  
Exception Type: Azure.RequestFailedException  
Message: Service request failed.  
 Status: 400 (BadRequest)  
 ErrorCode: IncomingOperationUntrusted_  
  
 _Headers:  
 x-ms-error-code: IncomingOperationUntrusted  
 Access-Control-Allow-Origin: \*  
 Access-Control-Allow-Headers: REDACTED  
 Access-Control-Allow-Methods: REDACTED  
 Access-Control-Expose-Headers: REDACTED  
 Strict-Transport-Security: REDACTED  
 X-Content-Type-Options: REDACTED  
 x-ms-root-activity-id: REDACTED  
 Content-Length: 0  
 Date: Thu, 06 Mar 2025 14:57:14 GMT  
 Server: Microsoft-HTTPAPI/2.0_  
  
 _Stack Trace: at Azure.Core.HttpPipelineExtensions.ProcessMessage(HttpPipeline pipeline, HttpMessage message, RequestContext requestContext, CancellationToken cancellationToken)  
 at Azure.Storage.Blobs.BlobRestClient.GetProperties(String snapshot, String versionId, Nullable`1 timeout, String leaseId, String encryptionKey, String encryptionKeySha256, String encryptionAlgorithm, String ifTags, RequestConditions requestConditions, RequestContext context)  
 at Azure.Storage.Blobs.Specialized.BlobBaseClient.\<GetPropertiesInternal\>d\_\_124.MoveNext()  
 --- End of stack trace from previous location where exception was thrown ---  
 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()  
 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)  
 at Azure.Storage.Blobs.Specialized.BlobBaseClient.\<ExistsInternal\>d\_\_118.MoveNext()  
 --- End of stack trace from previous location where exception was thrown ---  
 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()  
 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)  
 at Azure.Storage.Blobs.Specialized.BlobBaseClient.Exists(CancellationToken cancellationToken)  
 at Azure.Storage.Files.DataLake.DataLakePathClient.Exists(CancellationToken cancellationToken)  
 at DataStorageEngine.Fabric.FabricStorageEngine.ImportDataSourceMetaData(DataSourceModel dataSourceModel, List`1 tableModels)  
 at ExecutionEngine.Action.ExecutionAction.\<.ctor\>b\_\_11\_0()_

I dont't have a clue what is going wrong. Is there some way to test it another way?

I Understand a notebook will be created, but I don't see any in Fabric.

Also, using fabric as an ingest instance is in public preview for 11 mons now.

Can we use it in an production envirionment (so, when will it be GA)?

Kind regards,

Pieter

_Originally posted on the Timextender Community (Gainsight), 2025-03-07._

---

<div class="post-metadata">

**Author:** ![Christian\_Hauggaard](https://community.timextender.com/letter_avatar_proxy/v4/letter/c/ba8739/32.png) [@Christian\_Hauggaard](https://community.timextender.com/u/Christian_Hauggaard)\
**Post date:** [March 11, 2025, 12:00am UTC](https://community.timextender.com/t/fabric-lakehouse-ingest-error-import-metadata/1737/2 "2025-03-11T00:00:00Z")

</div>

Hi ​@PieterQ&nbsp;

what data source provider are you using for which the import metadata task fails ? e.g. TimeXtender SQL Data Source version 23.0.3.0

Can you please send some screenshots of data source settings?

&nbsp;

&nbsp;

---

<div class="post-metadata">

**Author:** ![mello.bogaarts](https://community.timextender.com/letter_avatar_proxy/v4/letter/m/54ee81/32.png) [@mello.bogaarts](https://community.timextender.com/u/mello.bogaarts)\
**Post date:** [March 11, 2025, 12:00am UTC](https://community.timextender.com/t/fabric-lakehouse-ingest-error-import-metadata/1737/3 "2025-03-11T00:00:00Z")

</div>

We had to enable the following setting in Fabric Portal:

 ![](https://community.timextender.com/uploads/default/original/2X/f/ffddf8b3bdb79cbdbf8fc907f0ffbf084c4041aa.webp)

---

<div class="post-metadata">

**Author:** ![PieterQ](https://community.timextender.com/letter_avatar_proxy/v4/letter/p/4da419/32.png) [@PieterQ](https://community.timextender.com/u/PieterQ)\
**Post date:** [March 11, 2025, 12:00am UTC](https://community.timextender.com/t/fabric-lakehouse-ingest-error-import-metadata/1737/4 "2025-03-11T00:00:00Z")

</div>

​@Christian\_Hauggaard

We found a new option in the Fabric admin portal:

 ![](https://community.timextender.com/uploads/default/original/2X/f/ffddf8b3bdb79cbdbf8fc907f0ffbf084c4041aa.webp)

After enabling this, meta-data is synching!

 ![](https://community.timextender.com/uploads/default/original/2X/a/a8a618b9d0a6d4ff081482770f226e4913378be7.webp)

In the lakehouse explorer, I now see this:

 ![](https://community.timextender.com/uploads/default/original/2X/a/a3733d5b0b9bfc3b05e768ae2f2ca0ac4ddfa59b.webp)

I assume a table will be available after loading the data, but I have to test this.

---

<div class="post-metadata">

**Author:** ![PieterQ](https://community.timextender.com/letter_avatar_proxy/v4/letter/p/4da419/32.png) [@PieterQ](https://community.timextender.com/u/PieterQ)\
**Post date:** [March 11, 2025, 12:00am UTC](https://community.timextender.com/t/fabric-lakehouse-ingest-error-import-metadata/1737/5 "2025-03-11T00:00:00Z")

</div>

​@Christian\_Hauggaard

UPDATE:

Loading data works, only in lahouse explorer, there is an ‘Unidentified’ item.

This is Ok?

 ![](https://community.timextender.com/uploads/default/original/2X/2/2323e55affd2131a8307969d3fce1e295d285382.webp)

Another question: do you know when Fabric as ingest will be GA?

---

<div class="post-metadata">

**Author:** ![Christian\_Hauggaard](https://community.timextender.com/letter_avatar_proxy/v4/letter/c/ba8739/32.png) [@Christian\_Hauggaard](https://community.timextender.com/u/Christian_Hauggaard)\
**Post date:** [March 12, 2025, 12:00am UTC](https://community.timextender.com/t/fabric-lakehouse-ingest-error-import-metadata/1737/6 "2025-03-12T00:00:00Z")

</div>

​@PieterQ&nbsp;yes that should be OK. Regarding GA, I cannot provide a timeline at the moment

---

<div class="post-metadata">

**Author:** ![PieterQ](https://community.timextender.com/letter_avatar_proxy/v4/letter/p/4da419/32.png) [@PieterQ](https://community.timextender.com/u/PieterQ)\
**Post date:** [October 1, 2026, 12:00am UTC](https://community.timextender.com/t/fabric-lakehouse-ingest-error-import-metadata/1737/7 "2026-10-01T00:00:00Z")

</div>

> ​@PieterQ&nbsp;yes that should be OK. Regarding GA, I cannot provide a timeline at the moment

Hi Christian,

Any news on the timeline regarding GA?
