talend connection with sql server 2008 R2 issues - sql-server

I've been trying to connect with SQL Server 2008 but I couldn't, and I'm getting the error below. It says that : I have to check if the TCP port is blocked with a firewall... well, no it's not !
what should I do ???
Echec de la connexion Vous devez modifier les paramètres de la base de données.
java.lang.RuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException: Échec de la connexion TCP/IP à l'hôte (local), port 1433. Erreur : « null. Vérifiez les propriétés de connexion. Assurez-vous qu'une instance de SQL Server est en cours d'exécution sur l'hôte et accepte les connexions TCP/IP au port. Vérifiez que les connexions TCP au port ne sont pas bloquées par un pare-feu. ».
at org.talend.core.model.metadata.builder.database.JDBCDriverLoader.getConnection(JDBCDriverLoader.java:195)
at org.talend.core.model.metadata.builder.database.ExtractMetaDataUtils.connect(ExtractMetaDataUtils.java:1092)
at org.talend.core.model.metadata.builder.database.ExtractMetaDataFromDataBase.testConnection(ExtractMetaDataFromDataBase.java:315)
at org.talend.metadata.managment.repository.ManagerConnection.check(ManagerConnection.java:289)
at org.talend.repository.ui.wizards.metadata.connection.database.DatabaseForm$62.runWithCancel(DatabaseForm.java:3953)
at org.talend.repository.ui.wizards.metadata.connection.database.DatabaseForm$62.runWithCancel(DatabaseForm.java:1)
at org.talend.repository.ui.dialog.AProgressMonitorDialogWithCancel$1.runnableWithCancel(AProgressMonitorDialogWithCancel.java:77)
at org.talend.repository.ui.dialog.AProgressMonitorDialogWithCancel$ARunnableWithProgressCancel$1.call(AProgressMonitorDialogWithCancel.java:161)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Échec de la connexion TCP/IP à l'hôte (local), port 1433. Erreur : « null. Vérifiez les propriétés de connexion. Assurez-vous qu'une instance de SQL Server est en cours d'exécution sur l'hôte et accepte les connexions TCP/IP au port. Vérifiez que les connexions TCP au port ne sont pas bloquées par un pare-feu. ».
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExceptionToSQLServerException(SQLServerException.java:241)
at com.microsoft.sqlserver.jdbc.SocketFinder.findSocket(IOBuffer.java:2243)
at com.microsoft.sqlserver.jdbc.TDSChannel.open(IOBuffer.java:491)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1309)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:827)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1012)
at org.talend.core.model.metadata.builder.database.DriverShim.connect(DriverShim.java:41)
at org.talend.core.model.metadata.builder.database.JDBCDriverLoader.getConnection(JDBCDriverLoader.java:186)
... 9 more

problem resolved ,
Talend and SQL server are in the same machine so...
how I did it: on Sql server
1 - server type : database engine
2- server name : 127.0.0.1
3- Authentication : Sql Server authentication
4- login : sa
5- password : ***** (any password you want )
then I went to Talend:
I did put the same specifications ( specially the pass and login name)

The connection may not work even if firewall is allowing the port traffic but the SQL server itself is not enabled for TCP/IP protocol.
Are able to connect to SQL server using other client tools using TCP/IP protocol? use SQL server configuration Manager to "Enable" the TCP/IP access.

Related

SQL Server jdbc driver not connect remote server

I'm trying to connect to a SQL Server whose database installation was done using an instance. When I try to connect to the server using the microsoft driver (com.microsoft.sqlserver.jdbc.SQLServerDriver), it returns an error stating that it could not connect. Using the same driver but connecting to a local database, it connects successfully.
The error is not in the SQL Server TCP/IP configuration, because if I make the connection using the "net.sourceforge.jtds.jdbc.Driver" driver, the application connects to the database.
But I can't use the jtds driver, because I'm using JetBrains / Exposed and it requires the use of the microsoft driver. So I need to make it work with "com.microsoft.sqlserver.jdbc.SQLServerDriver"
URL when I try to connect on SQL Server
jdbc:sqlserver://SERVER1:1433;database=db_test;instanceName=SQL2016;loginTimeout=5;
Error message
org.jetbrains.exposed.exceptions.ExposedSQLException: com.microsoft.sqlserver.jdbc.SQLServerException: Falha na conexão TCP/IP com o host ITALIA, porta 1433. Erro: "connect timed out. Verifique as propriedades da conexão. Verifique se uma instância do SQL Server está sendo executada no host e se está aceitando conexões TCP/IP na porta. Verifique se as conexões TCP na porta não foram bloqueadas por um firewall.".
SQL: [SELECT 1 AS Test]
at org.jetbrains.exposed.sql.statements.Statement.executeIn$exposed(Statement.kt:48)
at org.jetbrains.exposed.sql.Transaction.exec(Transaction.kt:128)
URL when I connect a local server successfully
jdbc:sqlserver://localhost:1433;database=db_test;loginTimeout=20;
URL when I connect successfully using jtds driver
jdbc:jtds:sqlserver://SERVER1:1433/db_test;instance=SQL2016;loginTimeout=30

Error OData Source SQL Server 2016

I'm using SQL Server 2016 with SharePoint 2013. I'm trying to access to SharePoint List.
I use the OData Source in my Package. The connection works succefully and I can preview (with the Preview button) data from the list.
But, when I try to execute it got an error :
Error: La connexion « Connexion » est introuvable. Vérifiez que le gestionnaire de connexions renferme une connexion de ce nom.
In English :
The connection "connexion" is not found. Check if the connections managers has a connection with this name.
I have no connection named "connexion" in my package.
Do you have any ideas on this error please ?

Can't use OData with SQL Server 2016 (DTExec 13)

I've build a simple package that extract data from an OData source.
It work with DTExec 12 (SQL Server 2014) but when I deploy to an SQL Server 2016 (DTExec 13) I got a weird error in french :
La connexion « Connexion » est introuvable. Vérifier que le gestionnaire de connexions renferme une connexion de ce nom.
Lousy translate in English it mean :
The connection "connexion" is not found. Check if the connections managers has a connection with this name.
I have no connection named connexion in my package.
Do you have any ideas how I could investigate this error ? How can I look at the available connections in the connection managers ?
I feel like there is no OData connector installed for SQL Server 2016 but there is an old one that was installed with SQL Server 2014 because DTExec 12 work on the same server with the same package.

Execute a job in SQL Server Agent : login from an untrusted domain

I have an issue with the execution of an SSIS Package within the SQL Server Agent.
Context :
I deployed a package into the Integrated Services Catalog : http://i.stack.imgur.com/m9Y9c.png I have not difficult to execute this package manually.
Problem :
When I try to execute this package within a job into the SQL Server Agent, I have an error : "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication."
Exécuté en tant qu'utilisateur : NT Service\SQLSERVERAGENT. Utilitaire d'exécution de package Microsoft (R) SQL Server Version 11.0.5058.0 for 64-bit
Échec de l'exécution du package serveur IS en raison de l'erreur 0x80131904. Serveur : OPP41****** Chemin du package : \SSISDB\automates\automate_PIT_pilotage\recuperation_cmd_a_traiter.dtsx
ID de référence environnementale : NULL. Description : Échec de la connexion. La connexion provient d'un domaine non approuvé et ne peut pas être utilisée avec l'authentification Windows. Source : .Net SqlClient Data Provider
The owner of the job is my AD account.
This is how the step is configured : http://i.stack.imgur.com/QrJf9.png
The SQL Server Agent service is running through the "NT Service\SQLSERVERAGENT" account.
Thank you very much by advance, I'm going crazy !
Create credentials: Security -> Credentials
Create a proxy account: SQL Server Agent -> Proxies -> SSIS Package Execution
Set SSIS package to run as proxy account.
Take a look at article.
I had found that my Job was executing against a DNS name and not the SQL Server Name. So check your SQL server name : select ##servername and make sure you use this name in referring to the SQL server where the catalog is located and not some or other DNS name. I have found that it will also succeed using the DNS name to call the packaged from a different SQL server, but if the job runs on the local SQL server calling a package on the same SQL server then the server name must refer to the value in ##Servername.

asp.net miscelenius error provider: Named Pipes Provider, error: 40

When starting the application, everything goes well and a query is done to the server with no problems.
Once I click on a link that requires another connection to the Sql Server 2008 express R2, I get an error :
Une erreur liée au réseau ou spécifique à l'instance s'est produite lors de l'établissement d'une connexion à SQL Server. Le serveur est introuvable ou n'est pas accessible. Vérifiez que le nom de l'instance est correct et que SQL Server est configuré pour autoriser les connexions distantes. (provider: Named Pipes Provider, error: 40 - Impossible d'ouvrir une connexion à SQL Server)
The problem does not happens on the server : www.jbusinesses.com
Any one can help ?
I tried almost everything and everything seems to be ok since the first cinnection seems to be good, its only on a second connection the problem shows itself...
Thank you !
This is a common error when you can't reach your sql database server.
The the server name and instance in the second connection string.
Test if you can connect to that server from SqlServer management studio.
Also check if a firewall is blocking connections to that particular sql server.

Resources