We've installed the SnowflakeDSIIDriver version 2.22.00.00 on our Windows server, and established the settings in the Windows registry that theoretically should allow logs to be created. However, none are being created. Rebooted the server after configuration as well.
The driver seems to be working just fine, so no issues there.. just trying to troubleshoot a UTF-8 issues and hoping the logs will help.
Thoughts?
Settings in the registry are:
CURLVerboseMode: true
LogLevel: 6
LogPath: c:\Users\Public\Snowflake ODBC Drive\log
This is on the following box:
OS Name: Microsoft Windows Server 2016 Datacenter
OS Version: 10.0.14393 N/A Build 14393
Related
My MS Access Client attaches to SQL Server tables via a DSNLess connection. It has been attaching successfully with no issues for several years, until January 14th 2023.
I now get an error 3125 with error description:'dbo.Denomination' is not a valid name. Make sure that it does not include invalid characters or punctuation and that it is not too long.
As can be seen, the table name 'Denomination' is short and contain no invalid characters. Even odder, table 'Denomination' is not the first table in my list. It is preceded by two other tables (AuditLog & lnkDBSCheck) that attach successfully.
The operating environment is: Windows 10 Pro 64-bit. Version 22H2. OS Build 19045.2486
I've tried the following to resolve the issue.
Decompiled the MS Access Client FE
Tried different drivers:
'ODBC Driver 18 for SQL Server', 'ODBC Driver 17 for SQL Server' & 'SQL Server Native Client 11.0'
Tried earlier versions of the Client.
The result is always the same - Error 3125.
I'm now wondering if the issue is related to Windows updates of a few days before (on 11th Jan, though I only rebooted my workstation on the 13th). The updates were KB5022282 (cumulative update for Windows 10 Version 22H2 for x64-based Systems) & KB890830 (Windows Malicious Software Removal Tool x64 - v5.109.
I'm out of ideas on this - help!
Run this from an administrator command prompt
Cd C:\program files\common files\microsoft shared\clicktorun
officec2rclient.exe /update user updatetoversion=16.0.15831.20208
Then disable update in Microsoft Office
Original Posting
https://www.devhut.net/microsoft-office-uninstall-an-update/
Our Access program gave us the same problem.
Office Release Notes: (This broke our DSN connection)
Version 2212: January 04
Version 2212 (Build 15928.20198)
Feature updates
Access
Enable the ability to code sign your Microsoft Access database and VBA code: This update enables the Tools/Digital Signature command within the VBA (Visual Basic for Applications) IDE (Integrated Development Environment) for current Microsoft Access database formats. Signing a database will allow VBA code in the database to be run even if Trust Center settings specify that only digitally signed code should be enabled.
Background: I have to transfer VS 2003 and VB6 applications from Windows 7 to a new Windows 10 Home machine. The applications are currently using DB2 9.7, Sql Server or Ms Access via ODBC. I decided to consolidate all dbs to DB2 on the W10 machine, using separate schemas for the different databases. The W10 machine is normally standalone (No Lan or Internet).
Details: I installed DB2 Express V10.5 and IBM Data Studio 4.1 on the W10 machine. DB2 Express gives me enough for my db needs, and I assume that Data Studio will give me similar GUI functionality as DB2 Control Center v9 on the W7 machine.
I installed DB2 and Data Studio under at least two different user ids(one being Db2admin), all with windows admin rights, and different credentials.
But every time I try to login/connect in Data Studio I'm rejected with SQ4499N, I must be doing something fundamentally Wrong.
when running the following commands from CMD I get the shown results.
db2val
DBI1379I The db2val command is running. This can take several minutes.
DBI1333I Installation file validation for the DB2 copy DB2COPY1
was successful.
DBI1339I The instance validation for the instance DB2 was
successful.
DBI1343I The db2val command completed successfully. For details, see
the log file C:\Users\User\DOCUME~1\DB2LOG\db2val-Wed Mar 02 16_28_37 2022.log.
DB2LEVEL returns:
DB21085I This instance or install (instance name, where applicable: "DB2")
uses "32" bits and DB2 code release "SQL10054" with level identifier
"0605010E".
Informational tokens are "DB2 v10.5.400.191", "s140813", "IP23617", and Fix
Pack "4".
Product is installed at "C:\PROGRA~2\IBM\SQLLIB" with DB2 Copy Name "DB2COPY1".
DB2Start returns:
SQL1026N The database manager is already active.
Switching to DB2 CLP
db2 => List Active Databases returns:
SQL1611W No data was returned by Database System Monitor.
db2 => List database directory returns:
SQL1057W The system database directory is empty. SQLSTATE=01606
db2 => list system odbc data sources returns:
DB21037W No data sources found.
Checking Google and stackoverflow didn't yield any suitable help, at least I didn't see it.
My experience is as app developer, not db2 admin except what is needed for app dev, and I had no problems with DB2 V9.7 on W7, but I'm lost what to do.
Any help is appreciated.
The prerequisites and expected behavior is described at the Configuring the IBM Data Studio client for remote operations link.
You got this error either because of misconfiguration or some DS bug / unexpected behavior.
The solution was to create the database manually and just to register this database in DS afterwards.
In practical terms: DB2 V10.5 SQL-Express failed to install the Sample Database. IBM Data Studio tried to connect to the Sample Database and failed the operation with SQL4499N. Manually creating a database overcame this problem.
I have a small home network of pc's all running Windows 10. None of the PC's have been or are in a domain. One (an intel NUC) runs Sql Server and my Surface 3 has Visual Studio. I use my Microsoft login for both. This setup has been running fine for almost 2 years.
Now I suddenly get the above error when trying to connect using integrated security.
Sql Authentication works fine.
I can also remote into the NUC and run SSMS without a problem.
I have followed the troubleshooting guide without success (KB 811889)
NTLM seems to be operating OK on the NUC.
I pinged -a IPAddress and it resolved correctly to the name of the NUC
SQL Server uses NT Service\MSSQLSERVER. I tried using LocalSystem but still didn't work
All the help articles I have found assume there is a domain or suggest Sql Authentication as a solution.
Only recent change has been installing Windows Update for Windows 10 Version 1607 on the NUC
Can anyone help me?
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.
This is giving me headache.
I just set up pentaho community edition on my laptop. I was able to connect to mysql server in xampp by following the instructions in the pdf documentation that comes with the enterprise edition getting_started_with_pentaho. I connect perfectly to mysql database.
However I need to also connect both locally and remotely to a sql server (mssql) but follwing the same process as i did for the mysql database does not work.
This is what i did:
I installed SQLServer2008R2SP1-KB2528583-x64-ENU.exe sql server and logged in successfully with the following input
server type: database engine
server name: ME-PC\SQLEXPRESS
authentication: windows authentication
login: ME-PC\ME
password:
Now I downloaded the jdbc driver for mssql from here and extracted the folder to my desktop. The folder contained sqljdbc4.jar and sqljdbc.jar as well as both x64 and x86 versions of sqljdbc_auth.dll.
I am running a x64 OS but but the jdk i installed went to the Programfiles(x86) so I guess the java i had install was for x86. Due to this reason I copied sqljdbc4.jar and the x86 version of sqljdbc_auth.dll to the directorys:
C:\Users\ELRAPHA\Desktop\PENTAHO\biserver-ce\tomcat\webapps\pentaho\WEB-INF\lib
C:\Users\ELRAPHA\Desktop\PENTAHO\administration-console\jdbc
C:\Users\ELRAPHA\Desktop\PENTAHO\data-integration\libext\JDBC
I also enabled TCI/IP on my local sql server.
As I mentioned, am able to connect to sql server via the management studio but when i try to create a new connection through pentaho in the web browser with the following
hostname: localhost
database name: master
instance name: ME-PC\SQLEXPRESS
port: 1433
username: ME-PC\ME
password:
I get the error
error connecting to database [mssqllocal]
org.pentaho.di.core.exception.KettleDatabaseException:
Error occured while trying to connect to the database
error connecting to database:(using class com.microsoft.sqlserver.JDBC.SqlServerDriver)
The TCP/IP connection to the host localhost, port 1433 has failed.
Error: Connection refused: connect.
I dont get what am doing wrongly especially since mysql was to straight forward. Been at this all day. I need help . Please can anyone see my error or something that am missing here? HELP
If you want to connect through JDBC to SQL Server via Windows Authentication, then the sqljdbc_auth.dll must be in the right location. On my system (x86) that this is relative to the install directory of the sqljdbc4 driver. By "extracted the folder to my desktop" I assume you mean you ran the installer, and that's where you choose the location of the driver. For example on my system, this file is not in the Pentaho folders, it's in:
C:\Program Files\Microsoft JDBC Driver 4.0 for SQL Server\sqljdbc_4.0\enu\auth\x86
I would ensure that both 32 and 64 bit versions of sqljdbc_auth.dll are in their respective locations since you seem to have a mixed system.
Alternatively, you can use SQL Server authentication which is simpler, but doesn't integrate with AD, etc.
EDIT:
Oops, I forgot something very important. The JVM must be made aware of the location of sqljdbc_auth.dll. I had to add the path of that dll to %LIBSPATH% in Spoon.bat (I'm only using PDI).
So essentially I changed this block of code in the batch file:
:USE32
REM ===========================================
REM Using 32bit Java, so include 32bit SWT Jar
REM ===========================================
set LIBSPATH=libswt\win32
GOTO :CONTINUE
:USE64
REM ===========================================
REM Using 64bit java, so include 64bit SWT Jar
REM ===========================================
set LIBSPATH=libswt\win64
set SWTJAR=..\libswt\win64
to this:
:USE32
REM ===========================================
REM Using 32bit Java, so include 32bit SWT Jar
REM ===========================================
set LIBSPATH=libswt\win32;C:\PROGRA~1\MICROS~1.0FO\sqljdbc_4.0\enu\auth\x86
GOTO :CONTINUE
:USE64
REM ===========================================
REM Using 64bit java, so include 64bit SWT Jar
REM ===========================================
set LIBSPATH=libswt\win64
set SWTJAR=..\libswt\win64
Note the shortened path names. In your case, I would add an entry for the 64 bit lib also since you have a mixed environment.
Essentially whatever program you're starting that uses the sqljdbc driver, you must add the path the sqljdbc_auth.dll to the Java library path (i.e. -Djava.library.path=%LIBSPATH%). After doing that, my instance of PDI can connect to SQL Server via Windows Authentication with no trouble. I don't use the BI_Server or the Admin Console, but I suspect you'll have the same issue.
Note, I have no experience with SQLEXPRESS, or a mixed 32 bit JVM/64 bit OS environment. There could be problems there too, but if you want to use Windows Authentication with SQL Server, you have to at least deal with the library path issue.
If you are using a intance of Sql Express in local machine and connecting Pentaho, you must empty the field Port Number. Try the configuration below:
Host Name: localhost
Database: database_name
Instance Name: sqlexpress
Port Number:
User Name: user_name
Password: *****
In case of having issues, together with empty the port number, is to manually set the instance name as a manual parameter:
instanceName=SQLEXPRESS
The default pentaho dialog (at least to 8.3) generates only the code "instance=SQLEXPRESS"