Forum Discussion
ERROR: ValidateWorkspaceOACAsync: exception occured
- Anonymous9 months ago
The solution from Microsoft is as follows:
Make a false edit on the pipeline for example, change parameter value, undo it and then save pipeline. Then try running again. This has fixed it for other users.
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
- Anonymous9 months agoNot applicable
Apologies, if the screen shot was misleading. When I select an input of files it still requests a connection. It previously didn't request a separate connection to the lakehouse as the lakehouse was the connection.
- tayloramy9 months agoSuper User
Hi Anonymous,
That new connection selection is part of a recent service update where you can explicitly set the connection the lakehouse uses, rather than it only using your user's credentials. This is intended and a good change, as you can now manage the connection properly, so if you change your password or leave the org everything doesn't break and you have one nice place to update the connection.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
- Anonymous9 months agoNot applicable
Was there a blog post or "What's New" that talks about this? I would have hoped it would be an option rather than forced upon the users?
Microsoft have also confirmed that what I'm seeing is an issue on their side so hopefully once they've investigated I can up date on here their suggestion/resolution.