I am trying to connect Power BI to an Azure SQL Database Server. I am able to connect to the database using SSMS and have added my IP to the firewall settings of the server. However, every time I try to connect Power BI to my SQL Server, I get the following error:
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)"
I am authenticating to the SQL Server using my Microsoft account, but the error still persists.
I am not sure if you have any network related issues. But, based on my test, everything works fine at my side.
Here are my steps:
1. Set Active Directory Admin for your Azure SQL
And my suggestion here is to add a security group as AD Admin. Then you can add uses to that groups, and all the added users will be administrators.
2. Add firewall rule for your Azure SQL
3. Connect to Azure SQL in Power BI
a). Get Data from Azure -> Azure SQL Database
b). Input your server name and database name
c). Sign in with Azure AD credentials and connect
The account should be set as Active Directory Admin for your Azure SQL Server in step 1.
d). Get data
Recently went through this and was able to connect to a SQL Server with AAD through PBI using the ODBC connection:
Get Data -> Other -> ODBC
Data source name dropdown: (None)
Advanced Options: enter the following connection string:
Driver={ODBC Driver 17 for SQL Server};Server=<SERVER NAME>;Database=<DB NAME>;Authentication=AticeDirectoryPassword
You will then be prompted for your username and password.
Related
I've been having troubles in creating new users on the SQL Server. Those were the steps I took:
Connect to the server via Windows authentication
Access Security > Logons > Create Logon
Create a new Logon to use SQL Server authentication
In each database, create new users (same name as logon). Those users were set Owned Schemas and Membership as db_datareader and db_datawriter
Close the connection and connect by the user created
After that process, I get the message:
It is not possible to connect to DESKTOP-QMQIHKL:
A connection with the server was successfully establishes, but during the logon process an error occurred. (provider: Shared Memory Provider, error: 0 - There is not a process in the other extreme of the pipe). (Microsoft SQL Server, Error: 233).
I've tried to overcome this error message by:
Opening SQL Server Configuration Manager and enable the TCP/IP protocol.
Opening Windows Services and executing both, SQL Server Browser and SQL Server (MSSQLSERVER).
None of that have worked. For that reason, I would like your help in solving this problem.
Have you enabled SQL Server authentication mode? By default, SQL Server is configured to use exclusively Windows authentication mode, so it will not accept your SQL Server authentication logins.
For changing the accepted authentication modes, see this article: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode?view=sql-server-ver15
I have recently installed SQL Server 2016 on Amazon EC2 instance so I can start developing various SSIS / SSRS applications.
I have enabled Remote connections, opened port 1433 in the security group and windows firewall, and created a user 'myuser123' who is enabled and and allowed SQL Server and Windows Authentication within the server properties.
I am trying to login using this connection
ec2-1-2-3-4.eu-west-1.compute.amazonaws.com\MSSQLSERVER,1433
SQL Server Authentication
username: myuser123
password: #########
The error message I am getting looks to be a user authentication error.
Cannot connect to ec2-1-2-3-4.eu-west-1.compute.amazonaws.com\MSSQLSERVER,1433
Additional Information
Login failed for user 'myuser123'. (Microsoft SQL Server, Error 18456)
However when I Remote Desktop to the EC2 Instance and try to log in locally using the same username / password I don't have any problem.
Do you have any idea why this may be?
Thanks
M
I have created a SQL Server Express instance on RDS. I have also created a security group and enabled SQL Server port range 1433 to everyone. I have also selected Yes for Publicly Accessible.
When I try to connect from the Management Studio, I do specify server name as endpoint of the instance including port number. I did specify the master username and master password with authentication type as SQL Server authentication.
I do get this error when connecting:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid) (Microsoft SQL Server, Error: 87)
When I try to see the RDS instance log I see below messages.
2016-12-01 22:31:19.65 Logon Login failed for user 'sa'. Reason: Could not find a login matching the name provided. [CLIENT: 123.249.0.134]
SA is not a possible login, it is disabled in RDS e.g. sysadmin does not exist, nor does the SQL Agent.
Use security groups to control what IP addresses or EC2 instances can connect to your databases on a DB instance. When you first create a DB instance, its firewall prevents any database access except through rules specified by an associated security group.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.html
This may be a duplicate question, but i tried all way to connect the SQL Azure database from my local SSMS.
I have created Azure database in cloud and added my system IP in firewall configuration section, As I am on being corporate network and trying to connect azure database from my local ssms then i am getting below error,
"A network-Related or instance-specific error occurred while establishing a connection to sql server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)"
You need to add your IP in Azure as an allowed IP address.
Go to your database in the Azure portal, select configure -> Add to the allowed ip addresses.
Then connect to < Database name >.database.windows.net
I am trying to connect to a remote sql server. I write the IP a.b.c.d into a server name, then I put username test and password test. This account has all Server Roles selected (I also tried with another account which only had public) and the databases I want to allow the user to manage (in User Mapping section) also have public and db owner. I have completed all the steps in here and I got it working on my local network with another computer in LAN having the server set up.
The error I get looks like this:
===================================
Cannot connect to a.b.c.d.
===================================
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
===================================
The user name or password is incorrect
But I can connect with the same credentials in the server itself, so I assume either: something is configured in a wrong way or I have to write the login name in some different fashion.
My both MSSQL programs (in two different computers) were installed with SQL Server 2012 Standard and SQL Server 2014 Express and the one I am trying to connect to is SQL Server 2008 R2 Express. However, at work, I have no problem connecting with version of MSSMS being different from the Server, so I doubt it is the case.
Any ideas what I am missing/doing wrong?