I'm trying to create connection to SQL Server database from InformaticaCloud Administrator menu.
So far getting below error:
The connection test failed because of the following error: [informatica][SQLServer JDBC Driver]The connection to the host COMPUTER, named instance COMPUTER has failed. Error: "Receive timed out". Verify the server and instance names, check that no firewall is blocking UDP traffic to port 1434, and for SQL Server 2005 or later verify that the SQL Server Browser Service is running on the host.
Prerequisites I have now:
1) Firewall is disabled
2) Secure Agent installed and Runtime Environment assosiated with connection is up and running
3) Both host and instance name is Computer (select HOST_NAME(), ##servername)
4) SQL Server Browser is running
Could you please help to resolve described error?
Was managed to find a solution:
1) leave Instance name field blank
2) use SQL Server Authentication instead of Windows one
Related
I have read this thread, however unfortunately couldn't find the solution to my problem. I have an ASP.Net Core project (that's called Rent) and it works without any problem on my local machine. However, once I publish the project to the IIS (still in development mode) I get the below error
fail: Rent.Program[0]An error occured during migration
Microsoft.Data.SqlClient.SqlException (0x80131904): 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: 50 - Local Database Runtime error occurred. Cannot create an automatic instance. See the Windows Application event log for error details.
---> System.ComponentModel.Win32Exception (0x89C50118): Unknown error (0x89c50118)
The connection string is called DefaultConnection and is the environment variable. Can anyone help me please? Can provide any additional information if required.
The first thing you should check is that your SQL Server instance is up and running and that your database is still available. This error means quite literally that it can't establish a connection to SQL Server from the Secret Server application.
And you can also check follow things in your environment:
Is something blocking the connection between your Secret Server server and SQL Server?
The standard SQL port is 1433. Check with your server administrator - is the Windows Firewall in use, blocking this port on your SQL server? Check with your network administrator - is there a firewall at some point in between that has closed off this port? Keep in mind that if you use a custom port for SQL, it need to be specified the Secret Server database connection using a SQLSERVER,port type of format.
On the server hosting your SQL Server database, is the SQL Server
service running?
Open services.msc or SQL Configuration Manager to view the status of your SQL Server service.
I have a local installed SQL Server 2016 (Developer edition) installation on Windows 10 Pro. There is one named instance. I am a developer using MS SQL Management Studio and JetBrains DataGrip.
I just want my connections within my local machine to work with SQL Server over TCPIP using a SQL Server user account..! At the moment this only works using my Windows Authentication mapped to ServerAdmin
Named instance
RAXLENOVOT560\MSSQL2016MAIN
(authentication is mixed mode)
There are 3 issues that maybe linked:
TCP Port number does not appear to take effect within the Sql Server Configuration Manager.
The Sql Server Configuration Manager only shows limited properties on the Client Protocols/TCPIP settings. (please see screen shots)
Sql Server login user account does not connect via TCP due to an error. Login within local machine, local development from DataGrip to SQL Server.
1. TCP Port number
I have set this to 65321. However when I try and connect using this port no connection is made.
When I checked using the following SQL query I see the port number is actually 65514
SELECT DISTINCT
local_tcp_port
FROM sys.dm_exec_connections
WHERE local_tcp_port IS NOT NULL
results
local_tcp_port
--------------
65514
I change the port number in the config tool, restart ALL SQL Server services, reboot and still nothing works. Still listening on port 65514
Note I did not choose 65514, this seems to be a default from SQL Server.
2. The Sql Server Configuration Manager Properties Missing
Note the properties screen is limited only to a few options, there are usually lots more why is is? Perhaps due to running on Windows 10 Pro vs Windows Server?
3. Connection Login failure
Login from the local machine only.
I have opened the firewall for all the relevant SQL Server ports
TCP 1433
TCP 65514 (the forced sql server port)
TCP 65123 (what I would like to use)
UDP 1434 Sql Server Browser
I attempted login via a number of means
Sql Server Management Studio
Udl File
Java connection via DataGrip
Since opening the firewall, all the connections work but only if the hostname is 127.0.0.1, why can't I use the computer name? The connections also work if I use my Windows Login but NOT a SQL Server login
The login fails due to the error shown below from the SQL Server Log (which proves the TCPIP connection is reaching SQL Server).
Login-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission
Date 24/04/2018 11:25:05
Log SQL Server (Current - 24/04/2018 11:20:00)
Source Logon
Message
Login failed for user 'SvrDeveloper'. Reason: Login-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission. [CLIENT: 127.0.0.1]
The Sql Server User has the following permissions and settings (please see screenshot)
Name = SvrDeveloper
Server Roles = public
Securables = RAXLENOVOT560\MSSQL2016MAIN Type=Server
Securables = TSQL Default TCP Type=EndPoint
Connections
Udl Connection
[oledb]
; Everything after this line is an OLE DB initstring
Provider=SQLNCLI11.1;Integrated Security=SSPI;Persist Security Info=True;User ID="SvrAdmin";Password="Password123";Initial Catalog="";Data Source=TCP:127.0.01\MSSQL2016MAIN,65514;Network Library=DBMSSOCN;Initial File Name="";Server SPN=""
Java connection:
jdbc:sqlserver://127.0.0.1:65514;databaseName=CcTools;user=SvrDeveloper; password=Password123
Some additional information:
Version
I've installed tigertoolbox from Microsoft and I'm using SQL Server Performance Dashboard Report daily.
It's very useful and I suggest you to install it if you are not using it yet.
BTW, when I connect to localhost everything works smoothly but when I'm trying to connect to another SQL Server instance on the network I receive the error
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DataSource1'. (rsErrorOpeningConnection)
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)
Access is denied
The answer is very easy: I can easily connect to localhost thanks to my credentials but I need to enter user/password for a remote SQL Server instance.
How can I ask to SSRS to prompt user and password for remote SQL Server instance?
The problem Cannot create a connection to data source ‘DataSource1’. (rsErrorOpeningConnection) is even mentioned in the comments on the official Microsoft page but it's not mentioned how to fix this issue.
Check if you are running the SSRS on the default port of Server. If not, inform the port in the connection.
The answer is very easy: I can easily connect to localhost thanks to
my credentials but I need to enter user/password for a remote SQL
Server instance
That is NOT the answer.
The error tells you that your server was not found, so it cannot be authentication error, the server is not reached so it just cannot authenticate you.
You should check your connection string if it's right. if it's correct, it can be firewall or your server is not configured to accept remote connections.
So for whe first thing post here your connection string, it looks like this:
My picture is for shared DSN, if you use it embedded you can find it in your report properties
I'm trying to set up TeamCity 9 locally to a local SQL Server Instance and getting the following error.
The connection to the host localhost, named instance (localdb)\v11.0 failed. Error: "java.net.SocketTimeoutException:
Receive timed out". Verify the server and instance names and check
that no firewall is blocking UDP traffic to port 1434. For SQL
Server 2005 or later, verify that the SQL Server Browser Service is
running on the host.
SQL exception: The connection to the host localhost, named instance (localdb)\v11.0 failed. Error:
"java.net.SocketTimeoutException: Receive timed out". Verify the
server and instance names and check that no firewall is blocking UDP
traffic to port 1434. For SQL Server 2005 or later, verify that the
SQL Server Browser Service is running on the host.
I've tested the connection via SSMS and the credentials I'm supplying the TC web set up are the same. The login has rights to the table.
Using sqljdbc41.jar
It has to be something simple.
Thanks!
It is difficult to know what might be the issue with your environment but I can tell you what worked for me. The key item was to use the JTDS JDBC driver rather than the Microsoft JDBC driver.
Download the latest driver from http://jtds.sourceforge.net/
Unpack the downloaded zip file into the %TEAMCITY_DATA_PATH%/config folder
If you are using NTLM (i.e. Windows) authentication to connect to your database then specify the following for the database.properties file:
# Database: Microsoft SQL server (via jtds driver)
connectionUrl=jdbc:jtds:sqlserver://localhost:1433/TeamCity
#connectionProperties.user=
#connectionProperties.password=
NOTE: This requires the TeamCity windows service to run under the credentials of the account that is the owner of the database. In addition, the ntlmauth.dll file needs to be copied from the JTDS zip file\x86\SSO folder to the TeamCityHome\bin folder as well.
If you are using SQL authentication to connect to your database then specify the following for the database.properties file:
# Database: Microsoft SQL server (via jtds driver)
connectionUrl=jdbc:jtds:sqlserver://localhost:1433/TeamCity
connectionProperties.user=<SQL Login Name>
connectionProperties.password=<SQL Login Password>
Because the JTDS driver does not have a default port to use, you must
specify a port in the value supplied for the connectionUrl.
If you use named instance you can specify the instance name by
following means:
For example if the instance name is sqlexpress then either add the
instance property into the connection URL, like the following:
connectionUrl=jdbc:jtds:sqlserver://localhost:1433/TeamCity;instance=sqlexpress
Or, specify corresponding property in the database.properties file:
connectionProperties.instance=sqlexpress
See also: http://confluence.jetbrains.com/display/TCD9/Setting+up+an+External+Database
I'm trying to connect from a local SQL Server Management Studio to a SQL Server hosted in a VM on Azure.
I followed all the instructions from
http://www.windowsazure.com/en-us/manage/windows/common-tasks/install-sql-server/ and created the necessary endpoints:
Somehow, I can't connect to the SQL Server, getting this error
Cannot connect to xxx.cloudapp.net.
ADDITIONAL INFORMATION:
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)
The network path was not found
I already tried to temporary disable the windows firewall on the vm - without success. Any suggestions?
I had the same problem, this troubleshot helped me getting close to the solution:
Use SQL Server Management Studio to connect remotely to an SQL Server Express instance hosted on an Azure Virtual Machine
Summing up, what i did, i don't know if all these steps are necessary, so you should test after each one:
1) In SQL Server configuration manager enable Named Pipes in protocols
2) In the VM add a windows firewall inbound rule for sql server port (in my case the default 1433, in yours it seems to be 1435, make sure it's 1435 in sql server configuration)
3) Make Sure you are using a sql server authentication login (not a windows authentication) if you don't have one create it locally in the VM>MSSMS
4) Make Sure the SQL server is configured for mixed authentication (http://www.katieandemil.com/microsoft-sql-server-error-18456-login-failed-for-user)
5) Make sure sql server browser is running
Hope this helps :)