Upgrading SolMan to EHP1

Hello Gurus,
Need a help,
I am in the process of upgrading the SolMan to EHP1.
I have read all the Docs available in SMP and also refered the Blogs.
Can any 1 please give the Brief steps that we need to follow to upgrade SolMan as i need to submit the request i need to specify the what all actions am going to perform. So i need the brief steps in order, that would of great help.
Our Kernel release is 700 SOlMan7. i know that we need to take SP to 17 before upgradation. But what abt Kernel level.
Here SP17 means is it only ABAP. Basis and Java or it it all the SP availabe in the system should be take to 17.
Please help.
Regards,
Sr

Hi Anjali,
Upgrade all components which are not upgraded by stack upgrade to highest level.
Does this mean i need to upgrade all the SP levels of all SP available in my system.
Upgrade Java to SP17 using JSPM
can you please let me know the path where i can download the Java SP17.
Download SPS tab file in XML from Marketplace for EhP1 and upload in /usr/sap/trans/EPS/in
As per the note sapnote_0001169247, there are 2 XML files SAP_SOLUTION_MANAGER_70_EHP1.xml and SPSTab.xml.
whats the main use of these files, whats the mai purpose, what they contain. How they are useful in upgrading SolMan to EHP1.
Please let me know.
Regards,
Sr

Similar Messages

Upgrading Solman from SP 17 to EHP1 errors with the Kernel install

I've been trying to upgrade solman to EHP1 but I get errors when I try to install Kernel 7.01. After I have copied the kernel to \SYS\exe\uc\NTAMD64 I can start SAP and for a while it works. Then SAP stops working and both services stop. I've tried to restart the services but I get and error telling me its the wrong product version and to re-install the software. Its a 64bit unicode kernel on windows 2003 64bit and I have the right kernel. Any ideas anyone?

HI
I am having the same issues. when upgrading via JSPM or manually, the sap services won't start and keep saying the version is incompatable, and suggested to reinstall.
Did you manage to get around it?
Regards
Kevin

Error in PREP_INIT/VERSCHK_INI phase during upgrade to NW70 EHP1 SR1

Hi All,
We have a NW system with the following components to NW 70 EHP1 SR1:
SAP_ABA     700     0013     SAPKA70013     Cross-Application Component
SAP_BASIS     700     0013     SAPKB70013     SAP Basis Component
PI_BASIS     2005_1_700     0013     SAPKIPYJ7D     PI_BASIS 2005_1_700
ST-PI     2005_1_700     0000          -     SAP Solution Tools Plug-In
SAP_BW     700     0015     SAPKW70015     SAP NetWeaver BI 7.0
BI_CONT     703     0000          -     Business Intelligence Content
We are in the process of upgrade to SAP EHP1 FOR SAP NETWEAVER 7.0 SR1 and we got the below error during the upgrade:
Checks after phase PREP_INIT/VERSCHK_INI were negative!
Last error code set: Start Release configuration 'SAP_ABA=700,SAP_BASIS=700,SAP_BW=700' is not supported Compare the release of your SAP system with the requirements listed in the documentation.
Choose action
     Repeat phase VERSCHK_INI to continue at the point it stopped
     Cancel the current phase VERSCHK_INI and go back to wizard
     Exit this program
We verified the DVDs (media list) we are uing for the upgarde and it is correct.
Any ideas on how this can be resolved?
Regards
ND

Have you read this note: https://service.sap.com/sap/support/notes/1568031
Looks like you have to include the latest corrections for EHPI installer.
Thanks
Srikanth Mandalapu
Cert Basis/Netweaver

Error start java upgrade SOLMAN 7.01 to 7.1

Hi gurus, I'm faced an error in a upgrade SOLMAN 7.01 to 7.1 when try to start de java instance: I'm using SUM 1.0 SP 12 Patch 13. Follow the START-AS-JAVA_01.LOG:
Apr 30, 2015 2:56:32 PM [Info ]: Start service for instance 10 on host srv-sum-ora ... Apr 30, 2015 2:56:32 PM [Info ]: Process ID 499, name sapstartsrv has been started. Apr 30, 2015 2:56:32 PM [Info ]: Command line: /usr/sap/SUD/DVEBMGS10/exe/sapstartsrv pf=/usr/sap/SUD/SYS/profile/START_DVEBMGS10_srv-sum-ora -D Apr 30, 2015 2:56:32 PM [Info ]: Standard out: /SUM/SUM/sdt/log/SUM/INSTALL_SERVICE_10_02.OUT Apr 30, 2015 2:56:32 PM [Info ]: Process ID 499 has been started. Apr 30, 2015 2:56:32 PM [Info ]: Waiting for process ID 499, name sapstartsrv to finish. Apr 30, 2015 2:56:32 PM [Info ]: Process ID 499, name sapstartsrv has been finished, exit code 0. Apr 30, 2015 2:56:32 PM [Info ]: Wait for service for instance 10 on host srv-sum-ora to start... Apr 30, 2015 2:56:34 PM [Info ]: Process ID 500, name sapcontrol has been started. Apr 30, 2015 2:56:34 PM [Info ]: Command line: /usr/sap/SUD/DVEBMGS10/exe/sapcontrol -nr 10 -host srv-sum-ora -prot NI_HTTPS -function GetProcessList Apr 30, 2015 2:56:34 PM [Info ]: Standard out: /SUM/SUM/sdt/tmp/SAPCONTROL_GETPROCESSLIST_10_03.OUT Apr 30, 2015 2:56:34 PM [Info ]: Process ID 500 has been started. Apr 30, 2015 2:56:34 PM [Info ]: Waiting for process ID 500, name sapcontrol to finish. Apr 30, 2015 2:56:37 PM [Info ]: Process ID 500, name sapcontrol has been finished, exit code 4. Apr 30, 2015 2:56:37 PM [Info ]: The sapcontrol service on host srv-sum-ora and instance 10 is started. Apr 30, 2015 2:56:37 PM [Info ]: Service for instance 10 on host srv-sum-ora has been started. Apr 30, 2015 2:56:37 PM [Info ]: Starting instance number 10 on host srv-sum-ora with timeout of 7200 seconds. Apr 30, 2015 2:56:37 PM [Info ]: Process ID 501, name sapcontrol has been started. Apr 30, 2015 2:56:37 PM [Info ]: Command line: /usr/sap/SUD/DVEBMGS10/exe/sapcontrol -nr 10 -host srv-sum-ora -prot NI_HTTPS -function GetProcessList Apr 30, 2015 2:56:37 PM [Info ]: Standard out: /SUM/SUM/sdt/tmp/SAPCONTROL_GETPROCESSLIST_10_04.OUT Apr 30, 2015 2:56:37 PM [Info ]: Process ID 501 has been started. Apr 30, 2015 2:56:37 PM [Info ]: Waiting for process ID 501, name sapcontrol to finish. Apr 30, 2015 2:56:38 PM [Info ]: Process ID 501, name sapcontrol has been finished, exit code 4. Apr 30, 2015 2:56:38 PM [Info ]: Starting instance number 10 on host srv-sum-ora with timeout of 7200 seconds. Apr 30, 2015 2:56:38 PM [Info ]: Triggering an instance start by sapcontrol... Apr 30, 2015 2:56:38 PM [Info ]: Process ID 502, name sapcontrol has been started. Apr 30, 2015 2:56:38 PM [Info ]: Command line: /usr/sap/SUD/DVEBMGS10/exe/sapcontrol -nr 10 -host srv-sum-ora -prot NI_HTTPS -function Start Apr 30, 2015 2:56:38 PM [Info ]: Standard out: /SUM/SUM/sdt/tmp/SAPCONTROL_START_10_01.OUT Apr 30, 2015 2:56:38 PM [Info ]: Process ID 502 has been started. Apr 30, 2015 2:56:38 PM [Info ]: Waiting for process ID 502, name sapcontrol to finish. Apr 30, 2015 2:56:40 PM [Info ]: Process ID 502, name sapcontrol has been finished, exit code 0. Apr 30, 2015 2:56:40 PM [Info ]: An instance start was triggered. Apr 30, 2015 2:56:40 PM [Info ]: Sent the start command to instance number 10 on host srv-sum-ora with timeout of 7200 seconds. Apr 30, 2015 2:56:40 PM [Info ]: Process ID 503, name sapcontrol has been started. Apr 30, 2015 2:56:40 PM [Info ]: Command line: /usr/sap/SUD/DVEBMGS10/exe/sapcontrol -nr 10 -host srv-sum-ora -prot NI_HTTPS -function WaitforStarted 7200 5 Apr 30, 2015 2:56:40 PM [Info ]: Standard out: /SUM/SUM/sdt/tmp/SAPCONTROL_WAITFORSTARTED_10_01.OUT Apr 30, 2015 2:56:40 PM [Info ]: Process ID 503 has been started. Apr 30, 2015 2:56:40 PM [Info ]: Waiting for process ID 503, name sapcontrol to finish. Apr 30, 2015 4:56:45 PM [Info ]: Process ID 503, name sapcontrol has been finished, exit code 1. Apr 30, 2015 4:56:45 PM [Error ]: Return code condition success evaluated to false for process sapcontrol for action wait for started. Apr 30, 2015 4:56:45 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not start SAP instance with number 10. Could not check if the instance number 10 on host srv-sum-ora is started. Sapcontrol client could not perform action wait for started on instance 10 Return code condition success evaluated to false for process sapcontrol for action wait for started. Thanks for the help!!!

check out this Kbase article
http://docs.info.apple.com/article.html?artnum=301422
it says
Logic Pro 7.1: Erroneous newer software message when installing in Tiger
When you're installing Logic Pro 7.1 on a Mac OS X 10.4 "Tiger" computer, certain circumstances may produce this alert message:
The chosen volume contains software which is newer then [sic] the software you are installing.
The message is erroneous; it can happen when you're updating from Logic Pro version 7.01. Simply click the Continue button in the dialog to ignore it.

Issue after upgrading SOLMAN-Kernel to 700-201

Hi Gurus,
I have upgraded SOLMAN Kernel from 700-144 to 700-201. I have done step by step upgrade i.e.,
700-147 to 700-175 - No issues
700-175 to 700-201 - Server started partially.
In the Console, the server is partially started after upgrading from 175 to 201(Yellow and Green).
"Dispatcher Running but not connected to Message Server, J2EE: All processes running"
I am able to login to all clients as well as J2EE.
are there any patch or any OSS notes to implement after upgrading to Kernel 700-201?
SOLMAN:
SP-17
WIN-32
Thanks in advance...
Regards
Shreeshail Ganiger

Dear Shreeshail,
Try to upgrade your kernel to 221, there are quite issues with 201for some installations.
Check if your satstartsrv.exe has been updated with new version too. this you can check with file version by right clicking.
Regards
Shailesh

SMD Post upgrade activities after EHP1

Hi,
We have recently upgraded our solution manager from SP15 to SP20(EHP1). We have upgraded our kernel to 7.01
I found that in the directory /usr/sap/SMD/exe, the kernel files are still in version 700.
So what is the exaxt post processing steps related to SMD and wily introscope in Solman and satellite system after EHP 1 upgrade
PS: We are upgrading our satellite systems ie ECC 6.0 to ECC 6.0 EHP4 and Netweaver 2007 systems to Netweaver 2007 EHP1.
Best Regards,
Sriram.S

Any updates...
Sriram.S

Is Wily Introscope a requirement with Solman 7 ehp1

We are finishing and upgrade from 3.2 to 7 EHP1.
Due to limited system capacity we have not installed the Wily Introscope product. At this time we were not planning on using its functionality. We are wanting to keep the basic functionality of solman 3.2 plus add the MOPZ piece.
I'm using the solman_setup tcode to go through the basic config wizard now. I've reached the Landscape Data step where it is asking for the Wily Introscope info. Since it doen't exist, can I bypass this step?
Thanks for your advice.
Laurie McGinley

Thanks Jarad,
That is what I thought (it isn't required), but needed to double check before I bypassed that bit of the setup.
Appreciate the quick response too!
Laurie

System Monitoring - Solman 7 EHP1

Hi
Solution Manager 7.0 EHP1 / Windows 2008 / Oracle
Satellite System R/3 Enterprise extn set 110 / Solaris on Sparc / Oracle
I am having trouble configuring System monitoring on solution Manager. Here is what I have done
Added the satellite system to SLD, Configured data collector (RZ70) in the satellite system, Pushed data from SLD to SMSYS (automatic transfer).
Installed CCMS agent + CCMSPING agent in satellite system. Checked connectivity in solman with RZ21. Connectivity is fine.
Created Monitor sets and monitors in CCMS for monitoring satellite system. Client data is visible in CCMS.
Created a solution in DSWP. Created logical component in SMSY. Assigned the logical component to the solution. Now I can see the data in DSWP.
Here are my questions
==================
1. In DSWP, everytime I have to view data, I have to click on "Setup System Monitoring" to view the alerts in the satellite system
I see a red alert reading for instance availability. Similarly,
In the system monitoring workcenter, I see the status of both the solution manager and the satellite system greyed out with a cross. When I move my mouse over it, it reads, no CCMSPING data available.
Any idea as to why this happens?
2. For what I see after I click on "Setup System Monitoring" I have parameters which I can configure. I see default values for these parameters. Is there like a recommendation or a template which can be used to setup these monitoring parameter values?
3. I have configured the ccmsping in the solution manager (for the solution manager) however the ccmsping service refuses to run. It throws a error reading "The system could not find the file specified". The ccmsping exe file is present in the location stated. Are there other files that this is looking for?
4. While registering the agent in the satellite system, I first registered with the CSMREG id. It failed with the message,
INFO: [SMG:040:CSMREG] connected to SMG, host sapsm.NA.XXX.NET, System Nr. 00, traceflag [ ]
INFO: SMG release is 701 , (kernel release 701 )
        RFC Error Info:
         message:
         status: EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
         intstat:
      Go Ahead anyway? n/[y] :
INFO: handling destination SAPCCM4X.SAPR3PR1.00
ERROR: can't register at SMG. RfcRc = 2, AUTHORITY_NOT_AVAILABLE
RFC Error Info for SALF_CSM_AGENT_REGISTER
message:
status: EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
intstat:
I then did this with a dialog user. That worked. Agent was registered in solution manager. Any idea on why this error would show up with the CSMREG? I am concerned about issues which can come up when the password for the dialog user changes.
I am not sure how to upload screenshots of what i see, probably if i do that, it will be easy to relate to the issue which I am mentioning here. Is there a way I can do that?
Let me know if you need any more information from my side to understand this.
Ideas will be appreciated.
thanks
Ravi

Hello Ravi,
Additionally you will want to look at SAP Note 1175058 - Problems with CCMSPING in SAP Solution Manager, especially
c) Ensure that the message server host name in the monitoring options of CCMSPING and the message server of the corresponding main instance of the relevant system is the same in the SAP Solution Manager landscape
(SMSY). Important: The monitoring options of CCMSPING must not be configured using an IP address.
Regards,
Paul

Upgrading SolMan 3.1 (32bit) to SolMan 4.0 (64bit)

Hello all,
We currently run SolMan v3.1 on aged 32bit hardware and we plan to upgrade this to SolMan v4 on a new 64bit infrastructure. As part of this task, we would also like to move from Windows 2000 to Windows 2003 x64 and from Oracle 9.2 to Oracle 10.2
The current situation is that the new server is built to Windows 2003 x64 level only. Nothing else is installed on the new server at this time. My plan was to install Oracle 9.2 and SolMan 3.1 and then take a system copy of the existing database and then upgrade it to SolMan v4 and Oracle 10.2 (leaving the old system as-is for recovery reasons, should we run into problems).
Has anyone any experience of doing this in a Windows and Oracle environment who could help me with getting this right?
Many thanks,
Arwel Owen.

I answered you in another duplicated post at Re: Upgrading Oracle 9.2 (32bit Windows 2000) to 10.2 (64bit Windows 2003)
Message was edited by:
Eric Brunelle

SAP ERP6 product version missing in SMSY for EHP4 upgrade Solman 7

Hello
I am trying to install Ehp 4 but when i try to create the new system as SAP ERP6 in solution manager (SMSY )but product version is missing ?
iam now stuck any ideas will be welcome as i need to get the stack.xml inorder to proceed with EHP installer

Hi,
Check below notes before proceeding with EHP download in solman,sap has recommaned to apply these notes when we tried to download EHP,
Must Implemeted
1238929 MOPZ: Solution Is Not Selected in Work Center
1240389 Maintenance optimizer transaction with incorrect Java host
1243197 MOPZ: Add Caption for Product and Stack of Stack Delta XML
1246549 Status were reset to step 1 after Download Basket approval
1247550 present all avaliable systems in mopz step 1
1250781 SMSY: Error for Java system components from the SLD
1255219 Java systems w/o ABAP instance in maintenance optimizer
1262239 SMSY: Database name *LOCAL
1273095 SMSY: Incorrect database server (Java)
1306173 Maintenance Optimizer: Enhancement Package Stacks
1308152 MOPZ: Check configuration for stack delta XML generation
1311841 Maintenance Optimizer: Rename stack delta index file
1319083 Maintenance Optimizer: Technical corrections
1326123 MOpz: Error "Update product data in Solution Manager"
1357565 MOpz: Maintain a system where EHP is installed
1402615 Translate hostname in Mopz to lower case
1407905 MOpz: Error when withdrawing in step 4
Cannot be implemented, but manual steps must be performed.
1141296 Solution Manager: ERP product data missing
1165587 Maintenance Optimizer: Enhancement Package stack selection
1277035 Solution Manager: EHP4 product data missing
Between what is your present stack level of solman
Regards
Uday

XPRA 70401INBICONT in Upgrade to NW EHP1 / BI EHP4

Hi all,
we are in an upgrade from NW700 BI-System with FINBASIS an SEM- Addons.
now we are running into the following error.
in the BIND_PATCH phase we added the support packages for BI_CONT 704 01-03.
Now in the XPRA-phase we get en Error:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ XPRA ERRORS and RETURN CODE in SAPR-70401INBICONT.DBW ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2EER7501XStart of the after-import method &3"RS_DTPD_AFTER_IMPORT" for object type(s) &1"DTPD" (&2"Delivery Mode") A2EERSAR 203 Source system "D01155" does not exist A2EERSAR 203 Source system "D01155" does not exist 2EEPU133 Errors occurred during post-handling "RS_AFTER_IMPORT_D" for "DSCS" "L"
The Source-System/mandant which is mentioned was deleted long time ago, but there is still some information of these deleted systems in the R/3, but i dont know where is can find these information so that it can be corrected.
Can someone help me to correct it ?
Regards
Bjoern Trabes

Thank you very much, that is the solution ....
i read so many notes, but this title seems to me to be not the right one, so i didn't read it
Regards
Bjoern

Error while upgrading solman sp12 in java stack

It error showing in java stack...please help me out...
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\DSO\DVEBMGS00\SDM\program\log\sdmcl20071008170730.log]/>
<!PATTERN[sdmcl20071008170730.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Oct 8, 2007 10:08:05 AM Info: -
Starting validation -
Oct 8, 2007 10:08:05 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
Oct 8, 2007 10:08:05 AM Info: Update strategy: UpdateLowerOrChangedVersions
Oct 8, 2007 10:08:05 AM Info: Starting deployment prerequisites:
Oct 8, 2007 10:08:07 AM Info: Loading selected archives...
Oct 8, 2007 10:08:07 AM Info: Loading archive 'C:\usr\sap\DSO\DVEBMGS00\SDM\program\temp\LMSERVICE12_0-20001429.SCA'
Oct 8, 2007 10:08:16 AM Info: Loading archive 'C:\usr\sap\DSO\DVEBMGS00\SDM\program\temp\ADSSAP12_0-10003001.SCA'
Oct 8, 2007 10:08:36 AM Info: Loading archive 'C:\usr\sap\DSO\DVEBMGS00\SDM\program\temp\BIMMR12_0-10002782.SCA'
Oct 8, 2007 10:08:38 AM Info: Loading archive 'C:\usr\sap\DSO\DVEBMGS00\SDM\program\temp\KMKWJIKS12_0-10003021.SCA'
Oct 8, 2007 10:08:39 AM Info: Loading archive 'C:\usr\sap\DSO\DVEBMGS00\SDM\program\temp\BIUDI12_0-10002781.SCA'
Oct 8, 2007 10:08:40 AM Info: Loading archive 'C:\usr\sap\DSO\DVEBMGS00\SDM\program\temp\CAFUM12_0-10003472.SCA'
Oct 8, 2007 10:08:41 AM Info: Loading archive 'C:\usr\sap\DSO\DVEBMGS00\SDM\program\temp\SAPJTECHS12_0-10003467.SCA'
Oct 8, 2007 10:08:47 AM Info: Loading archive 'C:\usr\sap\DSO\DVEBMGS00\SDM\program\temp\CAF12_0-10003464.SCA'
Oct 8, 2007 10:08:51 AM Info: Loading archive 'C:\usr\sap\DSO\DVEBMGS00\SDM\program\temp\LMTOOLS12_0-10003486.SCA'
Oct 8, 2007 10:08:59 AM Info: Loading archive 'C:\usr\sap\DSO\DVEBMGS00\SDM\program\temp\UMEADMIN12_0-10003471.SCA'
Oct 8, 2007 10:09:01 AM Info: Selected archives successfully loaded.
etc....
sed by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
     at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
     at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
     ... 38 more
Caused by: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
     at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:701)
     at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:689)
     at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
     at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:424)
     ... 1 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Oct 8, 2007 10:10:08 AM Info: Starting to save the repository
Oct 8, 2007 10:10:08 AM Info: Finished saving the repository
Oct 8, 2007 10:10:08 AM Info: Starting: Update: Selected software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.12.0.20070507083121''/'1' updates currently deployed software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.10.0.20061022041500''/'0'.
Oct 8, 2007 10:10:08 AM Error: Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.12.0.20070507083121''/'1':
Failed deployment of SDAs:
development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'710.20060929113452.336248'/'1' : aborted
Please, look at error logs above for more information!
Oct 8, 2007 10:10:08 AM Info: Starting to save the repository
Oct 8, 2007 10:10:09 AM Info: Finished saving the repository
Oct 8, 2007 10:10:09 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Oct 8, 2007 10:10:09 AM Error: -
At least one of the Deployments failed -

YES,
Reboot will stop all the other services that are running and jamed. also, it will clean the old buffer too.
Please try and it should work fine.
can you tell me briefly how r u applying sp12? kinda explain from step 1 please. I can correct it if anythign missin.
Thanks,

Sol man upgrade!

Dear All,
Could you please guide me in upgrading solution manager from 4.0 SR2(Patch level 11) to Solman 7 EHP1...
Can i upgrade it through EHPi or i have to deploy patches first through (SPAM/SAINT)
Any prompt help related to this is appreciated......
Regards,
Sohal....

Hi Harvinder,
In order to upgrade solman to EHP1. You cannot use EHPI installer. You have to do this via SAINT/JSPM.
Also, check 1169247, 822380
Also, link https://websmp201.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000065932
Thanks
Sunny

Solution Manager on 32-Bit for ECC-6

Hi Gurus,
We need to bring our 32-Bit ECC-6 system on EhP4 as soon as possible.
From installtion documents I found that its two step installation. First install EhP3 and then EhP4 using SAINT.
To install EhP we need use Solution Manager. Currently we dont have Solution Manager installed. Our first step would be installing Solution Manager. There are two options available:
1. SAP Solution Manager 7.0 including SAP Enhancement Package 1.
2. SAP Solution Manager 7.0.
As everywhere its written we can not install solution manager on 32-bit but some some threads say we can do.
Confirm that Solution Manager 7 cannot be installed on a 32-bit windows sys
Assuming that we can still install Solution manage on 32 bit, first we need to install EhP3, which solution manager version should we use 1 or 2?
Thanks in advance
Regards
Shreeshail Ganiger
Edited by: ssganiger on Nov 5, 2009 6:48 AM

Hi Shreeshail,
Please use opton 1. This way you can choose to install either EHP3 or EHP4 (as your case maybe).
Also, you wouldn't need to upgrade solman to ehp1, as ehp1 comes with a lot of corrections which otherwise you will have to manually implement on a Solution Manager 7.0 system.
Cheers
Rishi

Solman 7.0 with Willy Interscope 8.0 Upgrading EHP1

Hello Every body,
I am looking for the pre- requisites for Upgrading Solman 7.0 to EHP1And we have Willy Interscope 8.0 installed.
Do we have any impact for Sattilite Systems as they have Kernel 7.0.
And we are palnning to Install SMD in Solman and Sattilite system, So Which version is Compatible for our Scenario.
I have checked in Sap and found 7.11 is Suitable for EHP1.
I need some Suggestions.
Appriciate Quick Response,
Thank You,
SK.

Hi,
I am looking for the pre- requisites for Upgrading Solman 7.0 to EHP1
I would recommend to follow Upgrade Guide for the same and specially this [SAP Note 1146578 - Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP1|https://service.sap.com/sap/support/notes/1146578] to get more information. You will requried to use latest SAPup and correction pachkages for Upgrade.
we have Willy Interscope 8.0 installed.
Do we have any impact for Sattilite Systems as they have Kernel 7.0.
I think it will not affect. The main concern is that the version of Introscope Agents (on managed systems) should not be newer than the Introscop Enterprise Manager version (on solman host). To get more info, refer [FAQs - Willy Introscope|https://websmp110.sap-ag.de/~sapidb/012003146900000709302008E/IntroscopeFAQ.pdf] and SAP No[Note 797147 - Wily Introscope Installation for SAP Customers|https://service.sap.com/sap/support/notes/797147]
And we are palnning to Install SMD in Solman and Sattilite system,
So Which version is Compatible for our Scenario.
I have checked in Sap and found 7.11 is Suitable for EHP1.
With Solman 7.0 EhP1 >= SP 18 , SMD 7.01, 7.02 and 7.11 can be compitable. To get more information , refer point 2.2 of [Diagnostic Setup guide|https://websmp209.sap-ag.de/~sapidb/011000358700000952852009E.PDF].
Regards,
Bhavik G. Shroff

Upgrading SolMan to EHP1

Similar Messages

Maybe you are looking for