I have installed oracle express 10 on my localmachine in which all oracle client tools were already installed to connect to a remote oracle server before.After replicating the databses from remote server in the local when I try to connect to the local version or remote version from asp.net it throws an exception telling connection couldnot open.I can use the same connection parameters and connect in SQLdeveloper/toad.When I uninstall oracle express I can connect to remote server again.I am running windows xp 64 bit version.Can someone help me with this?
..installing oracleXE after installing oracle client was the problem.The real issue was in the order of the paths variable
Related
We have oracle oledb connections in SSIS packages that are working well on windows server 2008.
We moved them to windows server 2012 and installed the needed softwares. We installed oracle client (oraoledb driver), moved tnsnames.ora, ldap.ora and sqlnet.ora to %Oracle_Home%\Network\admin path, add %Oracle_Home% and %Oracle_Home%\bin to path variable.
But on server 2012 oracle connections are giving this error ORA-12541: TNS: no listener. Where as on server 2008 same oracle connections are working fine.
Looked so much across internet but found these solutions:
Check tnsnames.ora
Check listener is running
Check path variable contain oracle home, oracle_home\bin
I don't see a problem with tnsnames.ora because same file is present on both window servers. Correct path variables are also set. Listener is also running (since SSIS on server 2008 is connecting). And I am able to ping oracle db server from both machines.
Can anyone suggest anything that we may try.
To put a formal answer in here.
Basic troubleshooting steps with SSIS:
Use the database native tools to check connectivity
In this case for Oracle that is SQLPLUS.EXE
If you have an issue with native tools then it isn't an SSIS issue
Check that you can resolve the host by using PING <hostname>.
If that doesn't work try PING <ip address>
If ping works, check the port with TELNET <host> <port>
If that doesn't work, either the service is not listening or you need to get your network guys to open the port
This goes for any network service
i.e.
SQL Server (default port 1433)
a web server (default port 80 for unencrypted comms)
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
I'm getting the dreaded "A network-related or instance-specific error" error but only when attempting to connect from my local IIS server. IIS and SQL are both installed on the same machine.
SQL Server (EXPRESS) is running and the SQL Server Browser is also running. Client Protocols (Shared Memory, TCP/IP, and Named Pipes) are all enabled. I can connect and run queries via SSMS both locally and remotely using both Named Pipes and TCP using either Windows Authentication (My Account) or a SQL Server login.
Here is the connection string I am using in my web.config
Server=(local)\SQLEXPRESS;Database=MyDbName;User ID=MyUsername;Password=MyPassword"
Server=(local)\SQLEXPRESS;Database=MyDbName;Integrated Security=True;
Any recommendations are appreciated:
Win Server: 2016
IIS: 10.0.14393
SQL Server Express: 14.0.1
Solved: This was due to an additional connection string only used for Code Migration updates.
I have succeeded in hosting my applications locally but when i try to view it through a network outside it fails.
Same goes for my SQL Server, I am able to connect locally.
I have tried to open my port but it keeps failing, Is the port the cause of the problem?
Server Manager is also not found in my IIS
PS. I am using windows 8
Please help, it would benefit my school project alot
You need to open port 1433 for access to SQL Server:
Configure the Windows Firewall to Allow SQL Server Access
Similar question here.
You will also need to enable Named Pipes and TCP/IP in the SQL Server Configuration Manager.
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.