This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 97%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMA%3C/text%3E%3C/svg%3E)
DACPAC Deployment is failed as it says Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql150DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service. Target platform is SQL 2019.
The build agent used is 'windows-2019' which has DacFx version 16.0.5400.1 and the deployment SQL server has been installed with the same version. The database deployment is done through ADO. The database project target platform is updated to SQL Server 2019 using VS 2019.
What could be the issue here?
You are having this error on Azure DevOps. Right?
Hi @Mamatha A Thank you for posting your question on Microsoft Q&A and for using Azure services.
My understanding is that you are getting an error while deploying a DACPAC using Azure Dev Ops (ADO)
Could you please check if you downloaded the latest version of the build Agent? https://learn.microsoft.com/en-us/sql/tools/sqlpackage/sqlpackage-download?view=sql-server-ver15#dacfx
Regards,
Oury
Yes, on the Azure DevOps release pipeline.
You are right, this error occurs while deploying a Dacpac using Azure dev Ops pipeline. I did add a step to display sqlpackage version by following this link in the build pipeline. The build pipeline runs successfully and the version it displays 16.0.5400.1. According to the build agent image details (LINK), the “windows-2019” image contains DacFx version 16.0.5400.1
Hi @Mamatha A Thanks for getting back. You mentioned that you were able to successfully build the pipeline. Are you seeing the issue on the release pipeline? Would be helpful if you can share a screen shot.
Regards,
Oury
Hi @MamathaA-2835Could you please respond to the above asked so we can further assist you.
Regards,
Oury
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 97%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDS%3C/text%3E%3C/svg%3E)
2023-09-21T23:13:53.1412840Z Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql160DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service.
Having same issue, Let me know if you can help.
2023-09-21T23:13:53.1412840Z Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql160DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service.
Getting error with Realse pipeline. Deploying Dacpac in on-premise SQl2022 instance
Could you please create a support ticket so we can further look into this.
Regards,
Oury
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 18%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAD%3C/text%3E%3C/svg%3E)
Hi @Deepak Sharma ,
Above issue is resolved? if resolved pls let me know i am facing the same error
Check if the build agent used is ‘windows-2019’ which has DacFx version 16.0.5400.1 and the deployment SQL server has been installed with the same version, and check if the database project target platform is updated to SQL Server 2019 using VS 2019.
If the steps provided did not help. I would suggest raising a support ticket so we can further investigate.
Regards,
Oury