Forum Discussion
The database cannot be mirrored to Fabric due Data Factory disabled
I was trying to setup On prem SQL mirroring in a development Workspace but was given error messages below:
New SQL Mirror:
The database cannot be mirrored to Fabric due to below error: Test connection failed. Data Factory 801d6d4c-9d6f-4126-924d-8cae3d820a7e is in state Disabled. The requested operation is not permitted. Activity ID: 3a8b4029-9bed-45cf-9339-503a36b70625
Choose Data:
Data Factory 801d6d4c-9d6f-4126-924d-8cae3d820a7e is in state Disabled. The requested operation is not permitted. Activity ID: b7188a47-b26f-43d9-9bda-28f581c2c26f Refresh or troubleshoot the issue.
I went digging around with fab-cli command, but dont think that shows Data Factory <uuid> for me to debug further. Any suggestions to solve this issue is appreciated. I managed to create the SQL mirror in my other workspace.
Another strange behavior I found in this workspace is when i tried to create an item "Copy Data". I will get thrown with different error.
Create item "Copy Job"
{"message":"Request failed with 400(Bad Request): {\"error\":{\"code\":\"FactoryOperationNotPermitted\",\"pbi.error\":{\"code\":\"FactoryOperationNotPermitted\",\"exceptionCulprit\":1}}}, \nrequestid: 41e8edb5-b0cb-8c2b-4c7b-93f7d2ee24eb"}
Thanks & Regards,
Richard
richard-aik I am glad that suggestion helped. If you have useful items in your original workspace that you want to replicate you may be able to do that using Git integration. If you have to move data, you'll need to use a copy job or activity for that.
Back to your original issue. Generally speaking, the fact that a workload's runtime is not available means the workspace cannot reach a Fabric capacity that runs all the runtimes. One trick you could try to save your workspace is to reassign the workspace to another capacity and then back. Sometimes some metadata gets corrupted behind the scene due to frequent Fabric updates especially if you did not touch the workspace for some time.If you find this answer useful or solving your problem please consider giving kudos and/or marking as a solution.
7 Replies
- apturlov
Super User
richard-aik The errors you are receiving is most likely because you don't have a Fabric capacity assigned to your workspase as v-achippa explained in the above post. You should see the diamond icon beside your workspace name when it has a Fabric capacity attached. If you don't see it you cannot create any Fabric items in that workspace.
If you don't see a diamond icon like on the screenshot above please follow this instruction to assign a Fabric capacity to your workspace Reassign a workspace to a different capacity - Microsoft Fabric | Microsoft Learn
If you find this answer useful or solving your problem please consider giving kudos and/or marking as a solution.
- apturlov
richard-aik I am glad that suggestion helped. If you have useful items in your original workspace that you want to replicate you may be able to do that using Git integration. If you have to move data, you'll need to use a copy job or activity for that.
Back to your original issue. Generally speaking, the fact that a workload's runtime is not available means the workspace cannot reach a Fabric capacity that runs all the runtimes. One trick you could try to save your workspace is to reassign the workspace to another capacity and then back. Sometimes some metadata gets corrupted behind the scene due to frequent Fabric updates especially if you did not touch the workspace for some time.If you find this answer useful or solving your problem please consider giving kudos and/or marking as a solution.
v-achippaCommunity Support
Hi richard-aik,
Thank you for reaching out to Microsoft Fabric Community.
This is expected behavior. Sql Mirroring and Copy Data in microsoft fabric requires Fabric Data Factory to be enabled at the workspace or capacity level. In this workspace the data factory is disabled, so the mirror creation and copy jobs are blocked, this is not a gateway, sql or fab-cli issue.
To resolve the issue please create the mirror in a workspace on a capacity where the Data Factory is enabled.
Thanks and regards,
Anjan Kumar Chippa
Thanks for looking at this issue together with me. I have the same F2 capacity assigned to both workspaces.I also tried creating a new workspace to see if there's an enable/disable Data Factory option. (There's no such option).
With the same capacity licensing on both workspace. I don't understand why:
"Fabric Enginering Test Space" workspace mirroring + copyjob creation works, but
"F2 Development" workspace mirroring + copyjob failed ?Here's the screenshot to show the same capacity level assigned.
Thanks and regards,
Richard
- apturlov
richard-aik What is your role in the workspace? To create items you need to be a member or a contributor. I also see that your workspace is shared - the additional three-dot-circle icon. I am not sure what that could affect.
I don't think that the errors you see are real. I am not aware of any way to disable a Factory runtime in Fabric specifically in the context of a capacity. I think those errors are in reaction to your permissions. You also need to have a Power BI Premium personal license to work with Fabric that you should see in your account in the top right corner.
Please check your license and permissions. The better way is to create a new workspace, assign a Fabric capacity to it and try to create your items there. The shared workspace permissions/settings may be interfering with what you can do.
apturlov I'm the Fabric Administrator.
I managed to create new workspaces, and it is able to create sql mirroring without any issues.
Yes, at this stage, it looks like I have to blow away the workspace. Very unfortunate as there's no fix can be done to the workspace.
