I am trying to deploy test.dacpac file using vsts to azure sql server, Given connection details properly and it is getting connected if I try to connect it from visual studio.
But when it tries to deploy file using vsts, gets error message -
A network-related or instance-specific error occurred while
establishing a connection to SQL Server azure
Not sure why this is happening.
Note: There is no firewall rule applied, it has default settings, though the virtual machine on which VSTS agent is installed is in another Azure AD subscription.
Do I have to look into VPN for this?
Please use the FQDN for database name instead of the IP address. e.g. myAzureSQLDB.windows.database.net.
You need to configure Azure SQL Database firewall. Make sure "Allow access to Azure Services" is turned on. If that does not work, then try adding firewall rule 0.0.0.0 to 255.255.255.255.
Related
I am facing a problem that when i try to configure my TFS it show me the following Error Message
Error
TF255049: A connection cannot be made to the server that is running SQL Server. Verify that you have entered the correct name for the server, including the instance name, that the server you are attempting to connect to is online, and that you have the required permissions to connect. If you are attempting to connect to the remote SQL Server instance, then verify that it is configured to allow remote connections, that TCP/IP protocol is both enabled and configured to use port 1433 (default), and that Windows Firewall does not block this port.
Check whether the SQL version is supported by the TFS version: https://www.visualstudio.com/en-us/docs/setup-admin/requirements#sql-server
Check the permission of the account that you use, and make sure it belongs to SysAdmin Server Role.
As #Daniel mentioned in comment, follow the troubleshooting steps provided in the error message, and check this blog to see whether it is helpful: https://elhajj.wordpress.com/2013/02/25/workaround-error-tf255049-punching-a-hole-through-windows-firewall/
I was running an upgrade from TFS 2018 to Azure DevOps 2020.
After the server restart, the Azure DevOps Server Configuration wizard opened.
I was logged in as the local machine administrator and got this error (TF255049: A connection cannot be made to the server that is running SQL Server...) when trying to connect to my SQL Server machine (to chose the configuration database).
I logged in as Network Administrator, started the wizard again and the SQL connection worked.
To restart the Azure DevOps Configuration Wizard again...
Open the Azure DevOps Administration Console and choose Configure Installed Features to open the Server Configuration Wizard...
I have a SQL Azure database. For some reason, I can work with it when I'm at home, but not when I'm at Starbucks. I can successfully login to it and "manage" it via the web-based tool provided from the Windows Azure Portal. However:
When my web app tries to hit the database, I receive an error that says:
The provider did not return a ProviderManifestToken string.
When I try to hit the database from SQL Management Studio, I receive the following error:
Cannot connect to tcp:[serverName],[number].
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.)
(Microsoft SQL Server, Error: 10060)
I know my IP Address is unblocked, because as mentioned, I can use the web-based tool. I know the database is setup properly, because I can use it from home. However, when I seem to try to work from any local coffee shop, I'm stuck.
Thanks
the Web based Azure Portal doesn't use your local IP address to connect to your databases, it uses the ip address of the server hosting the portal.
since you're getting a new IP from coffee shops, either you add that in the Azure SQL Firewall or you open up your Azure SQL to all IPs.
if that doesn't work, then maybe your local coffee shop has firewall setting blocking port 1433...
Up until last night, my site (hosted by DiscountASP.net) and the SQL Azure database that it connects to were running normally.
For some reason, during the night, the site went down with a named pipe error. Error 40.
Having prefixed the server name with "tcp:" in the connection string, the error is now:
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.)
So, just to be clear, the web.config file did not change at all between the time the website last worked and the item the named pipe error came up.
Now, the username, password and instance name are all correct since the site runs locally against the remote SQl Azure server perfectly.
I've checked the instance name and the SQl Azure access rules, ensuring that the web server's IP address is whitelisted.
Any ideas on whats wrong?
If I understand this right, your local website (on-premise) can connect to SQL Azure, but your website deployed in Azure can't?
Make sure your firewall rules has the "allow other windows azure services to access this server". Checking this option off basically prevents any azure-hosted application/service from connecting to your database.
When I connect to SQL Azure from my code, I get the following error.. I am able to connect to SQL Azure from SQL Server Management Studio successfully.
System.Data.SqlClient.SqlException: 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 - The requested name is valid, but no data of the requested type was found.)
I also tried connecting using sqlCMD and that connects without any issue. Only issue arises is during runtime when I get this exception.
You might also want to check to make sure your firewall allows outbound connections on port 1433.
There can be numerous reasons for this failure, I am listing out the scenarios and the options that needs to be allowed on the server.
If you are connecting an Azure SQL Instance using Sql server management studio while inside you company's network/firewall, first of all you will need to check if your company's firewall rules allow that or not.
On the AZURE SQL Server, make sure your IP address is in the allowed list.
I believe you just need to tick the checkbox "Allow other Windows Azure services to access this server" in Firewall Rules on your SQL Azure account (this will allow connecting to the db server from your deployed Azure application). Hope this helps.
It would be helpful if you post your connection string here. Also a sample app on connecting to sql azure using ado.net: http://msdn.microsoft.com/en-us/library/windowsazure/ee336243.aspx
Makesure you pay attention to the SqlConnectionStringBuilder properties.
If you have your IP added into firewall rules and allowing SQL
connection to Azure Services Enabled. It should work fine!
I'm trying to connect to a remote SQL Server 2005 db from a .NET Windows service running in Vista Home Premium x64. I can access the remote db from a console app with no problem. I can connect to a local db from the Windows service with no problem. I was able to connect from a service from XP with no problem. There's no firewall or anti-virus running. How do I configure this service to be able to connect to the remote db?
I've tried to connect by running the Windows service as a local admin account, LocalSystem, LocalService, and NetworkService.
The connection string:
Data source=SERVER_NAME;Initial Catalog=DB_NAME;Integrated Security=True;
The 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)
MORE INFO:
I have also tried to connect using SQL Server authentication with no success:
Data Source=SERVER_NAME;User ID=USER_ID;Password=PWD;Initial Catalog=DB_NAME
This connection string works from the console app too.
MORE INFO:
I ran Process Monitor for the Windows Service and the console app. The Windows service showed \SERVER_NAME\pipe\sql\query was ACCESS DENIED but the console app showed SUCCESS when reading/writing files to \SERVER_NAME\pipe\sql\query.
Good Lord! Why all the gibberish and complex responses on this site. Create a User Account
Either local or Domain and set the service to use that account. Then go into your SQL Server and Add you new account to the Database and set permissions. Voila!
Oh yeah, dont plague yourself with SQL Authentication. Integrated Security is much easier to maintain and without a password in your web.config your much safer.
1) open a command prompt. Type "ping SERVER_NAME". Does it respond? You may have a DNS or connectivity issue if this doesn't work.
2) "telnet SERVER_NAME 1443". Do you see anything or does it refuse your connection? This will definitively tell you whether or not someone is listening on the other end.
3) Go into SQL Server Management Studio. Right click Properties of your server. Select "Connections" from the left side. Is "Allow Remote Connections" checked?
4) Since you're running using network service/system, you will need to make sure you have a login configured on your server for the machine account DOMAIN\CLIENTSYSTEMNAME$. Note the $ sign. This is your machine account, and this will be the user that SQL Server will see.