sql-action does not appear to be working with SQL Server setup on an VM
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- azure, github-actions, sql, typescript
Línea de trabajo
Empieza reproduciendo el despliegue con azure/[email protected], la cadena de conexión mostrada y SQL Server en una máquina virtual de Azure; después, compáralo con los destinos de Azure SQL que funcionan. Comprueba el fallo de autenticación de SqlPackage.exe y el error del firewall de v1.3; se considera terminado cuando se haya identificado el comportamiento compatible con Active Directory Password y el problema se haya solucionado o documentado claramente.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
We are working on migrating SQL Project build and deployment pipelines to GitHub Actions. We are encountering issues with running deployment workflow using the sql-action (using Authentication='Active Directory Password') when deploying to SQL Server on a virtual machine that is in Azure. Please note we are able to successfully deploy to Azure SQL Server and Azure SQL managed instance with same user and authentication.
Only SQL authentication is working fine with SQL Server on VM.
The error I get when I use azure/[email protected]
`-------------------------------------------
Run azure/[email protected]
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\130\SqlPackage.exe" /Action:Publish "/TargetConnectionString:***" /SourceFile:./DeployArtifacts/.database.dacpac /Profile:./DeployArtifacts/.TOKEN.publish.xml
Publishing to database '' on server 'tcp:,1433'.
The dac history table will not be updated.
An unexpected failure occurred: Login failed for user ''.
Unhandled Exception: System.Data.SqlClient.SqlException: Login failed for user ''.
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.Data.Tools.Schema.Sql.Dac.ConnectionManager.<>c__DisplayClass1.b__0()
at Microsoft.Data.Tools.Schema.Common.SqlClient.RetryPolicy.<>c__DisplayClass4.b__3(RetryState retryState)
at Microsoft.Data.Tools.Schema.Common.SqlClient.RetryPolicy.ExecuteAction[R](Func2 func, Nullable1 token)
at Microsoft.Data.Tools.Schema.Common.SqlClient.RetryPolicy.ExecuteAction(Action1 action, Nullable1 token)
at Microsoft.Data.Tools.Schema.Common.SqlClient.RetryPolicy.ExecuteAction(Action action, Nullable1 token)
at Microsoft.Data.Tools.Schema.Sql.Dac.ConnectionManager.Create(String connectionString, Boolean cacheConnections)
at Microsoft.Data.Tools.Schema.Sql.Dac.DacRegistrationManager.DacInstancesManager.GetDacRegistrationData(String connectionString, String databaseName)
at Microsoft.Data.Tools.Schema.Sql.Dac.DacRegistrationManager.StartDeploy()
at Microsoft.SqlServer.Dac.DacServices.InternalDeploy(IPackageSource packageSource, Boolean isDacpac, String targetDatabaseName, DacDeployOptions options, CancellationToken cancellationToken, DacLoggingContext loggingContext)
at Microsoft.SqlServer.Dac.DacServices.Deploy(DacPackage package, String targetDatabaseName, Boolean upgradeExisting, DacDeployOptions options, Nullable1 cancellationToken)
at Microsoft.Data.Tools.Schema.CommandLineTool.DacServiceUtil.<>c__DisplayClass8.b__0(DacServices service)
at Microsoft.Data.Tools.Schema.CommandLineTool.DacServiceUtil.ExecuteDeployOperation(String connectionString, String filePath, MessageWrapper messageWrapper, Boolean sourceIsPackage, Boolean targetIsPackage, Func1 generateScriptFromPackage, Func2 generateScriptFromDatabase)
at Microsoft.Data.Tools.Schema.CommandLineTool.DacServiceUtil.DoDeployAction(DeployArguments parsedArgs, Action1 writeError, Action2 writeMessage, Action1 writeWarning, CancellationToken cancellationToken)
at Microsoft.Data.Tools.Schema.CommandLineTool.Program.DoDeployActions(CommandLineArguments parsedArgs)
at Microsoft.Data.Tools.Schema.CommandLineTool.Program.PerformAction(CommandLineArguments parsedArgs)
at Microsoft.Data.Tools.Schema.CommandLineTool.Program.Run(String[] args)
at Microsoft.Data.Tools.Schema.CommandLineTool.Program.Main(String[] args)
Error: The process 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\130\SqlPackage.exe' failed with exit code 3762504530
-------------------------------------------`
Just for testing purpose I also tried running on azure/[email protected] but got different error
Error: Failed to add firewall rule. Unable to detect client IP Address. Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Login failed for user '<username>'..
Connection string format being used to connect to the sql server on the virtual machine
Server=tcp:<>,1433;Initial Catalog=<>;Persist Security Info=False;User ID=<>;Password=<>;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=True;Authentication='Active Directory Password';
Am I doing anything wrong? Any help is appreciated.
Thanks and Regards
Sreenath
- Lenguaje dominante
- TypeScript
- Estrellas
- 142
- Forks
- 73
- Merge medio
- 3 d 3 min
- PR fusionados (30 d)
- 1
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Azure/sql-action
-
Bump Major Tag VersionAbiertoneed-to-triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
Azure/sql-action#247 ·
-
need-to-triage
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
Azure/sql-action#282 ·
-
Database names with spaces cause firewall detection to fail - sqlcmd argument not quotedPosiblemente ocupada @dzsquared la tomó hace 257 días. Abiertobug
Azure/sql-action#267 · 1 asignado ·
-
need-to-triage
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
Azure/sql-action#262 · 2 comentarios ·
-
need-to-triage
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
Azure/sql-action#261 ·
Todos los issues de Azure/sql-action
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
bug:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
callstackincubator/simlock#350 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
openwatersio/maritime-zones#33 ·
Los mantenedores suelen responder en 1 día
-
Booking email verification fails for plus aliases with impersonation protection enabledPosiblemente ocupada @kankadev la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
calcom/cal.diy#30293 · 1 comentario ·
Los mantenedores suelen responder en 5 días
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
AOSSIE-Org/DebateAI#611 ·
Los mantenedores suelen responder en 3 días