Solution Manager 4.0 - MSCS Installation

Hi All,
We are planning for Solman 4.0 Installation in Cluster environment with Windows 2003 server and MS SQL Server 2005.
I have some queries related to this task.
1. Is it possible to install Central Instance in first MSCS node and Database Instance in Additional MSCS node, activate failover in both points. Like if CI system goes down first MSCS node should failover to addtional node and if DI goes down additioonal MSCS node should failover to first MSCS node. Since in cluster installation document of solman, this type of failovers is not mentioned.
2. Enqueue Replication Server Installation: Our solman has both ABAP+Java stack. For this case how we can install ERS. In document it has mentioned we have install 4 times means
ERS1(ABAP), ERS2(Java) - First MSCS Node
ERS3(ABAP), ERS4(Java) - Additional MSCS Node
3. Is it mandatory to install in Dialog Instance in the cluster installation. Since in installation document it is mentioned like atleast one dialog instance should be installed.
Pls give me some inputs for this queries
Thanks in Advance
Regards
KT

Got Solution...Its not Mandatory to install ERS

Similar Messages

Solution Manager 4.0 SR1 installation error

Hi there,
I am getting eblow error for Solution Manager 4.0 SR1 installation on aix-ora.
Any help much appreciated. Thanks.
Regards
Anil
INFO       2008-05-19 14:15:56 [syuxccuren.cpp:119]
           CSyCurrentProcessEnvironmentImpl::removeEnvironmentVariable
Removed environment variable SAPDATA_HOME from current process environment.
INFO       2008-05-19 14:15:58 [iaxxgenimp.cpp:630]
           showDialog()
Execute step PrepareOraCreateTablespace of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0.
ERROR      2008-05-19 14:15:59 [iaxxejsbas.cpp:178]
           EJS_ErrorReporter
FJS-00003 TypeError: sapdataNodeInfo[idx] has no properties (in script NW_Onehost|ind|ind|ind|ind, line 51567: ???)
ERROR      2008-05-19 14:15:59 [iaxxgenimp.cpp:728]
           showDialog()
FCO-00011 The step PrepareOraCreateTablespace 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_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|PrepareOraCreateTablespace was executed with status ERROR .

Why not use SR3 release? It contains MANY more fixes and will prevent you from the need of installing a bunch of support packages after your installation...
For your error: please check ora_sql_result.log
Markus

Issue on Solution Manager 4.0 SR3 installation

Dear all,
During the Oracle Client installation phase of a SAP Solution Manager 4.0
system installation with sapinst, I get the following error
ERROR 2008-01-21 16:04:06.776 iaxxejsbas.cpp:178
EJS_ErrorReporter
FJS-00003 TypeError: linkTarget has no properties (in script
NW_Onehost|ind|ind|ind|ind, line 3431: ???)
ERROR 2008-01-21 16:04:07.399 iaxxgenimp.cpp:731
showDialog()
FCO-00011 The step createOcl10Links with step key
|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_C
reateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|in
d|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraClient|ind|ind|ind|ind|3|0|createOcl10Links was executed with status ERROR .
TRACE 2008-01-21 16:04:07.443 iaxxgenimp.cpp:719
showDialog()
Any ideas?
Many thanks
Andreas

On Solaris 10 platform...
We found that we could correct the problem by extracting the SAR file OCL10264.SAR from the client DVD into the client directory /oracle/client/10x_64 (which we had to create) and execute "ln -s instantclient_10202 instantclient" to create the symbolic link for the instantclient directory. Then the installation continued successfully.
Credit to Rama Ekambaram for figuring this out...
Tim Pittman

Solution Manager 4.0 Linux installation remains in step 20

Hi,
I have two questions:
1.- We want to install NW04s with EP and WAS JAVA scenario, but first we have to install Solution Manager 4.0 with AS JAVA + AS ABAP instances, cause this is a necessary step for obtain the solution mananager key and for install NW04s. That's true?
2.- In Solution Manager 4.0 installation for Linux, the installation program remains in "step 20 - Import ABAP" for a long time (I leave it running for more than a 12 hours...), and show no errors, but still running and no goes to the next step. Any idea?
Information:
Server: Linux_x86_64.
Operating system: Suse Linux Enterprise Edition 9.2
kernel: 2.6.5.7-7.267-smp
java version: J2RE 1.4.2 IBM J9 2.2 Linux amd64-64
I had a lot of problems to find jdk 1.4.xx for Linux on 64 bits that works with sapinst. For this reason, I had to install this IBM jdk.
Message was edited by: Soporte OSS Soporte OSS

Hi,
I'm me again. xD
Now I pass the step 20 but in the "Object_checker.log" shows that some objects can not be imported.
Now it stops in step 23 with this error on logs: "JDBCDriverException: Can not connect to DB"
Anyone knows what should I do?
TIA,
Arnau
Message was edited by: Soporte OSS Soporte OSS

Error at "CAF" phase of Solution Manager 4.0 SR3 installation

Hello,
When we install Solution Manager SR3 at phase 57 of 59, we get an error when sapinst configures "use type as java" CAF configuration parameters.
Line: -
ERROR
CJS-30059 Java EE Engine configuration error. DIAGNOSIS: See output of logfile java.log: 'JSE '.
Line: -
1. sapinst.log :
ConfigMainExt state500
TYPE=A
STATE=500
INFO_SHORT=Error connecting to --http://yanbalsm:50000/ctc/ -- ConfigServlet?param=com.sap.ctc.util.OfflineConfig;PROPSHEETVALUE;CONFIGURATION=
apps/sap.com/caf~runtime~ear/appcfg/application.global.properties,KEY=WAS_MACHIN
E_ADDRESS,VALUE=yanbalsm. The provided user data might be incorrect or user migh
t be locked.
CONFIGURATION=
ERROR 2008-02-23 18:30:52.811
CJS-30059 Java EE Engine configuration error. DIAGNOSIS: See output of logfile
java.log: 'JSE '.
ERROR 2008-02-23 18:30:52.812
FCO-00011 The step configCAFPropSheet with step key |NW_Onehost|ind|ind|ind|ind
|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Usage_Types_Conf
iguration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_CAF|ind|ind|ind|ind|1|0|configCAFProp
Sheet was executed with status ERROR .
Line: -
the usser JSE means for J2ee_admin or other? . i looged into abap stack 001 with sap* and validate that that user is not blocked.
Line: -
2. java.log
TYPE=A
STATE=500
INFO_SHORT=Error connecting to --http://yanbalsm:50000/ctc/
-- ConfigServlet?param=com.sap.ctc.util.OfflineConfig;PROPSHEETVALUE;CONFIGURATION=
apps/sap.com/cafruntimeear/appcfg/application.global.properties,KEY=WAS_MACHIN
E_ADDRESS,VALUE=yanbalsm. The provided user data might be incorrect or user migh
t be locked.
CONFIGURATION=
Line: -
I look into http:// hostanme:port/nwa and users are ok and come from abap stack.
but when try to uses config tool or VA with de sidadm user none load , i got a error message "JAVA_HOME" not set.
i look into .j2eeenv file and is set with setenv.
Line: -
3. sapinst_dev.log .-
TRACE      2008-02-24 00:02:56.72 [iaxxejsexp.cpp:199]
           EJS_Installer::writeTraceToLogBook()
NWException thrown: nw.configError:
Java EE Engine configuration error. DIAGNOSIS: See output of logfile java.log: '
JSE '.
ERROR      2008-02-24 00:02:56.72
           CJSlibModule::writeError_impl()
CJS-30059 Java EE Engine configuration error. DIAGNOSIS: See output of logfile
java.log: 'JSE '.
Line: -
could any one please tell me what can i check to solve this and finish my installation process.
Thank,
Daniel

Hi
We have the same problem but in AIX/Oracle
Any suggestions?

Solution Manager 7.1 Post-installation upgrade SPS04

Hi
I just installed Solution Manager 7.1, on Windows server 2008 R2 / 64 bits with Oracle database.
In post installation steps I have to update my installation.
According to note 1577909, I have downloaded the Stack DVD : " SAP Solution Manager 7.1 SPS04" from SAP marketplace and copied the java files in usr\sap\trans\EPS\in and unpacked the ABAP files in the same directory.
Then I have downloaded the Stack Kernel files & copied in usr\sap\trans\EPS\in.
Now I'm a little bit confused : I'm supposed to call transaction SAINT and use maintenance xml in the EPS inbox & JSPM and use maintenance XML in the EPS inbox => witch XML files should I use : the one in the support package stack or the one generated in the service marketplace in "link to SP Stack application" ?
Is that all to update my solution manager? what about maintenance optimizer? ( in which I have errors ).
Would the SPS 04 be installed? as well as the stack files?
Is there a guide or a more detailed implementation procedure for this purpose?
Should I make a backup before upgrading?
Thanks for your input.
Guillaume Blanchard

Thanks a lot for your inputs.
1 ) In SP Stack Application, my start SP Stack is "SAP SOLUTION MANAGER 7.1 - ISS Initial Shipment Stack"
and my target one is SAP SOLUTION MANAGER 7.1 - SPS 04 (12/2011 )
I'm in 64 bit so i have selected SAP KERNET 7.20 32-BIT and Alternativest => SAP KERNEL 7.20 EXT 64-BIT but in the next step i have to pick the software component versions : in note 1577909 it's say to only select kernel file, but
I'm gettting warning on the next screen : 9 messages :
- Step 2 : WILY Introscope workstation 8 and Alternative SCV : We recommend selecting at least one alternative
- Step 2 : SAP KERNEL 7.20 32-BIT UNITOCDE and Alternative SCV : We recommend selecting at least one alternative
- Step 2 : SAP IGS 7.20 and Alternative SCV : We recommend selecting at least one alternative
- Step 2 : SAP IGS 7.20 and Alternative SCV : We recommend selecting at least one alternative
- Step 2 : SAP HOST AGENT 7.20 : We recomment selecting at least one alternative
- Step 2 : BMC APPSIGHT BLACKBOX 6.0.2 : We recomment selecting at least one instantiation
- Step 2 : SAP GUI FOR WINDOWS 7.20 CORE : We recomment selecting at least one instantiation
- Step 2 : NWBC NW BUSINESS CLIENT 3.0 : We recomment selecting at least one instantiation
- Step 2 : SAP BUSINESS BLUEPRT TOOL 101 : We recomment selecting at least one instantiation
Is it right to keep up without considering those warnings?
About the ABAP file from the SPS04 dvd there is many files without label : am i supposed to extract all of the SAR files ?
Should i do the same for the sar files downloaded from SP Stack application ?
Should i download the last SPAM/SAINT update from sap marketplace ( 730 ) ? how to install it ?
Is there a guide about this procedure ?
Still Really thanks for the inputs

Solution Manager can't generate installation key for Netweaver 2004s

I am trying to generate installation key for a new installation of
Netweaver 2004s or 7.0 and the Solution Manager only display SAP ECC
5.0 or 6.0 in the field production version, when i am trying do create
a new system landscape. My Solution Manager is 4.0 release and support
package 10. The keys generated by ECC 5.0 or 6.0 doesn't work.

That is because SAP has not released an ECC 7.0
NW2004s is also refered to as 7.0. It appears that you are confusing this with ECC 5.0 and ECC 6.0
A NW2004s installation can contain an ECC5.0 or ECC 6.0, just like it can contain a CRM 5.0 or SRM, or EP, et cetera
The generated keys probably do not work because you have wrong hostname or instance number entered.

Preparing Solution Manager for SMD Agents Installation

Hello everyone
I have to configure the Solution Manager of QAS to receive new SMD Agents, I looking at the transaction SOLMAN_SETUP.
Does anybdoy know what do I have to do to prepare the environment for the installation of SMD agents?
Thank

Hi Marcelo,
Check note 1365123 - Installation of Diagnostics Agents, this note shows the agent installation strategy. You must install one SMD agent per host (physical or virtual) . The SMD agent should be installed in all host you want to monitor.
In order to connect the SMD agent into your Solution check the following WIKI:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents#DiagnosticsAgents-Connectionoptions
Also, you can managed the SMD agent in the "Agent Administration", it can be found at:
- SOLMAN_WORKCENTER
- Tab Root Cause Analysis
- "Agent Administration"
I recommend you to use the "Direct connection to solution manager" for your agents. It is easier than the SLD registration.
Regards,
Allam

Solution Manager on Linux x86_64 installation problem

I try to install Solution Manager 4.0 on Linux X86_64 platform. Unfortunately i receive error "the JDK installed in directory /usr/lib/java does not support the 64 bit data model". And there is no J2SDK for Suse linux x86_64 (or at least i can't find it. Please help!!!

OK. I solved the problem by using IBM Java. Also there is an SUSE version of SUN Java 1.4.2 for 64 bit systems.

Recieved error during Solution Manager EHP1 Java Components installation.

I successfully installed EHP1 ABAP components but I'm have a problem with the Java components. I recieved the following error. Import aborted during ADSSAP02_0-20002778.SCA
Feb 20, 2009 3:17:59 PM Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application com.adobe/DocumentServicesLicenseManager..
Reason: Exception during generation of components of application com.adobe/DocumentServicesLicenseManager in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application com.adobe/DocumentServicesLicenseManager in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Feb 20, 2009 3:17:59 PM Info: Starting to save the repository
Feb 20, 2009 3:18:01 PM Info: Finished saving the repository
Feb 20, 2009 3:18:01 PM Info: Starting: Update: Selected software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1' updates currently deployed software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.16.0.20080610114809''/'0'.
Feb 20, 2009 3:18:01 PM Error: Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Failed deployment of SDAs:
development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1' : aborted
Please, look at error logs above for more information!
Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.200712
13024549.437972'/'1', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application com.adobe/DocumentServicesLicenseManager..
Reason: Cannot load one of the bean interfaces or the bean class of bean LicenseEJBBean.; nested exception is:
com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: Cannot load one of the bean interfaces or the bean cla
ss of bean LicenseEJBBean.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Feb 20, 2009 11:25:59... Info: Starting to save the repository
Feb 20, 2009 11:26:01... Info: Finished saving the repository
Feb 20, 2009 11:26:01... Info: Starting: Update: Selected software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634'
'/'1' updates currently deployed software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.16.0.20080610114809''/'0'.
Feb 20, 2009 11:26:01... Error: Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Failed deployment of SDAs:
development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1' : aborted
Edited by: Darrell Kirklen on Feb 23, 2009 5:03 PM

Just resolved problem. While reviewing the sdmlog20090310.log I found
error "java.lang.UnsupportedClassVersionError?" when I goggled this
error "How do I resolve a java.lang.UnsupportedClassVersionError? I
found the following solution:
http://support.codegear.com/article/35846 : This exception can occur
when the source is built targeting a JDK that is not supported by the
JDK attempting to run it. In the above example, if the servlet was
built targeting only JDK 1.5, but the web server runs JDK 1.4, the
above exception will occur. Check, Project Properties | Build | Java |
Target VM, and verify that the Target VM indicates a JDK compatibility
that is appropriate for the JDK that is running it. It is recommended
to set this field to 'All Java SDKs' for the most compatibility. The
only reason you would want to specify a particular version is if your
code uses language features that only appear in a particular version of
the JDK, and you want to ensure that users use only a compatible JDK.
Also check, Project Properties | Build | Java | Language Features, and
verify that the Language Features are applicable with JDK that is
running it
A this point I checked the java -version at the os level and it showed
1.5.0_17 we are aware the supported version of java should be 1.4.2_16
our Unix team (Solaris) recently installed new patches and didnu2019t
remember to leave the java version at 1.4.2_16 after their were done.
Once the java version was set back to 1.4.2_16 I was able to complete
the java portion of EHP1 using the JSPM successfully.
Edited by: Darrell Kirklen on Mar 13, 2009 4:37 PM

What are installations material for Solution Manager 7.0 EHP 1

hi friends,
we plan to do installing Solution Manager 7.0 ehp1,
can any help me to get the path for installation media for Solution Manager 7.0 EHP 1 in service market place.
thanks..

https://service.sap.com/swdc
-> SAP Installations and Upgrades
-> Installations and Upgrades - Entry by Application Group
-> SAP Technology Components
-> SAP SOLUTION MANAGER
-> SAP SOLUTION MANAGER 7.0 EHP 1
-> Installation and Upgrade
Also check https://service.sap.com/instguides for the install guide and SAP Note 1276022 - SAP Solution Manager 7.0 EHP1
Installation.
Nelis

Issue on Solution Manager 4.0 installation SR3

Dear all,
During the Oracle Client installation phase of a SAP Solution Manager 4.0
system installation with sapinst, I get the following error
ERROR 2008-01-21 16:04:06.776 [iaxxejsbas.cpp:178]
EJS_ErrorReporter
FJS-00003 TypeError: linkTarget has no properties (in script
NW_Onehost|ind|ind|ind|ind, line 3431: ???)
ERROR 2008-01-21 16:04:07.399 [iaxxgenimp.cpp:731]
showDialog()
FCO-00011 The step createOcl10Links with step key
|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_C
reateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|in
d|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraClient|ind|ind|ind|ind|3|0|createOcl10Links was executed with status ERROR .
TRACE 2008-01-21 16:04:07.443 [iaxxgenimp.cpp:719]
showDialog()
Any ideas?
Many thanks
Andreas

On Solaris 10 platform...
We found that we could correct the problem by extracting the SAR file OCL10264.SAR from the client DVD into the client directory /oracle/client/10x_64 (which we had to create) and execute "ln -s instantclient_10202 instantclient" to create the symbolic link for the instantclient directory. Then the installation continued successfully.
Credit to Rama Ekambaram for figuring this out...
Tim Pittman

STEPS FOR THE SOLUTION MANAGER INSTALLATION

Dear All,
Pls let me know what r the steps and procedure fir the installation of Solman.
Pls tell which is the latest version of sol man is available in the market.
Thanks and Regards
Amit Saini

Hi ,
check
https://websmp103.sap-ag.de/solutionmanager
For all necessary information and roadmaps
Last release is 7.0
Fo installation guide go to
http://service.sap.com/instguides
Installation & Upgrade Guides
Industry Solutions
SAP Business Suite Applications
SAP NetWeaver
SAP Solution Extensions
SAP Components
Adaptive Computing Controller
RWD
SAP Bank Analyzer
SAP Basis
SAP Billing Consolidation
SAP BW
SAP Content Server
SAP CRM Server
SAP Enterprise Portal
SAP Exchange Infrastructure
SAP Frontend Components (ITS / GUI)
SAP Global Trade Services
SAP Knowledge Warehouse
SAP MDM
SAP Mobile Applications
SAP Mobile Infrastructure
SAP R/3
SAP R/3 Enterprise
SAP SCM Server
SAP Solution Manager
Release 7.0
Release 3.2
Release 3.1
SAP Solution Manager 4.0 becomes SAP Solution Manager 7.0
SAP Solution Manager 4.0 is officially renamed to SAP Solution Manager 7.0 as of May 1st, 2008.
The new name SAP Solution Manager 7.0 brings with it the advantage of both SAP Solution Manager and SAP NetWeaver having the same release number, and is aligned with SAP's decision to streamline its product offerings. This decision also highlights the close alignment and joint go-to-market strategy of these two products.
The renaming of SAP Solution Manager 4.0 to SAP Solution Manager 7.0 is a name change only, therefore the SAP Solution Manager functionality, release schedule, installations, or other technical aspects of SAP Solution Manager will not be affected.
For further information regarding the renaming of SAP Solution Manager, please see the FAQ list. Furthermore, SAP will provide you with additional details explaining the renaming during SAPPHIRE 2008 Orlando (May 4th u2013 7th) and SAPPHIRE 2008 Berlin (May 19th u2013 21st).
Your SAP Solution Manager Product Management Team
Reward points if it help you .
antonio.

Setting up EarlyWatch in Solution manager

Hi Guys
I am trying to configure Early Watch in solution manager(System Id u2013SOL , Installation No - 0020306432) for an satellite system (System Id -DEV u2013Installation No : 0020181089).
I have followed all the configuration steps listed below :
1.     Configuration RFCs to market place SAPOSS and to satellite Systems and RFC Back to solution manager. All RFC like SAPOSS and Back has been tested from SDCCN (Solution manager and satellite system)
2.     Configured SDCCN in solution manager and in satellite system except u201CGenerate Includes for Service data control centeru201D in SPRO of solution manager as this process is getting time out and not letting us to generate all the includes
3.     Activated Service data Control center locally and assign solution manager as u2018Master system for allu2019.
4.     Activated SDCCN in satellite system(DEV) ,Created Earlywatch Service in Solution manager for DEV system and also created/Started u2018Refresh Sessionu2019 in SDCCN of DEV(Satellite system)
5.     This successfully shows me Early watch link in u2018Waitingu2019 Status in solution manager.
6.     I click on u2018Start Service Processingu2019 to Schedule/Run u201CSM:EXEC SERVICESu201D background job .
Problem : Background job u201CSM:EXEC SERVICESu201D get cancelled after some time and throws a Dump which is pasted below.
Dump shows that an include u2018/1CAGTF/IF_LOGFUNC_000393u2019 is missing which should have been generated while activating the includes for SDCCN in SPRO of solution manager.
I found includes from u2018/1CAGTF/IF_LOGFUNC_000001u2019 to u2018/1CAGTF/IF_LOGFUNC_000353u2019 in the system as it seems that not all include have been generated .
*Could you please help me to provide some SAP note so that I would be able to generate all the includes . *
DUMP
Runtime Errors         SYNTAX_ERROR
Date and Time          24.05.2008 00:01:02
Short text
Syntax error in program "RDSVASAEW_ROOT_____________073 ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASAEW_ROOT_____________073
" in include "RDSVASAEW_ROOT_____________073 " in
line 96:
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "RDSVASAEW_ROOT_____________073
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program
RDSVASAEW_ROOT_____________073 :
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "mslsol"
Network address...... "192.168.193.154"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 10
Shortdump setting.... "full"
Database server... "MSLSOL"
Database type..... "ORACLE"
Database name..... "SOL"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 29 2006 00:18:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.2.0) "
Patch level. 75
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 29266272
Heap.... 0
Page.... 24576
MM Used. 24845128
MM Free. 236264
User and Transaction
Client.............. 600
User................ "BASISA"
Language key........ "E"
Transaction......... " "
Program............. "SAPLDSVAS_PROC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLDSVAS_PROC" - in "EXECUTE".
The main program was "RDSMOPBACK_AUTOSESSIONS ".
In the source code you have the termination point in line 2146
of the (Include) program "LDSVAS_PROCCD0".
The program "SAPLDSVAS_PROC" was started as a background job.
Job Name....... "SM:EXEC SERVICES"
Job Initiator.. "BASISA"
Job Number..... 00384300
Source Code Extract
Line
SourceCde
2116
ls_stdparameter-versnr           = po_ctnode->versnr.
2117
ls_stdparameter-grp              = po_ctnode->grp.
2118
ls_stdparameter-id               = po_ctnode->id.
2119
ls_stdparameter-reference_versnr = po_ctnode->reference_versnr.
2120
ls_stdparameter-reference_grp    = po_ctnode->reference_grp.
2121
ls_stdparameter-reference_id     = po_ctnode->reference_id.
2122
else.
2123
ls_stdparameter-grp              = pf_grp.
2124
ls_stdparameter-versnr           = pf_versnr.
2125
ls_stdparameter-reference_grp    = pf_grp.
2126
ls_stdparameter-reference_versnr = pf_versnr.
2127
endif.
2128
2129
Formroutinen aufrufen
2130
loop at    actseq
2131
into ls_actrel
2132
where exec_time = pf_exec_time.
2133
check ls_actrel-exec_time ne gf_exec_time_event
2134
or ( ls_actrel-exec_time = gf_exec_time_event and
2135
ls_actrel-event     = pf_event               ).
2136
call function 'DSVAS_CDMNT_FORM_NAME'
2137
exporting
2138
pf_container_type = 'A'
2139
pf_form_number    = ls_actrel-action
2140
importing
2141
pf_form_name      = lf_form_name.
2142
perform (lf_form_name)
2143
in program (program)
2144
using ls_stdparameter
2145
if found.
>>>>>
endloop.
2147
endmethod.                    "execute
2148
2149
Collect_Known_Events
2150
method collect_known_events.
2151
data: ls_actseq type line of ltype_action_sequence_table,
2152
lf_event type dsvasactseq-event.
2153
2154
loop at actseq into ls_actseq
2155
where ( exec_time = gf_exec_time_event and
2156
event     ne space                 )
2157
or   exec_time = gf_exec_time_1
2158
or   exec_time = gf_exec_time_2
2159
or   exec_time = gf_exec_time_3
2160
or   exec_time = gf_exec_time_modus_close.
2161
if ls_actseq-exec_time = gf_exec_time_event.
2162
read table pt_events with table key table_line = ls_actseq-event
2163
transporting no fields.
2164
if sy-subrc ne 0.
2165
insert ls_actseq-event into table pt_events.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
30
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
DSWP: Execute rule set
SY-MSGTY
E
SY-MSGID
FL
SY-MSGNO
046
SY-MSGV1
DSVAS_TOOLS_PACKAGE_GET
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080524
SY-UZEIT
000049
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
11 FORM         SAPLDSVAS_PROC                      LDSVAS_PROCCD0                       2146
EXECUTE
10 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCD0                       2142
LCL_ACTION_SEQUENCE=>EXECUTE
9 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1741
LCL_CHECK_TREENODE=>EXECUTE
8 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1792
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
7 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1806
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
6 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       2025
LCL_SESSION=>EXECUTE
5 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       1582
LCL_SESSION=>CONTEXT_INSTANCES_CREATE
4 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       1995
LCL_SESSION=>EXECUTE
3 FUNCTION     SAPLDSVAS_PROC                      LDSVAS_PROCU02                        303
DSVAS_PROC_SESSION_OPEN
2 METHOD       CL_DSMOP_SOLUTION=============CP    CL_DSMOP_SOLUTION=============CM01P   184
CL_DSMOP_SOLUTION=>START_PERIODIC_SERVICES
1 EVENT        RDSMOPBACK_AUTOSESSIONS             RDSMOPBACK_AUTOSESSIONS                72
START-OF-SELECTION
Chosen variables
Name
Val.
No.      11 Ty.          FORM
Name EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PO_CTNODE
|
| 2000D000 |
| E0001C00 |
| PF_GRP |
| |
| 22222222222222222222 |
| 00000000000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| PF_VERSNR |
| 00000 |
| 33333 |
| 00000 |
| 00000 |
| 00000 |
| <%_L02E>-EXEC_TIME |
| ??? |
| ?????? |
| ?????? |
| <%_L02F> |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| LS_ACTREL-EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| GF_EXEC_TIME_EVENT |
| E |
| 4 |
| 5 |
| 0 |
| 0 |
| SYST-REPID |
| SAPLDSVAS_PROC |
| 5454455455554422222222222222222222222222 |
| 310C43613F02F300000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| LS_ACTREL-EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-SAPRL+0(4) |
| 70 |
| 33 |
| 70 |
| 00 |
| 00 |
| LS_ACTREL-ACTION |
| 108 |
| 333 |
| 108 |
| 000 |
| 000 |
| LF_FORM_NAME |
| ACTION_108 |
| 44544453332222222222222222222222 |
| 1349FEF1080000000000000000000000 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| ME->PROGRAM |
| RDSVASAEW_ROOT_____________073 |
| 5455454455544555555555555553332222222222 |
| 243613157F2FF4FFFFFFFFFFFFF0730000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| LS_STDPARAMETER |
| EA6000000000255###ESESSION                                           00047EA_ROOT |
| 4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222 |
| 516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No.      10 Ty.          METHOD |
| Name LCL_ACTION_SEQUENCE=>EXECUTE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PO_CTNODE |
|
2000D000
E0001C00
PF_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_VERSNR
00000
33333
00000
00000
00000
<%_L02E>-EXEC_TIME
<%_L02F>
I
4
9
0
0
LS_ACTREL-EXEC_TIME
I
4
9
0
0
LS_ACTREL-EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_ACTREL-ACTION
108
333
108
000
000
LF_FORM_NAME
ACTION_108
44544453332222222222222222222222
1349FEF1080000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
ME->PROGRAM
RDSVASAEW_ROOT_____________073
5455454455544555555555555553332222222222
243613157F2FF4FFFFFFFFFFFFF0730000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_STDPARAMETER
EA6000000000255###ESESSION                                           00047EA_ROOT
4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222
516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.       9 Ty.          METHOD
Name LCL_CHECK_TREENODE=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GF_EXEC_TIME_ATTRIBUTES
a
6
1
0
0
RSJOBINFO
00000000000000                                  ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME
|
| 2000D000 |
| E0001C00 |
| GT_OPEN_SESSIONS |
| Table IT_3668[1x44] |
| FUNCTION-POOL=DSVAS_PROCDATA=GT_OPEN_SESSIONS |
| Table reference: 1911 |
| TABH+ 0(20) = 807E0D3E000000000000000077070000540E0000 |
| TABH+ 20(20) = 010000002C000000FFFFFFFF0417010010040000 |
| TABH+ 40( 8) = 10000000A4318001 |
| store        = 0x807E0D3E |
| ext1         = 0x00000000 |
| shmId        = 0     (0x00000000) |
| id           = 1911 (0x77070000) |
| label        = 3668 (0x540E0000) |
| fill         = 1     (0x01000000) |
| leng         = 44    (0x2C000000) |
| loop         = -1    (0xFFFFFFFF) |
| xtyp         = TYPE#000007 |
| occu         = 16    (0x10000000) |
| access       = 4     (ItAccessHashed) |
| idxKind      = 0     (ItIndexNone) |
| uniKind      = 1     (ItUnique) |
| keyKind      = 3     (user defined) |
| cmpMode      = 8     (cmpManyEq) |
| occu0        = 1 |
| groupCntl    = 0 |
| rfc          = 0 |
| unShareable = 0 |
| mightBeShared = 0 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind       = 0 |
| isUsed       = 1 |
| isCtfyAble   = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi         = 0xC0AB0D3E |
| pgHook       = 0x00000000 |
| idxPtr       = 0x78F10D3E |
| shmTabhSet   = 0x00000000 |
| id           = 2504 (0xC8090000) |
| refCount     = 0     (0x00000000) |
| tstRefCount = 0     (0x00000000) |
| lineAdmin    = 16    (0x10000000) |
| lineAlloc    = 16    (0x10000000) |
| shmVersId    = 0     (0x00000000) |
| shmRefCount = 1     (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook      = Not allocated |
| collHook     = Not allocated |
| ext2         = Not allocated |
| >>>>> 2nd level extension part <<<<< |
| tabhBack     = Not allocated |
| delta_head   = Not allocated |
| pb_func      = Not allocated |
| pb_handle    = Not allocated |
| GF_EXEC_TIME_BEFORE_REPORT_GEN |
| R |
| 5 |
| 2 |
| 0 |
| 0 |
| GF_EXEC_TIME_INIT |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| ME->INITIALIZED |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| GF_EXEC_TIME_AFTER |
| A |
| 4 |
| 1 |
| 0 |
| 0 |
| ME->ACTSEQ |
|
2000D000
C0003C00
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME->HAS_TABLES
X
5
8
0
0
SYST
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
SY-REPID
SAPLDSVAS_PROC
5454455455554422222222222222222222222222
310C43613F02F300000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHECK_TABLES
|
| 2000D000 |
| 3000CC00 |
| No.       8 Ty.          METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME->DYNAMIC |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| ME |
|
2000D000
E0001C00
GF_SESSION_DEF_TYPE_MORE_DEV
L
4
C
0
0
ME->ACTIVE
X
5
8
0
0
GF_SESSION_DEF_TYPE_VERSION
V
5
6
0
0
ME->CON
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHILD_CONDSEQ
F0000000
F0000000
GF_CONTEXT_SESSION
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->CHILDREN
Table[initial]
LO_TNODE
|
| F0000000 |
| F0000000 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No.       7 Ty.          METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME |
|
2000D000
F0000C00
ME->CHILD_CONDSEQ
|
| F0000000 |
| F0000000 |
| ME->CHILDREN |
| Table IT_3674[26x8] |
| DATA=CHILDREN
Table reference: 1919
TABH+ 0(20) = 68550D3E00000000000000007F0700005A0E0000
TABH+ 20(20) = 1A00000008000000800100000417010030080000
TABH+ 40( 8) = 10000000C1288001
store        = 0x68550D3E
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 1919 (0x7F070000)
label        = 3674 (0x5A0E0000)
fill         = 26    (0x1A000000)
leng         = 8     (0x08000000)
loop         = 384   (0x80010000)
xtyp         = TYPE#000029
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 4     (cmpSingleEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xB0B10D3E
pgHook       = 0xF0882E3E
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 2508 (0xCC090000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 48    (0x30000000)
lineAlloc    = 48    (0x30000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
LO_TNODE
|
| 2000D000 |
| E0001C00 |
| LO_CTNODE |
|
2000D000
E0001C00
%_SPACE
2
0
0
0
No.       6 Ty.          METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
SESSION
5455444222
35339FE000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME->GLOBAL_CHECK_GRP |
| EA_ROOT |
| 44554452222222222222 |
| 51F2FF40000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| ME->GLOBAL_VERSNR |
| 00047 |
| 33333 |
| 00047 |
| 00000 |
| 00000 |
| ME->CHECK_TREE |
|
2000D000
F0000C00
GF_EXEC_TIME_MODUS_CLOSE
W
5
7
0
0
ME->RAISED_EVENTS
Table[initial]
GF_EXEC_TIME_LOGICAL_COMPLETE
L
4
C
0
0
No.       5 Ty.          METHOD
Name LCL_SESSION=>CONTEXT_INSTANCES_CREATE
LT_ZOMBIES
Table[initial]
LS_CTREL-TREENODE
F0000000
F0000000
LO_ZOMBIE
|
| F0000000 |
| F0000000 |
| LT_NEW_CONINS |
| Table IT_3670[1x100] |
| FUNCTION-POOL=DSVAS_PROCCLASS=LCL_SESSIONMETHOD=CONTEXT_INSTANCES_CREATEDATA=LT_NEW_CONINS |
| Table reference: 1920 |
| TABH+ 0(20) = 90C50D3E30F3DE3D0000000080070000560E0000 |
| TABH+ 20(20) = 0100000064000000080100000417010060140000 |
| TABH+ 40( 8) = 01000000C1248401 |
| store        = 0x90C50D3E |
| ext1         = 0x30F3DE3D |
| shmId        = 0     (0x00000000) |
| id           = 1920 (0x80070000) |
| label        = 3670 (0x560E0000) |
| fill         = 1     (0x01000000) |
| leng         = 100   (0x64000000) |
| loop         = 264   (0x08010000) |
| xtyp         = TYPE#000094 |
| occu         = 1     (0x01000000) |
| access       = 1     (ItAccessStandard) |
| idxKind      = 0     (ItIndexNone) |
| uniKind      = 2     (ItUniqueNon) |
| keyKind      = 1     (default) |
| cmpMode      = 2     (cmpSingleMcmpR) |
| occu0        = 1 |
| groupCntl    = 0 |
| rfc          = 0 |
| unShareable = 0 |
| mightBeShared = 1 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind       = 0 |
| isUsed       = 1 |
| isCtfyAble   = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi         = 0x08AB0D3E |
| pgHook       = 0x00000000 |
| idxPtr       = 0x00000000 |
| shmTabhSet   = 0x00000000 |
| id           = 2505 (0xC9090000) |
| refCount     = 0     (0x00000000) |
| tstRefCount = 0     (0x00000000) |
| lineAdmin    = 1     (0x01000000) |
| lineAlloc    = 1     (0x01000000) |
| shmVersId    = 0     (0x00000000) |
| shmRefCount = 1     (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook      = 0xB0F0BE3D |
| collHook     = 0x00000000 |
| ext2         = 0x00000000 |
| >>>>> 2nd level extension part <<<<< |
| tabhBack     = Not allocated |
| delta_head   = Not allocated |
| pb_func      = Not allocated |
| pb_handle    = Not allocated |
| <LFS_CONINS> |
| SESSION |
| 54554442222222222222222222222222222222222222222222 |
| 35339FE0000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| ME |
|
90006000
4000B000
<LFS_CONINS>-CON
SESSION
5455444222
35339FE000
0000000000
0000000000
<LFS_CONINS>-INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
GF_EXEC_TIME_BEFORE
B
4
2
0
0
No.       4 Ty.          METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
2222222222
0000000000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME |
|
90006000
4000B000
ME->LOGICAL_COMPLETE
2
0
0
0
GF_EXEC_TIME_COMPLETE
C
4
3
0
0
ME->COMPLETE
2
0
0
0
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
No.       3 Ty.          FUNCTION
Name DSVAS_PROC_SESSION_OPEN
PF_HANDLE_TO_USE
0
0000
0000
PF_MAX_TREE
2
0
0
0
PF_MODE
C
4
3
0
0
PS_SESSION_NUMBER
EA6000000000255
443333333333333
516000000000255
000000000000000
000000000000000
PF_HANDLE
1
0000
1000
PF_HIDE_TREE
2
0
0
0
PF_MODE_USED
2
0
0
0
PF_NEXT_CHECK_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_NEXT_CHECK_ID
00000
33333
00000
00000
00000
PF_NEXT_CON
2222222222
0000000000
0000000000
0000000000
PF_NEXT_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PT_ERRORS
Table[initial]
PT_FRONTEND_TREE[]
Table[initial]
PF_LANGUAGE
E
4
5
0
0
<%_TABLE_DSVASSESSADMIN>
LF_BUNDLE_VERSNR
00038
33333
00038
00000
00000
DSVASRESULTSGEN-CLUSTR
0
00
00
PS_SESSION_NUMBER-SESSNO
6000000000255
3333333333333
6000000000255
0000000000000
0000000000000
LS_OPEN_SESSIONS-SESSION
|
| 90006000 |
| 4000B000 |
| LO_SESSION |
|
90006000
4000B000
LS_OPEN_SESSIONS
EA6000000000255C####k#
4433333333333334009060
51600000000025531040B0
0000000000000000000000
0000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_SESSDEFGEN-MULTI_USER

Please replace the Service Definitions in your SAP Solution Manager
system as described in SAP Note 727998.
As of SAP Solution Manager 7.0 (= 4.0) Support Package Stack 15 (which
includes ST-PI 700_2005_1 SP06) you can trigger the required steps
within transaction SDCCN:
Menu Utilities -> Maintain Service Definitions ->
Select 'Delete and Replace Service Definitions -> Confirm this
selection-> Confirm that you want to delete the definitions -> Confirm
that a new task 'Service Definition Refresh' was created
Take a note of the task id -> Review the log for this task id when it
is completed. You should not see any errors for either the update
of a Service Definitions table or the generation of any re-import
include.
Reschedule SM:EXEC SERVICES and the reported dump will no longer
occur.

Can I install Solution Manager 7.0 in Window Server 2008 R2 Enterprise ed.?

Hi, SDN experts.
I am trying to install Solution Manager 7.0 in in Window Server 2008 R2?
I checked the the software requirement for SAP Solution Manager 7.0, it only mentioned Window Server 2003 and 2008 enterprise edition.
I am trying to install Solution Manager 7.0 in in Window Server 2008 R2 enterprise edition?
When I ran the Solution Manager Master Installer, the Pre-requisite Checker gave a warning message saying that it detected incompatible server version, that the server version is Windows NT 6.1 (Build 7601: Service Pack 1) (I guess it meant Window Server 2008 R2).
=======
The following Windows operating system version is supported: Windows Server 2003 (i.e. Version 5.2) and Windows Server 2008 (i.e. Version 6.0).
Current Windows version: Version 6.1, Service Pack 1.0, productive type: Server.
You can check the current version of you operating system by runningu2026u2026..
========
Can I actually install Solution Manager 7.0 in Window Server 2008 R2? Will this cause problem during the installation/post-installation if I ignore this message?
Thanks,
KC

Hi,
I think it is not straight forward to install SAP Solution Manager 7.0 in MS Window Server 2008 R2.
I am installing Solution Manager 7.0 , the installation encountered error on Create Java Users step (Phase 31 of 44). When I login to SAP solution Manager system through SAP GUI. I encountered this error:
"OS release Windows NT 6.1 7601 Service Pack 1 4x AMD64 Level 6 (Mod 44 Step 2) is not supported with this kernel (700)'
I found that it is because I am installing SAP Solution Manger 7.0 in MS Window Server 2008 R2, which the existing kernel version does not support.
Do you know which kernel I should install?
I browsed in:
SAP Application Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0" Entry by Component" Solution Manager ABAP Stack
SAP KERNEL 7.00 64-BIT UNICODE --> Windows Server on x64 64bit -->MS SQL SERVER
I downloaded:
SAPEXEDB_291-20001361.SAR Kernel Part II (for Basis 7.00) 291
Is this the right Kernel patch I should use?
If it is the right kernel patch file, how do I apply the latest kernel to existing Solution Manager system? Can you give me some guidance on this?
Thanks,
KC

Solution Manager 4.0 - MSCS Installation

Similar Messages

Maybe you are looking for