SAP Security Note 1487730

Last week we saw SAP releasing its SAP Security Notes as per its SAP Security Patch Day Practice .
One of thenotes released was related to a BUG FIX in a Kernel as per note 1487730
https://websmp130.sap-ag.de/sap/support/notes/1487330
Now the issue goes this way .
We are on Kernel 7.01 SP Level 79.
According to the NOTE we need to be atleast on SP Level 103 .
When I check out at Marketplace I can only Find SP Level 111 which is the latest and released on 14.10.2010 ie. 2 days after the NOTER was released .
Apprantely we follow a Thumbs Rule here to Implement the Kernel which is lower than the latest Kernel .
The issue is I cant find Kernel SP Level 103 .
Is it safe to go for SP Level 111 .
Our Database is ORACLE 10.2.0.4
OS PLatform :- Solaris Sparc 64- Bit NON UNICODE
Regards,
Ashish .A. Poojary
Edited by: Ashish Poojary on Oct 21, 2010 7:10 AM

Hi Ashish,
Generally the rule of N - 1 is followed for SAP Application patches and not for kernel.
You can go for latest kernel, it will not be any problem.
Thanks
Anil

Similar Messages

  • Do SAP Security Notes contain hacker and/or virus defence?

    Dear SCN fellows,
    I am new to this community and generally new to asking for SAP help in discussions and blogs.
    I need some advice on whether SAP Security Notes contain hacker and/or virus defences?
    I am investigating a companies SAP Security settings against its policy and global market standards.  I have identified that since our SAP rollout SAP Security notes patches have not been maintained.  RSECNOTE provides a large list of missing security notes.  I'm writing a report and what to confirm whether these notes offer any advice, support or notification of hacking or viruses.  Similar to Internet security software I guess.
    Can anyone advise if my thoughts and questioning is heading in the right direction or have I got the concept of SAP Security Notes completely wrong?
    Thank you kindly.
    Paul

    Hi Paul,
    I need some advice on whether SAP Security Notes contain hacker and/or virus defences?
    SAP releases respective security notes as per the loophole identification.  Once you run RSECNOTE you get the list of all applicable notes to your software release.
    Applying these notes will help you to remove the vulnerability SAP identified, So yes it contains solution to remove vulnerability.
    I'm writing a report and what to confirm whether these notes offer any advice, support or notification of hacking or viruses.  Similar to Internet security software I guess.
    Could you please elaborate it is not that clear to me.
    BR,
    Mangesh

  • Apply SAP Security Notes to all components?

    Dear Forum,
    Is it possible to take advantage of exploits in installed components although theyre not in use? I mean, when patching SAP Security Notes, does it make sence to patch components which are installed but not in use?
    Rough example:
    We have a system with 10 components (according to SPAM status) only 7 of these modules are actively used. Should all 10 receive applicable SAP Security Notes, or would it be enough to patch the ones in use?
    I hope someone is able to elaborate on this
    Thanks in advance guys,
    Kind Regards,
    Soren

    HI,
    for example reading a file. Let's say there is a bug in a program which allows malicious user to read any file on the application server. Obviously, you want to patch this even that program is not used by normal users. Another example is missing authorization checks for table view. You can have assigned proper authorizations for S_TABU_DIS but if a malicious user can trick a program without authorization check to display data from any table then you have a problem.  A real example could be an issues fixed in note 1558740. Even if you don't use IS-U those FMs are still in your system.
    Don't forget that it's good to have multiple layers of protection. So you keep authorizations tight but still you patch all security issues.
    Cheers

  • SAP Security Notes: ABAP and Kernel Software Corrections

    Hi all,
    I have a quick question, hopefully it's just as quick an answer.
    Under the Early Watch section in the title it states
    Security-related SAP Notes cannot be checked because the results of the RSECNOTE tool are missing.
    What does this actually mean and how do I make the results of RSECNOTE available to the early watch report?
    It says this in all my systems, I can run the tool via ST13 or SE38 > RSECNOTE manually but surely it's must be referring to some automated results.
    Thanks
    Craig

    Sorry but this note is not relevant, we are using ST-A/PI 01Q_700 SP2 (SAPKITAB7L).
    It also refers to RSECNOTE not existing in the system.  As I mentioned the tool exists and I can run this manually, but as noted the Early Watch report states
    Security-related SAP Notes cannot be checked because the results of the RSECNOTE tool are missing.
    Suggesting that somehow results of the tool are held somewhere and are read by the Early Watch report processing. So my question still stands, how are these results made available to the Early Watch report, what batch job needs to be running on a regular basis for this to work?
    The very first sentence after the section says
    You have marked 2 security-related SAP Notes as not to be considered.
    So it must be reading this from somewhere!
    Thanks
    Craig

  • Post-upgrade ToDo, PI configuration Wizard: com.sap.security.api.DuplicateKeyException Group found, but unique name "SAP_SLD_DATA_SUPPLIER" is not unique!

    after PI-Upgrade to NW-PI-731-SP07,  executing the PI-configuration wizard:
    step 126 of 162
    Assign SLD Data Supplier user to Group SAP_SLD_DATA_SUPPLIER (local SLD)
    Error:
    Group found, but unique name "SAP_SLD_DATA_SUPPLIER" is not unique!
    Execute Java Service
    Library: sap.com/tc~lm~ctc~util~core_ear
    Class: com.sap.ctc.util.core.services.UserFacade
    Method: void com.sap.ctc.util.core.services.UserFacade.addUserToGroup(java.lang.String, java.lang.String)
    Arguments (2)
    userName : SLD_DS_EXE
    groupName : SAP_SLD_DATA_SUPPLIER
    InvokeService- Result: ERROR
    Refresh Env. Messages: false
    Duration: 1.936 sec
    Library Info
    Default Trace
    Exception Class: com.sap.security.api.DuplicateKeyException
    Exception Message: Group found, but unique name "SAP_SLD_DATA_SUPPLIER" is not unique!
    com.sap.security.api.DuplicateKeyException: Group found, but unique name "SAP_SLD_DATA_SUPPLIER" is not unique!
    at com.sap.ctc.util.infra.rfc.BaseConfig.dispatchException(BaseConfig.java:230)
    at com.sap.ctc.util.core.services.impl.ume.java.GroupJavaImpl.verify(GroupJavaImpl.java:121)
    at com.sap.ctc.util.core.services.impl.ume.DualGroupImpl.verify(DualGroupImpl.java:118)
    at com.sap.ctc.util.core.services.content.ume.UserService.addToGroup(UserService.java:725)
    at com.sap.ctc.util.core.services.UserFacade.addUserToGroup(UserFacade.java:288)
    what to do?
    ============
    o.k.
    https://service.sap.com/sap/support/notes/1016283
    first run the UME consistency check => found some inconsistency => did repair UME
    then run again UME consistency check => found no more inconsistency !!
    the again - try to run the PI-Upgrade-Wizard => but again error on executing .....

    see this sap-notes:
    http://service.sap.com/sap/support/notes/1617234
    http://service.sap.com/sap/support/notes/1661135
    http://service.sap.com/sap/support/notes/1678815
    http://service.sap.com/sap/support/notes/1626747

  • Does SAP upgrade cover prievious security notes.

    Hi, i am beginner in security field and have this confusion. I am using Solution Manager to find out missing security notes from my system. Should i filter the result and implement security notes that have been released after the date of the upgrade or should I include all security notes including thoses notes relased before the upgrade date.
    Thank You..

    In addition to the list of security notes at https://service.sap.com/securitynotes you should have a look to the Security Patch Process FAQ as well.
    Concerning your question:
    Yes, all security corrections of SAP are part of a Support Package.
    But there exist some pitfalls:
    By the time when you finally have upgraded your production system, it's already some month old compared with the corresponding development close date for the support package at SAP. Therefore you always will find some new security notes -> Use the Maintenace Optimizer to find new security notes while you are preparing the upgrade and the application System Recommendations monthly. 
    Several security notes contain manual instructions to configure the system (e.g. concerning profile parameters, RFC Gateway access control lists or logical filenames), which are valid for the new support package. -> I recommend to skip any date selection while searching for security notes. (Use a date interval only if you explicitely want to have a look, e.g. to the notes of the most recent patch day.)
    Kind regards
    Frank

  • SAP published security note 2113995

    Could someone tell me where the below issues was discussed on SCN so that I can subscribe to the appropriate groups?
    https://www.trustwave.com/Resources/Security-Advisories/Advisories/TWSL2015-004/?fid=6200
    Revision History:
    01/15/2014 - Vulnerability disclosed
    04/22/2015 - SAP published security note 2113995
    04/23/2015 - Advisory published

    I don't think this issue has been discussed yet on SCN.  The three spaces that I think it would most likely be discussed on are:
    SAP Adaptive Server Enterprise (SAP ASE) for Custom Applications  [this one we are on now]
    SAP Adaptive Server Enterprise Developer Center
    SAP Applications on SAP ASE
    -bret

  • Com.sap.security.core.ume.service failed. J2EE Engine cannot be started

    Hi,
    I have configured SNC on NetWeaver 7.0 (ABAP+JAVA) System on Windows 2003 Server with MS-SQL 2005 Database.
    After the SNC configuration restarted the Server but the JAVA Server process is going down with EXIT Code -11113. The SNC Configuration is working fine but JAVA is not running. SDM and dispatcher are in green but server process is going gray.
    I have checked the log files under C:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log
    The following is the part of log file.
    #1.5#005056BA6C3F001D0000000F000008D8000489ACAFC86070#1277274683393#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_71##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    [EXCEPTION]
    #1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    #1.5#005056BA6C3F001D00000011000008D8000489ACAFC8628E#1277274683393#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_71##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
    Please help me to solve the issue.
    Thanks,
    Ajay.

    Hi Tim,
    I have configured using Kerberos library for 32 bit on Net Weaver 7.0 with MS SQL 2005 Server on Windows 2003 Server. I didnt change any thing on JAVA side. I have configured as per the Kerberos configuration steps  as per below URL
    http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/frameset.htm
    The configuration was successful and I am able to login with out asking password, but After the configuration when I have restarted every thing on ABAP side works well but JAVA server process going down with EXIT code -11113. One of the log file contains follows error message.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Jun 25, 2010 3:05:24 AM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    One of the line says "SNC required for this connection". What does this mean? What else need to be done for JAVA to communicate with ABAP?
    Thanks,
    Ajay.

  • Com.sap.security.core.server.secstorefs.WrongKeyException

    Hi,
    we have done a system copy,while starting the java stack we are getting the below error.
    Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong..
            at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
            at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
            at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
            at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
            at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:112)
            ... 15 more
    Caused by: com.sap.security.core.server.secstorefs.WrongKeyException: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong.
            at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:2017)
            at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
            at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
            at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
            ... 17 more
    Caused by: com.sap.security.core.server.secstorefs.InvalidStateException: Internal error during the decryption process.
            at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:850)
            at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1985)
            ... 20 more
    Caused by: javax.crypto.BadPaddingException: Invalid PKCS\#5 padding length: 30
            at iaik.security.cipher.s.b(Unknown Source)
            at iaik.security.cipher.w.a(Unknown Source)
            at iaik.security.cipher.w.engineDoFinal(Unknown Source)
            at javax.crypto.Cipher.doFinal(Unknown Source)
            at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:825)
            ... 21 more
    #1.#000255334607000000000015000640DE00046E8629009A5B#1247422399420#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Loading: ConfigurationManager returned false! #
    #1.#000255334607000000000017000640DE00046E8629009BC2#1247422399421#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Kernel not loaded. System halted.#
    #1.#00025533460700000000001A000640DE00046E862908A703#1247422399948#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#######Thread[Thread-1,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
    Thread[SAPEngine_System_Thread[impl:5]_2]
    Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.core.cluster.impl6.JoinPortListener | toString: com.sap.engine.core.cluster.impl6.JoinPortListener@252e252e] with classloader [com.sap.engine.boot.CoreClassLoader@21d821d8]#
    Regards,
    Sam

    Hi,
    Check with this note,
    Note 791574 -
    Also
    Secure Storage for Application Specific Data
    Applications or application components, deployed on the J2EE Engine, can save sensitive data
    in encrypted form in a secure storage area in the J2EE Engineu2019s configuration database. The
    data saved in this area is encrypted using a secret key that is created explicitly for the application
    or service. The J2EE Engine uses the triple DES algorithm to perform the encryption.
    You can use two approaches for storing and maintaining the encrypted data for the individual
    applications or application components:
    u2022 Centralized storage
    With centralized storage, applications or application components use the Secure Storage
    service on the J2EE Engine to encrypt and decrypt the data. This data is also stored in the
    corresponding secure storage context on the J2EE Engine. You can control the
    parameters of this secure storage area from the properties of the Configuration Manager.
    For more information
    u2022 Decentralized storage
    With decentralized storage, the applications and application component maintain their own
    storage area for the encrypted data. They only uses the Secure Storage service on the
    J2EE Engine to retrieve the key, which is necessary to encrypt and decrypt the data.
    Regards,
    Ravi

  • Web service security not configured

    Hi All,
    We have new PI system 7.1 ehp1, as an initial step installation is done including post installation.I have a task of checking if
    everything is in place as the same have to be confirmed to the team which did the installation.
    When i open RWB , i could see a message with warning "WS security not configured". aprat from this everything seems to be
    fine.
    Can anyone guide me on how to set us WS security and what is the use ,importance of having that configured?

    Hi,
    I dont think you have to configure Message level security configuration manually, i have done instaltion of PI 7.1,i have not seen any step like this.
    by default it will come after completion of postinstaltion succesfully.
    my advice better to move thread to SAP NetWeaver Administartion forums,you may get good replies./
    Regards.,
    Raj

  • Web Service Security not configured on this component.

    Hi Experts,
                           Before configuring the scenario, i went to RWB to check whether the comopnents are in active mode or not.
                                  Integration Engine XID 
                                  Business Process Engine XID 
                                  Mapping Runtime XID 
                                  Adapter Engine XID 
                                  Integration Engines
                          All components are in Green mode  Except Integration Engine, The Integration is in yellow mode
                           and shows the following details.
                         Details for 'Is Web service security available?'
                           Web Service Security not configured on this component.
    Can you give the solution for this.

    Hi,
                      1, While sending idoc from sapR/3 to PI , in r/3 sm58 shows the foll error:
    "No service for system SAPQA,client 200 in integration directory"*
                               Even the Bussiness sytem pointing R/3.
    From your initial post, it appears that you are using XID system and from above error, I believe you are trying to send the IDoc from QA system. R3 dev will communicate to PI dev, so verify the partner profile and ports in your IDoc Header settings.
                         2, When i execute the tcode sm58 in PI   it shows the following error:
                                   "Syntax error in program SAPLSXI_AC_CACHE _REFERESH"
    I am kinda confused how come sm58 tcode can show an error for this program, as sm58 is for checking the transactional RFCs and  SAPLSXI_AC_CACHE_REFERESH is for XI Cache refresh for Alert Category. Might be some one else can explain this.
                         3, WHEN I EXECUTE THE tcode SXI_CACHE
                                             Under the *STATUS OF RUNTIME CACHE
                                                           Unable to refresh cache contents
                                                           Error during last attempt toreferesh cache
                                                             (red colour triangle leading above both)
    Check this SAP Note 764176, might help in your situation.
    Worth reading - http://help.sap.com/saphelp_nw04/helpdata/en/0d/28e1c20a9d374cbb71875c5f89093b/frameset.htm
                        4, Still there is no messages in Message monitoring.
    Obviously because of error # 1, you are unable to send IDocs, how come you expect messages to reach PI ... strange, isn't it
    Hope this helps.
    Regards,
    Neetesh

  • In SOLMAN after applying security notes warings are coming

    Hi All,
    Please help here
    We have applied some security notes in SOMAN Dev & made the TR for the same
    after importing the TR in Live we are getting warining.
    log detail is as below
    Post-import method SCWN_AFTER_IMP_METHOD started for NOTE L, date and time: 2010111705264
    Beginn: After import method for SAP Note 0001379987
    No release data for Note 0001379987 in the data file in the request
    End:    After import method for SAP Note 0001379987
    Beginn: After import method for SAP Note 0001380710
    No release data for Note 0001380710 in the data file in the request
    End:    After import method for SAP Note 0001380710
    Beginn: After import method for SAP Note 0001381719
    No release data for Note 0001381719 in the data file in the request
    End:    After import method for SAP Note 0001381719
    Beginn: After import method for SAP Note 0001402132
    No release data for Note 0001402132 in the data file in the request
    End:    After import method for SAP Note 0001402132
    Beginn: After import method for SAP Note 0001412774
    No release data for Note 0001412774 in the data file in the request
    End:    After import method for SAP Note 0001412774
    Beginn: After import method for SAP Note 0001430970
    End:    After import method for SAP Note 0001430970
    Execution of programs after import (XPRA)
    End date and time : 20101117052647
    Ended with return code:  ===> 4 <===
    we checked and could see these SAP Notes coming in warning message has been implemented in our Dev & Live suuccessfully
    still waring is coming
    please help here to avoid this warnings
    Regards,
    Vyash

    Hi,
    Regarding the message "No release data for Note XXXXXXXXX in the data file in the request"
    You can normally ignore this warning.
    The warning's meaning:
    When a Note (R3TR NOTE) is transported, the release data for the
    software components affected by the Note is normally transported too. If
    a transport request contains several Notes, however, the release data
    is only transported with one of the Notes, and not with all of them.
    When a transport request containing several Notes is imported, the
    system issues a warning for all Notes that do not have release data
    transported with them.
    If the system issues this warning for all Notes during a transport
    request import, however, this might mean that the data in the target
    system is incomplete. If this is the case, the system will issue an
    error message when the imported Notes are displayed with transaction
    SNOTE.
    You can solve this display problem by downloading one of the Notes again
    from SAP Service Marketplace. The functionality of your system is in no
    way impaired.
    Hope the above information could be helpful to your situation.
    Kind regards,
    Fabricius

  • Advice needed: what does your company log for SAP security role changes?

    My client has a situation where for many years, they never logged changes to SAP security roles.  By that I mean, they never logged even basic details, like who requested a change, tested it, approved it, and what changed!!  Sadly their ticketing system is terrible, completely free-form text and not even searchable. 
    Does anyone here use Word docs, Excel sheets, or some other way to capture security role change details?   What details do you capture?  What about Projects, that involve dozens of changes and testing over several months?
    I plan to recommend, at least, they need to use a unique# (a ticket#, or whatever) for every change and update the same in PFCG role desc tab, plus in CTS description of transports... but what about other details, since they have a bad ticketing system?  I spoke with internal audit and change Mgmnt "manager" about it, and they are clueless and will not make recommendations.  It's really weird but they will get into big trouble eventually without any logs for security changes!

    Does anyone here use Word docs, Excel sheets, or some other way to capture security role change details? What details do you capture? What about Projects, that involve dozens of changes and testing over several months?
    I have questions:
    a) Do you want to make things straight
    b) Do you want to implement a versioning mechanism
    c) You cannot implement anything technical, but you`re asking about best "paper" practise?
    The mentioned scenarios can be well maintained if you use SAP GRC Solutions 10 (Business Role Management)
    Task Based, Approvals, Risk Analysis, SOD and role generation and maintenance in a structured way (Business Role Management). Workflow based, staged process with approvals.
    PFCG transaction usage will be curtailed to minimum if implemented fully.
    Do we really want to do things "outside" PFCG?
    @all:
    a) do you guys use custom approval workflows for roles?
    b) how tight your processes are? how much paperwork, workflow, tickets, requests and incidents you have to go through to change a role?
    c) who is a friend of GRC here, raise your hand
    Cheers Otto
    p.s.: very interesting discussion, I would like to learn something here about how it works out there in the wild

  • SAP XI and SAP Security...

    Hi Friends..
    Iam an ABAP Developer in U.S. and planning to change my field into either SAP XI or SAP Security...
    Can you please suggest me depending on the current market which field is better to choose and which one is in demand and has good pay..
    I appreciate your proper guidance for the change of my career..
    Thanks,

    Kanthi,
    SAP XI seems to be doing pretty well and should be able to find something eventually. That is not to say that SAP Security in not a good choice, but jumping into SAP Security would be a totally new concept (unless you have already been exposed to that area as part of your ABAP experience)

  • Error while starting J2EE Engine:com.sap.security.core.persistence.datasour

    I would like to ask for your help to look into the problem being encountered  in starting J2EE Engine
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
    At first we identified that the user EPQASCONNECT was not created in R3 QAS system, we have created this one. At the same time, we have changed the ume.r3.connection.master.passwd to reflect the password set in R3 QAS. But still it is not working.
    Also, checking the trace file for server0, the rc code is -11113.
    The following users SAPJSF,J2EE_GUEST and J2EE_admin were not locked.
    Followed the http://help.sap.com/saphelp_nw70/helpdata/EN/45/1bbdccc7850064e10000000a1553f7/frameset.htm. link to make changes.
    The problem raised after the system refresh in QAS system. License was also installed after System refresh.
    ERROR:
    stdout/stderr redirect
    node name   : server0
    pid         : 5088
    system name : EQ7
    system nr.  : 03
    started at  : Tue Nov 25 17:24:12 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 5444] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 1078 ms.
    Loading: PoolManager ... 16 ms.
    Loading: ApplicationThreadManager ... 94 ms.
    Loading: ThreadManager ... 31 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 390 ms.
    Loading: LockingManager ... 125 ms.
    Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87039K->2386K(130560K), 0.0150914 secs] 87039K->2386K(1005056K), 0.0152223 secs]
    4969 ms.
    Loading: LicensingManager ... 47 ms.
    Loading: CacheManager ... 359 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (0 ms).
      Service memory started. (47 ms).
      Service cross started. (47 ms).
      Service file started. (156 ms).
      Service timeout started. (109 ms).
      Service runtimeinfo started. (15 ms).
      Service trex.service started. (94 ms).
      Service cafeucc~api started. (141 ms).
      Service userstore started. (47 ms).
      Service jmx_notification started. (47 ms).
      Service p4 started. (297 ms).
      Service classpath_resolver started. (31 ms).
    9.789: [GC 9.789: [ParNew: 89426K->9626K(130560K), 0.0389830 secs] 89426K->9626K(1005056K), 0.0390998 secs]
      Service log_configurator started. (5797 ms).
      Service locking started. (16 ms).
      Service http started. (328 ms).
      Service naming started. (469 ms).
      Service failover started. (141 ms).
      Service appclient started. (188 ms).
      Service ts started. (235 ms).
      Service javamail started. (250 ms).
      Service licensing started. (0 ms).
      Service jmsconnector started. (312 ms).
      Service connector started. (391 ms).
      Service iiop started. (312 ms).
      Service webservices started. (766 ms).
    19.167: [GC 19.167: [ParNew: 96666K->19159K(130560K), 0.0812264 secs] 96666K->19159K(1005056K), 0.0813454 secs]
      Service deploy started. (15422 ms).
      Service MigrationService started. (47 ms).
      Service configuration started. (62 ms).
      Service bimmrdeployer started. (31 ms).
    24.849: [GC 24.849: [ParNew: 106199K->17756K(130560K), 0.0546511 secs] 106199K->17756K(1005056K), 0.0547691 secs]
      Service dbpool started. (2688 ms).
      Service cafeugpmailcf started. (62 ms).
    Nov 25, 2008 5:24:47 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_70] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      lang=EN
      receiverid=master
      sysnr=01
      client=888
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=R3DEVSER
    Nov 25, 2008 5:24:47 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_70] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Nov 25, 2008 5:24:47 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_70] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 5088
    system name : EQ7
    system nr.  : 03
    started at  : Tue Nov 25 17:24:52 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 4672] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 672 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 93 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 31 ms.
    Loading: ClusterManager ... 234 ms.
    Loading: LockingManager ... 110 ms.
    Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87040K->2403K(130560K), 0.0136260 secs] 87040K->2403K(1005056K), 0.0137788 secs]
    3203 ms.
    Loading: LicensingManager ... 31 ms.
    Loading: CacheManager ... 203 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (0 ms).
      Service memory started. (47 ms).
      Service cross started. (32 ms).
      Service file started. (47 ms).
      Service timeout started. (63 ms).
      Service runtimeinfo started. (0 ms).
      Service trex.service started. (63 ms).
      Service cafeucc~api started. (203 ms).
      Service p4 started. (328 ms).
      Service jmx_notification started. (78 ms).
      Service userstore started. (78 ms).
      Service classpath_resolver started. (46 ms).
    6.865: [GC 6.865: [ParNew: 89443K->9702K(130560K), 0.0411006 secs] 89443K->9702K(1005056K), 0.0412578 secs]
      Service log_configurator started. (6141 ms).
      Service locking started. (0 ms).
      Service naming started. (484 ms).
      Service failover started. (172 ms).
      Service appclient started. (219 ms).
      Service http started. (813 ms).
      Service jmsconnector started. (422 ms).
      Service ts started. (422 ms).
      Service javamail started. (469 ms).
      Service connector started. (453 ms).
      Service licensing started. (110 ms).
      Service iiop started. (313 ms).
      Service webservices started. (1063 ms).
    16.407: [GC 16.407: [ParNew: 96742K->19088K(130560K), 0.0834244 secs] 96742K->19088K(1005056K), 0.0835901 secs]
      Service deploy started. (15859 ms).
      Service MigrationService started. (47 ms).
      Service configuration started. (47 ms).
      Service bimmrdeployer started. (16 ms).
    22.173: [GC 22.173: [ParNew: 106113K->17739K(130560K), 0.0551702 secs] 106113K->17739K(1005056K), 0.0553234 secs]
      Service dbpool started. (2625 ms).
      Service cafeugpmailcf started. (78 ms).
    Nov 25, 2008 5:25:22 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      lang=EN
      receiverid=master
      sysnr=01
      client=888
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=R3DEVSER
    Nov 25, 2008 5:25:22 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Nov 25, 2008 5:25:22 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_62] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 5088
    system name : EQ7
    system nr.  : 03
    started at  : Tue Nov 25 17:25:27 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 9304] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 656 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 94 ms.
    Loading: ThreadManager ... 15 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 31 ms.
    Loading: ClusterManager ... 219 ms.
    Loading: LockingManager ... 94 ms.
    Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87040K->2414K(130560K), 0.0145828 secs] 87040K->2414K(1005056K), 0.0147378 secs]
    3015 ms.
    Loading: LicensingManager ... 47 ms.
    Loading: CacheManager ... 172 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (0 ms).
      Service memory started. (47 ms).
      Service cross started. (31 ms).
      Service file started. (63 ms).
      Service timeout started. (46 ms).
      Service runtimeinfo started. (16 ms).
      Service trex.service started. (78 ms).
      Service cafeucc~api started. (156 ms).
      Service p4 started. (282 ms).
      Service classpath_resolver started. (32 ms).
      Service userstore started. (15 ms).
      Service jmx_notification started. (47 ms).
    6.784: [GC 6.784: [ParNew: 89454K->9721K(130560K), 0.0417499 secs] 89454K->9721K(1005056K), 0.0419073 secs]
      Service log_configurator started. (5266 ms).
      Service locking started. (0 ms).
      Service http started. (406 ms).
      Service naming started. (469 ms).
      Service failover started. (94 ms).
      Service javamail started. (250 ms).
      Service ts started. (235 ms).
      Service appclient started. (250 ms).
      Service licensing started. (31 ms).
      Service jmsconnector started. (329 ms).
      Service connector started. (406 ms).
      Service iiop started. (312 ms).
      Service webservices started. (688 ms).
    16.028: [GC 16.028: [ParNew: 96761K->19104K(130560K), 0.0751680 secs] 96761K->19104K(1005056K), 0.0753377 secs]
      Service deploy started. (15438 ms).
      Service MigrationService started. (47 ms).
      Service bimmrdeployer started. (16 ms).
      Service configuration started. (62 ms).
    21.840: [GC 21.840: [ParNew: 106140K->17748K(130560K), 0.0443068 secs] 106140K->17748K(1005056K), 0.0444546 secs]
      Service dbpool started. (2656 ms).
      Service cafeugpmailcf started. (78 ms).
    Nov 25, 2008 5:25:57 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_63] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      lang=EN
      receiverid=master
      sysnr=01
      client=888
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=R3DEVSER
    Nov 25, 2008 5:25:57 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_63] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Nov 25, 2008 5:25:57 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_63] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 5088
    system name : EQ7
    system nr.  : 03
    started at  : Tue Nov 25 17:25:58 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 8240] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 656 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 94 ms.
    Loading: ThreadManager ... 31 ms.
    Loading: IpVerificationManager ... 15 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 266 ms.
    Loading: LockingManager ... 79 ms.
    Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87039K->2718K(130560K), 0.0175167 secs] 87039K->2718K(1005056K), 0.0176768 secs]
    4250 ms.
    Loading: LicensingManager ... 46 ms.
    Loading: CacheManager ... 250 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (15 ms).
      service telnet ================= ERROR =================
      Service memory started. (31 ms).
      Service cross started. (32 ms).
      Service file started. (63 ms).
    7.854: [GC 7.855: [ParNew: 89758K->7739K(130560K), 0.0387127 secs] 89758K->7739K(1005056K), 0.0388651 secs]
      Service timeout started. (94 ms).
      Service runtimeinfo started. (15 ms).
      Service cafeucc~api started. (141 ms).
      Service trex.service started. (141 ms).
      Service userstore started. (79 ms).
      Service jmx_notification started. (47 ms).
      Service p4 started. (375 ms).
      Service classpath_resolver started. (47 ms).
      Service log_configurator started. (6343 ms).
      Service locking started. (0 ms).
      Service naming started. (641 ms).
      Service failover started. (172 ms).
      Service ts started. (281 ms).
      Service appclient started. (187 ms).
      Service javamail started. (312 ms).
      Service licensing started. (31 ms).
      Service jmsconnector started. (297 ms).
      Service http started. (1000 ms).
      Service connector started. (453 ms).
      Service iiop started. (281 ms).
      Service webservices started. (906 ms).
    16.628: [GC 16.628: [ParNew: 94779K->15719K(130560K), 0.0715624 secs] 94779K->15719K(1005056K), 0.0717470 secs]
    23.824: [GC 23.824: [ParNew: 102759K->17568K(130560K), 0.0594877 secs] 102759K->17568K(1005056K), 0.0596196 secs]
      Service deploy started. (21469 ms).
      Service configuration started. (47 ms).
      Service bimmrdeployer started. (15 ms).
      Service MigrationService started. (78 ms).
      Service dbpool started. (3641 ms).
    33.638: [GC 33.638: [ParNew: 104608K->20954K(130560K), 0.0721131 secs] 104608K->20954K(1005056K), 0.0722444 secs]
      Service cafeugpmailcf started. (156 ms).
    Nov 25, 2008 5:26:38 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_71] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      lang=EN
      receiverid=master
      sysnr=01
      client=888
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=R3DEVSER
    Nov 25, 2008 5:26:38 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_71] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:338)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:259)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Nov 25, 2008 5:26:38 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_71] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Regards,
    Ramana

    Hi Friends,
    Issue got resolved.. Sorry for delay reply.
    The following parameters need to check in Config tool.
    ume.r3.connection.master.client -
    ume.r3.connection.master.user -
    ume.r3.connection.master.passwrd
    ume.r3.connection.master.ashost
    ume.r3.connection.master.sysnr
    ume.datasource
    Regards,
    Ramana

Maybe you are looking for