Forum Discussion
Debugging Warehouse deployment errors
Hi All,
what is the best way to debug warehouse deployment errors during deployment via pipelines.
I keep getting "Import failure: DmsImportDatabaseException" during deployment and I have no clue whats causing the issue.
I have checked and can confirm that none of the possible reasons flagged on the below issue apply in my case -
At the very least Microsoft should provide some avenues to debug the deployment issues or suggest some ways to do it no matter how cumbersome it may be.
Any suggestions would be greatly appreciated. It is worrisome to go live with the inability to debug deployment errors without raising with Microsoft support.
Cheers,
AK
Hi Yang,
I have not managed to raise a support ticket for the overall issue of "lack of avenues to debug pipeline deployment errors", but I have now found that any procs with CTAS statements in them need to be dropped in the target before deployment. I am using CTAS statements to fill the gap due to lack of temp tables in fabric. So , we need to add this to the list of checks prior to triggering a pipeline deployment.
Cheers,
Amit
12 Replies
Hi Amit_K,
I run into this issue once when the name of a table or view (please check the views too) was not correct. In my case, there was a dot in the name of the view. You could also check for other strange characters in the name.
The API of the deployment pipelines does give some information about an error that has occured, but I don't know if that gives more information than the "Import failure: DmsImportDatabaseException" message you already got. You could try it to be sure: https://learn.microsoft.com/en-us/rest/api/power-bi/pipelines/get-pipeline-operation#deploymenterrorThanks FabianSchut . I dont think that is the issue here. The reason being the fact when I deleted the target warehouse and redeployed, it deployed fine. I could do that now as we are still in development phase and a complete no go when we go live. I will check out the link that you have posted and see if it provides some extra details on the error.
Cheers,
AK
You can check this Amit. I hope it helps.
Find all deployment related issues with their creative solutions here. I tested and implemented all of them. Hope it helps.
Hi Amit_K ,
Thanks for the reply from FabianSchut .
Here are some of my suggestions:
Ensure that there are no special characters or reserved words in table or column names.
Avoid using special characters such as hyphens in schema names.
If the table creation script is very large (more than 4000 characters), try breaking it up.
Here's a user with a similar problem to yours that may help you:
Solved: Anyone else unable to deploy a data warehouse with... - Page 3 - Microsoft Fabric Community
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!Hi Anonymous , I did go through the list of potential issues in the raised in the link that flagged but none of them apply in my case. I just tried to use the API link mentioned here (https://learn.microsoft.com/en-us/rest/api/power-bi/pipelines/get-pipeline-operation#deploymenterror) to check if it provides a little bit more detail . I see this :
"error": {"errorCode": "CopyOverwriteResult.GenericError","errorDetails": "Import failure: DmsImportDatabaseException"}Now , what does this errorcode indicate. It would be very helpful if microsoft can provide some documentation around these error codes at the very least, not that we have an API which seems to provide a tiny little bit more information on the deployment failuresHi Amit_K ,
Unfortunately, there is no detailed documentation specific to this error code.
You can create a support ticket for free, providing them with the error code and any associated logs will help speed up the troubleshooting process and a dedicated Microsoft engineer will resolve the issue for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.
The link of Power BI Support: https://powerbi.microsoft.com/en-us/support/
For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Fabric Community
Thank you for your understanding.
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Hi Amit_K ,
Is my follow-up just to ask if the problem has been solved?
If so, can you accept the correct answer as a solution or share your solution to help other members find it faster?
Thank you very much for your cooperation!
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!Hi Yang,
I have not managed to raise a support ticket for the overall issue of "lack of avenues to debug pipeline deployment errors", but I have now found that any procs with CTAS statements in them need to be dropped in the target before deployment. I am using CTAS statements to fill the gap due to lack of temp tables in fabric. So , we need to add this to the list of checks prior to triggering a pipeline deployment.
Cheers,
Amit
Hi Amit_Kar ,
It looks like you have found a solution. Could you please mark this helpful post as “Answered”?
This will help others in the community to easily find a solution if they are experiencing the same problem as you.
Thank you for your cooperation!
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Find the solution here guys.
Find all deployment related issues with their creative solutions here. I tested and implemented all of them. Hope it helps.
