Removing SQL Server Management Studio client, on a running environment with 5 proper configured 32-bits DSN on the ODBC (admin tool), prevented my configured DSN to properly work: they were un.configurable (no chance to click the configure button) and the sub-system working with them was of course running anymore.
Re-installing SSMS client keep the DSN working once again.
I did not find any explanation on this on the web: does somebody knows the why?
Related
I've installed Firebird 3.0.3 Classic Server 32-bit on a newly setup Windows Server 2016 (32-bit because I have to use a legacy UDF dll that's only available in 32-bit). Except for the 64-bit ODBC connection, all connections work fine from client machines (32-bit ODBC connection, FlameRobin). But when I try to access the database through the 64-bit ODBC DSN, I get the error "your username and password are not defined".
My client machine in this case is a Windows Server 2012 R2. I've done the following steps:
install the 32-bit Firebird Client libraries (version 3.0.3)
install the 64-bit Firebird Client libraries (version 3.0.3)
install the 32-bit ODBC driver (version 2.0.5.156)
install the 64-bit ODBC driver (version 2.0.5.156)
open the 32-bit Windows ODBC administration console and create the DSN - connection test OK
Screenshot: https://postimg.cc/WDrJQryH
open the 64-bit Windows ODBC administration console and create the DSN - connection error!
Screenshot: https://postimg.cc/5XDC7psz
I'm sure I haven't missspelled the password. What could I have missed? Thanks a lot!
In general problems like this (when you have two almost identical applications and only one of them working) are often diagnosed by comparing their behavior and looking for differences, then trying to change computer or application setting to eliminate suspicious and unneeded differences unless both program work. A useful tool for it would be for example SysInternals Process Monitor, which can be set to record files I/O tracks (also registry and other things), which can give a valuable insight into program implementation and its failure. In this particular case when u press "test connection" buttons in ODBC32 and ODBC64 windows the track of files and registry accesses would probably highlight where things start go wrong for 64-bits application in contrast with the 32-bits one.
If to skip systematic diagnostic for a while and try mere guessing, then Mark suggests that the 64-bit app fails to locate the proper fbclient.dll (where proper might mean many things: FB version, 32/64-bitness, textual configuration files and what not).
Seeing your ODBC setup windows have an explicit fields "Client" with "Browse" button I make a guesstimation that ODBC tries to auto-locate the client library and for some reason locates some unlucky one.
Then I suggest you to try to set that "Client" field to precisely the fbclient.dll file that the Firebird engine itself uses, and if you did not changed default installation settings it would be something like something like "c:\Program Files\Firebird\Firebird_3_0\bin\fbclient.dll"
I need to do Data Migration task from MySQL database to SQL Server Database 2012. I have created SSIS package for doing it. I have installed ODBC drivers of version 5.2.7 for both 32 bit and 64 bit. I have created DSN for connecting with MySQL database. This SSIS package is running successfully using Visual Studio.I have deployed SSIS package to Integration Service Catalogs and created SQL Server Agent job to run this package.But I am getting following error while running SQL Server Agent job:
"Acquireconnection method call to the connection manager failed with error code 0xc0014009"
"odbc source failed validation and returned error code 0x80004005."
I am connecting MySQL database and SQL Server using VM. I have tried to run this SSIS package with 32 bit runtime marked and changed Run64BitRuntime property to False. But still I am facing the same error.
Please note that, there is no odbc driver for MySQL is installed on the Server where SQL Server is residing but on the VM, both 32bit and 64 bit MySQL ODBC drivers are installed.
Is this the cause of mentioned error?
Please check whether you are using User DSN or system DSN in the odbc driver configuration. When deploying your packages user DSN may not work. Try creating a System DSN. That should work. I have faced the same issue. Please check my notes.
https://jyothishbhaskaran.wordpress.com/2017/09/07/how-to-create-and-use-data-source-for-mysql-using-odbc-driver/
Within the SQLAgent Job's TASK settings, I had to go into the "Advanced" tab and set it to run with the 32-bit system.
I'm trying to setup a local version of a website that's online and working. The site is built with Umbraco V6, and is using an SQL Server database. My test server is a fresh install of Server Standard 2012 and SQL Server 2012.
My process has been to:
Install the O/S and SQL Server
Setup a test Umbraco site in IIS, installing from scratch into a fresh database
Once 2. is working, download the source code from the live server and install in a new site in IIS
Download a copy of the live SQL Server database and restore it into the server
Add a new user account into SQL Server, granting permissions onto the SQL database i've restored
When I try to access the website through a browser, I get an error. This shows up in IIS as:
Event Code 3005. An unhandled exception has occurred. No connection could be made because the target machine actively refused it
I've disabled the Windows Firewall and have checked I can telnet into the server on port 1433. I know the Web.config is using the right credentials, as I can change it to a different user account and see a different error.
Can anyone point me in the right direction to resolve the error?
You should go through the steps listed over here:
http://blogs.msdn.com/b/sql_protocols/archive/2007/07/19/tcp-provider-no-connection-could-be-made-because-the-target-machine-actively-refused-it.aspx
I suspect that your connection string is pointing to the wrong server instance or that the TCP protocol is not configured correctly.
Tip: You can always copy and paste the settings from your connectionstring into the Connect Object Explorer of SQL Management Studio to verify that they work.
I have setup a Wallboard for our Cisco Call Center connecting to the ccx database and everything works fine when I run it through Visual Studio however when I publish it out to IIS and try to view the page I am getting an:
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver
when it goes to access the dataSource. In my searches all I can find is that I need to add the driver to my connections string which I have attempted to do but still no luck. What am missing?
connectionString="Dsn=Wallboard-1;driver={INFORMIX 3.50 32 BIT};server=uccx1_uccx;host=xxxx;service=1504;protocol=onsoctcp;database=db_cra;uid=xxx;pwd=xxxx"
Got it! When running on a 64-bit environment you need to go into the app pool your site is running on through IIS an enable 32-Bit Applications so it can access the SysWOW64 folder. It couldn't find the driver because it couldn't find the odbc dsn.
I have a freshly built 64-bit Windows Server 2008 R2 box that I have installed 64-bit Coldfusion 9 Standard on. I've upgraded and hotfixed it up to the most current version of CF. I also had 64-bit Oracle 11g (11.1.0.7.0) Client installed on the box. I've created a System DSN using the 64-bit ODBC Data Source Administrator in Windows and can successfully test the connection of the data source.
All of these installations went smoothly, however, when I went to add a datasource in the Coldfusion Administrator I receive the error:
Connection verification failed for data source: myDatabaseName
java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application
The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application
I am having a hard time understanding exactly where this architecture mismatch is coming from since the box is entirely 64-bit. I see while looking at all the processes that are running, some related CF processes are running in 32-bit (Verity related processes, SOLR and CFDotNetSVC). I am not sure if those could cause this issue but I am at a loss to explain were this mismatch would come from otherwise.
Anyone have any ideas?
Using Dan's advice I grabbed a JDBC Driver from Oracle here:
http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-111060-084321.html
I then moved the JAR (ojdbc6.jar in my case) and added it to my Coldfusion Class Path.
Determining the correct settings for using the datasource to Coldfusion was slightly harder but here are the settings I ended up going with:
JDBC URL: jdbc:oracle:thin:#//dbsrv.mydomain.com:1521/myDB.world
Driver Class: oracle.jdbc.driver.OracleDriver
Driver Name: Oracle Thin Driver
Then the username and password for the DB.
Sure enough it worked like a charm.
Dan, I want to give you a check mark because you definitely put me in the right direction, but I can only mark one correct.
I believe you need to either step down to the 32-bit drivers, or use native JDBC drivers to connect to Oracle successfully. My suggestion would be to go the JDBC route, and connect directly through a native Oracle JDBC driver by using the "other" selection on the Datasource screen. You'll get better performance that way, and have more control over your connection via ColdFusion.
Connecting to Oracle information in ColdFusion Livedocs.
i found an alternate way to do this
install the ODBC drivers for 64bit and 32bit (in that order) on your win2008 64bit OS
thereafter create the DSNs on both the System32 folder and SysWow64 folder by running the odbc32ad32.exe
ensure your tnsnames are setup fine in the respective network/admin folder (if you use tnsnames to maintain your sids)
now on the CF admin you creaet a new ODBC source with aODBC Socket and name. the next page should show you a drop down of all DSNs that exists in the 64bit DSN setup. When you go and test it in CF, it will strangely use the config of the 32bit DSN setup for validationb
voila....your connections should work. No worries of those architectural failures etc
We needed to setup 64 bit ODBC connections for a ColdFusion 11 server to query against 2012 SQL Server instance on Windows 2008 R2 Server. The ODBC connections would show up but would never work. We received so many various messages when verifying such as "needing SSL connections to work" and also timeout messages as it was having problems logging into SQL Server.
I stumbled across this post and we decided to follow setting up 64bit ODBC connections and then effectively overwriting them--preserving the name using the 32bit ODBC. Thank you again fellow developers, especially Souzam! My instructions are below:
For Windows 2008R2 Server you must disguise 64bit ODBC socket configurations for 32 bit in order for them to appear in CF Admin as datasources (obvious bug in CF 11):
Creating 64bit ODBC connections via 2008 R2 ODBC application, follow a naming convention that will allow you to recall in 32 bit configuration.
Configure ODBC 32bit connection in SYSWOW64 (C:\Windows\SysWOW64) using the odbcad32.exe using the previous 64bit names in Step #1.
Create data sources in CF Admin as these should appear in a dropdown when creating ODBC Socket Type connections.