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 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.
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.
- vanessa_fvg9 months agoAdvocate I
100% agree, i can't see anything on whats new
i have reported our issue to microsoft too. pipelines broken is not a 'good change' in my opinion.
- tayloramy9 months agoSuper User
The lakehouse connection option is described here:
Configure Lakehouse in a copy activity - Microsoft Fabric | Microsoft LearnIn my environment, this change did not break existing things, but when modifying things I did need to select the proper connection. If this is breaking your stuff then it is likely a bug and needs to be corrected.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.