×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The problem occurred when using JDBC to connect to MS Sql Server with
user accounts defined in our MS Active Directory that were limited
to Windows Authentication.
The messages returned from Scott Klement's JDBCR4 service program:
1) Unable to connect.
proc: DRIVER_CONNPROP
stmt: 87000
2) Login failed for user 'xxxx'
proc: JNI_CHECKERROR
stmt: 224500
The error returned changed depending on minor changes
on the MS Sql Server user account that did not correct the
user account lack of Sql Server Authentication function.
As Scott Klement has stated in another thread; connections from system i
to MS Sql Server must use Sql Server Authentication.
From what I see, Sql Server Authentication must be set at three levels:
1) the Microsoft Sql Server instance
2) the named instance of the database
3) the Microsoft Sql Server user account
Because we had already addressed 1) and 2), the solution was to create a
new Microsoft SQL server account and define this account with
both Windows and Sql Server Authentication and use this account
to make the connection.
midrange.com
