Error in logfile of Solution Manager on iSeries (AS/400)

Hi all,
We run Solution Manager on (IBM) iSeries (AS/400) and when run SAPOSCOLL the program gives an large spoolfile with the following error codes:
      O4PRTLIB Loaded as /sapmnt/SOL/exe/O4PRTLIB
Remote Call Failed in O4PRTLIB::pf_dlpar_get_info
Errno = 2
FILE=pfas41c2.c - LINE=1883
SharedLibCache Information:
Search Path:
     /sapmnt/SOL/exe
     *LIBL
     /usr/sap/SOL/SCS61/work
     /usr/sap/SOL/SYS/exe/run
     /QOpenSys/usr/bin
     /usr/ccs/bin
     /QOpenSys/usr/bin/X11
     /usr/sbin
     /usr/bin
     /usr/sap/SOL/SYS/exe/run
Load Cache:
Does anyone know what the error means and how to resolve this ??
With kind regards
Herman Haan
IB-Groep (Groningen, The Netherlands)

Hi,
I guess you added the entry in /etc/hosts after you got the error.
That being true, stop and start your sapinst again. This will allow you to continue. The information is cached and the only way is to stop and start sapinst.
Cheers,
Amerjit

Similar Messages

Error in RFC & to Solution Manager System

Hi,
Error in RFC & to Solution Manager System
can anyone tells me why this error occurs???
With regards
kulwinder

FYI
We have just had same issue thaat in certain scenarios with RFC communication BACK to Solution Manager from Satellite system we got the error. We resolved this by looking at the RFC user used in the BACK connection (i.e. SOLMAN<SID>) on the Solution Manager and changing the user type from communications.
Hope this helps someone else, I spent ages digging around for an answer to such a simple fix
Paul

Error in Installation of Solution Manager on Virtualbox centOS

Error in Installation of Solution Manager on Virtualbox centOS .
I tried as per the solution given in the error.
Please go through attachment for error and my /etc/hosts file.

Hi,
I guess you added the entry in /etc/hosts after you got the error.
That being true, stop and start your sapinst again. This will allow you to continue. The information is cached and the only way is to stop and start sapinst.
Cheers,
Amerjit

I got errors while installation of solution manager 4.0 sr2

I faced the errors below while installing Solution Manager 4.0 sr2.
How can I solve these problems?
Thanks.
ERROR 2007-03-13 17:30:12
FSL-00001 System call failed. Error 13 (Permission denied) in execution of system call 'openU' with parameter (/opt/cdler/CD2/IM_HPUX_PARISC/COMMON/INSTALL/JDBCCONNECT.JAR, O_RDONLY), line (368) in file (syuxcfile.cpp).
ERROR 2007-03-13 17:30:12
FSL-02015 Node /opt/cdler/CD2/IM_HPUX_PARISC/COMMON/INSTALL/JDBCCONNECT.JAR does not exist.
ERROR 2007-03-13 17:30:12
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text undefined.
ERROR 2007-03-13 17:30:12
FCO-00011 The step copyScripts with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_Unpack|ind|ind|ind|ind|8|0|copyScripts was executed with status ERROR .

Hello Cemil,
The errors you are recieving are most likely user or permissions
related.
Can you please verify that there are 777 permissions on the
installation directories? Also are you installing as User Root?
Are you installing from an NFS Mount or network drive? If so it could be
possible that the user does not have enough permissions on this. If
so I recommend copying the installation files to a local directory and
retrying the installation from there.
Best regards,
Dolores

Error in SAPinst installing Solution Manager

SAP Solution Manager 4 Support Release 4
OS: UNIX 11.23
DB: Oracle 10g
Hi,
    The SAPinst show me this error in the step: Configure Adobe Document Services when I trying to install the Solution Manager:
ERROR      2010-01-14 10:20:50.804
           CJSlibModule::writeError_impl()
CJS-30059 Java EE Engine configuration error. DIAGNOSIS: See output of logfile java.log: 'IO EXCEPTION: Connection refused (errno:239):: '.
ERROR      2010-01-14 10:20:51.384 [sixxcstepexecute.cpp:951]
FCO-00011 The step createGroupADSCallers with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|6|0|NW_Usage_Types_Configuration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_ADS|ind|ind|ind|ind|2|0|createGroupADSCallers was executed with status ERROR ( Last error reported by the step :Java EE Engine configuration error. DIAGNOSIS: See output of logfile java.log: 'IO EXCEPTION: Connection refused (errno:239):: '.).
I try to find a note or something but I don't have a solution yet...
Thanks a lot for the help!!

Hi digeshjoshi,
      I check all the software that I'm using and is for a 64bit system, is correct because our machine is PARISK 64 bit.
Right now I'm using the SAPinst: SAPINST7001_4-20002035.SAR, I see that exist other one new but I don't think that's can be a problem.

Runtime Errors Raise Exception in Solution Manager

Hi Guru's,
While I try to excute the transaction solman_issue_mgnt in solution manager for issue tracking, runtime errors occurs.
Error analysis
    A RAISE statement in the program "CL_GUI_HTML_VIEWER============CP" raised the
     exception
    condition "CNHT_ERROR_PARAMETER".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
Could anyone suggest me on this issue.
regards,
Guna

Hi Juan,
As per the note, everything was fine there. We have SAP_Basis 700 with SP16.
Earlier it was worked fine. Now only we are facing this issue while excuting the t-code solman_issue_mgmt.
regards,
Guna

Errors during install of Solution Manager 7.0 w/MaxDB (central)

Hi
I am trying to install Solution Manager 7.0 w/MaxDB on a linux box. I have reached phase 47/50 and am running into errors that say:
ERROR 2011-07-14 16:29:54.609
CJS-30151 Java process server0 of instance OSM/DVEBMGS00 [ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)] did not start after 1:30 minutes. Giving up.
ERROR 2011-07-14 16:29:54.757
FCO-00011 The step startJava with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|6|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0|startJava was executed with status ERROR ( Last error reported by the step :Java process server0 of instance OSM/DVEBMGS00 [ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)] did not start after 1:30 minutes. Giving up.).
Here is the java version I am using (JVM 4.1)
atl-osm-01:osmadm 80> java -version
java version "1.4.2_30"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.009)
SAP Java Server VM (build 4.1.009 17.0-b16, May 27 2011 00:12:32 - 41_REL - optU - linux amd64 - 6 - bas2:154157 (mixed mode))
in the dev_jcontrol log I see:
-> lib path = LD_LIBRARY_PATH=/opt/java/sapjvm_4/jre/lib/amd64/server:/opt/java/sapjvm_4/jre/lib/amd64:/opt/java/sapjvm_4/jre/../lib/amd64:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/tmp/sapinst_exe.26924.1310559612:/usr/sap/OSM/SYS/exe/run:/sapdb/programs/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib:/usr/sap/OSM/DVEBMGS00/j2ee/os_libs:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/SYS/exe/run:/sapdb/programs/lib
-> exe path = PATH=/opt/java/java/bin:/usr/sap/OSM/DVEBMGS00/j2ee/os_libs:/sapdb/programs/bin:/opt/java/java/bin:.:/home/osmadm:/usr/sap/OSM/SYS/exe/run:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/opt/dell/srvadmin/bin
[Thr 47171544096752] JStartupICreateProcess: fork process (pid 5857)
[Thr 47171544096752] JControlICheckProcessList: process server0 started (PID:5857)
[Thr 47171544096752] Thu Jul 14 16:29:19 2011
[Thr 47171544096752] JControlICheckProcessList: process server0 (pid:5857) died (RUN-FLAG)
[Thr 47171544096752] JControlIResetProcess: reset process server0
[Thr 47171544096752] JControlIResetProcess: [server0] not running -> increase error count (4)
[Thr 47171544096752] JControlICheckProcessList: running flight recorder:
        /opt/java/java/bin/java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID3888650 1310675354 -bz /usr/sap/OSM/SYS/global
In the dev_w12 trace log I see:
M *****************************************************************************
M *
M * LOCATION    SAP-Gateway on host atl-osm-01 / sapgw00
M * ERROR       program SLD_UC not registered
M *
M * TIME        Thu Jul 14 16:25:52 2011
M * RELEASE     700
M * COMPONENT   SAP-Gateway
M * VERSION     2
M * RC          679
M * MODULE      gwr3cpic.c
M * LINE        1778
M * DETAIL      TP SLD_UC not registered
M * COUNTER     3
M *
M *****************************************************************************
M
A RFC 1485 CONVID 80159271
A   * CMRC=2 DATA=0 STATUS=0 SAPRC=679 ThSAPOCMINIT
A RFC> ABAP Programm: RSLDAGDS (Transaction: )
A RFC> User: DDIC (Client: 001)
A RFC> Destination: SLD_UC (handle: 1, , )
A *** ERROR => RFC ======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Transaction program not registered
[abrfcio.c    8141]
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Transaction program not registered
DEST =SLD_UC
HOST =%%RFCSERVER%%
PROG =SLD_UC
GWHOST =atl-osm-01
GWSERV =sapgw00
[abrfcio.c    8141]
A TH VERBOSE LEVEL FULL
A ** RABAX: end RX_GET_MESSAGE
B table logging switched off for all clients
S handle memory type is RSTSPROMMM
Any ideas on how I can fix this? Anything else that I should post that will help with analyzing the issue?
Thanks in advance!

Hi Sunny -
Thank you for your quick response. I will have to ask a beginner's question now, but how do I restart the system manually? Is that just the startsap/stopsap scripts that I need to run?
How would I know if the server0 is actually up and running after restarting?
Also, Here is the dev_server0 log (I am posting snippets of the logs as they repeat):
1
   2 -
   3 trc file: "/usr/sap/OSM/DVEBMGS00/work/dev_server0", trc level: 1, release: "700"
   4 -
   5 node name   : ID3888650
   6 pid         : 5639
   7 system name : OSM
   8 system nr. : 00
   9 started at : Thu Jul 14 16:28:59 2011
10 arguments         :
11           arg[00] : /usr/sap/OSM/DVEBMGS00/exe/jlaunch
12           arg[01] : pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
13           arg[02] : -DSAPINFO=OSM_00_server
14           arg[03] : pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
15           arg[04] : -DSAPSTART=1
16           arg[05] : -DCONNECT_PORT=60140
17           arg[06] : -DSAPSYSTEM=00
18           arg[07] : -DSAPSYSTEMNAME=OSM
19           arg[08] : -DSAPMYNAME=atl-osm-01_OSM_00
20           arg[09] : -DSAPPROFILE=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
21           arg[10] : -DFRFC_FALLBACK=ON
22           arg[11] : -DFRFC_FALLBACK_HOST=localhost
23
24
25 [Thr 47057802424304] Thu Jul 14 16:28:59 2011
26 [Thr 47057802424304] *** WARNING => INFO: Unknown property [instance.box.number=OSMDVEBMGS00atl-osm-01] [jstartxx_mt. 841]
27 [Thr 47057802424304] *** WARNING => INFO: Unknown property [instance.en.host=atl-osm-01] [jstartxx_mt. 841]
28 [Thr 47057802424304] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx_mt. 841]
29 [Thr 47057802424304] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx_mt. 841]
30
31 **********************************************************************
32 JStartupReadInstanceProperties: read instance properties [/usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties]
33 -> ms host    : atl-osm-01
34 -> ms port    : 3901
35 -> OS libs    : /usr/sap/OSM/DVEBMGS00/j2ee/os_libs
36 -> Admin URL :
37 -> run mode   : NORMAL
38 -> run action : NONE
39 -> enabled    : yes
40 **********************************************************************
41
42
43 **********************************************************************
44 Used property files
45 -> files [00] : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
46 **********************************************************************
46 **********************************************************************
47
48 **********************************************************************
49 Instance properties
50 -> ms host    : atl-osm-01
51 -> ms port    : 3901
52 -> os libs    : /usr/sap/OSM/DVEBMGS00/j2ee/os_libs
53 -> admin URL :
54 -> run mode   : NORMAL
55 -> run action : NONE
56 -> enabled    : yes
57 **********************************************************************
58
59 **********************************************************************
60 Bootstrap nodes
61 -> [00] bootstrap            : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
62 -> [01] bootstrap_ID3888600 : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
63 -> [02] bootstrap_ID3888650 : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
64 **********************************************************************
65
66 **********************************************************************
67 Worker nodes
68 -> [00] ID3888600            : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
69 -> [01] ID3888650            : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
70 **********************************************************************
71
72 [Thr 47057802424304] JLaunchRequestQueueInit: create named pipe for ipc
73 [Thr 47057802424304] JLaunchRequestQueueInit: create pipe listener thread
74 [Thr 1115011392] WaitSyncSemThread: Thread 1115011392 started as semaphore monitor thread.
75 [Thr 1104521536] JLaunchRequestFunc: Thread 1104521536 started as listener thread for np messages.
76 [Thr 47057802424304] SigISetDefaultAction : default handling for signal 17
77
78 [Thr 47057802424304] Thu Jul 14 16:29:00 2011
79 [Thr 47057802424304] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
80 [Thr 47057802424304] CPIC (version=700.2006.09.13)
81 [Thr 47057802424304] [Node: server0] java home is set by profile parameter
82         Java Home: /opt/java/java
83 [Thr 47057802424304] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/OSM/DVEBMGS00/exe/jvmx.jar
84
85 **********************************************************************
86 JStartupIReadSection: read node properties [ID3888650]
87 -> node name          : server0
88 -> node type          : server
89 -> node execute       : yes
90 -> jlaunch parameters :
91 -> java path          : /opt/java/java
92 -> java parameters    : -verbose:gc -Xtrace -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.     engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.eng     ine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Xmn400m -XX:PermSize=2048m -XX:MaxPermSize=2048m -Dorg.omg.PortableInterceptor.ORBInitializerClass.co     m.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
93 -> java vm version    : 4.1.009 17.0-b16
94 -> java vm vendor     : SAP Java Server VM (SAP AG)
95 -> java vm type       : server
96 -> java vm cpu        : amd64
97 -> heap size          : 2048M
98 -> init heap size     : 2048M
99 -> root path          : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/server0
100 -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
101 -> OS libs path       : /usr/sap/OSM/DVEBMGS00/j2ee/os_libs
102 -> main class         : com.sap.engine.boot.Start
103 -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
104 -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
105 -> framework path     : /usr/sap/OSM/DVEBMGS00/exe/jstartup.jar:/usr/sap/OSM/DVEBMGS00/exe/jvmx.jar
106 -> shutdown class     : com.sap.engine.boot.Start
107 -> parameters         :
108 -> debuggable         : no
109 -> debug mode         : no
110 -> debug port         : 50021
111 -> shutdown timeout   : 120000
112 **********************************************************************
113
114 [Thr 47057802424304] JLaunchISetDebugMode: set debug mode [no]
115 [Thr 1101179200] JLaunchIStartFunc: Thread 1101179200 started as Java VM thread.
116
117 **********************************************************************
118 JHVM_LoadJavaVM: VM Arguments of node [server0]
119 -> stack   : 1048576 Bytes
120 -> arg[ 0]: exit
121 -> arg[ 1]: abort
122 -> arg[ 2]: vfprintf
123 -> arg[ 3]: -verbose:gc
124 -> arg[ 4]: -Xtrace
125 -> arg[ 5]: -Djava.security.policy=./java.policy
126 -> arg[ 6]: -Djava.security.egd=file:/dev/urandom
127 -> arg[ 7]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
128 -> arg[ 8]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
129 -> arg[ 9]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
130 -> arg[ 10]: -Djco.jarm=1
131 -> arg[ 11]: -Xmn400m
132 -> arg[ 12]: -XX:PermSize=2048m
133 -> arg[ 13]: -XX:MaxPermSize=2048m
134 -> arg[ 14]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
135 -> arg[ 15]: -Dsys.global.dir=/usr/sap/OSM/SYS/global
136 -> arg[ 16]: -Dapplication.home=/usr/sap/OSM/DVEBMGS00/exe
137 -> arg[ 17]: -Djava.class.path=/usr/sap/OSM/DVEBMGS00/exe/jstartup.jar:/usr/sap/OSM/DVEBMGS00/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin     /system/bytecode.jar:.
138 -> arg[ 18]: -Djava.library.path=/opt/java/sapjvm_4/jre/lib/amd64/server:/opt/java/sapjvm_4/jre/lib/amd64:/opt/java/sapjvm_4/jre/../lib/amd64:/usr/sap/O     SM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/tmp/sapinst_exe.26924.1310559612:/usr/sap/OSM/SYS/exe/run:/sapdb/programs/lib:/u     sr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib:/usr/sap/OSM/DVEBMGS00/j2ee/os_libs:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/us     r/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/SYS/exe/run:/sapdb/programs/lib
139 -> arg[ 19]: -Dmemory.manager=2048M
140 -> arg[ 20]: -Xmx2048M
141 -> arg[ 21]: -Xms2048M
142 -> arg[ 22]: -DLoadBalanceRestricted=no
143 -> arg[ 23]: -Djstartup.mode=JCONTROL
144 -> arg[ 24]: -Djstartup.ownProcessId=5639
145 -> arg[ 25]: -Djstartup.ownHardwareId=H0868704103
146 -> arg[ 26]: -Djstartup.whoami=server
147 -> arg[ 27]: -Djstartup.debuggable=no
148 -> arg[ 28]: -DSAPINFO=OSM_00_server
149 -> arg[ 29]: -DSAPSTART=1
150 -> arg[ 30]: -DCONNECT_PORT=60140
151 -> arg[ 31]: -DSAPSYSTEM=00
152 -> arg[ 32]: -DSAPSYSTEMNAME=OSM
153 -> arg[ 33]: -DSAPMYNAME=atl-osm-01_OSM_00
154 -> arg[ 34]: -DSAPPROFILE=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
155 -> arg[ 35]: -DFRFC_FALLBACK=ON
156 -> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
157 -> arg[ 37]: -DSAPSTARTUP=1
158 -> arg[ 38]: -DSAPSYSTEM=00
159 -> arg[ 39]: -DSAPSYSTEMNAME=OSM
160 -> arg[ 40]: -DSAPMYNAME=atl-osm-01_OSM_00
161 -> arg[ 41]: -DSAPDBHOST=atl-osm-01
162 -> arg[ 42]: -Dj2ee.dbhost=atl-osm-01
163 **********************************************************************

Error message in "Check Solution Manager"

I'm running SolMan EHP1 SP6. The BI repository and Solution Manager are running on the same box. The BI repository is loaded in client 001. The System SID is PS4.
I'm performing the "Diagnostic Self Check" in Root Cause Analysis. When I select the "Check Solution Manager" button I'm getting an error message
Text = BI Setup check 'MYSELF_DEST' failed - Reason: ;Incorrect client 300; use BI client 001
Action = The CCMSBISETUP job was not completed successfully. Please run CCMSBISETUP again from the transaction solman_admin and/or adjust the corresponding BI objects in RSA1 if necessary.
In RSA1 the source system is defined as PS4CLNT001. So I'm not sure what the problem is.
It is my understanding that I can configure CCMSBISETUP in solman_workcenter by selecting "System Monitoring", then Setup, then Configure IT Performance Reporting. When I do this the default value for RFC destination from Solution Manager to BI: is set to NONE
The system requires and entry for the RFC destination from BI to Solution Manager - Does anybody know what RFC destination belongs here?

Hi,
The CCMSBISETUP job was not completed successfully. Please run
CCMSBISETUP again from the transaction solman_admin and/or adjust the
corresponding BI objects in RSA1 if necessary.
Alternatively, please perform again Initial and Basic configuration
for SolMan by running transaction solman_setup. This should solve the
issue.
Notice that you must have the latest version (13) of SAP Note 1405878
applied in the solution manager system.
Hope this helps.
Cheers
SH

Error 1314 in the Solution Manager Installation

I'm installing Solution Manager 4.0 SR1 in Windows 2003 + Oracle 10g.
In the second step of the "Task Progress", "Create users for SAP System"
I've the error message :
"ERROR 2007-03-15 18:07:29
FSL-00001 System call failed. Error 1314 (A required privilege is not
held by the client.
) in execution of system call 'LoadUserProfile' with parameter (thread
token for FIG\smpadm, smpadm), line (706) in file (synxccuren.cpp)."
I'm executing the installation with the domain administrator, and I
review the local policies for this user (Act part of operating system,
adjust memory quotas for a process and replace a process level token).
Thank's in advanced
Francesc Segura

I am getting the same error. How do i resolve it?
Thanks
Pooja

Error when installing sap solution manager

Dear all,
When i am installing SAP solution manager (SAP SOLMAN 7.0 EHP1SR1 WINDOWS_X86_64), I meet the following error:
An error occurred while processing option SAP Solution Manager 7.0 EhP1 > SAP Systems > MS SQL Server > Central System > Central System( Last error reported by the step: ABAP processes of instance S01/DVEBMGS00 [ABAP: UNKNOWN] did not start after 10:30 minutes. Giving up.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS.
Do anyone meet the same error before? Please help...
Thanks.

I had a similar issue because the size of the pagiing file, after increase the size of paging file to 20Gb, I solved the issue in my system. The instance wasn't up because the size of paging file.

Error importing SP in Solution Manager System (phase XPRA_EXECUTION)

Dear community,
I have a fresh installation of Solution Manager System 7.1 (central system) in a test environment.
During post-installation I wanted to apply SP (user DDIC, client 000), but my update queue via SPAM failed in phase 23 (XPRA_EXECUTION) and I have no idea how to handle that. Error message:
- Error in phase: XPRA_EXECUTION
- Reason for error: TP_STEP_FAILURE
- Return code: 0008
- Error message: OCS Package SAPK-70203INSAPBSFND, tp step R, return code 0008
To check the cause of the error it is recommended to choose Goto -> Log -> Queue.
Choosing Goto -> Action Log, I find:
Error during executing the tp command 'tp XPA ALL SOL ...'
tp return code: '0008' , tp message: 'A tool used by tp produced errors', tp output:
Choosing Goto -> Import Logs -> tp system logs, I find:
START EXECUTION OF REPORTS SOL R      20120104111325              DDIC         biss-labor01
START tp_getprots          SOL R      20120104111325              DDIC         biss-labor01
ERROR SAPK-70203INSAPBSFND SOL R 0008 20120104111331 SAPBSFNDUSER DDIC         biss-labor01
ERROR SAPK-70204INSAPBSFND SOL R 0008 20120104111331 SAPBSFNDUSER DDIC         biss-labor01
ERROR SAPKITL701           SOL R 0008 20120104111335 STUSER       DDIC         biss-labor01
STOP tp_getprots          SOL R      20120104111338              DDIC         biss-labor01
STOP EXECUTION OF REPORTS SOL R      20120104111338              DDIC         biss-labor01
An excerpt (3 lines) from ulog:
APServiceSOL 20120104122229 RFC: tp SHOWPARAMS SOL pf=
biss-labor01sapmnt     rans inTP_DOMAIN_SOL.PFL -Dtransdir=
biss-labor01sapmnt     rans (pid=6232)
APServiceSOL 20120104122229 RFC: tp CONNECT SOL pf=
biss-labor01sapmnt     rans inTP_DOMAIN_SOL.PFL -Dtransdir=
biss-labor01sapmnt     rans (pid=6232)
APServiceSOL 20120104122231 RFC: tp XPA ALL SOL pf=
biss-labor01sapmnt     rans inTP_DOMAIN_SOL.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -Dtransdir=
biss-labor01sapmnt     rans (pid=6232)
What I already tried:
- retry importing
- stop and start the system, then retry importing
- check for background jobs (rdd* ) that failed via transaction SM37, but there are none that have been canceled
- reset buffers via transaction /$sync
Any input, suggestions or help is highly appreciated!
Regards
Sönke

Hi Sönke,
it seems we are making progress at last.
I'm afraid I didn't make my suggestion about splitting items very clear. I meant to say try applying your SPAM queue in several parts splitting up the packages affected so they are applied individually.
SAPK-70203INSAPBSFND
SAPK-70204INSAPBSFND
SAPKITL701
SAPKB70207
I think default behaviour for SPAM/SAINT is to calculate the entire queue automatically based on EPSIN but you can override this behaviour and choose to split your queue into shorter ones, you simply choose carefully the last package, apply this queue, then choose the next queue and so on until you are done. There used to be special notes which had recommended split points for package queues
EDIT: I checked your link and I don't think it is helpful unfortunately.
Best regards,
Mark.
Edited by: Mark Birch on Jan 11, 2012 2:07 PM

Error in implimentation of Solution Manager

HI,
I am Installing Solution manager4.0 on Windows 2003- 32 bit. oracle DB.
in the Execute service phase at 18 of 45 stage i got error log file shows below error can some body look into this ??
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
32-bit Windows Error: 2: No such file or directory
Error resolved.-Thanks
Edited by: Murali Lakkoju on Jan 18, 2009 11:01 PM

error resolved, error during input phase found worng inputs.

Error while upgrading to Solution Manager EHP1 from 3.2

Hi All,
I am trying to upgrade the solution manager3.2 to EHP1.
OS: Linux RHEL 4
DB: Oracle 10.2.0.2
I am in the Prepare phase.....
When I try to run the JPREPARE command( /dump/smrtest/SMR_UP/51036444/JPREPARE) I get the following error message
An unrecoverable error has occured:
Could not execute dialog SelectModulDialog. See previous messages.
Input output exception while processing dialog SelectModulDialog. See previous messages.
Could not send dialog message. See previous messages.
Could not bind to port 6240.
java.net.BindException: Address already in use
Can anyone help asap?

> I am in the Prepare phase.....
> When I try to run the JPREPARE command( /dump/smrtest/SMR_UP/51036444/JPREPARE) I get the following error message
You have a Java instance installed on 3.2?
> An unrecoverable error has occured:
>
> Could not execute dialog SelectModulDialog. See previous messages.
> Input output exception while processing dialog SelectModulDialog. See previous messages.
> Could not send dialog message. See previous messages.
> Could not bind to port 6240.
> java.net.BindException: Address already in use
Read the documentation about SAPJup - you have to change the default port (because most likely your ABAP part uses that one).
Markus

Error While Loggin in Solution Manager 3.2

Hello there!!
I have HP-UX, Oracle 9i,Sol MAn 3.2
I have installed Sol Man3.2 on my Dev Server under instance SM1 and system number 00
now when i add this system on my SAP Logon
and click on the logon button
i get error as connection refused.
details error is mentioned below.
I have started the Instance SM1 and it is showing instance started.
Component:NI
Release:640
Version:37
Module: nixxi_r.cpp
Line:8716
Method: NiPConnect2
return Code -10
System Call: SiPeekPendConn
Error No 10061
Error text WSAECONNREFUSED: Connection refused
kindly help
saurabh

Hi Saurabh,
sorry, I am not able to support you in finding the cause for the connection problem.
Anyway, my recommendation:
- Delete the SolMan 3.2 installation
- Install Solman 4.0
- Apply all Support Packages
- perform the configuration on 4.0 according the IMG
Configuring SolMan 3.2 is wasted time, if it has not been used in the past. SolMan 4.0 supports implementation / upgrade from/to SAP ERP 2004.
An upgrade in the future costs much more time and money, then to reinstall 4.0 now.
Deleting SolMan 3.2 and reinstall SolMan 4.0, this will only 2 extra days. Upgrade takes about 4-10 days.
Best regards,
Ruediger Stoecker
Message was edited by: Ruediger Stoecker
Spelling mistakes corrected, more information on days.

Runtime Errors SYNTAX_ERROR in SAP Solution Manager 4.0

Hi every body,
     After in install of support packages SAP_BASIS SAP_ABA and ST. When I logon in the SAPGui I received this error:
Runtime Errors         SYNTAX_ERROR
Short text
    Syntax error in program "SAPLSCP2 ".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLOLEA" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLSCP2 " in include "LSCP2U09
     " in
    line 66:
    "The field "ZCSA_SYSTEM_LANGUAGE" is unknown, but there is a field with"
    " the similar name "ZCSA_INSTALLED_LANGUAGES". "ZCSA_INSTALLED_LANGUAGE"
    "S"."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
Error analysis
    The following syntax error was found in the program SAPLSCP2 :
    "The field "ZCSA_SYSTEM_LANGUAGE" is unknown, but there is a field with"
    " the similar name "ZCSA_INSTALLED_LANGUAGES". "ZCSA_INSTALLED_LANGUAGE"
    "S"."
Trigger Location of Runtime Error
    Program                                 SAPLOLEA
    Include                                 LOLEAU13
    Row                                     71
    Module type                             (FUNCTION)
    Module Name                             AC_CALL_METHOD
Please help me
Regards.

Hi,
Have upgrade kernel?
Regards
Ben

Error in logfile of Solution Manager on iSeries (AS/400)

Similar Messages

Maybe you are looking for