|
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.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.