I am unable to connect to Azure SQL and access my database from Report builder.
Getting following error:
I had enabled the access in Azure portal for the above IP mentioned. Still getting the error.
I was able to repro successfully, Make sure you specify the Database Name explicitly and try again.
Related
We were not able add Azure SQL Server as external data source in Dremio. We have disabled the firewall to allow all access (at the Azure SQL Server end) to connect to Azure SQL Server, but it was still throwing an error and it was not able to connect from Dremio.
Please let us know if we will need to configure a firewall on route from the Dremio server end to connect to the Azure SQL Server.
Error output:
> Error : Could not connect to intake-dev,
> check your JDBC connection information and credentials.
Note: We have checked that the credentials passed are accurate, and we were able to connect from SSMS using these.
Unfortunately, Dremio does not support Azure SQL Server as a source.
Check this post on dremio community.
We are trying to run sql files from Jenkins Linux machine using Liquibase to the Microsoft SQL server db and getting the error as:
ERROR: Build step failed with exception java.lang.RuntimeException:
Error getting database connection using driver
com.microsoft.sqlserver.jdbc.SQLServerDriver using url
jdbc:sqlserver://*********.database.windows.net:***;database=*********;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=30;Authentication=ActiveDirectoryIntegrated'
at org.jenkinsci.plugins.liquibase.evaluator.AbstractLiquibaseBuilder.createJdbcConnection(AbstractLiquibaseBuilder.java:236)
at org.jenkinsci.plugins.liquibase.evaluator.AbstractLiquibaseBuilder.createLiquibase(AbstractLiquibaseBuilder.java:164)
at org.jenkinsci.plugins.liquibase.evaluator.AbstractLiquibaseBuilder.perform(AbstractLiquibaseBuilder.java:129)at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)at hudson.model.Build$BuildExecution.build(Build.java:205)at hudson.model.Build$BuildExecution.doRun(Build.java:162)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1720)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:404)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: **Azure
Active Directory is only supported on Windows operating
systems.**at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1289)at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:773)
We have tried connecting directly with SQL server authentication and it was successful but while using Azure service principal credential we are getting this error. How do we use Azure SPN to work with Liquibase?
Are you sure you want to connect using active directory integrated to SQL Azure? You should try to connect using the admin server login of SQL Azure or using a login created on SQL Azure. If that is the case, please look how to create the connection string on the samples contained on below article.
https://learn.microsoft.com/en-us/azure/sql-database/sql-database-connect-query-java
Hope this helps.
Regards,
Alberto Morillo
I am new to Talend application, while I am trying to connect to SQL Server database, I'm getting the error shown below. I googled it for resolve this issue few people were commenting as need to be start the SQL Server services in services.msc as they suggested I have enabled the services and but facing same issue so far.
Please kindly help me on this issue and find the attached screen shot which are facing an issue.
Services error of SQL error 2:
Talend error:
There is two option to connect to SQL Server,
1) Mix Mode
2) Window Authentication
Use Microsoft SQL Management Studio and try connect into the database.
I'm facing the issue while creating a azure database in the local machine by sql server 2012 ,
this is my error:
TITLE: Connect to Server
Cannot connect to tcp:ServerName.database.windows.net.
ADDITIONAL INFORMATION:
Login failed for user 'UserName'.
This session has been assigned a tracing ID of '041a1130-65a5-4ad6-91c0-02ff3b4fbca5'. Provide this tracing ID to customer support when you need assistance. (Microsoft SQL Server, Error: 18456)
The issue is occurring might be due to following the following, I have specified how to overcome against each issue:
Check if your IP is added in the firewall, if not refer to http://msdn.microsoft.com/en-us/library/azure/jj553530.aspx
Check if you have configured the wrong IP in Azure Firewall. Try opening SQL Azure Management Studio online http://msdn.microsoft.com/en-us/library/azure/ee621784.aspx#WinAzMgtPort where it asks you to add the IP in firewall.
If above is not working then check if the user credentials is correct, if you forgot the credentials then resetting it might help.
Good Afternoon,
I'm having difficulty running a report with a data source saved on the Report Server using credentials for a user I created on SQL Server named 'ReportUser'. Attempting to resolve this I've mapped the user to the 'ReportServer' database with the db_owner role as well as setting the default database to the 'ReportServer'. However, each time I attempt to run the report I receive the error message:
Cannot create a connection to data source 'Test'. Login failed for user 'ReportUser'.
I'm running SQL Server 2008 from my local machine and am able to successfully run the reports when I setup the datasource using Windows Authentication. Any idea on what could be causing the issues when attempting to use the SQL Authentication with the 'ReportUser'
Thank you very much for your help!
Thank you for your reply.
I believe I found the cause of my issue. Since this was a local install for testing purposes I just set up the instance of SQL Server with Windows Authentication. However, I made the mistake of not setting up the server for both Windows and SQL Authentication. The following link helped me resolve this.
http://forums.asp.net/t/1784261.aspx/1?Could+not+connect+to+database+login+failed+for+user+sa
After changing this setting and restarting the SQL Server everything appears to be running properly now.