Error when creating new semantic model from a lakehouse into different workspace

[amaaiia]

I've created a new workspace and a F64 capacity it's been attached. Then, I've tried to create new semantic model in this new workspace from a lakehouse hosted in another workspace, and this error is given:

{"error":{"code":"ExternalServiceUserFailed","pbi.error":{"code":"ExternalServiceUserFailed","parameters":{},"details":[{"code":"ModelingServiceError_Reason","detail":{"type":1,"value":"Error in PowerBIDataAccess"}},{"code":"ModelingServiceError_Location","detail":{"type":1,"value":"GetModelId"}},{"code":"ModelingServiceError_ExceptionType","detail":{"type":1,"value":"PowerBIEntityNotFoundException"}},{"code":"ModelingServiceError_Message","detail":{"type":1,"value":"The model with id xxxxxxxxxxxxxxxxxxxxxx was not found"}},{"code":"ModelingServiceError_ExceptionErrorCode","detail":{"type":1,"value":"PowerBIEntityNotFound"}}],"exceptionCulprit":1}}}

The point is that if I try to create the semantic model into another workspace (one workspace I have from some days ago, same capacity attached), I'm able to create it, it's just being an issue for this new workspace.

Is there any additional configuration I have to add to my new workspace that I'm missing?

[amaaiia · Accepted solution]

Finally, the issue was that the owner of the Lakehouse didn't have contributor role or above in target workspace. Once added LH owner as Contributor in tarhet workspace, it works, I've been able to create the semantic model.

However, for support team this doesn't seem to be a normal behavior because engineers working on Lakehouse might not have acces to semantic models, so they are investigating it to check if it's the best behaviour.

[Anonymous]

Thanks for providing the details here @amaaiia 
Please continue using Fabric Community for any help regarding your queries.

[Anonymous]

Hi @amaaiia 
Thanks for using Fabric Community.

The error code “ExternalServiceUserFailed” in Power BI typically indicates an issue with accessing the Power BI service or a specific resource within it. The details of the error suggest that the model with a certain ID was not found, which could mean that the model does not exist in the new workspace or there are permission issues preventing access to it.

Here are some steps you can take to troubleshoot this issue:

• Check Model Existence: Ensure that the model you’re trying to access actually exists in the new workspace.
• Verify Permissions: Confirm that you have the necessary permissions to access the model and the lakehouse in the new workspace.
• Review Workspace Configuration: Compare the configurations of the new workspace with the one where model creation is successful to identify any discrepancies.
• Redeploy Model: If the model was deleted or not properly deployed, consider redeploying it to the new workspace.

There are similar cases like this and this was identified as a bug:
https://community.fabric.microsoft.com/t5/Service/Get-Unexpected-error-when-creating-semantic-model-...
Solved: Re: Error on creating New Semantic Model - Microsoft Fabric Community

The fix will be deployed soon. I will keep you posted regarding the updates.
Hope this helps. Please let me know if you have any further questions.

[amaaiia]

Hi @Anonymous 

Well, I'm not trying to access an existing model. I'm trying to CREATE new one from an existing lakehouse. That's why I can't understand. The new workspace is empty, I've just created it a few hours ago. I've just created the workspace and then tried to create a NEW SEMANTIC MODEL from a lakehouse hosted in another workspace.

[Anonymous]

Hi @amaaiia 
Thanks for creating a support ticket. We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond back with the more details and we will try to help.
Thanks

[amaaiia]

Not yet. Support team is checking internally.