cancel
Showing results for 
Search instead for 
Did you mean: 

IDES installation problem with DDIC password

Former Member
0 Kudos

Hello everybody,

After hours of searching and trying..

I have here a problem during a local installation of IDES ECC 6.0 on Windows Server 2008 with MAXDB. The installation stops in phase 27 of 29 u201Ccheck DDIC passwordu201D - test logon to SAP system failed, with the error message FRF-00007 "Unable to open RFC connection" in sapinst.

The MMC shows in the process list that the following processes stands oon "green": igswd, mag_Server and disp+work are running. The message of servers connection is OK, acts dialogue queue time is 0.00 sec.

I have already searched the forum, but I am not able to logon as user SAP* with u201C060. u2026u201D or as user DDIC with the password u201C199. u2026u201D to change the DDIC password to my password set during the installation (transaction -S000 / SU01). The login fails over the MMC as well as over the SAP GUI 7.10. I have tried this on the client 000, 001 and 800. The error message is u201CSAP Logon Failed - connection closed without message (CM_NO_DATA_RECEIVEDu201D). The SAP GUI gets down with "Work process restartet, session terminated".

What can help to solve the problem? Can it be a problem with the ms loop adaptor? Which static address IP must assign to the loop adaptor? Did i have to update the kernel of the data bank or is this not necessary? Can the information from dev_w help?

Can this link help me:

Thanks in advance

Lenvy

Edited by: Lenvy Gee on Sep 6, 2009 2:30 AM

Edited by: Lenvy Gee on Sep 6, 2009 2:34 AM

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

Good Morning everybody,

I started a next try, the mmc is running on green, the login starts up and......failed.

So the network setting seems to be correct.

The log files included following:

..........................................(just the last lines).............................

M

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

M *

M * LOCATION SAP-Server BASIS_A23_00 on host BASED (wp 0)

M * ERROR ThSigHandler: signal

M *

M * TIME Mon Nov 26 08:06:26 2009

M * RELEASE 700

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 11

M * MODULE thxxhead.c

M * LINE 10688

M * COUNTER 1

M *

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

M

M PfStatDisconnect: disconnect statistics

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >SAP-Trace buffer write< for event BEFORE_DUMP

M TrThHookFunc: called for WP dump

M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP

M ThrSaveSPAFields: save spa fields

M Entering ThSetStatError

M ThIErrHandle: incomplete previous roll out, do a full roll out

M ThRollOut: roll out T17/U25/M0/I0 (level=7, short_roll_out=0)

M ThRollOut: call rrol_out (1)

M ThRollOut: act roll state = DP_ROLLED_OUT

M ThRollOut: roll level <> 0, don't call ab_rollout

M ThRollOut: full roll out of U25 M0 I0 (Level 7) ok

M ThIErrHandle: prv_action of W0: 0x8

M ThCallDbBreak: use db_sqlbreak

C CANCEL rejected, because there is no SQL statement active

M ThIErrHandle: don't try rollback again

M ThIErrHandle: call ThrCoreInfo

A TH VERBOSE LEVEL FULL

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A ** RABAX: level LEV_RX_ROLLBACK entered.

A ** RABAX: level LEV_RX_ROLLBACK completed.

A ** RABAX: level LEV_RX_DB_ALIVE entered.

A ** RABAX: level LEV_RX_DB_ALIVE completed.

A ** RABAX: level LEV_RX_HOOKS entered.

A ** RABAX: level LEV_RX_HOOKS completed.

A ** RABAX: level LEV_RX_STANDARD entered.

A ** RABAX: level LEV_RX_STANDARD completed.

A ** RABAX: level LEV_RX_STOR_VALUES entered.

A ** RABAX: level LEV_RX_STOR_VALUES completed.

A ** RABAX: level LEV_RX_C_STACK entered.

A ** RABAX: level LEV_RX_C_STACK completed.

A ** RABAX: level LEV_RX_MEMO_CHECK entered.

A ** RABAX: level LEV_RX_MEMO_CHECK completed.

A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.

A ** RABAX: level LEV_RX_INTERFACES entered.

A ** RABAX: level LEV_RX_INTERFACES completed.

A ** RABAX: level LEV_RX_GET_MESS entered.

A ** RABAX: level LEV_RX_GET_MESS completed.

A ** RABAX: level LEV_RX_INIT_SNAP entered.

A ** RABAX: level LEV_RX_INIT_SNAP completed.

A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.

A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.

A ** RABAX: level LEV_RX_WRITE_SNAP entered.

M ThContextId: context_id = >0001700020019C010D31F2D5BD12D1714B103838<

M ThContextId: context_id_uuid = {29019C01-7F24-F235-BD12-D1714B103838}

M ThGetTransId2: got trans id (spa) >29019C017F24F239BD12D1714B103838< (32)

A ** RABAX: level LEV_SN_END completed.

A ** RABAX: level LEV_RX_SET_ALERT entered.

A ** RABAX: level LEV_RX_SET_ALERT completed.

A ** RABAX: level LEV_RX_COMMIT entered.

A ** RABAX: level LEV_RX_COMMIT completed.

A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.

A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.

A ** RABAX: level LEV_RX_RESET_PROGS entered.

A ** RABAX: level LEV_RX_RESET_PROGS completed.

A ** RABAX: level LEV_RX_STDERR entered.

A ** RABAX: level LEV_RX_STDERR completed.

A ** RABAX: level LEV_RX_RFC_ERROR entered.

A ** RABAX: level LEV_RX_RFC_ERROR completed.

A ** RABAX: level LEV_RX_RFC_CLOSE entered.

A ** RABAX: level LEV_RX_RFC_CLOSE completed.

A ** RABAX: level LEV_RX_IMC_ERROR entered.

A ** RABAX: level LEV_RX_IMC_ERROR completed.

A ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A ** RABAX: level LEV_RX_ERROR_SAVE entered.

A ** RABAX: level LEV_RX_ERROR_SAVE completed.

A ** RABAX: level LEV_RX_ERROR_TPDA entered.

A ** RABAX: level LEV_RX_ERROR_TPDA completed.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

M RmCleanUpResources3: hdr/tbl/ext_tbl/free/keep = 000000000F67D3C8/0000000000000000/0/0/1

M RmCleanUpResources3: no resources registered

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A ** RABAX: level LEV_RX_END entered.

A ** RABAX: level LEV_RX_END completed.

A ** RABAX: end RX_RETURN

M ThIErrHandle: ThrCoreInfo o.k.

M ThIErrHandle: Entering ThReplyToMsg

M ThIErrHandle: Entering ThErrHdlUser

M ThErrHdlUser: set th_errno (11)

M ThErrHdlUser: save context

M ThEmContextDetach2: detach T17/M0 from em memory (em_hdl=0, force=0)

M ThEmContextDetach2: reset local em info

B Disconnecting from ALL connections:

B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost

B 000 000 R/3 000000000 ACTIVE YES YES NO 000 255 255 20401126 080533 BASIS

C Disconnecting from connection 0 ...

C Now I'm disconnected from SAP DB

B Disconnected from connection 0

B statistics db_con_commit (com_total=4, com_tx=0)

B statistics db_con_rollback (roll_total=1, roll_tx=0)

M ***LOG Q02=> wp_halt, WPStop (Workproc 0 816) [dpnttool.c 327]

M return from clean-up function ...

-


and:

-


trc file: "dev_disp", trc level: 1, release: "700"

-


sysno 00

sid A23

systemid 562 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 144

intno 20050900

make: multithreaded, Unicode, 64 bit, optimized

pid 2928

Mon Nov 26 08:03:01 2009

kernel runs with dp version 232000(ext=109000) (@(#) DPLIB-INT-VERSION-232000-UC)

length of sys_adm_ext is 576 bytes

      • SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (00 2928) [dpxxdisp.c 1243]

shared lib "dw_xml.dll" version 144 successfully loaded

shared lib "dw_xtc.dll" version 144 successfully loaded

shared lib "dw_stl.dll" version 144 successfully loaded

shared lib "dw_gui.dll" version 144 successfully loaded

shared lib "dw_mdm.dll" version 144 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3900

Mon Nov 26 08:03:10 2040

      • WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 9 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5371]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >BASIS_I23_00 <

DpShMCreate: sizeof(wp_adm) 25168 (1480)

DpShMCreate: sizeof(tm_adm) 5652128 (28120)

DpShMCreate: sizeof(wp_ca_adm) 24000 (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: 000000000D800050, size: 6348592)

DpShMCreate: allocated sys_adm at 000000000D800050

DpShMCreate: allocated wp_adm at 000000000D802150

DpShMCreate: allocated tm_adm_list at 000000000D8083A0

DpShMCreate: allocated tm_adm at 000000000D808400

DpShMCreate: allocated wp_ca_adm at 000000000DD6C2A0

DpShMCreate: allocated appc_ca_adm at 000000000DD72060

DpShMCreate: allocated comm_adm at 000000000DD73FA0

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 000000000DDFAC30

DpShMCreate: allocated gw_adm at 000000000DDFACB0

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 000000000DDFACE0

DpShMCreate: allocated wall_adm at 000000000DDFACF0

MBUF state OFF

DpCommInitTable: init table for 500 entries

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( 4093MB) not multiple of em/blocksize_KB( 4096KB)

<ES> Info: em/initial_size_MB rounded up to 4096MB

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

<ES> 1023 blocks reserved for free list.

ES initialized.

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1633]

***LOG Q0K=> DpMsAttach, mscon ( BASIS) [dpxxdisp.c 11822]

DpStartStopMsg: send start message (myname is >BASIS_I23_00 <)

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 60000000 for monitoring segment.

Mon Nov 26 08:03:11 2040

CCMS: start to initalize 3.X shared alert area (first segment).

DpMsgAdmin: Set release to 7000, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]

DpMsgAdmin: Set patchno for this platform to 144

Release check o.K.

Mon Nov 26 08:03:17 2040

MBUF state ACTIVE

DpModState: change server state from STARTING to ACTIVE

Mon Nov 26 08:04:26 2040

SoftCancel request for T17 U18 M0 received from IC_MAN

SoftCancel request for T19 U20 M0 received from IC_MAN

      • ERROR => DpWpKill(3092, SIGUSR2) failed [dpxxtool.c 2496]

Mon Nov 26 08:04:30 2040

      • ERROR => DpHdlDeadWp: W0 (pid 3200) died [dpxxdisp.c 14532]

Mon Nov 26 08:04:31 2040

      • ERROR => DpHdlDeadWp: W1 (pid 3220) died [dpxxdisp.c 14532]

DpHdlDeadWp: restart wp (pid=3092) automatically

      • ERROR => DpHdlDeadWp: W3 (pid 3296) died [dpxxdisp.c 14532]

DpHdlDeadWp: restart wp (pid=3268) automatically

      • ERROR => DpHdlDeadWp: W10 (pid 2032) died [dpxxdisp.c 14532]

      • ERROR => DpHdlDeadWp: W15 (pid 3312) died [dpxxdisp.c 14532]

Mon Nov 26 08:04:45 2040

      • ERROR => DpRqCheck: mode 0 in status CANCEL [dpxxdisp.c 6971]

Mon Nov 26 08:05:10 2040

      • ERROR => DpHdlDeadWp: W4 (pid 3260) died [dpxxdisp.c 14532]

Mon Nov 26 08:05:30 2040

      • ERROR => DpHdlDeadWp: W0 (pid 3788) died [dpxxdisp.c 14532]

      • ERROR => DpHdlDeadWp: W1 (pid 2108) died [dpxxdisp.c 14532]

      • ERROR => DpHdlDeadWp: W6 (pid 3108) died [dpxxdisp.c 14532]

      • ERROR => DpHdlDeadWp: W15 (pid 464) died [dpxxdisp.c 14532]

Mon Nov 26 08:05:33 2040

      • ERROR => DpRqCheck: mode 0 in status CANCEL [dpxxdisp.c 6971]

-


The kernel is not patched. I just (try) to install the kernel files from the sap market place

IDES download destination. The install kernel file was: 51033508_7 - NW7 SR3 Kernel 7.00 for Windows / LNX X86_X64. I got an update / upgrade file, which is called: 51033508_8 - NW7 SR3 Kernel .... Upg ABAP.

Can anybody give me an adwise by reading those logfiles? Is the file ok for updating the kernel?

How do I upgrade the kernel by having no .exe - file? May the installation go on after patching the kernel?

Thanks you really much

Lenvy

Former Member
0 Kudos

Hello Subhash,

thanks for link - it helped me to reset the SAP* password in maxdb. The operation was succesfull executed by the sql prompt for SAP* (usr01/usr02) as SAP<SID> user. But, after I proofed every step 2 or more times, wtih:

- changing the default.pfl to open the user SAP*

- writing the sql prompt to the database, to reset the SAP* password

- restarting the components and

- retry the logon with SAP*/PASS on client 000/800 to change the SAP User settings for DDCI with TA SU01

the original problem still exist. I can't logon to the application server with the mmc or even with SAPLogon. The programm just told me, that the "Work process restarted, session ........" The mmc looks fine, but it seems that there

is no connection...

That brings me back to the loopback adaptor settings. Are there relevant or just settings? My windows network connecting shows always a limited connectivity. Is the kernel update a second chance to bring me back into the installation progress? What is wrong in the settings (IP, etc.) or which step did I miss?

Thanks and Regards

Lenvy

former_member185031
Active Contributor
0 Kudos

Hello Lenvy,

If your SAP login screen is coming by clicking on Sap Gui then there is not any issue with IP Address. The only concern is that your SAP Server is properly running on, you can check in SAP MMC console, where all the process should be green. Once your login screen is appeared, then login into client 000 via SAP* and pass and then changed the password of DDIC. and continue the instalation. if you find grey or yellow process in SAP MMC console then check the log files under C:\usr\sap\SID\*\work directory and paste the error here from the log files

dev_w*

dev_disp

Regards,

Subhash

Former Member
0 Kudos

A short update:

I have installed the MaxDB Database Studio yet. I can now logon to the MaxDB Database with the account "SUPERDBA" using the password from the installation. But I don't know how to change the SAP* account via the SQL command, like it is mentioned for oracle. So what is to do next? Is that the right way to solve the problem.

Can anybody give more inputs please.....

former_member185031
Active Contributor
0 Kudos

Hello Lenvy,

Please check this thread, it will help to reset the password of SAP* in maxdb

Regards,

Subhash

Former Member
0 Kudos

I started the whole system again and put the account data into the mmc. The errorcode is still the same, "SAP logon failed: connection closed without message".

So what should i do with the sql line? Can anybody give me some details, or quote a thread?

What is with the kernel update? Is this solving the problem of the DDIC password to continuing the installation....

A lot of questions, can anybody help?

Former Member
0 Kudos

What is your kernel patch level ?

Update your kernel to latest patch level and retry.

Regards,

Nikunj Thaker.

Former Member
0 Kudos

Hello Subhash,

So in this case the default.pfl is edited correct and the setting of the ms loopback is also right?

I will try to logon as you mentioned and use the client 000 / user SAP* and my installation password.

If this failed - where can I find the SQL prompt? Is this related to the databank, in this case maxdb?

Can you explain it more detailed?

Thanks

Lenvy

Former Member
0 Kudos

Hello Anjali Sharma

First - I started again shutting the databank instance down and editing the default.pfl by putting the parameter: login/no_automatic_user_sapstar = 0 in de DEFAULT.PFL and restart the instance. In order to that my default.pfl looks like this:

SAPDBHOST = BASED

j2ee/dbtype = sap

j2ee/dbname = A28

j2ee/dbhost = BASED

j2ee/dbadminurl = http://BASIS:9999/webdbm?Server=BASED&Database=A28&User=control

SAPSYSTEMNAME = A28

SAPGLOBALHOST = BASED

rdisp/bufrefmode = sendoff,exeauto

#----


  1. SAP Message Server for ABAP

#----


rdisp/mshost = BASED

rdisp/msserv = sapmsA28

rdisp/msserv_internal = 3900

#----


  1. SAP Message Server for ABAP

#----


login/system_client = 001

login/no_automatic_user_sapstar = 0

But the problem still exist. The error code is exactly the same and the installation instance will not prompt for a new password for the DDIC User. Did I miss something? What is with the TA RZ11 - I cannot use them, because I am still not logon to the system

Second is the MS Loopback Adaptor. My current settings in the TCP/IPv4 are: IP address: 192.100.10.1 and the subnet mask is already: 255.255.255. 0 - I have set no default gateway. Are these setting right, or did I have to use different or additional settings? The windows firewall is down but my connecting is still: u201CLimitedu201D - Is that alright?

I think I am getting mad with this installation,-(

Meanwhile i have read the note: 68048 / 8852 and the given threads again and again, but still the same problem.

Any guess??

former_member185031
Active Contributor
0 Kudos

Hello Lenvy,

1.You can login into client 000 by SAP* and password will be your master password then you can chage the password of DDIC

2. If the user SAP* has already locked due to incorrect login in client 000 then you have to delete the password of SAP* from SQL prompt.

3. Then you can login into client 000 by SAP* ans password pass then you can change the password if DDIC in client 000 and then you can continue the installation.

Regards,

Subhash

Former Member
0 Kudos

Yes, that thread will help you and you may want to see the following too for clear understanding

Note 68048 - Deactivating the automatic SAP* user

And, if you already did set the ms loopback adapter and IP, then it should not cause any problem now.