on 07-28-2010 2:52 PM
Hello Guys
Have a big problem. hope that you could help me.
Can't to run the SSM Ehp1 Instance in MMC, because the admin credentials in SecureStore@ConfigTool and MS SQL 2003 are mismatch.The Eventviewer of Windows 2003, show in the events:
Event: Failure Audit
Source: MSSQLSERVER
Description: Login failed for user 'SAPSMADB'. CLIENT: 10.5.4.100. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Where SAPSMADB is the JDBC user maintained in SecureStore@ConfigTool. And, 10.5.4.100 is the host instance.
Need match both credentials, and can to run the SSM Ehp1 Instance.
This issue happened, because i'm set up the SAP service CQC Security Optimization and after coming CQC BPPO, SolManDiag is a pre-requisite. The credentials in SolManDiag were maintained, in: AS Java, RFC, ConfigTool, and MS SQL Server 2003. In ConfigTool was where succed the issue.
Thanks for you HELP, and Regards
Please check the firewall rules on message server port as it was blocking
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to understand, what was changed to have this issue ? was kernel updated to version 94 ? Can you change to the original version that was installed before the update ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK. is a less complicated to explain.
How part of the preparation of CQC Security Optimization Service and CQC BPPO, from SAP AG. Some pre-requisites are:
- Upgrade Kernel 7.00 to 7.01. This was delivered in past week without troubles.
- Set up SolMandDiag and Wily Instroscope 8. Follow up the Set up of SolManDiag, one of the steps is to install Wiliy Introscope. Here some SAP Notes must follow up these.The trouble was, that in ConfigTool, changed the password JDBC User and AS Java Admin in section Secure Data, and here begins the troubles, can't to run whole instance. I think, both passwords are match, but some happened that unable to run tha Instance.
Regards
Thanks so much for to reply
The service thats see it in yellow is: disp+work.EXE. With the msg: Running, Message Server connection ok, Dialog Queue:
0.00 sec, J2EE status info unavaliable.
And J2EE Process Table; is empty
With trace, this yellow service:
-
trc file: "dev_disp", trc level: 1, release: "701"
-
sysno 00
sid SMA
systemid 562 (PC with Windows NT)
relno 7010
patchlevel 0
patchno 94
intno 20020600
make: multithreaded, Unicode, 64 bit, optimized
pid 4048
Wed Jul 28 15:25:43 2010
kernel runs with dp version 244000(ext=110000) (@(#) DPLIB-INT-VERSION-244000-UC)
length of sys_adm_ext is 576 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 4048) [dpxxdisp.c 1287]
shared lib "dw_xml.dll" version 94 successfully loaded
shared lib "dw_xtc.dll" version 94 successfully loaded
shared lib "dw_stl.dll" version 94 successfully loaded
shared lib "dw_gui.dll" version 94 successfully loaded
shared lib "dw_mdm.dll" version 94 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
Wed Jul 28 15:25:49 2010
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 6 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5534]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >sap-solman_SMA_00 <
DpShMCreate: sizeof(wp_adm) 56064 (1752)
DpShMCreate: sizeof(tm_adm) 5912704 (29416)
DpShMCreate: sizeof(wp_ca_adm) 24064 (80)
DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080
DpShMCreate: sizeof(comm_adm) 552080 (1088)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (104)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (1864)
DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 00000000092C0050, size: 6640416)
DpShMCreate: allocated sys_adm at 00000000092C0050
DpShMCreate: allocated wp_adm at 00000000092C2270
DpShMCreate: allocated tm_adm_list at 00000000092CFD70
DpShMCreate: allocated tm_adm at 00000000092CFDD0
DpShMCreate: allocated wp_ca_adm at 0000000009873650
DpShMCreate: allocated appc_ca_adm at 0000000009879450
DpShMCreate: allocated comm_adm at 000000000987B390
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 0000000009902020
DpShMCreate: allocated gw_adm at 00000000099020A0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 00000000099020D0
DpShMCreate: allocated wall_adm at 00000000099020E0
MBUF state OFF
DpCommInitTable: init table for 500 entries
rdisp/queue_size_check_value : -> off
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
<ES> Info: em/initial_size_MB( 8190MB) not multiple of em/blocksize_KB( 4096KB)
<ES> Info: em/initial_size_MB rounded up to 8192MB
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 2047 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 96 MB
J2EE server info
start = TRUE
state = STARTED
pid = 4964
argv[0] = S:\usr\sap\SMA\DVEBMGS00\exe\jcontrol.EXE
argv[1] = S:\usr\sap\SMA\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=S:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_sap-solman
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=65000
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=SMA
argv[7] = -DSAPMYNAME=sap-solman_SMA_00
argv[8] = -DSAPPROFILE=S:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_sap-solman
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1682]
***LOG Q0K=> DpMsAttach, mscon ( sap-solman) [dpxxdisp.c 12696]
DpStartStopMsg: send start message (myname is >sap-solman_SMA_00 <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: start to initalize 3.X shared alert area (first segment).
DpJ2eeLogin: j2ee state = CONNECTED
DpMsgAdmin: Set release to 7010, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1048]
DpMsgAdmin: Set patchno for this platform to 94
Release check o.K.
Wed Jul 28 15:25:53 2010
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
change reqtype of W18 from 2 to 3
***LOG Q0V=> DpAdXWpConf, mod_req (18UPDENQ) [dpxxdisp.c 14798]
change reqtype of W19 from 2 to 6
***LOG Q0V=> DpAdXWpConf, mod_req (19UPDUP2) [dpxxdisp.c 14798]
Wed Jul 28 15:25:55 2010
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4436]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1176
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4730) [nixxi.cpp 4436]
ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Wed Jul 28 15:26:29 2010
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What service in MMC is failing ? In what service you are seeing a yellow or gray status ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.