Pipelines topics

What Are the Best Practices for Building Reliable and Scalable Data Pipelines?

codeautomation — Tue, 03 Nov 2026 19:35:40 GMT

As organizations integrate data from multiple applications, databases, APIs, and cloud platforms, building reliable data pipelines becomes increasingly important.

A pipeline that works well with small datasets may encounter problems as data volumes grow and workflows become more complex. Failed activities, dependency issues, schema changes, and inconsistent execution can affect downstream processes and reporting.

I'd like to learn how the community handles these challenges in Microsoft Fabric Data Factory.

A few questions:

How do you design pipelines to handle large datasets efficiently?
What is your approach to implementing retries, failure handling, and recovery mechanisms?
How do you manage dependencies between multiple pipelines and activities?
What strategies do you use for incremental data loading and avoiding duplicate records?
How do you monitor pipeline execution and identify failures before they affect downstream systems?

I'd especially appreciate practical examples involving Microsoft Fabric Data Factory, pipeline orchestration, and automated monitoring.

What practices have helped you build more reliable data pipelines?

How can AI agents improve Microsoft Fabric Data Factory pipeline automation?

codeautomation — Tue, 03 Nov 2026 19:32:07 GMT

I am exploring how AI agents can help make data pipeline development and monitoring more efficient in Microsoft Fabric Data Factory.

Some potential use cases:

Automatically creating pipeline workflows based on business requirements
Detecting pipeline failures and suggesting fixes
Optimizing data movement and transformation steps
Monitoring data quality and identifying anomalies
Triggering automated actions through APIs or external tools

I would like to understand how teams are currently combining AI agents with Fabric Data Factory.

Are you using:

AI-assisted pipeline generation?
Automated error analysis and recovery workflows?
Fabric notebooks with AI models for data operations?
Custom agents connected with Data Factory pipelines?

Would appreciate insights, real-world examples, or architecture patterns from developers working with Fabric Data Factory automation.

Fabric Pipeline: Best way to handle incremental loads from multiple source tables?

Ar_Sh — Mon, 02 Nov 2026 20:02:44 GMT

I'm building a Fabric pipeline to load around 40 SQL Server tables into a Lakehouse. Some tables contain millions of records, so full loads are not practical.

Would you recommend using a single metadata control table to manage incremental loads, or maintaining separate watermarks for each table?

Also, how would you handle tables without a LastModifiedDate column?

Would love to hear how others are handling this in production.

Fabric Pipeline: Best way to handle incremental loads from multiple source tables?

Ar_Sh — Mon, 02 Nov 2026 20:02:40 GMT

I'm building a Fabric pipeline to load around 40 SQL Server tables into a Lakehouse. Some tables contain millions of records, so full loads are not practical.

Would you recommend using a single metadata control table to manage incremental loads, or maintaining separate watermarks for each table?

Also, how would you handle tables without a LastModifiedDate column?

Would love to hear how others are handling this in production.

Error handling pattern for ForEach with partial failures: continue and report, or fail fast?

jubinsoni — Fri, 30 Oct 2026 05:28:08 GMT

Hi everyone,

I have a pipeline that loops over a list of tables with ForEach and runs a Copy activity per item. When one table fails, I would like the remaining tables to still load, and to get one consolidated failure report at the end instead of the whole run failing on the first error.

The pattern I am considering:

Wrap the Copy activity so its failure path (the On fail dependency) logs the table name and error message to a control table, and the ForEach item itself finishes as succeeded.
After the loop, a Script or Lookup activity counts rows in the control table for this run, and a Fail activity raises one error with the summary if the count is above zero.

A sketch of the final check:

SELECT COUNT(*) AS failed_tables FROM ctl.load_log WHERE run_id = @{pipeline().RunId} AND status = 'Failed';

Questions:

Is this the usual approach, or is there a built-in way to get partial-success semantics for a ForEach?
How do you make sure the pipeline run status still reflects the failures so alerts fire?
Any gotchas with the sequential versus parallel setting when logging from inside the loop?

Thanks in advance.

Will Invoke Pipeline (Legacy) be deprecated?

benitovbreugel — Thu, 29 Oct 2026 09:30:45 GMT

Is there currently any plan or timeline to deprecate Invoke Pipeline (Legacy) in Microsoft Fabric?

For same-workspace pipeline orchestration, the Legacy activity is still very convenient. The new Invoke Pipeline activity provides additional capabilities, such as cross-workspace invocation and child-pipeline monitoring, but it also requires a Connection object.

Given the performance concerns that have been reported by multiple users, I’m wondering what the recommended approach is:

Is it safe to continue using Invoke Pipeline (Legacy) for now?
Does Microsoft recommend migrating existing pipelines to the new Invoke Pipeline activity?
Is there any indication that the Legacy activity will eventually be deprecated or removed?
Should we already start rebuilding existing pipeline orchestration using the new activity and Connections?

It would be great to understand the intended direction, especially before investing time in rebuilding existing pipeline implementations.

Thanks!

Can parallel pipeline runs upsert into the same Lakehouse table without commit conflicts?

Microfyx — Wed, 28 Oct 2026 07:01:04 GMT

I want to ingest from 10 DB2 databases into a Lakehouse using one generic pipeline, invoked once per DB. They all write into the same Bronze tables (e.g. .raw_<table>). Every row carries a _db_id, so no two runs ever touch the same record.

The Copy activity uses Table action = Upsert with key columns _db_id + the source primary key. The tables are not partitioned or clustered. In DESCRIBE HISTORY the commits show operation = MERGE, engineInfo = datafactorycopy, and operationParameters, operationMetrics, readVersion and isBlindAppend are all NULL.

I would like to run the DBs in parallel, but we are unsure about commit conflicts. The concurrency control article says conflicts depend on the files a MERGE reads, and that the partition column must be a literal in the merge condition. It describes Spark, though, and I could not find anything about the Copy sink.

Questions:

Does the Copy activity upsert read the whole target table during the MERGE, or can it prune files, for example by _db_id?
Can two parallel Copy upserts (different DBs, same table) fail with something like ConcurrentAppendException? Does the sink retry internally?
Would partitioning the table by _db_id help with the Copy sink, even though we cannot set a literal predicate?
Is there a recommended pattern for this, for example append into per-DB staging tables and a single MERGE afterwards?

For now we run the DBs sequentially. Any experience or documentation pointers would be appreciated.

Fabric Pipeline fails with 'WorkspaceNotFound' on ADLS Gen2/OneLake connection

debiagui — Mon, 26 Oct 2026 12:14:07 GMT

Hi everyone,

I am facing a critical issue with a Fabric pipeline that started last week. I would appreciate any insights or workarounds.

The Context & Trigger Event:

Last week, all stored connections in my Fabric user profile under "Manage connections and gateways"started expiring
I received a warning/banner indicating that I was very close to reaching the tenant limit of 1,000 stored cloud connections.
In parallel to this credential expiration event, a step in one of my pipelines started failing.

The Pipeline Step:

What it does:It connects to an external SFTP server, downloads data, and writes it directly toOneLake Storage using an Azure Data Lake Storage Gen2 (ADLS Gen2) connection.

The Odd Behavior:

If I go to "Manage connections and gateways", the connection shows as Online and healthy.
I have manually re-entered and updated the credentials there, and the UI says everything is OK (connection test passes in the gateway/connection manager).
However, when I run or test the connection directly inside the Pipeline, it immediately fails with the following error:

ADLS Gen2 operation failed for: Operation returned an invalid status code 'NotFound'. Account: 'onelake'. ErrorCode: 'WorkspaceNotFound'. Message: 'Not Found'. TimeStamp: 'Mon, 26 Oct 2026 11:49:43 GMT'.. Operation returned an invalid status code 'NotFound'

What I have tried so far:

Cleared and re-entered credentials in the connection settings.
Deleted unused connections to free up slot space below the 1,000 limit, but the pipeline error persists
It seems like the pipeline is pointing to a cached, corrupted connection ID token that cannot resolve the workspace path anymore, even though the connection is "green" in settings.

Has anyone encountered this WorkspaceNotFound error on >onelake after hitting the connection limit? Is there a way to force the pipeline to bind to a fresh connection instance?

Thanks in advance!

Session tag restrictions for high concurrency mode in pipelines

AvdBerg — Tue, 20 Oct 2026 07:59:37 GMT

Hi all,

Our pipeline runs 3 notebooks in succession using high concurrency mode for pipelines with a session tag. The run failed with this error:

Failed to run notebook due to invalid request. [Error: Session tag can only contain letters, numbers, and underscores. (Parameter 'HighConcurrencyModeOptions.SessionTag')]

The tag we used was dataverse-ingest, so the hyphen seems to be the cause. We will switch to underscores, but I could not find this restriction in the Microsoft documentation.

Is the allowed character set for session tags documented anywhere? Are there other limitations (length, reserved words, case sensitivity) we should know about?

Thanks!

Connect to SFTP server using key-pair auth via. onprem gateway and datapipeline

KimTutein — Tue, 20 Oct 2026 06:57:52 GMT

Has anyone have success with copying a file from SFTP server using key-pair authentication and on premise gateway? It seems no matter what I do I end up with this error (not supported):

Link to error code: Troubleshoot connectors - Microsoft Fabric | Microsoft Learn

We are able to use the key-pair in a notebook and get data (and we have verified that network is open on the gateway servers as well) – however we are not able to get a connection working so we may use it in a data pipeline in a “copy activity”.

Specs

We are located in WestEuorpe

our on-premise-gateway is version 3000.334.4 (sept 2026).

We have generated the key pair using this powershell script:

ssh-keygen -t rsa -b 4096 -f .\pbi_sftp

I have also tried to convet the private key to a “traditional RSA PEM version” (with some copilot help)

It simply seems to me that key-pair for SFTP is not supported even though it is an option in the GUI (see below):

I found this overview which states it is not supported: SFTP connector overview - Microsoft Fabric | Microsoft Learn

However it does not match very good with giving us the option in the GUI

How to write data directly from Microsoft Fabric to a SharePoint Online List without Power Automate?

nikhil1609 — Thu, 15 Oct 2026 11:18:57 GMT

Hi everyone,

I am building an automated enterprise data pipeline in Microsoft Fabric (Medallion architecture) using scheduled pipelines and PySpark Notebooks.

My final stage requires pushing a clean, curated Gold Lakehouse table (ranging from 500 to 3,000+ rows) directly into an existing SharePoint Online List.

Currently, we are using a workaround: Dataflow Gen2 exports the data as a CSV file to a SharePoint document library, which then triggers a Power Automate cloud flow. The cloud flow parses the CSV and uses a loop to delete the old items and insert the new rows into the SharePoint list.

However, this low-code approach is highly inefficient, hits API throttling ceilings, takes a long time to run, and risks breaking when row counts increase.

When attempting to streamline this by setting the data destination inside Dataflow Gen2, we discovered that SharePoint Online List is completely unavailable as a "Data Destination" option (it only appears as an inbound data source).

My questions:

Is there an out-of-the-box or native native Fabric feature (e.g., via Pipelines, Copy Activities, or shortcuts) that allows us to bulk-write or overwrite data tables directly into a SharePoint Online List?
If a native connector for writing doesn't exist yet, what is the recommended, high-performance enterprise method to achieve this direct bulk sync entirely within the Fabric ecosystem? (e.g., executing Microsoft Graph API batch requests via a PySpark notebook, using an Azure Logic App, or another method?)

Any architecture advice, script blueprints, or best practices would be greatly appreciated.

Thank you!

FabricSqlEndpointMetadata Connector kind is not valid for RefreshSqlEndpoint Activity

fpvmorais1 — Wed, 14 Oct 2026 08:42:40 GMT

Hi,

I am getting this error when configuring a RefreshSqlEndpoint:

I've recreated the connection and I am also using OAuth with a service account.

Any tips on what I could be doing wrong?

Thanks

Copy Data Activity failed on Upsert

olivs — Wed, 07 Oct 2026 14:14:09 GMT

I'm currently building a pipeline to copy data from a Fabric warehouse to a Fabric lakehouse. Everything from source to destination is configured in a config table. Including the column mapping. While executing the pipeline with Table action: "Overwrite" defined, the pipeline executes succesfully. When changing the Table action to "Upsert", the pipeline fails.

Which Error do I get?

ErrorCode=FailedToUpsertDataIntoDeltaTable,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Hit an error when upsert data to table in Lakehouse. Error message: Specified cast is not valid.,Source=Microsoft.DataTransfer.Connectors.LakehouseTableConnector,''Type=System.InvalidCastException,Message=Specified cast is not valid.,Source=Microsoft.DataTransfer.Connectors.LakehouseTableConnector,'

What did I configure?

How does the input for the Key columns look like during execution?

Does anyone has any ideas?

I have been searching for this specific error but couldn't find any details...

Thanks for the help :)

How can AI agents improve Microsoft Fabric Data Factory pipeline automation?

codeautomation — Mon, 28 Sep 2026 20:29:25 GMT

I am exploring how AI agents can help make data pipeline development and monitoring more efficient in Microsoft Fabric Data Factory.

Some potential use cases:

Automatically creating pipeline workflows based on business requirements
Detecting pipeline failures and suggesting fixes
Optimizing data movement and transformation steps
Monitoring data quality and identifying anomalies
Triggering automated actions through APIs or external tools

I would like to understand how teams are currently combining AI agents with Fabric Data Factory.

Are you using:

AI-assisted pipeline generation?
Automated error analysis and recovery workflows?
Fabric notebooks with AI models for data operations?
Custom agents connected with Data Factory pipelines?

Would appreciate insights, real-world examples, or architecture patterns from developers working with Fabric Data Factory automation.

What are the actual network settings for Gateway access without needing to open source

MOVC — Fri, 25 Sep 2026 11:25:14 GMT

When we first adopted Fabric we ran into an issue where we had granted access to the Fabric endpoints as indicated in the Microsoft docs to our Gateway server but could not get data up via the Copy Data activity. In the end we resolved this by putting the same Fabric access on our source SQL server which resolved the issue but didn't seem to fit the Microsoft advice. This was never required for Power BI connections via the Gateway, it doesn't make sense for this to be a requirement at all.

It has been several years since this and we are now migrating into another set of servers. The set up is exactly the same, a gateway server with fabric endpoints allowed and the source sql server without and we cannot transfer data via data factory copy activities. We had effectively forgotten that we allowed source to Fabric connections to resolve this issue, and before doing it again wanted to investigate why this is the case. I cannot see anything in the docs that would suggest anything needs to be opened on the source server.

How to access on-premises data sources in Data Factory - Microsoft Fabric | Microsoft Learn

Adjust communication settings for the on-premises data gateway | Microsoft Learn

Is anyone aware of any potential configuration mistakes we could have made with our servers that would require this to be the case? For clarity, the gateway and source server are actually separate servers completely.

Fabric Data Factory system variable pipeline().triggertype

JaneLHunt — Fri, 25 Sep 2026 09:00:00 GMT

Hello

I would be grateful if someone from Microsoft would clarify whether, for Fabric Pipelines, the system variable pipeline.triggertype() is officially supported.

Our pipeline is set up to be triggered by a schedule.

At the moment, on pipeline run, when we pass the value of the system variable pipeline.triggertype() through to our own logging tables, it returns the value of either Manual or 1.

This is different to what is stated in the pipeline development user interface, which shows that it passes through value of either Manual or Scheduler.

Also in the documentation below re pipeline scope variables for Fabric data factory, no mention is made of the system variable pipeline.TriggerType()

https://learn.microsoft.com/en-us/fabric/data-factory/expression-language#pipeline-scope-variables

Please clarify if the values of Manual and 1 currently being passed through are a reliable means to determine whether the pipeline was a manual or scheduled trigger - or will these values be subject to change?

If not reliable, I will have to develop a manual work around.

Many thanks for your help in anticipation.

Intermittent Gateway Connectivity Error in Fabric Pipelines

Aventuran — Fri, 25 Sep 2026 07:09:44 GMT

Hi everyone,

I'm posting because we're experiencing an issue with some of our Fabric pipeline executions and would like to know if anyone has encountered something similar.

We have an on-premises SQL Server and an on-premises data gateway installed on a dedicated gateway server. The issue is that, intermittently, approximately 60% of pipeline executions fail when a pipeline activity executes a query against the SQL Server database.

The error returned is:

"Please check your network connectivity to ensure your on-premises data gateway can access ne.frontend.clouddatahub.net and restart the service to retry the connection again once the connectivity issue has been resolved."

What makes this error difficult to understand is that:

We currently have more than 800 Power BI Dataflows Gen1 running through the same gateway, and none of them experience this issue.
The same pipeline sometimes runs successfully and sometimes fails with the error above.
Because of this inconsistent behavior, it does not appear to be a permanent connectivity problem between the gateway and the cloud service.

Has anyone experienced a similar issue or found a solution?

Any guidance or suggestions would be greatly appreciated.

Thanks in advance!

Office 365 Outlook activity cannot bind Workspace Identity or Service Principal connection

vicenteajm — Tue, 15 Sep 2026 23:47:21 GMT

Hi Fabric Community,

I am testing the Office 365 Outlook / Office 365 Email activity in Microsoft Fabric Data Factory for a CI/CD scenario.

According to the current Microsoft Learn documentation, the Office 365 Outlook activity supports User Authentication OAuth, Workspace Identity WI, and Service Principal SPN.

I tested both Service Principal and Workspace Identity.

The Fabric workspace has an active Workspace Identity.

The corresponding Microsoft Entra application and service principal exist.

The Office 365 Email / MicrosoftOutlook cloud connection can be created successfully.

The connection is visible in Manage connections and gateways.

From the pipeline Outlook activity, the connection is also visible through Browse all.

The issue is that when I select the WI or SPN connection from Browse all, Fabric shows the loading indicator but does not bind the connection to the Outlook activity.

No error is displayed.

The problem occurs before pipeline execution, so this is not a Microsoft Graph Mail.Send runtime error.

Expected behavior:

The selected Workspace Identity or Service Principal connection should be associated with the Office 365 Outlook activity.

Actual behavior:

The connection is visible and discoverable, but selecting it does nothing and the activity remains without a connection.

This blocks our CI/CD scenario because we want to avoid user OAuth connections that must be recreated or rebound between DEV, TEST and PROD.

I also noticed a documentation inconsistency.

The current Office 365 Outlook activity documentation explicitly says that Workspace Identity and Service Principal are supported.

However, the general Service Principal support page does not currently list Outlook as a supported data source.

The general Workspace Identity support page also does not list Outlook among the supported data sources.

Can Microsoft confirm whether Workspace Identity and Service Principal support for the Office 365 Outlook activity is fully GA, under staged rollout, or currently affected by a known issue?

Microsoft Learn references:

Office 365 Outlook activity

learn.microsoft.com/en-us/fabric/data-factory/outlook-activity

Service Principal support in Data Factory

learn.microsoft.com/en-us/fabric/data-factory/service-principals

Workspace Identity support in Data Factory

learn.microsoft.com/en-us/fabric/data-factory/workspace-identity

I can provide additional diagnostics or tenant details privately if required.

Thanks.

Bug: QuickBooks connector (QuickBooks for Pipeline) fails OAuth login

Vitaliy3 — Fri, 11 Sep 2026 06:19:22 GMT

When attempting to create a connection of type QuickBooks for Pipeline (Cloud category) via Manage Connections and Gateways in Microsoft Fabric, with the authentication method automatically set to OAuth 2.0, clicking the Edit credentials button results in an error when trying to initiate the OAuth login flow.

Error message:

Unable to start OAuth login for this data source. Connection string is not supported.

Details: Query contains unsupported function. Function name: QuickBooksForPipeline.Contents

Session Id: 6fb86dae-dc71-4a06-8f7f-b99aee7885df

RequestId: 710bfcb8-ff7a-444d-90dc-c2dcc311e0f9

Cluster URI: https://api.powerbi.com

Status code: 400

Time: Fri Sep 11 2026 07:54:51 GMT+0300 (Eastern European Summer Time)

Steps to reproduce:

In a Fabric workspace, open a Copy Data activity (Source) or go to Manage Connections and Gateways.

Click "+ New" to create a new connection.

Select connection type Cloud.

Search for and select QuickBooks for Pipeline as the data source.

Authentication method is automatically set to OAuth 2.0.

Click Edit credentials.

The error above appears instead of the expected QuickBooks OAuth consent screen.

Expected behavior: Clicking Edit credentials should open the standard Intuit OAuth 2.0 consent screen, as described in the QuickBooks connector documentation for Data Factory / Fabric pipelines.

Impact: It is currently impossible to create a working QuickBooks Online connection in a Fabric pipeline using this connector, which blocks migrating an existing pipeline (where tokens are currently passed manually as parameters) to native OAuth authentication.

Environment: Microsoft Fabric (trial capacity), browser: Chrome, date: 2026-09-11.

Faulting application FabricPipelineWorker.exe

ThomasPluemper — Thu, 03 Sep 2026 08:40:03 GMT

Hello,
we installed an On-premise data gateway version 3000.330.1 (August 2026) on a Windows Server 2025.

Every time we connect to SAP over SAP Table Application Server to our SAP System on SAP Cloud, we get the following error:

Application: FabricPipelineWorker.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at Microsoft.DataTransfer.Common.ProcessManagement.Communication.MessageHandlerSet.Dispatch(Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessageChannel, Microsoft.DataTransfer.Common.ProcessManagement.Communication.Message)
at Microsoft.DataTransfer.Common.ProcessManagement.Communication.MultiplexingMessenger.OnMessageToOtherChannel(Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessageChannel, MessageToOtherChannel)
at Microsoft.DataTransfer.Common.ProcessManagement.Communication.MessageHandlerSet.Dispatch(Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessageChannel, Microsoft.DataTransfer.Common.ProcessManagement.Communication.Message)
at Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessengerExtensions+<WaitForAsync>d__0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessengerExtensions+<WaitForAsync>d__1`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.DataTransfer.Common.ProcessManagement.RemoteService.RemoteServiceEnvironment+<DisposeServiceStubsAsync>d__4.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.DataTransfer.DataMovementGateway.WorkerProcess.WorkerContainer+<StartAsync>d__11.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.DataTransfer.DataMovementGateway.WorkerProcess.Program+<Main>d__1.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.DataTransfer.DataMovementGateway.WorkerProcess.Program.<Main>(System.String[])

AND:

Faulting application name: FabricPipelineWorker.exe, version: 5.68.9706.2, time stamp: 0x900a871d
Faulting module name: KERNELBASE.dll, version: 10.0.26100.33158, time stamp: 0x4332201f
Exception code: 0xe0434352
Fault offset: 0x00000000000c75fa
Faulting process id: 0x2234
Faulting application start time: 0x1DD3B1901C52B57
Faulting application path: C:\Program Files\On-premises data gateway\FabricIntegrationRuntime\5.0\Shared\FabricPipelineWorker.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: a3bc643f-227b-4f9e-b7b7-45ff005eb05f
Faulting package full name:
Faulting package-relative application ID:

Has anyone an idea?

BR Thomas