Solution Manager Diagonostic Agent:Start Error

Hi All,
We are facing problem while starting SMD agent in Solution Manager System in I series.
The Landscape browser in the Solution Manager Diagnostics shows SMD Agent Status : Agent not found.
We tried starting the same through: \usr\sap\SMD\J98\script but while doing so we were getting following error:
Starting at 2010/01/14 16:24:21
Startup Profile: "/usr/sap/SMD/SYS/profile/START_J98_SPLBWPRD"
Starting Programs
14.01.2010 16:24:21
ShmDetach
FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fop
en()
(2465) Spawning program "/usr/sap/SMD/exe/jcontrol pf=/usr/sap/SMD/SYS/profil
e/SMD_J98_SPLBWPRD" asynchronously...
Any inputs are much appreciated.
Regards,
Prasad

I just saw a different forum with NIECONN_REFUSED, his was fixed after the port number was corrected.
Try 5xx04.
Edited by: Ryan Cossette on Jan 18, 2010 6:47 PM

Similar Messages

Solutions Manager 700--Not Starting up -Urgent

Hi,
My solutions manager is not starting up.
The message I get is the following;
When restrart the system I get the
1.message " Process disp+Work is starteed but not connected.
2. Later I get the message I get is " disp+work is stopped"
How do I get around it !!
urgent please

Nice to see your response Here is the trace file info :
[Thr 4584] Thu May 24 11:53:31 2007
[Thr 4584] JLaunchRequestFunc: receive command:17, argument:0 from pid:3048
[Thr 4584] JLaunchIShutdownInvoke: set shutdown interval (stop:1180032811/end:1180032931/TO:120)
[Thr 4584] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 4584] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 276] JLaunchISetP4Port: set p4 port 50104
[Thr 276] JLaunchISetHttpPort: set http port 50100
[Thr 3820] JLaunchISetP4Port: set p4 port 50104
[Thr 276] JLaunchISetHttpsPort: set https port 50101
[Thr 2184] JLaunchISetState: change state from [Running (3)] to [Waiting for stop (4)]
[Thr 2184] JLaunchISetState: change state from [Waiting for stop (4)] to [Stopping (5)]
[Thr 5440] Thu May 24 11:53:37 2007
[Thr 5440] JLaunchISetP4Port: set p4 port 50104
[Thr 5172] Thu May 24 11:53:39 2007
[Thr 5172] JLaunchISetHttpsPort: set https port 50101
[Thr 5172] JLaunchISetHttpPort: set http port 50100
[Thr 4620] Thu May 24 11:53:41 2007
[Thr 4620] JLaunchISetHttpPort: set http port 50100
[Thr 3404] JLaunchISetHttpPort: set http port 50100
[Thr 3036] Thu May 24 11:53:53 2007
[Thr 3036] JLaunchISetTelnetPort: set telnet port 50108
[Thr 4304] Thu May 24 11:53:54 2007
[Thr 4304] JLaunchISetHttpPort: set http port 50100
[Thr 2184] Thu May 24 11:53:59 2007
[Thr 2184] JLaunchISetState: change state from [Stopping (5)] to [Stopped (6)]
[Thr 4492] Thu May 24 11:54:02 2007
[Thr 4492] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 4492] JLaunchCloseProgram: good bye (exitcode = 0)

Install ECC 6.0 and Solution Manager on same server Error (MaxDB/Linux)

I have installed Solution manager on one server and then ECC 6 also in the same server with another SID. during the installation it errored out at phase "SLD configuration" with UME error , J2EE_ADMIN locked etc..we checked the user id and noticed it got locked in ECC 6 system and we unlocked it.
But after the ECC installation the solution manager java engine is not coming up error with "com.sap.security.core.ume.service failed" error. Prior to the ECC installation the Solution Manager J2EE was working.
thanks in advance
Mathew

error in the /j2ee/cluster/server0/log/defaultTrace.1.trc
is as follows
#1.5#00137256A483001E0000001700006F190004163784D40864#1150327614343#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_61##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
When I looked at using jcmon the dispacher is up and the server0 and SDM is down

Solution Manager 4.0 Installation Error AIX 5.3 / Oracle 10.2.0.1

Hi All,
I am facing an error in the installation step of Solution Manager 4.0 on AIX 5.3 / Oracle 10.2.0.1
Hostname : INXXXXSAPIDES
The ABAP instance is not coming up and the Installation failed.I tried to bring up the instance manually.But was not successful.
Workprocess traces :
S queue size (profile) = 300
S hostspool list size = 3000
S option list size is 30
S found processing queue enabled
S found spool memory service RSPO-RCLOCKS at 0x7000001732fa070
S doing lock recovery
S setting server cache root
S found spool memory service RSPO-SERVERCACHE at 0x7000001732fa470
S using messages for server info
S size of spec char cache entry: 297032 bytes (timeout 100 sec)
S size of open spool request entry: 2176 bytes
S immediate print option for implicitely closed spool requests is disabled
A
A -PXA--
A PXA INITIALIZATION
A System page size: 4kb, total admin_size: 5720kb, dir_size: 5664kb.
A Attached to PXA (address 0x7000001e0000000, size 150000K)
A abap/pxa = shared unprotect gen_local
A PXA INITIALIZATION FINISHED
A -PXA--
A
Signal 6 encountered.
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = unlimited
=> Core limit = unlimited
=> File size limit = unlimited
=> Heap address = 0x0x113a1f5c0
=> Stack address = 0xfffffffffffded0
=> Stack low = 0xfffffffffffb5e0
=> Stack high = 0xffffffffffff810
=> Stack Trace:
 pthread_kill() at 0x900000000490650
 praise() at 0x900000000490070
 raise() at 0x900000000059624
 abort() at 0x900000000084a90
TrThHookFunc: called for WP dump
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 720]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 260]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M ThErrPrivHandle: set th_errno (11)
M Entering ThReadDetachMode
M *** ERROR => ThIErrHandle: bad value for th_act_em_hdl (8), detach T0/M0 [thxxhead.c 10721]

DEV_DISP 
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
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 102
Release check o.K.
Sat Jul 28 22:41:18 2007
ERROR => W0 (pid 442462) died [dpxxdisp.c 14319]
ERROR => W2 (pid 635048) died [dpxxdisp.c 14319]
ERROR => W3 (pid 598164) died [dpxxdisp.c 14319]
ERROR => W4 (pid 770084) died [dpxxdisp.c 14319]
ERROR => W5 (pid 815142) died [dpxxdisp.c 14319]
ERROR => W6 (pid 761862) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0xbf --> 0xbd
ERROR => W7 (pid 671804) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0xbd --> 0xb9
ERROR => W8 (pid 630958) died [dpxxdisp.c 14319]
ERROR => W9 (pid 622786) died [dpxxdisp.c 14319]
ERROR => W10 (pid 549070) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0xb9 --> 0xb1
ERROR => W11 (pid 544802) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0xb1 --> 0xa1
ERROR => W12 (pid 508062) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0xa1 --> 0x81
Sat Jul 28 22:41:55 2007
ERROR => W1 (pid 802934) died [dpxxdisp.c 14319]
my types changed after wp death/restart 0x81 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
stderr1
Command: dw.sapSM4_DVEBMGS10
 pf=/usr/sap/SM4/SYS/profile/SM4_DVEBMGS10_INSISCSAPIDES
ICM up and operational (pid: 675892) ***
timezone value meaningless. BSD libraries linked?
work process W1 died => ThSigHandler: signal
timezone value meaningless. BSD libraries linked?
work process W2 died => ThSigHandler: signal
timezone value meaningless. BSD libraries linked?
work process W12 died => ThSigHandler: signal
timezone value meaningless. BSD libraries linked?
.timezone value meaningless. BSD libraries linked?
work process W4 died => ThSigHandler: signal
work process W8 died => ThSigHandler: signal
timezone value meaningless. BSD libraries linked?
Can someone please help me in this.
Thanks
Siva
Message was edited by:
 siva sakthi

I found the solution..
There was a a problem in the timezone setting for the server.After changing it and rebooting it worked perfectely.

Solution Manager 4.0 SR2: Error during step 1 installPolicyArchive

Hi,
I faced a really annoying problem in first step of Installation of a SAP Solution Manager 4.0 SR2 on Suse Linux Enterprise Server 10.
The Installation hangs in Phase 1 installPolicyArchive.
I think i have passed all prerequisites before starting the Installation.
Perhaps for help:
i set the Environment Variables as follows:
JDK_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
JRE_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/jre
JAVA_BINDIR=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/bin
JAVA_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
SAPINST_JAVA_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
JAVA_ROOT=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
As you see Java Version is java-1_4_2-sun-1.4.2.11.
The Error in sapinst.log is as follows:
ERROR 2009-03-03 15:58:44
FSL-00001 System call failed. Error 2 (No such file or directory) in execution of system call 'realpath' with parameter (/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/jre/lib/security/local_policy.jar), line (346) in file (syuxclink.cpp).
ERROR 2009-03-03 15:58:44
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text undefined.
ERROR 2009-03-03 15:58:44
FCO-00011 The step installPolicyArchive with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_getJavaHome|ind|ind|ind|ind|1|0|NW_getJavaHome_jcePolicy|ind|ind|ind|ind|0|0|installPolicyArchive was executed with status ERROR .
Can anyone help me solve the problem?
Thanks beforehand and Best Regards,
C. Peifer

> I'm on 32 bit
Ok - then the JDK correct.
sapinst searches for a policy file, is the given filename there?
/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/jre/lib/security/local_policy.jar

Solution Manager 4.0 install Error

I am trying to install Solution Manager 4.0 on a IA64 server running Windows 2003(64 bit edition). I have SQL Server 2005. I have JDK versionj2sdk1.4.2_12-x64.
The sapinst.exe error log is as follows:
+++++++++++++++++++++++++++++++++++++++++++++++++++++
SAPINST.EXE error
ERROR 2006-08-09 11:00:23
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2006-08-09 11:00:23
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|
ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|
NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import
|ind|ind|ind|ind|0|0|runMigrationMonitor was executed
with status ERROR .
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
The Error entries in the Import_monitor log is as follows:
+++++++++++++++++++++++++++++++++++++++++++++++++
ERROR: 2006-08-09 10:39:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2006-08-09 10:39:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL0.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
++++++++++++++++++++++++++++++++++++++++++++++++++++
The error entry in the SAPSSEXC.log mention in the Import_monitor log is as follows:
++++++++++++++++++++++++++++++++++++++++++++++++++
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPSSEXC.TSK.bck already seems to exist
a previous run may not have been finished cleanly
file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPSSEXC.TSK possibly corrupted
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809103927
++++++++++++++++++++++++++++++++++++++++++++++++++++
The error entry in the SAPAPPL0.log mention in the Import_monitor log is as follows:
+++++++++++++++++++++++++++++++++++++++++++++++++
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPAPPL0.TSK.bck already seems to exist
a previous run may not have been finished cleanly
file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPAPPL0.TSK possibly corrupted
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809103927
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: START OF LOG: 20060809111000
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Apr 3 2006 02:55:14
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPAPPL0.TSK.bck already seems to exist
a previous run may not have been finished cleanly
file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPAPPL0.TSK possibly corrupted
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809111001
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please let me know.
Thanks
Mikir

Hello.
I'm currently installing SAP BW 3.50 on Oracle 10.2, Windows 2003, J2SDK 1.4.2_11. As of now, i've got an error when i put these reference:
SAP:BW-MMR:630_SP3_REL:::*
SAP:BW-SDK:630_SP3_REL:::*
Kindly help on how to resolve this.
Thanks.

Solution Manager 7.0 Installation Error on Import ABAP -Test DB connection

Hi, SDN fellows.
I am installing Solution Manager 7.0. In Step 16 of 44 - Import ABAP, I encountered an error when the installer was testing the database connection. It failed at this command:
R3load.exe -testconnect
Below is the error I copied from the log viewer. Thanks for all possible advices/suggestions to fix this issue.
=================
WARNING 2011-07-12 03:51:49.188
Execution of the command "C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect" finished with return code 2. Output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110712035148
(DB) ERROR: db_connect rc = 256
(DB) ERROR: DbSlErrorMsg rc = 99
WARNING[E] 2011-07-12 03:51:49.188
CJS-30023 Process call 'C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.
ERROR 2011-07-12 03:51:49.204
FCO-00011 The step testDatabaseConnection with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testDatabaseConnection was executed with status ERROR .
=============
KC

cont....
4 ETW000 33 1.576524
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum: 1112312
4 ETW000 24 1.576548
4 ETW000 [dev trc ,00000] DbSlRead - Error 103 (dbcode 208) on open 19 1.576567
4 ETW000 [dev trc ,00000] DbSlRead - <##Y4ISBDCAPPsm100000045960000000001234118>
4 ETW000 19 1.576586
4 ETW000 [dev trc ,00000] DbSlRead - Error 103 (dbcode 208) on fetch 13 1.576599
4 ETW000 [dev trc ,00000] DbSlRead - <##Y4ISBDCAPPsm100000045960000000001234118>
4 ETW000 18 1.576617
4 ETW000 [dblink ,01299] ***LOG BZA=>table SVERS does not exist on database [dblink#5 @ 1299]
4 ETW000 8060 1.584677
4 ETW000 [dev trc ,00000] Wed Jul 13 23:41:19 2011 41342 1.626019
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000002234118
4 ETW000 25 1.626044
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 3649 1.629693
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 33 1.629726
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000002234118]
4 ETW000 19 1.629745
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 27 1.629772
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000002234118]
4 ETW000 19 1.629791
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 COMPCNT FROM "DDNTT" ]
4 ETW000 28 1.629819
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 20 1.629839
4 ETW000 [dev trc ,00000] NTAB: SELECT COMPCNT FROM DDNTT FAILED 277 1.630116
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000003234118
4 ETW000 44 1.630160
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 459 1.630619
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 33 1.630652
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000003234118]
4 ETW000 18 1.630670
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 29 1.630699
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000003234118]
4 ETW000 23 1.630722
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 VERSION FROM "DDNTT" ]
4 ETW000 29 1.630751
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 20 1.630771
4 ETW000 [dev trc ,00000] NTAB: SELECT VERSION FROM DDNTT FAILED 267 1.631038
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000004234118
4 ETW000 43 1.631081
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 436 1.631517
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.631549
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000004234118]
4 ETW000 18 1.631567
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 58 1.631625
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000004234118]
4 ETW000 19 1.631644
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 DBASE FROM "DDNTT" ]
4 ETW000 28 1.631672
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.631693
4 ETW000 [dbntab.c ,00000] *** ERROR => NTAB: SELECT VERSION/DBASE FROM DDNTT FAILED
4 ETW000 284 1.631977
4 ETW000 [dbntab ,01276] ***LOG BZY=>unexpected return code 103 calling NTAB [dbntab#4 @ 12761]
4 ETW000 31 1.632008
4 ETW000 [twdydbacc.c ,00568] i:0 8690 1.640698
4 ETW000 [twdydbacc.c ,00569] db_fd_p.fname: PGMID 20 1.640718
4 ETW000 [twdydbacc.c ,00570] db_fd_p.is_key: 0 11 1.640729
4 ETW000 [twdydbacc.c ,00571] db_fd_p.offset: 0 10 1.640739
4 ETW000 [twdydbacc.c ,00572] db_fd_p.db_length: 0 10 1.640749
4 ETW000 [twdydbacc.c ,00573] db_fd_p.fixed_length:4 10 1.640759
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000005234118
4 ETW000 40 1.640799
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 434 1.641233
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.641265
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000005234118]
4 ETW000 75 1.641340
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 31 1.641371
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000005234118]
4 ETW000 18 1.641389
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 COMPCNT FROM "XXXXT" ]
4 ETW000 28 1.641417
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.641438
4 ETW000 [dev trc ,00000] NTAB: SELECT COMPCNT FROM XXXXT FAILED 269 1.641707
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000006234118
4 ETW000 44 1.641751
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 437 1.642188
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.642220
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000006234118]
4 ETW000 18 1.642238
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 28 1.642266
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000006234118]
4 ETW000 19 1.642285
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 VERSION FROM "XXXXT" ]
4 ETW000 27 1.642312
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 70 1.642382
4 ETW000 [dev trc ,00000] NTAB: SELECT VERSION FROM XXXXT FAILED 273 1.642655
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000007234118
4 ETW000 44 1.642699
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 435 1.643134
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.643166
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000007234118]
4 ETW000 19 1.643185
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 28 1.643213
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000007234118]
4 ETW000 20 1.643233
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 DBASE FROM "XXXXT" ]
4 ETW000 30 1.643263
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.643284
4 ETW000 [dbntab.c ,00000] *** ERROR => NTAB: SELECT VERSION/DBASE FROM XXXXT FAILED
4 ETW000 324 1.643608
4 ETW000 [dbntab ,01276] ***LOG BZY=>unexpected return code 103 calling NTAB [dbntab#4 @ 12761]
4 ETW000 27 1.643635
2EETW000 sap_dext called with msgnr "2":
2EETW000 -
db call info -
2EETW000 function: db_ntab
2EETW000 fcode: NT_RDTDESCR
2EETW000 tabname: TADIR
2EETW000 len (char): 5
2EETW000 key: TADIR
2EETW000 retcode: 2
4 ETW000 [dev trc ,00000] db_con_rollback (con_da={R/3,0,0},th_rollback=1,tx=0)
4 ETW000 9946 1.653581
4 ETW000 [dev trc ,00000] Rollback: TestConnection(1) successful 36526 1.690107

Solution manager 7.1 sp4 , error @Bytecode adpater installation

HI All,
 I am facing the below issue while executing the managed system wizard @ Bytecode adapter installation.
Error @ Managed system
Failed to create Introscope Agent Connector at: /usr/sap/SMD/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors: - java.io.IOException: Cannot run program "null/bin/java" (in directory "/usr/sap/SMD/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors"): java.io.IOException: error=2, No such file or directory.
Error @ Diagnostic agent level
Jun 6, 2014 10:52:31 AM [Thread[Thread-19,5,main]
] Error
Operation Failed :
[EXCEPTION]
com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 48161
at com.sap.smdagent.vmmanager.impl700.VMManager._getSettings(VMManager.java:170)
at com.sap.smdagent.vmmanager.impl700.VMManager.getSettings(VMManager.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:94)
at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:285)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.SecurityException: User is not authorized to access Configuration Manager.
at com.sap.engine.services.configuration.ConfigurationRuntimeInterfaceImpl.checkAuthorization(ConfigurationRuntimeInterfaceImpl.java:62)
at com.sap.engine.services.configuration.ConfigurationRuntimeInterfaceImpl.getConfigurationContext(ConfigurationRuntimeInterfaceImpl.java:48)
at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:159)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
1. As per standard note , patch levels are on sap recommended level only.
2. Created connector manually as per wily documentation , but still no use.
3. Given the permissions for temp,<SID>cluster etc.. as per sap notes and restarted all the services including sapstartsrv
4. Assigend SPML roles as suggested by note.
5. checked java environment and umask for diagnostic users , everything looks ok.
 Checked couple of notes related to the above issue ,
 1616058 - XSRF possible in SPML Services in AS Java
 1820230 - Byte Code Adapter Installation error in Solution Manager 7.1 Managed System Configuration step Configure Automatically
 1752441 - Introscope Agent Connector generation is done using JDK at: null

I would like paste few more error lines,
Jun 9, 2014 6:43:33 AM [Thread[FileSystemService_4cdecd7c,5,main]
] Error
[WHS] Failed to find javaPath for node 5818350
[EXCEPTION]
com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 58183
at com.sap.smdagent.vmmanager.impl700.VMManager._getSettings(VMManager.java:170)
at com.sap.smdagent.vmmanager.impl700.VMManager.getSettings(VMManager.java:156)
at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:94)
at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:285)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.SecurityException: User is not authorized to access Configuration Manager.

Solution manger daa agent giving error

Hi
i want to configure manged system in my solman, i got error with daa agenet iam unable to assigin the daa agent attached the screen shot 1.
i got the bellow error server name assignment on the agent failed. how to troubleshoot the issue
regards
vreddy

Hi,
prior to all, You need to register the agent either to the solution manager directly or to the SLD during the installation of diagnostic agent itself.
If you registered before only, you can see the agents in managed system configuration on step 4 'Assign Diagnostics Agent' -> Assign agent. Else you can see empty as in your image 2.
Please follow the below link and make sure you done registration of smd agents.
Diagnostics Agents - SAP Solution Manager Setup - SCN Wiki
Thanks
Jansii

Solution Manager Learning Map http error 403

Hi,
I created a new learning map in solution manager using solar_learning_map, when I attempted to display the learning map in the web browser i received the following error.
<URL> call was terminated because the corresponding service is not available.
The termination occurred in system ISD with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
If anyone else has experienced this error before can you please give me some guidance on resolving this issue.

The Note exists in service marketplace. (Topic is Inactive services in the Internet Comm Framework).Here is the solution as per the Note.
Solution
Listed below are some services that must be activated in the system
depending on the operational scenario:
Support for the Internet protocol (HTTP, HTTPS and SMTP) in the SAP Web Application Server
/default_host/sap/public/icman
Note: After you have installed SAP Web Application Server, you must ensure that this service is activated in transaction SICF. Through this the ICMan process can (for example) make decisions concerning the distribution of HTTP requests to the corresponding server.
Using load distribution
with the message server
/default_host/sap/public/icf_info
/default_host/sap/public/icf_info/logon_groups
/default_host/sap/public/icf_info/urlprefix
with the Web Dispatcher
/default_host/sap/public/icf_info
/default_host/sap/public/icf_info/icr_groups
/default_host/sap/public/icf_info/icr_urlprefix
Using Business Server Pages (BSP)
/default_host/sap/bc/bsp/sap
/default_host/sap/bc/bsp/sap/system
/default_host/sap/bc/bsp/sap/public/bc
/default_host/sap/public/bc (available for 620 with Support Package 34)
/default_host/sap/public/bc/ur (available for 620 with Support Package34)
/default_host/sap/public/bsp/sap/public
/default_host/sap/public/bsp/sap/public/bc
/default_host/sap/public/bsp/sap/system
/default_host/sap/public/bsp/sap/htmlb (as of Release 620 Support Package SAPKB62026)
Note: In addition to these general BSP services, you still have to activate the corresponding application services in the ICF tree. The service for the application is generally found under the ICF node /default_host/sap/bc/bsp/sap/<application>.
Using the BSP logon procedure
/default_host/sap/public/bsp/sap
/default_host/sap/bc/bsp/sap/system
/default_host/sap/public/bsp/sap/public
/default_host/sap/public/bsp/sap/system
BSP test applications for troubleshooting
/default_host/sap/bc/bsp/sap/it00
/default_host/sap/bc/bsp/sap/sbspext_htmlb
/default_host/sap/bc/bsp/sap/sbspext_xhtmlb
/default_host/sap/bc/bsp/sap/htmlb_samples
As of Release 6.30:
/default_host/sap/bc/bsp/sap/bsp_verificatio
Using Business Information Warehouse (BW)
/default_host/sap/bw
Web Applications
/default_host/sap/bw/BEx
/default_host/sap/bw/Mime
Reporting agent preliminary calculation
/default_host/sap/bw/ps
Drag and Relate in the portal
/default_host/sap/bw/dr
Data access using XMLA
/default_host/sap/bw/xml and all subordinate subservices
Document integration in the BEx Analyzer and Web Applications.
/default_host/sap/bw/doc and all subordinate subservices
Formatted reporting
/default_host/sap/bw/ce_url
Assignment of SAP icons
/default_host/sap/public/bc
/default_host/sap/public/bc/icons
/default_host/sap/public/bc/icons_rtl
/default_host/sap/public/bc/webicons
/default_host/sap/public/bc/pictograms
Assignment of Web Dynpro ABAP (WDA) applications
/default_host/sap/bc/webdynpro
/default_host/sap/public/bc
/default_host/sap/public/bc/ur
/default_host/sap/public/bc/icons
/default_host/sap/public/bc/icons_rtl
/default_host/sap/public/bc/webicons
/default_host/sap/public/bc/pictograms
/default_host/sap/public/bc/webdynpro/* (ssr, mimes, and so on)
/default_host/sap/public/myssocntl
Note: In addition to these general WDA services, the corresponding application services in the ICF tree also need to be activated. The service for the application is generally found under the ICF node /default_host/sap/bc/webdynpro/sap/<application>.
Assignment of Web Dynpro ABAP (WDA) development environment
/default_host/sap/bc/webdynpro/sap/public/bc/viewdesigner/
/default_host/sap/bc/wdvd/
/default_host/sap/bc/webdynpro/sap/configure_application
/default_host/sap/bc/webdynpro/sap/configure_component
/default_host/sap/bc/webdynpro/sap/wd_analyze_config_appl
/default_host/sap/bc/webdynpro/sap/wd_analyze_config_comp
/default_host/sap/bc/webdynpro/sap/wd_analyze_config_user
Note: These ICF nodes are used for the WDA configuration editor ONLY. The nodes are only allowed to be active in a development system, and under no circumstances in a production system (due to a security risk).
WDA test applications for troubleshooting
/default_host/sap/bc/webdynpro/sap/wdr_test_events
/default_host/sap/bc/webdynpro/sap/wdr_test_ui_elements
/default_host/sap/bc/webdynpro/sap/wdr_test_table
/default_host/sap/bc/webdynpro/sap/wdr_test_popups_rt
ICF test applications:
/default_host/sap/bc/echo
Among other things, this service returns information about the registration procedure being used, the header and form fields, and the generated SSO cookie for the executed request. Therefore, this service should only be activated for troubleshooting purposes.
/default_host/sap/bc/error
This service generates some error situations in the system and should only be activated for troubleshooting purposes.
/default_host/sap/bc/srt/xip/sap
You want to fix the Web service error message "Could not determine WSDL address (ICF_ERROR), SRT_REG038" in connection with XI services.
Using Support Package SAPKB62006, the following problems were solved in connection with inactive services:
The "RAISE_EXCEPTION" ABAP runtime error no longer occurs for an inactive host.
The error text "Forbidden" was replaced with "Service is not active" for an inactive service.
Thanks
Sudhan Shan

Solution Manager Diagnostics: Agent Architecture

Hi there,
current I write a degree dissertation about Solution Manager Diagnostics. In different books, documentations and manuals I read about Agents which must be installed on the managed system. But I find no exactly description about the agents architecture. In a book about the Solution Manager is written, that the structure includes two tiers. The first tier are the core agents, but there is nothing explained about the second tier ... Is a core agent the same like a host agent?
Can anybody explain me (exactly) the differnt functions of the agents (core, host, diagnostics, wily-agent)?? Or maybe some links will be helpful.
Thanks and best regards,
Andreas

> Can anybody explain me (exactly) the differnt functions of the agents (core, host, diagnostics, wily-agent)?? Or maybe some links will be helpful.
I would start with
http://service.sap.com/diagnostics
There are lots of (detailed) documentations available.
Markus

Solution Manager Diagnostics Self Check Error with Enterprise Manager

I'm trying to get the Solution Manager Self Diagnostics Self Check running,
but I'm always getting the follwing Error:
The Enterprise Manager on host 'hdeas81' and port '6443' cannot be reached.
The Log File of the Introscope Manager shows the following line:
6/29/09 01:15:36 PM CEST [INFO] [Manager.PostOfficeHub] Server listening for incoming ssl socket connections on port 6443
Netstat -a is also showing that Port 6443 is open and Listening.
The Port is also reachable via telnet.
any suggestions what might be the problem?
Thanks in advance
Marco

thanks, but i'm trying to get a ssl connection on port 6443.
I have also another error in the diagnostics check (maybe related)
An unexpected error occured
in Detail i get the error:
java.lang.RuntimeException: Error while silently connecting: org.w3c.www.protocol.http.HttpException: Connection refused: connect
     at org.w3c.www.protocol.http.HttpURLConnection.error(Unknown Source)
     at org.w3c.www.protocol.http.HttpURLConnection.checkReply(Unknown Source)
     at org.w3c.www.protocol.http.HttpURLConnection.getResponseCode(Unknown Source)
     at com.sap.sup.admin.selfcheck.checks.helper.HttpHelper.getHttpResponseCode(HttpHelper.java:48)
     at com.sap.sup.admin.selfcheck.checks.wily.em.UICheck.process(UICheck.java:78)
     at com.sap.sup.admin.selfcheck.fwk.check.AbstractCheck.processImpl(AbstractCheck.java:165)
     at sun.reflect.GeneratedMethodAccessor541.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)
     at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
     at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:274)
     at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)
     at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
     at java.lang.Thread.run(Thread.java:534)

Solution Manager 4.0 Installation Error

am doing the Solution Manager 40 installation on AIX as root.
FYI: We are using central SLD.
During the installation in phase 30 "check DDIC password"
Sapinst stops with the following error.
In sapinst.log the error is:
In the installation log it says ERROR 2006-09-01 16:53:47
FRF-00025 Unable to call function. Error message: Large time
difference between application server a .
INFO 2006-09-01 16:53:47
RFC connection closed.
In sapinst_dev.log the error is:
FCO-00011 The step runRUTTTYPSET with step key
|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_I
nstance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|1|0|runRUTTTYPSET
was executed with status ERROR .
I did tried retry,stopped exit out and stopsap and stared again.
Even I upgraded it to the latest kernel(75) and tried again but no luck.
I see the follwoing error in dev_w0:
A Large time difference between application server and database..
A
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 13155]
A *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY
MODE. [zdate.c 1390].
Should I rollback to the old kernel which was 52, which came with
installation DVD's ?
The permissions of /usr/sap/trans and files and dir below is ok and owned by sidadm.
Does anyone has any idea ?
Thanks & Regards
Haq

Hi,
Could you please tell me what was the solution to this error. I am facing the similar issue.
Please help, thanks
Regards,
Nitin Nayyar

Solution Manager 4.0 Installation error on vmware

Hi guys,
I try to install the solution Manager 4.0 SR4 in a vmware server Win2003 64bit
and get the following error message in phase 17 (import ABAP)
Execution of the command "C:\j2sdk1.4.2_17-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 2. Output:
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Required system resources are missing or not available:
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 1\EXP1' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 1\EXP2' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 2\EXP3' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 2\EXP4' does not exist.
of course the path exists and the further dvd locations where also found?
is ther something wrong with the naming of the install dir?
must I have a character for the "harddrive"
Plse help
thank you and br
Wolfgang

Hello shareef,
there is no extra recommendation from SAP regarding SolMan on vmware.
SAP supports installations on vmware wheanwhile also for productive systems (plse check PAM).
The experience I have for my installation:
I works fine til now, no probs.
cu Wolfgang

Solution Manager 4.0 install error logging in for DDIC step 29

Has anyone else seen the error 'Test logon to SAP System <sid> failed"? It states that it cannot login for DDIC. This is at step 29 during the install of the solution manager 4.0.
We are running on a Windows 2003 Server/Oracle 10g.
Any help would be greatly appreciated. We've been hitting this same error for the last couple of days.
Thanks,
DBB

Dear Derrick,
I have run into the exact same problem!!!!
During step 29 of the install does it ask you to enter the DDIC password?
It will ask you twice for a password if both the times the login fails then you will have no other option but to uninstall and reinstall Sol Man 4.
The tactic that worked for me is that when it will ask u the passowrd the first time.......before you enter the password.......login in to Sol Man 4 using the default DDIC password 19920706. then change the default password. And then go back to the install and give this new ddic password.
This is the only thing that worked with me.
Let me know if anything else works.
Email me @ [email protected] if you have any other questions.
thanks
Mikir

Solution Manager Diagonostic Agent:Start Error

Similar Messages

Maybe you are looking for