SOLUTION MANAGER 4.0 SR2 - SP12 deployment issue

Dear all,
in our Solution Manager system we're moving our SP stack level from 10 to 12.
We could successfully deploy via JSPM all the needed components except sap.com/CAF 12, here's the relevant part of the JSPM log:
Jul 23, 2007 8:57:44 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 23, 2007 8:59:37 AM Info: Begin of log messages of the target system:
07/07/23 08:57:44 - ***********************************************************
07/07/23 08:57:47 - Start updating EAR file...
07/07/23 08:57:47 - start-up mode is lazy
07/07/23 08:57:47 - EAR file updated successfully for 63ms.
07/07/23 08:57:47 - Start updating...
07/07/23 08:57:47 - EAR file uploaded to server for 47ms.
07/07/23 08:59:37 - ERROR: Not updated. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/caf~km.proxies..
                     Reason: Webservices common deployment exception! The reason is: Error occured, trying to update ws clients for application sap.com/caf~km.proxies. . Additional info: ; nested exception is:
                          java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occured, trying to update ws clients for application sap.com/caf~km.proxies. . Additional info:
                          at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:162)
                          at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:118)
                          at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:104)
                          at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:77)
                          at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateManager.makeUpdate(WSClientsUpdateManager.java:53)
                          at com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate(WSDeployer.java:275)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                          at java.security.AccessController.doPrivileged(Native Method)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
I've found an interesting, Note 956443 - In NW04s deploy of Java WS with security fails, but here they speak about SP6 and we're already at 10, moving to 12... so I'm not sure.
Any advice will be greatly appreciated.
Franco.

Deal all,
thanks for all the suggestion.
Even though we tried all the advices we received the solution came from Note 941595 - Download J2SE 1.4.2 for the x64 : we switched to JDK version 1.4.2_15 and sap.com/CAF was deployed just smoothly as all the other SPs.
Again thank you !
Franco.

Similar Messages

Solution Manager 4.0 SR2: Error during step 1 installPolicyArchive

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

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

I got errors while installation of solution manager 4.0 sr2

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

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

Deploy Ic Web Client in the Solution Manager 4.0 SR2

Hi,
We have been using solution manager 4.0 service desk, and would like to deploy the IC Web Client. request if some can help with the ear/sda/sca file needed to depoly the same andso that i can start working on the same.
awaiting your response on the same. Thanks a lot in advance.
Best Regards
Mahendra K

Hi,
IC Webclient is a BSP based Application.
Activate the Correspondending Nodes in TA SCIF and you can use the IC WebClient. See also SPRO SolMan -> Config -> scenario specific -> Service Desk -> ICWebClient.
BR
Volker

Installation Problem: Solution Manager 4.0 SR2 on SLES9 MaxDB7.6

Hello altogether,
when performing an Installation of SolMan 4 on SLES9 with MaxDB7.6, it crashes on Phase 40 of 47 with the following hints:
ERROR 2007-04-18 10:31:21
 CJS-30156 SDM deployment failed for at least one of the components to deploy. SOLUTION: Check '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/callSdmViaSapinst.log' for more information.
ERROR 2007-04-18 10:31:21
 FCO-00011 The step redeployForJSPM with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|4|0|redeployForJSPM was executed with status ERROR.
(typed it from screen, maybe there are type-errors).
The "funny" thing about it:
 the file "callSdmViaSapinst.log" is looking just fine:
 Apr 18, 2007 8:31:05 AM Info: Start logging to console
 Apr 18, 2007 8:31:05 AM Info:
 Apr 18, 2007 8:31:05 AM Info: ==============================================
 Apr 18, 2007 8:31:05 AM Info: = Starting to execute command 'jstartup' =
 Apr 18, 2007 8:31:05 AM Info: ==============================================
 Apr 18, 2007 8:31:05 AM Info: Starting SDM - Software Deployment Manager...
 Apr 18, 2007 8:31:05 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0010.20061019070020.0000
 Apr 18, 2007 8:31:06 AM Info: SDM operation mode successfully set to: Integrated
 Apr 18, 2007 8:31:07 AM Info: Initializing Network Manager (50017)
 Apr 18, 2007 8:31:07 AM Info: Checking if another SDM is running on port 50018
 Apr 18, 2007 8:31:07 AM Info: Operationmode for JStartupFramework has already been set to "integrated".
 Apr 18, 2007 8:31:07 AM Info: Successfully executed. Return code: 0
Retrying as well as new Starting do not help.
Will be greatful for any help that solves this special error. Thx in advance.
Greetz,
 Dirk
Message was edited by:
Dirk Malas

..well, I "solved" the issue myself: although not explicit recommended, I switched the corresponding status from "ERROR" to "OK" in the keydb.xml file.
This completed the installation and I am looking forward to consequential damages.. <img src="http://www.cheesebuerger.de/images/smilie/konfus/a025.gif">

BOBJ Monitoring in Solution Manager

Hi
How to Monitoring Business Objects in solution manager system?
If SAPHOSTAGENT deploy is it sufficient to do the monitoring?As i find the Note 1031096 - Installing Package SAPHOSTAGENT
if this is implement can we get the alerts as same as CCMS alerts?
What shlould be the SM SP for SM system to do the monitoring the BOBJ?
As this SAP Note 1393207 Say to about Monitoring..but i am not sure only we this not we have to follow
please help to configure BOBJ for Monitoring.
Regards,
Neni

Hi;
yes, you can use probes that will do some basic workflows on the system and return feedback to your enterprise monitoring system, have a look at this document:
http://help.sap.com/businessobject/product_guides/boexir3/en/xi3_monitoring_guide_en.pdf
Regards;
Lionel

Solution Manager 4.0 & SQL Server 2005

I see in the documentation the step to install SQL Server 2005 with the 850 character set. If I want to add the solution manager database to an existing instance (which uses the default char set), but give the database itself the 850 character set...will this cause an issue. I have read some posts where this causes issues for other SAP products...but have not read anything specific to solution manager. If this does cause issues, are there any workarounds, other than creating a new instance, changing the default char set for the entire instance, or finding a new db server?

Dear John,
unfortunately there is no other solution. To ensure, that the database can work correctly it is necessary, that the SQL Server installation as well as all databases within the instance have the same collation. For new installations the SAP installation tools automatically use BIN2 as this will ensure compatibility with unicode. To find out which collation is installed for the server instance you can use the following query:
select serverproperty('collation')
To find out the collation of a specific database you need to execute the following query:
select databasepropertyex('<db-name>', 'collation')
The fact that the database collation and the server collation must match has nothing to do with the installed SAP Product - the two collations need to be the same in any case.
Please read SAP Note #600027 to find the necessary procedure for changing the server / database collation,
hope this information helps you,
kind regards,
beate

Issue management in Solution manager

Hi,
We are in design phase for Solution manager 4.0. The requirement is now that we want to Internally (250 Sap experts divided in functional groups) involve other support groups or employees to the support message.
From the theories available I would say to use Issues (SLF2 or SLFI (4.0), linked to the support message (SLFN), eventual changes can be linked to this issue as well. within the issue it is possible to assign tasks to groups and(?)/or employees.
When a change request is available, no issue is necessary to involve (assign tasks) to employees or groups?
Another sound here is to use the "task" message in order to involve other people.
I am wondering what would be the smartest solution and why. Please help.
Jos

Nadine the only pain that I see by using the Issues Management component for project issues is that people who wont normally log into Solution Manager (project managers, integration leads, org change leads, etc) will now need a SAP user ID and training on the system. Even though this is very minimal training, and its probably good for them to use the SAP interface, it isnt as quick as using Sharepoint, an E room or spreadsheets.
But if it is project issues associated to business processes (thats how it sounds based on your other posts), this could be very useful. Again the functionality is mature enough to deploy according to your requirements, but prepared for some whining and pushback.
Good luck

Service desk issue in Solution manager

Dear Friend's
I have configured Service desk in our Solution manager .
Solution manager version is 7.0 , on windows 2003 & oracle 10.2.0.2.0.
I am able create messages in our satilite systems . And sending to solution manager also.
Here issue is , when I click on send button in created message box , then our satilite system will asking password of basis user , which is present in solution manager. If I entered that password then It shows successfully send message with number.
I want's to skip the screen , where it's asking the basis user ,password.
So please give me solution , If you come across this problem.
Thanks in advance,
R.k sindol
Edited by: Raj kumar sindol on Jan 20, 2009 3:30 PM

Hello Raj,
see SAP Note [153743|https://service.sap.com/sap/support/notes/153743] chapter "In the R/3 system of the notifier (customer data entry systems).". Changing that RFC destination should be the solution for your case.
Best regards,
Andreas

Early watch Report issue in Solution Manager

HI
I have configured the EWA report for system in Solution Manager 4.0 and report is generating but the issue is in the report EWA for Solution following section remain empty
Workload and Performance Analysis
Exception Analysis and Change Analysis
and one more issue for our production system the EWA report status is showing Not Productive
Thanks for your help
Harish

>
Harish Kumar Jaiswal wrote:
> I have configured the EWA report for system in Solution Manager 4.0 and report is generating but the issue is in the report EWA for Solution following section remain empty
>
> Workload and Performance Analysis
> Exception Analysis and Change Analysis
>
> and one more issue for our production system the EWA report status is showing Not Productive
Please check, whether the managed system is well prepared.
It requires add-ons ST-PI and ST-A/PI, data in workload statistics ST03N.
Run RTCCTOOL via SE38 and check the results.
See SAP Note 91488
Ruediger

SAP NW 7.4 as java system sync with solution manager system 7.1 issue

Dear all,
I have installed SAP NW 7.4 system SP level is SP5 ,after that i have cheked in service marlket palce Now service market plkace latest SP level SP7.
For manula downlowd( directly from service market place) is difficult for java system and i have started sysnc with solution manager system to download patches through MOPZ.
Below are the activities completed:
1) Through template installed I have rgeisterd the system into Solman SLD.
2) Sync completed succfully exact product version is shwoing in solman SLD
3) after that I have checked in SMSY and LMDB its showing prefectly
4) But in SMSY its shwoing only under technical system,not showing product systems
5) I have assigned in product system in LMDB
Now the issues while selecting the system group and logical componensts I have created one logical componnets -but in that SAP NW 7.4 is not showing and I have assumed SAP NW 7.3 EHP1 after creating my newly create dsystem is not shwoing in drop down.
I ma getting belwo error.
No system found for this product/product instance
Message no. SOLAR_SPROJECT110
Please sugegst how to reslove the error ,and a;lso please let me know is there any way to download latest pathces to dpownload from service market place .
Advance Thanks

Hi,
re-check if the 7.4 system is correctly registered in the solman SLD system.
Re-check LMDB definition for your 7.4 as JAVA system. you have to manually created the Product system. Ensure all the Component and definitions are correct.
Also do a verrification run within the LMDB. This will confirm whether all the information is correctly defined.
Please note - SLD -> LMDB -> SMSY.
So, if the first 2 don't have the correct information, you wont have much joy with smsy.
Rgds
Deepak

MOPZ has issues calculating stack XML file in SOLUTION MANAGER

Hello,
We have a SOLUTION MANAGER system on NW 7.0 EHP1 SP stack level at initial support stack (ISS).
Recently we upgraded all our R/3 systems to ECC6.0 EHP4 SPS04 and now we are trying to upgrade the stack level to EHP4 SPS07. So we are trying to get a XML file from MOPZ but no luck.
The backend system has all the correct data updated in SMSY and all looks fine but while we try to calculate the stack for EHP4 SPS07 it ends with error like below mentioned.
Please look into the errors and throw some light if anyone has come across the same.
Error details:
System Messages
Type Message Text
Error The Installation/Upgrade Package for Add-on EA-APP L rel. 600 is not available
Error ABAP queue check failed
But the backend system has EA-APPL level at 604, we do not know why it is looking for installation/upgrade package for
EA-APPL 600.
Regards,
Yoganand.V

hi
can you check the sap note
1. Note 1277035 - Solution Manager: EHP4 product data missing
might be this could be the reason for your issue
or
check the thread already discussed the same and the solution also provided
[EHP4 upgrade error on SAPK-603DHINEAPS|EHP4 upgrade error on SAPK-603DHINEAPS]
////////////////It seems that there is a small bug in teh software vector for EA-PS.
Essentially, SAINT prevents you from going forward because it thinks that you don't have the correct version of EA-PS installed.
The solution for this is described in OSS Note: 1143022
"To import EA-PS in a system that already has the level EA-APPL 604, load the attached file ACP_EAPS.SAR into your system (SPAM-> Support Package -> Load Packages -> from Frontend) before you start the import using SAPehpi. Otherwise, an error may occur in the queue calculation, which can be solved by reloading the ACP"////////////////////////
check and update
Jansi

Solution manager Remote Connection issues

Hi
I'm currently in the process of setting up Solution Manager 7.1 on windows Server 2008r2 using central system.
I did the prerequisite check & the Solman installation and i'm actuallly working on the post-installation steps.
I'm experiencing difficulty with the step : "Configure Remote Connection to SAP".
I followed the informations provided on : http://service.sap.com/remoteconnection
In the technical prerequesite you have to set up a connection to sap support.
So i have to choose a connection type : I selected Internet connection so my first question is : do we need "VPN with SNC" or "VPN OR SNC" ?
I personnaly understood VPN or SNC.
So from here i decided to use SNC.
The first step was to set up & configure the SAProuter. I decided to do it on an another computer on the same domain ( not on the same computer where Solution Manager is installed ) but i'm not sure it is necesary
I assume I can install Saprouter on the same location as the Solution manager? do you recommend it ?
The Basic Functions testing with niping is working.
The next step is : "establish Internet Connections"
So now i can choose between SNC or VPN : my goal is to establish the connection as fast as possible.
I actually don't have a switch available ( i can get one if necesary but time is running ... ) so i'm opting for the SNC solution.
I tryed to get the certificate for the saprouter but i don't have a register SAProuter, but when i opened a customer messager for component XX-SER-NET, SAP answered about the impossibility to access SAP service Backbone with an SNC , saying that i will need to register a VPN site to site connection to SAP => i don't get it .... Can someone explain it to me ?
So please can one of you guru's tell me how to set this remote connection :
-which materials ( server / switch / firewalls ) ?
-where to get the right documentation ?
-What about DMZ ?
-I have a single IP Address is that enough ? ( setting up nat for port 3299 )
- do i have to contact a service provider ?
My idea was initially to set up the SAProuter on the same computer as the SOLMAN setup & use SNC communication to communicate with SAP but it doesn't seems that easy. Do i need separate installation for Saprouter <=> Solution Manager. ?
What's the minimal infrastructure to establish this connection ?
In addition to that, after configuring the SAProuter, i had trouble with the SAPMMC : on my system , on the instance 0 , the process disp+work.EXE won't run ( yellow light )and i can't find where i made a mistake if you have suggestions ...
Really need your help, i'm on a short deadline ... Any help, even incomplete, would be appreciated.
Thanks a lot.

Thx for the answer.
I actually managed to register my saprouter with SAP and was granted with CN/OU & connection informations.
I followed this guide : http://service.sap.com/saprouter-sncdoc with the addition of this guide : http://wiki.sdn.sap.com/wiki/display/Basis/SAProuterviaSNC.
My first issue : I'm running with a Windows server 2008 r2 enterprise edition 64 bits with a processor Intel Xeon 2.4ghz ( dualcore). so i decided to use the crypto folder "nt-x86_64"
For the environment variable i set as System variables SECUDIR = C:\usr\sap\saprouter and SNC_LIB = C:\usr\sap\saprouter\nt-x86_64\sapcrypto.dll
The generation/install of the certificate is alright ( sapgenpse get_my_name -v -n Issuer is OK )
using the command :saprouter -r -K "p:CN=mycn, OU=myOUnbr, OU=SAProuter, O=SAP, C=DE" i have
I get the following message : trc file dev_rout
 no ligging active
Its strange cause it looks like its running but when i check the services running on windows saprouter isn't started .... How to know if SAProuter is running right ?
If i folow the SAP procedure : Step 3 : test of the ip connection by the customer : SAP Remote Services : technical preparation ( see SAP Note 812386 ) : it's ask in the note to implement note 766505 via SNOTE : i get the following error msg : Error in remote connection to destination SAPOSS : Error when opening an RFC connection ( LB: Hostname or service of the message server unknown#DEST = SA
What's wrong ?
If i use T oss1 in parameter => technical setting => i set my saprouter info in SAProuter 1 ( at customer site ) with instance no. 99 and if SAProuter and SAPNet Message Server at SAP i put the following : Name : sapserv2 / IP Address 194.39.131.34 intance no. 99 and message server name oss001/ DB Name 001/ Instance no.01.
When trying to "Logon to SAPNet" i have an error Unable to connect to SAPNet message server ( default connection will be used ... )
and followed by the error screen : "partner '80.15.173.168:sapdp99' not reached WSAECONNREFUSED : Connection refused. do you want to see the detailed error description ? "
Details : module nixxi.cpp / line 3286 / Method : NipConnect2:80.15.173.168:3299 / Return code : -10 / System call : connect / Error No : 10061 / Error Text WSAECONNREFUSED: Connection refused / Counter : 10
Any idea ?
when doing niping.exe -c -H /H/mylocalSR/H/194.39.131.34/H/194/39.131.34 i obtain :
Wed Dec 07 21:20:09 2011
connect to server o.k
Wed Dec 07 21:20:09 2011
send and receive 10 messages (len 1000)
times -
avg 122.148 ms
max 193.731 ms
min 81.564 ms
tr 15.990 kB/s
excluding max and min :
av2 118.273 ms
tr2 16.514 kB/s
Is it the expected output ?
I've maintained system data in service.sap.com/system-data ( selecting the sap router ) then i tryed to use the SAP service connection, downloaded the .exe but i can't find the stfk.oez. I realized that in my maintain connection screen i have no space for entering any routestring. Seems wrong ?
Do i have to use the SAO?
i've made nat redirection from my router as this : from my public ip to my lan ip ( 192.168.x.x) what should i enter in the routestring : /H/public or lan or hostname ?/S/3299 ?
Hoping you can help me ! ( the goal of all this is to set up RFC connection for postinst step of Solution manager ).
Edited by: BLANCHARD Guillaume on Dec 7, 2011 10:47 PM

Solution Manager 7.1 Upgrade - ST add on release Issue

Good day
I have the following issue where the ST add on's are = the target release of the upgrade. The release is only on a higher patch level in 7.1(SPS4)
The step is Configuration(3) in SOLMANUP, it will not get past the phase of deciding to keep the add on's, the error is:
For the following Add-on component(s) the KEEP YOURS decision is not longer valid,
since at least for one of the base components an Add-on upgrade has been included:
ST-ICO     (changed base component: ST)
ST-PI      (changed base component: SAP_BASIS)
ST-SER     (changed base component: ST-PI)
You need to change the decision of the above Add-on(s).
Any ideas?
Thanks

Hi Miguel,
I am using SOLMANUP, I am using the installation/upgrade software and using SPS 4 as my target release. I am using SPS4_upgrade.xml in my download directory.
If I try using SPS 2 with SPS2_upgrade.xml it produces an error because my patch level of ST-PI is already patch 5 in my current system(Solution Manager 7.01 EHP1), and SPS 2 of Solution Manager 7.1 ST-PI = patch 4, that's why I am using SPS 4 stack as it is a higher level that my current patch level of ST-PI.
The issue is that the mentioned ST add-on's are the same release as the target release, the only difference is the patch level. The upgrade recognises that the source and target release is the same, but will not let me keep with Decision = Keep
Thanks
Derek

User synchronization issue between Active Directory and Solution manager.

Requirement:
Synchronize the users between Active directory and solution manager system.
What we did:
1. Created RFC connection (LDAP_RFC) for LDAP connector.
2. Created new LDAP connector that utilize the RFC (LDAP_RFC).
3. Created new logical LDAP Server(CUA).Here we have to maintain the connection
details to the physical directory.
4. We maintained the communication user that is used by the LDAP connector to bind the LDAP Directory Server.
5. In transaction LDAPMAP specific SAP data fields, we mapped to the desired
directory attributes.
6. Testing from LDAP transaction working fine. We are able to see the attributes and
values from Active directory.
Issue:
When executed the program RSLDAPSYNC_USER for user synchronization from t-code se38 with below selection .
LDAP Server = CUA (created earlier)
LDAP Connector = LDAP_RFC (RFC connection created created ealier)
In the tab: (Object that exist both in the directory and in the Database:)
Selected: Compare Time Stamp.
In the tab: (Objects the only exist in the Directory.)
Selected : Create in Database.
In the tab(Objects that only Exist in the Database:
Selected: Ignore Object.
Result from the report shows that connection to LDAP server is fine and 0(zero) objects in Directory.
The program does not create any new user in the Solution Manager system.
Any help on this issue greatly appreciated.
Thanks & Regards,
Harish

where did you see this error ? is there anymore details.
i think the account you are using for Sync does not have Replicate Directory Changes permission in AD. follow below article and give Replicate directory changes permission.
http://technet.microsoft.com/en-us/library/hh296982(v=office.15).aspx
Thanks, Noddy

SOLUTION MANAGER 4.0 SR2 - SP12 deployment issue

Similar Messages

Maybe you are looking for