Another team in my company commissioned a new server and installed Netezza on it, along with a bunch of internal programs. All of their programs that connect to Netezza are now giving this error:
A connection error has occurred: Invalid packet length
Attempting to connect to the database using a GUI such as DbVisualizer or RazorSQL gives the same error. Connecting to the "old" server still works fine. One of the differences between the two boxes is the Java version, 1.5 on the old one and 1.7 on the new one... not sure if that is relevant. (I'm not a Netezza expert, not really a Netezza user either!)
Any ideas?
I was under the impression from the start that both NZ1 and NZ2 were running the same Netezza version. Apparently that was not the case.
The new NZ2 host was running against version 6.0 whereas NZ2 was running against 3.0. The JDBC driver we were using for NZ2 was 3 major versions too old. This also explains why the nzsql client on NZ1 couldn't connect to the NZ2 host.
We updated to the latest JDBC driver from IBM and can now connect just fine.
Related
Deat experts, We migrated from Oracle 12c to Oracle 19c in the windows server 2016 last week.
The DBA did not remove the previous version of oracle client - 12c and in addition installed the latest version of Oracle 19c.
Also I can see the environment variable has below 2 entry in addition to both the client installation
C:\Oracle\product\19.0.0\client_32\bin;
C:\Oracle\product\12.1.0\client_1\bin;
When we connect to the database using external connection, we get the below error. The DB was working fine prior to the oracle 19c installation.
The program has ended abnormally due to an unhandled exception.
Exception Code (OCI[DBConnectOCI.cpp[192]]
ORA-12557:TNS:protocol adapter not loadable)
Clarification:
I am not a DBA person but technically oracle has what it needs, why does it not getting connected to the DB using oracle client 19c?
Is it 100% true that we need to remove the previous version of the DB Client and always have only one client version?
Is the environment variable creating the issue ? or both env variable and oracle client ?
I have an IIS web application which connects to a SQL Server like this:
set objConn = Server.CreateObject("ADODB.Connection")
objConn.Open("DRIVER={SQL Server};SERVER=servername;DATABASE=dbname;UID=username;PASSWORD=pwd)
Recently I started getting the following error:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error
When I asked my server admin what this meant, he said that they had recently removed TLS 1.0 from the IIS server my web application is mounted on. He made sure the new SQL ODBC 13 drivers were installed on the web server, but it did not help.
Although the web app has never had a DSN before, we created one for it using the ODBC 13 driver. When I tried connecting like this:
objConn.Open "DSNname"
I got the following error:
[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
I looked up ConnectionStrings.com to see if there were a way of specifying a different driver. I tried this:
objConn.Open("DRIVER={SQL Server Native Client 13.0};SERVER=servername;DATABASE=dbname;UID=username;PASSWORD=pwd)
And this is the error message that was produced:
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Don't know what else to do. Any ideas?
We had to update 3 servers that are running several Classic ASP websites. The main reason was we need to implement Twillio API SMS messaging wich required TLS 1.0 and TLS 1.1 to be disabled/removed.
It took several days and we had the websites go up and down through the process.
I wrote a blog post to document the process for other team members. I hope it helps.
https://dhali.com/programming/tls-1-2-with-classic-asp/
Here are the outlined steps:
https://www.ssllabs.com/ssltest to get the current TLS Configuration
Using IISCrypto Tool we updated the Registry Files on the server
Ran https://www.ssllabs.com/ssltest to prove TLS 1.0 and 1.1 removed
Update ODBC to the latest ver supports TLS 1.2 [Microsoft® ODBC Driver 13.1 for SQL Server]
Update the connection string to use the current ODBC SQL 13 driver
The specified DSN contains an architecture mismatch between the Driver and Application
You can create either a 32bit DSN or a 64bit DSN. You need to create one matching the bitness of your program. Probably 32-bit.
We are trying to install HP ALM 12.5 on a Windows Server 2012 OS.
We have pre-requisite components .Net framework 3.5,4.5, JRE 1.8
During installation, we face an error Unable to validate DB connection parameters.
Checked with vendor, but they are repeatedly pointing to DB only.
However, nothing seems to be wrong with the db. we were able to make connections using SQL Developer and Express. Able to view table schema
Tried installing with SYSDB role, however that also fails making connection. On the listener we find some traffic from the app machine, in which we are attempting an installation.
We are so confused as to whether it is a App server issue or DB server issue. Port checks were done and no question of firewall. All open.
Any suggestions here is much appreciated !!
Db details: Oracle 12.1.0.2 Enterprise
DB server: Unix
App server: Win 2012 Server standard
ALM: 12.5 for HP PC 12.5
Check, please, in ALM installation if you are using SID or Service Name of your Oracle instance.
By default you should provide service name - but you can use SID by modifying Connection string directly (put SID instead of ServiceName).
1 - see screenshot.
Also you can check installation log at User folder\IA_logo for additional information on specific issue you met.
I am using pentaho data integration 4.1 (Kettle) to build an ETL system. My customer requires connecting to database (MS SQL Server) using window authentication, I knew that Kettle supported it . However when I run my Kettle job, it throws the exception
"I/O Error: SSO Failed: SSPI Not Initialized".
From an article on a forum, I copy library sqljdbc_auth.dll into jre/bin folder. The result is quite good, I can use window authentication to connect to SQL server. But this function is not stable, I mean sometimes it works well, sometimes it throws exception
"I/O Error: SSO Failed: SSPI Not Initialized".
Please tell me how to fix this error.
Thank you.
To connect to SQL Server 2008, I had to install the 'Microsoft JDBC Driver 4.0 for SQL Server' and then add the path to sqljdbc_auth.dll to Spoon.bat in %PENTAHO_DI_JAVA_OPTIONS%. Like this:
set OPT=%PENTAHO_DI_JAVA_OPTIONS% "-Djava.library.path=%LIBSPATH%;C:\PROGRA~1\MICROS~1.0FO\sqljdbc_4.0\enu\auth\x86;C:\PROGRA~1\IBM\SQLLIB\BIN" "-DKETTLE_HOME=%KETTLE_HOME%" "-DKETTLE_REPOSITORY=%KETTLE_REPOSITORY%" "-DKETTLE_USER=%KETTLE_USER%" "-DKETTLE_PASSWORD=%KETTLE_PASSWORD%" "-DKETTLE_PLUGIN_PACKAGES=%KETTLE_PLUGIN_PACKAGES%" "-DKETTLE_LOG_SIZE_LIMIT=%KETTLE_LOG_SIZE_LIMIT%"
Ugly, but that's Java under Windows for you. Works quite reliably now though.
Are you using the JTDS driver? Try that combined with the ntlmauth.dll - that works great for us when running PDI on Windows Server 2003 connecting to various remote sqlserver databases.
We place the DLL in this folder:
libswt\win64
I've had the same issue while using JDBC 1.2.2 with MSSQL 2008. It turns out that there is a bug in the driver, making it randomly crash if you initialize it with more than one connection.
If we used only one initial connection to the DB this error never presented itself.
The issue is fixed in a later versions of JDBC. We currently use 1.3.0 and I/O Error: SSO Failed: SSPI Not Initialized never comes up.
I'm building database application with delphi 2010 in which the database i used is ms access 2007 and ado as the connection....
then, i used installshield express from delphi 7 to do the deployment....
i open the setup file in my computer and there is no problem with it..but when i open the setup file in client computer, there is some error...
what makes me confused is what files needed to be added in the setup file for the deployment?
i've installed mdac 2.8 sp1 in the client, but it's still not working...
the error messages i got are : [microsoft][ODBC MIcrosoft Access Driver] general error unable to open registry key temporary (volatile) Ace DSN for process 0x16c8 thread 0x628 DBC 0x 3dc7eec
[micorsoft][ODBC Driver Manager] Data source name not found and no default driver specified..
then, when i try to another client computer, the error message i got are: [Microsoft][ODBC Microsoft Access Driver]'(Unknown)' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides
Exception EOle Exception in module 'module_name'.exe at 001A26AC
that's all the error messages i got... any clues?
Are you using the ACCDB format files? If so the version of ADO that comes with Windows knows nothing about that file format. You will need to install 2007 Office System Driver: Data Connectivity Components I would suggest using an MDB format file unless you are using some of the Access 2007 specific features as ADO knows all about MDB format.
It's very doubtful you'd need to install MDAC on the client system so long as it's Windows XP SP3 or newer. Windows XP SP2 installed MDAC 2.8 SP1. So don't much with the ADO version. For some information on how ADO works at the version level see I've never quite trusted ADO because … That article is written from the Access perspective but should give you some useful information on ADO versioning.
Perhaps the ADO connection component in your app has it's Active property set to true, or is set to true on startup, but the connection string is not valid on client machines as opposed to your dev machine? In this case you would receive a connnection error.
Without the error message it's hard to tell as jachguate says, but theoretically you should not need anything additional to deploy it according to the information you have provided.
As already said, without more information, it's hard to tell.
Please read and follow the advices on writing a good question by Jon Skeet.
It will boost your chances of getting an actionable answer...
Three basic things you need for connecting to Access:
the Data access layer: you should have it covered with installing MDAC.
the DB itself: either you create it from your application or the DB must already exist on the target machine. If not, you must deploy the DB files.
the connection to the DB: you must ensure the ConnectionString is valid for the target machine and you don't try to connect or activate any dataset before it is checked.
This is working now.
I installed 2007 Office System Driver: Data Connectivity Components as Tony recommended, then I also added midas.dll to system32 on the client computer.