I am trying to set up a user DSN on Windows 2012 server. Oracle Client, both 32 and 64 bit are installed as well as ODBC. They are installed on C:\Oracle\product\11.2.0\client_1 and C:\Oracle\product\11.2.0\client_2 respectively. I used ODBC Data Source Administrator (32 bit) to set up the DSN and used information as it exists in tnsname.ora file. However, when I test the connection I keep getting:
"Unable to connect
SQLState=08004
[Oracle][ODBC][Ora]ORA-12154: could not resolve the connect identifier specified"
I searched and they all point to an issue with tnsnames.ora file but all the info I entered when creating DSN is correct, Network Services and IIS_USRS have access to the folder containing the file, I put the service name in quotes as some suggested but just can't shake off the error.
Any ideas on what else I can check?
Related
I have set up a webserver (OS Raspbian, Apache, MariaDB) and now I want to read the database into Qlik Sense (on my desktop PC).
If I want to create a new ODBC connection in Windows, I get the following error message:
"[ma-3.1.4] Can't connect to MySQL server on 'localhost' (10061)"
I am using the "MariaDB ODBC 3.1 Driver". The specified user has all rights.
Do you have any idea where the error is? I am doing this for the first time. Please let me know if you are missing crucial information.
Greetings
Can anyone help me with this?
I have to connect the oracle data source in MS access which has already connected with some HANA server. But now i want to connect it to oracle.
I have done the odbc connection in System DSN from Administrator tools. Connection successful. But, still i cannot see that DSN in System DSN.
Tried the following steps but still not working
1. Modified default value as "value not set" in regedit.
2. created System DSN through this "C:\windows\SysWOW64"
TIA
I'm trying to setup a ODBC connection from a Windows XP/Pro (32bit) client to a MySQL database running on a CentOS 6.3 64bit server.
Both systems are on the same subnet.
I have Samba installed and working on the CentOS server.
I can map the server directory that contains the database tables on the XP system.
The DB server is fully updated on all packages.
I can login to the server with myid:mypw via ssh, a standard user. Same user can make SELECTS from the database.
Can not ssh to root on CentOS server, root is excluded in the ssh config.
When I try to run the ODBC Data Source Administrator on the XP client, on the Create a New
Data Source to SQL Server screen, I select using a login ID entered by the user. I'm
entering the same ID:pw I use to ssh into the server. At that point I get an error,
SQLState = '08001';
SQL Server error: 17;
SQL Server does not exist or access denied"
The Server name I'm entering for "Which SQL Server do you want to connect to?", I've entered the host name of the CentOS that is defined in the XP's /etc/host file. It does appear in the drop down list for that question.
I have installed unixODBC*, mysql-connector-odbc & libtool* packages via yum.
On the server, odbc -q -d returns: [MySQL]
odbcinst.ini includes lines for Driver | Setup | Driver64 | Setup64. The 64 versions do point to /usr/lib64.....
odbc.ini includes: [MyDSN} & Driver = MySQL ODBC 5.1 Driver
Any idea what I've missed so far? Am I running into 32/64 bit system issues? And if so how do I solve this, I will have both 32 & 64 bit users most of them on Windows 7/Pro 64 bit, a few stuck on XP/Pro 32 bit.
I'm a bit lost in this task, so some detailed instructions would be great.
Thanks in advance..
Assuming you have not made a mistake and you really want to access a MySQL database on a remote Centos based system from Windows using ODBC you'll need to install the MySQL ODBC Driver on your Windows machine. You cannot use the MS SQL Server driver to access MySQL. Once you've done that you create a MySQL ODBC data source (although you can use DSNless connections) and not a SQL Server DSN.
2 and 3 are irrelevant as the MySQL ODBC driver is capable of talking directly to your MySQL Database server over the network assuming your server is set up to listen for external connections.
5 is also irrelevant as you'll need a MySQL database username and password and you database needs to allow connections from your windows machine.
(9-12) You also do not need to install unixODBC of the MySQL connector on your Centos box unless you want to access that same MySQL database with an application running on Centos that uses ODBC. 10 just tells you you've got an entry in your odbcinst.ini file for the MySQL ODBC driver which you don't need. 11 is the same info. 12 is a MySQL ODBC DSN which you also don't need.
In one of the Lotus Notes application which requires connection with external SQL DB, we have one user who is getting error message prompt because ODBC driver is not able to connect.
I did following checks:
1. User had permissions to EDIT registry HKLM-Software-ODBC
2. User is able to access the db server (i pinged server IP from user's machine)
3. Made sure that user had admin acces to computer.
This is how code works. The code first runs a VBscript which sets registry variables, then uses LotusScript with NSLXODBC to connect to the DB (ConnectTo method).
The only difference I found between users not having issue and those reporting issue is that USER REPORTING ISSUE had new laptop and it had windows 7 OS.
Lotus Notes Version: 6.5
The problem is likely in the ODBC setup then. The registry changes are supposed to set up the ODBC connection but I'd bet the same code doesn't work for Windows 7. Try manually creating the ODBC connection from that user's laptop.
My java webapp is working fine in my windows XP 64bit with System DSN, by deploying manually in tomcat.
When i am running my webapp in Tomcat on windows server 2008 64bit. I am using a System DSN, because with user DSN it's not detecting the datasource. In this scenario it is throwing me an error as follows:
java.sql.SQLException: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
So far I have tried:
I compared SQL server and DSN registry values, and they are same.
I deployed on other XP machine, it's working fine but not on Windows Server 2008
Thank you in advance.
When trying to run query against System ODBC DSN (MS Access .mdb file) from an app deployed to Jboss 4.x, I get same error: "SQL state [S1090]; error code [0]; [Microsoft][ODBC Driver Manager] Invalid string or buffer length" in Windows Server R2.
I reproduced same error on 2 different Windows Server R2 machines. On Windows Server Standard (i guess R1) and Windows 7 Professional x64 the problem is not reproducible.
Further more, on same Windows Server R2 when trying to connect directly (from a standalone app), i don't get this problem.
If the application wouldn't connect/detect data source, you'd get an error saying that there is no such DSN name or it's not found.
The same error message is thrown when trying to send an empty query to ODBC Data Source (registered Data Source Name - DSN). So i guess the ODBC gets an empty query which tries to execute against the DS and the result is: Invalid string or buffer length.
Since i can read the .mdb file registered as a ODBC DS with given DSN, and i don't get this error when querying it from the standalone app, i'm going to make a standalone app that will read the .mdb file through ODBC and write it's content to a .csv file, which Jboss apps will read.
If anyone finds a better solution, please let me know.