I am trying to connect to one of my MS SQL Server databases with the Filemaker Pro ODBC driver. I am using the database service. However, whenever I try to connect to my database it sends either an error that it can't connect to the datasource or an error that the username or password is incorrect. I know the credentials I am using are correct because I can connect to my Jetbrains IDE and to the mssql library in node.js with the same credentials. Does anyone know what the problem could be? My database is running on Azure. Do any setting need to be changed in the driver based on using Azure that could cause the problem?
Related
Hi,
I am trying to connect Azure sql database from Access database . However its giving me the following error.
When I try with the same credential from SSMS its connects perfect however, can't connect through ODBC.
Can anyone had the same experience or anyone has any input to resolve this issue?
Thanks in advance!
You need to install ODBC driver 17 for SQL Server. You need to restart computer after installing the driver or the connection won't work. Create a Machine ODBC DSN using this driver.
Provide now the Azure SQL server name:
Use SQL authentication.
On the next screen specify the database name (catalog).
Make sure you set Encrypt=True
I have a problem on connecting microstrategy to a local database:
I'm unable to resolve this error, though I have tried everything in ODBC origins, and tried various drivers.
The server name is correct (SQLExpress2017)
If anyone knows how to resolve this issue, please help.
How to connect Micro Strategy 10 to SQL Server
We cannot connect the SQL SERVER 2017 through local by making the sql server dynamic access by allowing TCP/IP using(sql configuration manager)
NOTE
1)Within your network your system be accessible making dynamic sql server
After create odbc in Microstrategy server.in creating ODBC password should be your sql server username and password and create database instance in microstrategy.using datawarehouse catalog fetch the table based upon the instance you created
My objective is to use the migration tool in SQL Developer to migrate 2 SQL Server databases to Oracle. I am attempting to connect to a SQL Server database at a remote location using Oracle SQL Developer 4.0.
I have installed jtds.1.3.0.jar per instructions, and get the SQL Server and Sybase tabs in the connection properties window.
I have entered the user, pw, hostname, port, and database name. When I try to Retrieve Database, or connect, I get the error message:
Status : Failure -Test failed: I/O Error: DB server closed connection.
The SQL Server DBA tells me her error logs contain the following error message:
Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library. [CLIENT: (my computer's IP address)] Error: 17835, Severity: 20, State: 1.
When I look at SQL Server documentation about this error message, it talks about certificates and SQL Server Connection Manager. Some relevant information to show that I've covered the basics:
Using the same connection parameters, I am able to connect to the SQL Server database using Toad for SQL Server.
Using the same connection parameters, a DBA set up an Oracle Transparent Gateway, and I can connect to the SQL Server database using the gateway and a database link. (As far as I know, neither of these methods required a certificate to connect.)
Both of these use ODBC; SQL Developer uses jdbc with TCP/IP.
The DBA assures me TCP/IP connection is turned on for the SQL Server databases.
I have gone into the XML file where SQL Developer stores the connection string. It has the form jdbc:jtds:sqlserver://sql-xxx-xxx.mw.nos.xxx.com:1433/my_db, which looks correct. I have tweaked it by adding the instance name, but no difference. The database has a default instance name, anyway, so it shouldn't be necessary.
A co-worker has been able to connect to a local SQL Server database on the same machine where SQL Developer was running (both on his laptop).
As a workaround, I am also pursuing the possibility of installing SQL Server on a local workstation, and copying the databases there for processing, but I don't know if I can get approval. If you know another tool for migrating from SQL Server to Oracle, please also let me know.
Thanks in advance.
I've successfully configured oracle wallet in my machine in windows 7. I also checked by executing the below command
sqlplus /#myoracleDB
and it gets connected to the DB successfully.
I'm trying to execute the SSIS package(DTSX) version 2012 in my machine. In the Data Flow task, I'm using Oracle Provider for OLEDB Connector. I wanted to connect the myoracleDB Database through oracle wallet in the OLEDB connector. I used the below configuration,
Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;OSAuthent=1;
But the Connection is failing with invalid username/password.
Please advise how to resolve this problem.
When I was using "externally identified" logins setup on the Oracle server (basically windows trusted authentication), I used
/ as login
blank password
Inside my SSIS packages and it worked.
I don't know if this is the same as Oracle wallet - I don't think so, but try it.
Using OSAuthent=1; you are trying to establish a Trusted Connection using the current OS authentication, then make sure that you have authenticated the current user
If you have the oracle login credentials try connecting using the following Connectionstring
Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;
Also you can use Microsoft OLE DB Provider for Oracle
Provider=MSDAORA;Data Source=MyOracleDB;Integrated Security = SSPI;
References
Oracle provider for OLEDB connectionstrings
Oracle connectionstrings
Authenticating Database Users with Windows
I'm failing to connect to a SQL server SQLExpress. The connection worked fine a few days ago.
This is how I tried to connect (I'm using Microsoft SQL server management studio):
connection = pyodbc.connect("DSN=sqlServer; UID=myuser;PWD=mypassword")
cursor = connection.cursor()
The error I get:
('HYT00', '[HYT00] [Microsoft][ODBC SQL Server Driver]Login timeout expired (0) (SQLDriverConnect)')
In the ODBC Data Source Administrator, when I test the data source I get:
I got the similar issue.
The problem was actually I was using "SQL Server" as the driver in my ODBC settings in my DSN.
The driver should be "SQL Server Native Client 11.0".
It fixed the issue for me.
Because you are having the same issue in the ODBC Data Source Administrator I would try to focus on that first not on your code.
Here you can find a list with possible problems
Maybe this can help you find out what the problem is.
I also would try to connect with the SQL Server Management Studio.
Maybe it is possible to connect with a different user or via Windows login.
That would mean that your user might not exist anymore (maybe because you renewed tha database or something).
Also I sometimes have the problem that the SQL Server is not started either locally or on the server.
Maybe you could check if the service is started and the database is running.