Topic
  • 1 reply
  • Latest Post - ‏2012-08-30T15:03:00Z by SystemAdmin
Kanatay
Kanatay
38 Posts

Pinned topic DGL7334A: The library server connection failed due to an error in the DKDat

‏2012-08-05T10:10:11Z |
DKDatastoreICM connect() method.

Hello all,
I've created a test user today inside the System Administration Client.
When I tried to log on using Client for Windows, I got this error
message:

"DGL7334A: The library server connection failed due to an error in the
DKDatastoreICM connect() method. The library server return message
was: SERVER = icmnlsdb, USERID = TEST; ICM7191: The database
connection user ID that you use is not properly configured. Check with
your DB2 Content Manager administrator to make sure that you are using
the correct database connection user ID, then refer to the section
"Changing the database ID and password" in the System Administration
Guide for details on how to configure it properly. (STATE) : [LS RC =
7191, LS reasonCode = 7, SQL RC = 8]"
Today I received another error message as well:
"þDGL0394A:þ ùâéàä áúåê :þError - SQL_ERROR
IBMCLI Driver SQL30082N Attempt to establish connection failed with security reason "19" ("USERID DISABLED or RESTRICTED"). SQLSTATE=08001 (STATE) : 08001"

icmserver.log says:

"ICMPLSLG ICMLOGON 01457 08/05 09:16:41.093 GMT ; 2012/08/05 12:16:41.093 LCT ; 6872 PID;05091641326164 71806404413087315844 TEST
Logon is denied by CM:
User TEST
Database connect ID ICMCONCT
Password is not empty
Server allow trusted logon flag 0
Ignore trust logon option 0
Reason:
CM Administrator TEST with system password can not
logon using database connection ID ICMCONCT.
ICMPLSLG ICMLOGON 01460 08/05 09:16:41.093 GMT ; 2012/08/05 12:16:41.093 LCT ; 6872 PID;05091641326164 71806404413087315844 TEST Exit rc=7172 reason=9 extrc=0 extreason=9
ICMPLSLG ICMLOGON 01036 08/05 09:18:23.171 GMT ; 2012/08/05 12:18:23.171 LCT ; 3436 PID;05091823394058 99225911211382189617 TEST
Logon is denied.
User TEST is not defined in CM.

ICMPLSLG ICMLOGON 01039 08/05 09:18:23.171 GMT ; 2012/08/05 12:18:23.171 LCT ; 3436 PID;05091823394058 99225911211382189617 TEST Exit rc=7127 reason=0 extrc=0 extreason=0
ICMPLSLG ICMLOGON 01036 08/05 09:18:33.562 GMT ; 2012/08/05 12:18:33.562 LCT ; 3436 PID;05091833783125 99225911211382189617 TEST
Logon is denied.
User TEST is not defined in CM.

ICMPLSLG ICMLOGON 01039 08/05 09:18:33.562 GMT ; 2012/08/05 12:18:33.562 LCT ; 3436 PID;05091833783125 99225911211382189617 TEST Exit rc=7127 reason=0 extrc=0 extreason=0
ICMPLSLG ICMLOGON 01036 08/05 09:18:40.796 GMT ; 2012/08/05 12:18:40.796 LCT ; 3436 PID;05091840019283 99225911211382189617 TEST
Logon is denied.
User TEST is not defined in CM.

ICMPLSLG ICMLOGON 01039 08/05 09:18:40.796 GMT ; 2012/08/05 12:18:40.796 LCT ; 3436 PID;05091840019283 99225911211382189617 TEST Exit rc=7127 reason=0 extrc=0 extreason=0"
How can I resolve this issue? Please see the log files attached.

Regards,
Assaf
  • SystemAdmin
    SystemAdmin
    228 Posts

    Re: DGL7334A: The library server connection failed due to an error in the DKDat

    ‏2012-08-30T15:03:00Z  
    It looks like there could be a few different things going on here, probably best to open a PMR if this problem persists, but let me give some background and thoughts on this issue...

    In CM there are two ways to connect and logon to the server. The first is with a database userid. All admins are generally database ids, as special database privileges are needed to manipulate tables and so on. The second way is via a CM userid. With the CM userid, we use the connect id (icmconct by default) to connect to the database and then call CM to authenticate the userid itself.

    We do not allow admins to connect to the database via the connect id, because they would not have the privileges they need to perform admin operations. One of the things I see in the information below is the message:

    
    CM Administrator TEST with system password can not logon using database connection ID ICMCONCT
    


    This seems to point to an issue where an admin is trying to connect to the database using the connect id. This could be because the admin does not have a database userid, in which case, you just need to define the database userid for the admin user TEST, and then the logon should work as the user will be authenticated via the database id and the connect id will not be used.

    Via the API you can control whether database id or connect id is tried first. This can be done with the ICMSERVERREPTYPE in the cmbicmsrvs.ini file or with options when calling connect. In general, if the first method fails we try the second, but controlling the order is important in many applications to avoid unneeded overhead and errors.

    The second thing I see in the post is this message:
    
    SQL30082N Attempt to establish connection failed with security reason 
    "19" (
    "USERID DISABLED or RESTRICTED").
    


    This seems to indicate that possibly the connect id is not setup properly in the database or its password has expired. This would be another thing to check. In this case, since TEST appears to be an admin id, the connect id should not be used, however this error might still cause issues with other userids.

    If this does not give the answer you need, I would encourage you to open a PMR, our support team can walk you through checking all of the things I have mentioned above.