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

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

SAP EHP1 for Solution Manager 7.0 - Post Install Procedure

Hello Folks:
I completed Sol Manager 7.0 EHP1 installation on Win 2008 R2 with MS SQL in a sandbox environment. This is the first time I ever installed SAP on my own and i am in the process of performing post installation steps from Installation Guide.
In the install guide, there is no mention of creating a new client ex: 100. Could you please, provide a list of tasks that generally needed to perform after the installation is completed and before doing any configuration in Solution manager.
I have some very basic idea on the Basis but while going thru Installation Guide I am not sure if there any steps that generally need to perform to complete the installation. My goal is to complete the Sol Mgr installation first and then start preparing for ECC 6.0 Installation.
Thanks a lot in Advance.

Hi,
First - the basic post installation steps are:
1. sick t-code need to execute
2. se06 --> Perform Post-Installation Actions
3. RZ10 --> Utilities --> Import profiles --> Of active servers
4. execute sgen T-code --> This will take some time
5. setup STMS
6. create client (If custom required)
7. Take backup of the system
For the solution manager client you could use the default created '001' client.
Next you need to run the solman_setup template which 'sets up' the SolMan for usage.
Follow config guide at: https://service.sap.com/~sapidb/011000358700000308502009E.PDF
For installing the ECC system, only a install key(from SMSY) is to be generated from SolMan. But if you want to use the SolMan effectively, suggest you to run the entire solman_setup.
Regards,
Srikishan

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?

Is it a must to use Solution manager for ECC 6.0 upgrade

Is it a must to use Solution Manager for ECC 6.0 (FICO & HR) upgrade? I am told Solution Manager is required only if it has ABAP and JAVA stacks, or involves Enhancement Packages; and could be optional if it is only ECC 6.0 with ABAP stacks.

Hi,
I'm having a difficult time finding some guidance for setting up our R/3 Enterprise system in solman properly, so that I can create the upgrade XML file required to go directly to ERP 6.0 EHP4.
I've set up the R/3 system fine, but when i create a maintenance transaction i cannot for the life of me figure out how to tell it I want to go from r/3 to ERP6 ehp4.
Any docs out there for this?
Thanks!
I figured it out... i had to add the R/3 Enterprise logical components to my system landscape. After that I was able to select R/3 as the initial data in the maintenance transaction and then the system i wanted to upgrade, and then the option to upgrade.
Never mind!
Edited by: Tom Janes on Sep 9, 2009 12:52 AM

Upgrade to Solution Manager 7.1 missing Master upgrade DVD

Hi,
I'm upgrading Solution Manager 7.0 EHP1 to Solution Manager 7.1 . I've got the following error;
Please enter mount points for the DVDs required for the upgrade.
Enter at least the mount point containing "Upgrade master DVD"
I Can't find this "Upgrade master DVD" on market place. I've opend an OSS message but no answer yet. Anyone had that problem?
Thanks!

I had the same issue. It turns out that what it was really asking for was a SAP Kernel DVD in the correct format.
When I downloaded the SAP Kernel DVD from the Market Place, the Zip file included a directory for my platform at the first level on the DVD, and then in that directory it contains the LABEL.ASC file.
You need to ensure that when you stage the Kernel DVD, the LABEL.ASC files etc should be in the Top Level directory, or it won't be recognised as a DVD, and you'll get the erroneous message about needing an "Upgrade Export DVD" (which does not exist for Solman 7.1).
Hope this helps!

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.

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

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

Upgrade Solution Manager 4 to 7.1

Hi all,
Is it possible to have a direct upgrade from a solution manager 4 to 7.1? Or do i need to do other installation or upgrade before it is comparable for 7.1?
Pls advise. Thanks
Regard
Gary

Hello,
Solution manager 4 is synonymous with Solution Manager 7.0
The upgrade guide refere to the source system being
SAP Solution Manager 7.0
SAP Enhancement Package 1 for Solution Manager 7.0
And the target system being SAP Solution Manager 7.1
Therefore the answer is yes, you can upgrade from release 4.0/7.0 to 7.1
Have you visited
https://websmp105.sap-ag.de/~form/sapnet?_SCENARIO=01100035870000000202&_SHORTKEY=00200797470000065932
And also
http://service.sap.com/instguides -> SAP Components -> SAP Solution Manager -> Release 7.1. Upgrades
Regards,
Paul

Solution Manager 7.1 Post-installation upgrade SPS04

Similar Messages

Maybe you are looking for