Forum Discussion
ERROR: ValidateWorkspaceOACAsync: exception occured
Hi,
Could anyone provide any guidance on what the following error message means and what I need to check on my Fabric Workspace.
Internal Server Error: Unexpected failure during execution. Exception: 'ValidateWorkspaceOACAsync: exception occured - Failed to get cluster details with http error code - 'Unauthorized', error message - '' '. Please retry. If problem persists, contact customer support.
I have a number of Workspaces that are configured, I believe, identically but today I have a few workspaces that are failing as soon as I trigger a pipeline where the first step is to read a file held within a lakehouse within the same workspace. I don't think it's the reading of the file that's the issue persay, it seems to be more about the triggering of the pipeline that the issue.
13 Replies
we are also getting this issue. I think it is potentially a Fabric issue.
Hi Anonymous - has this worked correctly in the past? If so, have any changes to the files or pipeline been made since its last successful run? Since the error occurred on the data pipeline and includes 'unauthorized', it implies that the pipeline cannot authenticate to the lakehouse. I recommend checking that connection to ensure it is configured properly and has the appropriate permissions. If you provide some additional information such as what type of account you are using in the connection (user, workspace Identity, service principal), I'll be glad to further assist.
Hi jennratten its worked consistenly since June 2025.
The pipeline sits in the same workspace as the lakehouse I'm trying to connect to and I own the workspace, pipeline and lakehouse.
I've tried recreating the pipeline this morning and it appears you can't connect directly to a Lakehouse anymore, it wants a connection first?
New LookUp from Today
Existing LookUp
Hi Anonymous - the two screenshots you showed would have different inputs because in one you selected lakehouse tables and in the other you selected lakehouse files.
If this post helps to answer your questions, please consider marking it as a solution so others can find it more quickly when faced with a similar challenge.
Proud to be a Microsoft Fabric Super User
We’ve also been facing this issue since November 6th. No changes have been made to the environment, yet the schedule and manualy pipelines are failing.
yes it is working on our side thanks!
