Solman down due to Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID")

[zulfadzlyiqbal]

Hi Gurus,

We are using Solman on DB2 and currently it is down due to error Security processing failed with reason "24" ("USERNAME C &+ AND/OR PASSWORD INVALID"). Please help. TQ

Below is dev_w0 logs:

---------------------------------------------------

trc file: "dev_w0", trc level: 1, release: "745"

---------------------------------------------------

*

* ACTIVE TRACE LEVEL 1

* ACTIVE TRACE COMPONENTS all, MJ

*

M sysno 00

M sid SOL

M systemid 562 (PC with Windows NT)

M relno 7450

M patchlevel 0

M patchno 816

M intno 20151301

M make multithreaded, Unicode, 64 bit, optimized

M profile \\IFAMSDB01P\sapmnt\SOL\SYS\profile\SOL_DVEBMGS00_IFAMSDB01P

M pid 7932

M

M

M Wed Oct 04 12:35:10 2023

M kernel runs with dp version 9000(ext=118000) (@(#) DPLIB-INT-VERSION-0+9000-UC)

M length of sys_adm_ext is 500 bytes

M ***LOG Q0Q=> tskh_init, WPStart (Workp. 0 7932) [dpInit.c 756]

M DpCommonParamInit: rdisp/core_file_size = default --> no change

I MtxInit: 0 0 0

M DpIPCInit2: read dp-profile-values from sys_adm_ext

M DpShMCreate: alloate/attach shared memory (mode=ATTACH)

M DpShMCreate: sizeof(wp_adm) 26880 (1120)

M DpShMCreate: sizeof(tm_adm) 52932880 (RDISPTERM=52880,MODEINFO=3024, IMODE_INFO=80)

M DpShMCreate: sizeof(ca_adm) 864000 (72)

M DpCommTableSize: max/headSize/ftSize/tableSize=1500/16/5712064/6003152

M DpShMCreate: sizeof(comm_adm) 6003152 (3784)

M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

M DpShMCreate: sizeof(slock_adm) 0 (296)

M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

M DpShMCreate: sizeof(file_adm) 0 (80)

M DpSockTableSize: max/headSize/ftSize/tableSize=1500/16/1560064/1560080

M DpShMCreate: sizeof(sock_adm) 1560080 (1016)

M DpShMCreate: sizeof(vmc_adm) 0 (3216)

M DpShMCreate: sizeof(wall_adm) (ft=208064/fi=205072/hd=64/rec=192)

M DpShMCreate: sizeof(amc_rec_adm) (ft=1376064/fi=377072/hd=64/rec=672)

M DpShMCreate: sizeof(websocket_adm) (ft=288064/hd=80/rec=560)

M DpShMCreate: sizeof(gw_adm) 64

M DpShMCreate: sizeof(j2ee_adm) 3936

M DpShMCreate: SHM_DP_ADM_KEY (addr: 0000000001490050, size: 63952096

M DpShMCreate: allocated sys_adm at 0000000001490250

M DpShMCreate: allocated wp_adm_list at 00000000014A2210

M DpShMCreate: allocated wp_adm at 00000000014A2530

M DpShMCreate: allocated tm_adm_list at 00000000014A9030

M DpShMCreate: allocated tm_adm at 00000000014A92B0

M DpShMCreate: allocated ca_adm at 00000000047245C0

M DpShMCreate: allocated comm_adm at 00000000047F76C0

M DpShMCreate: system runs without slock table

M DpShMCreate: allocated sock_adm at 0000000004DB1290

M DpShMCreate: allocated vmc_adm_list at 0000000004F2E2A0

M DpShMCreate: system runs without VMC

M DpShMCreate: allocated gw_adm at 0000000004F2E540

M DpShMCreate: allocated j2ee_adm at 0000000004F2E780

M DpShMCreate: allocated ca_info at 0000000004F2F8E0

M DpShMCreate: allocated wall_adm (ft) at 0000000004F2FB20

M

M Wed Oct 04 12:35:10 2023

M DpShMCreate: allocated wall_adm (fi) at 0000000004F629E0

M DpShMCreate: allocated wall_adm (head) at 0000000004F94CF0

M DpShMCreate: allocated amc_rec_adm (ft) at 0000000004F94F30

M DpShMCreate: allocated amc_rec_adm (fi) at 00000000050E5070

M DpShMCreate: allocated amc_rec_adm (head) at 0000000005141360

M DpShMCreate: allocated websocket_adm (ft) at 00000000051415A0

M DpShMCreate: allocated websocket_adm (head) at 0000000005187CE0

M DpShMCreate: initialized 21 eyes

M

M Wed Oct 04 12:35:11 2023

M DpCommAttachTable: attached comm table (header=00000000047F76C0/ft=00000000047F76D0/fi=0000000004D69F90)

M DpSockAttachTable: attached sock table (header=0000000004DB1290/ft=0000000004DB12A0)

X EM: Initializing PROC global storage: quota=0 use_stdheap=0

X EM: Initializing PROC local storage: quota=0 use_stdheap=0

X EmInit: MmSetImplementation( 2 ).

X MM global diagnostic options set: 0

X EmSetReserve: set EM reserve to 0 EM blocks

X <ES> client 0 initializing ....

X <ES> EsILock: use Mutex for locking

X Using implementation view

X <EsNT> Using memory model view.

M <EsNT> Memory Reset disabled as NT default

X ES initialized.

X mm.dump: set global maximum dump mem to 192 MB

X EsRegisterEmCheck: Register EmGetEsHandles at 00007FF669D6AE68

M ThStart: taskhandler started

M ThInit: initializing DIA work process W0

X MMX: use precise segment size globally

M ThStopHeapLockChecker: stop heap lock checker

M

M Wed Oct 04 12:35:13 2023

M ThInit: running on host IFAMSDB01P

I MtxInit: 0 0 0

M

M Wed Oct 04 12:35:21 2023

M calling db_connect ...

B Loading DB library 'E:\usr\sap\SOL\DVEBMGS00\exe\dbdb6slib.dll' ...

B Library 'E:\usr\sap\SOL\DVEBMGS00\exe\dbdb6slib.dll' loaded

B Version of 'E:\usr\sap\SOL\DVEBMGS00\exe\dbdb6slib.dll' is "745.04", patchlevel (0.812)

C DbSl trace SM50: switch request to level 1

C Registering callback for dynamic profile parameters

C

C Wed Oct 04 12:35:22 2023

C

C DB6 (DB2 UDB) UNICODE database interface 745.04 [opt]

C

C DB6 shared library (dbdb6slib) patchlevels

C (0.1) SAP kernel corrections prior to delivery (note 1226290)

C (0.3) DB6: performance of ABAP MODIFY ... FROM TABLE ... (note 2178105)

C (0.5) SAP kernel corrections prior to delivery (note 1226290)

C (0.6) DB6: increase maximum number of external connections to 16 (note 2185047)

C (0.8) DB6: Explain does not find matching optimizer profile (note 2191320)

C (0.8) DB6: ignore warings during array MODIFY (note 2195601)

C (0.13) DB6: Set CURRENT REFRESH AGE = 0 at connect time (note 2207807)

C (0.18) DB6: early close INSERT statement on duprec (note 2221224)

C (0.24) DB6: CLI overflow in DMO migration phase (note 2230417)

C (0.26) DB6: No short dump when ADBC program binds too many parame (note 2243695)

C (0.27) DB6: dynamically enable/disable netstatis collection (note 1625157)

C (0.31) DB6: cast to SSTRING (note 2261398)

C (0.34) DB6: network statistics data shows time_period=0 (note 2265329)

C (0.36) DB6: Unexpected VBKEY value found in VBHDR (note 2274012)

C (0.100) SAP Support Package Stack Kernel 7.45 Patch Level 100 (note 2276394)

C (0.110) DB6: Missing double qoutes in CREATE TABLE statement (note 2283384)

C (0.110) DB6: Support for tablespace pools (note 2267446)

C (0.200) SAP Support Package Stack Kernel 7.45 Patch Level 200 (note 2299971)

C (0.211) DB6: LEFT OUTER TO ONE JOIN (note 2329646)

C (0.211) DB6: SQL cache analysis does not show ABAP location (note 2309280)

C (0.213) DB6: inline length 8K for column DCONTENT in TST03 (note 2317433)

C (0.300) SAP Support Package Stack Kernel 7.45 Patch Level 300 (note 2361598)

C (0.301) SAP Support Package Stack Kernel 7.45 Patch Level 301 (note 2389206)

C (0.310) DB6: RENAME INDEX on virtual tables (note 2349635)

C (0.316) DB6: database connection using SSL encryption (note 2385640)

C (0.318) DB6: dev trace entries with SYSPROC.ADMIN_REVALIDATE_DB_OBJECT (note 2388505)

C (0.319) DB6: wrong VALUES CURRENT TIMESTAMP statement executed (note 2397610)

C (0.400) SAP Support Package Stack Kernel 7.45 Patch Level 400 (note 2417597)

C (0.410) DB6: ST05 trace shows OTHER SQL for FOR ALL ENTRIES statement (note 2416250)

C (0.412) DB6: skip adjacent duplicate input tuples for FOR ALL ENTRIES statemen (note 2428614)

C (0.413) DB6: lock wait on cursor executed WITH RS clause (note 2431750)

C (0.413) DB6: schema name in SYSTEM comment (note 2437149)

C (0.500) SAP Support Package Stack Kernel 7.45 Patch Level 500 (note 2469219)

C (0.510) DB6: improved error handling for CLI function SQLPutData (note 2461903)

C (0.510) DB6: change connect user password on DB2 pureScale system (note 2483331)

C (0.600) SAP Support Package Stack Kernel 7.45 Patch Level 600 (note 2531561)

C (0.610) DB6: call out script to collect support data after SQL exceptions (note 2535913)

C (0.613) DB6: error handling on connection attempts without password (note 2550653)

C

C Wed Oct 04 12:35:22 2023

C (0.700) SAP Support Package Stack Kernel 7.45 Patch Level 700 (note 2596010)

C (0.710) DB6: incorrect member number in network statistics (note 2594089)

C (0.711) DB6: statement string is blank or empty (note 2602538)

C (0.800) SAP Support Package Stack Kernel 7.45 Patch Level 800 (note 2666684)

C (0.812) DB6: no DB error message was returned on MOD (note 2677032)

C

C Supported features:

C

C ..retrieving configuration parameters

C ..done

C

C Wed Oct 04 12:35:23 2023

C DB2 library has been loaded.

C Info: successfully loaded DB2 library 'E:\usr\sap\SOL\DVEBMGS00\exe/db6_clidriver\bin\db2app64.dll'

C Running with UTF-8 Unicode

C

C Wed Oct 04 12:35:24 2023

C DB2 client driver version '10.05.0007'

C

C Wed Oct 04 12:35:25 2023

C Running with CLI driver.

C

C Wed Oct 04 12:35:26 2023

C *** ERROR in DB6Connect[D:/depot/bas/745_REL/src/dbs/db6/dbdb6.c, 1918] CON = 0 CACHEID = -1 (BEGIN)

C &+ DbSlConnectDB6( SQLConnect 😞 [IBM][CLI Driver] SQL30082N Security processing failed with reason "24" ("USERNAME

C &+ AND/OR PASSWORD INVALID"). SQLSTATE=08001

C &+

C &+

C *** ERROR in DB6Connect[D:/depot/bas/745_REL/src/dbs/db6/dbdb6.c, 1918] (END)

C *** ERROR => DbSlConnect to 'SOL' as 'sapsol' failed

[dbdb6.c 1925]

M ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 86]

M in_ThErrHandle: 1

M *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c 2560]

M

M Info for wp 0

M

M pid = 7932

M severity = 0

M status = 0

M stat = WP_NEW

M waiting_for = NO_WAITING

M workerType = DP_WORKER_DIAWP

M act_cs_count = 0

M csTrack = 0

M csTrackRwExcl = 0

M csTrackRwShrd = 0

M mode_cleaned_counter = 0

M control_flag = 0

M report = > <

M action = 0

M tab_name = > <

M

M ThIErrHandle: no current incoming request

M

M

M *****************************************************************************

M *

M * LOCATION SAP-Server IFAMSDB01P_SOL_00 on host IFAMSDB01P (wp 0)

M * ERROR ThInit: db_connect

M *

M * TIME Wed Oct 04 12:35:26 2023

M * RELEASE 745

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 16797709

M * MODULE D:/depot/bas/745_REL/src/krn/si/th/thxxhead.c

M * LINE 2742

M * COUNTER 1

M *

M Wed Oct 04 12:35:26 2023

M *****************************************************************************

M

M PfRejectStatistic: clear statistic record

M PfClearAllRec: clear statistic area

M PfClearAllRec: set statRecordAction = STAT_RECORD_ACTION_REJECT

M Entering TH_CALLHOOKS

M ThCallHooks: call hooks for event BEFORE_DUMP

M ThIErrHandle: entering ThSetStatError

M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)

M

M ***

M *** work process W0 died => ThInit: db_connect

M call ThrShutDown (1)...

M ***LOG Q02=> wp_halt, WPStop (Workp. 0 7932) [dpnttool.c 334]

[moshenaveh]

Welcome to the SAP Community. Thank you for visiting us to get answers to your questions.

Since you're asking a question here for the first time, I'd like to offer some friendly advice on how to get the most out of your community membership and experience.

First, please see https://community.sap.com/resources/questions-and-answers, as this resource page provides tips for preparing questions that draw responses from our members. Second, feel free to take our Q&A tutorial at https://developers.sap.com/tutorials/community-qa.html, as that will help you when submitting questions to the community.

I also recommend that you include a profile picture. By personalizing your profile, you encourage readers to respond: https://developers.sap.com/tutorials/community-profile.html.

Now for some specific suggestions on how you might improve your question:

* Outline what steps you took to find answers (and why they weren't helpful) -- so members don't make suggestions that you've already tried.

* Share screenshots of what you've seen/done (if possible), as images always helps our members better understand your problem.

* Make sure you've applied the appropriate tags -- because if you don't apply the correct tags, the right experts won't see your question to answer it.

* Use the "insert code" feature when sharing your code, so members have an easier time reading.

Should you wish, you can revise your question by selecting Actions, then Edit.

The more details you provide (in questions tagged correctly), the more likely it is that members will be able to respond.

I hope you find this advice useful, and we're happy to have you as part of SAP Community!

[Frank-Martin · Accepted solution]

Somebody must have changed the password of user SAPSOL on your database server without updating the password in the SAP password store.

Update the password store on one of your SolMan appservers with:

dscdb6up -create <current pwd of user SAPSOL> "dummy"

Afterwards test with "R3trans -x" if the connect is working again.
Regards
Frank

[zulfadzlyiqbal · Accepted solution]

Hi Frank,
Thank you very much.
It is working.
You save my life