Hi,

We are looking to implement a SAP PI 7.5 landscape and I understand that a range of things including number of server nodes are now determined using zero admin templates. What I have not been able to find a list of templates available from SAP and what each one does.

I am specifically interested in how it will work out the number of server nodes and memory params and whether I should be planning to override this in view of our design. I have come to a point where I think the template used for PI is Usage_Type_All_in_One. Can anyone from experience confirm if this is correct and what it would translate into once used.

Thanks,

Ahsan

Hi Team,

It`s vert complecated issue.

i run http://<IP ADDRESS>:<PORT>/sap/opu/odata/sap/ZHR_VF_RCV_SRV/PurchaseOrders('4500000215')/PurchaseOrderItems

Error List

1) RFC call ended with "Communication Failure" exception (Call of the function Z_GET_PO_ITEMS failed; a field should be assigned to the parameter PO_ITEMS - the types match, but not the length).

2)  <code>/IWBEP/CX_SD_GEN_DPC_TECH</code>

when i run web service then getting above error message. i did not usderstand whats a problem because ERROR LOG also not working.

if i run below URL from browser getting below error message

http://<IP ADDRESS>:<PORT>/sap/opu/odata/sap/ZHR_VF_RCV_SRV/PurchaseOrderItems('4500000215')?$format=xml

  <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">

            <script id="tinyhippos-injected"/>

            <code>005056A509B11EE1B9A8FEC11C22378E</code>

            <message xml:lang="en">Invalid key predicate</message>

    <innererror xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">

            <transactionid>7F6E02E42C3BF1469C3B000C29845429</transactionid>

            <timestamp>20140703045714.2460000</timestamp>

            <Error_Resolution>

                        <SAP_Transaction>

                        Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details

                        </SAP_Transaction>

                            <SAP_Note>

                            See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)

                            </SAP_Note>

            </Error_Resolution>

    </innererror>

</error>

guys please guide me. its very high priority.

Regards

Pankaj Kamble

Sometimes the consultants come to the Basis guy asking to do unusual things but required by the business. I ain't different and some requirements come and I would like to share with you one of them: schedule not supported by SAP standard.

Requirement

The project needs is following:

1. Hourly job
2. Must run between 03:00am and noon.

As known by Basis, this kind schedule isn't supported by SAP. If you set an hourly job there isn't option for time frame, window or anything like. After think a little about possible solutions, I conclude there are only 2 possible solutions without ABAP development:

1. Schedule multiple daily jobs, one for each hour
2. Schedule single jobs with external trigger

For the first solution it is easily configured but with high maintenance effort, because if for some reason the business decided to add steps or even change the variant, will exist lots of different jobs to change.

Jobs and External triggers

The default job triggers are described bellow:

Immediate

This runs the job immediately you save the job

Date/Time

Set an schedule to the job (specified date and time)

After Job

Run the job after another job.

After event

Run the job after an occurrence of an SAP event <--- This is the matter of the Blog!

At operational mode

Run the job only determined operational mode is running. This option can be used if the job schedule is the same of the operational mode configured.

SAP Events

In SAP Netweaver some events are triggered for too many different reasons. The standard installation comes with lots of pre configured events and allows to create your own events. Following the SAP standardization create your own starting with "Z" or "Y".

SM62

On SM62, click on new. The following window pops up:

Set the event's name (starting by Z or Y) and a description for your event.

SM36

The matter of this blog is not to teach you how to schedule a job but how to make it using a special schedule. Due this, I will only take care about whats change on the regular configuration. To use the event, click on after event. This will enable the After Event area to be filed up. Select your event from the math box and do not forget to set it as Periodic Job.

Windows Task Scheduler

My servers are windows servers, but this setup can be done in any operational system (on linux use the crontab and etc). The most important is to understand the procedure by itself than only follow a procedure. On windows task scheduler create a new task and set your schedule. Here I will show you an example. Adjust it for in accordance of your need.

Details	Screenshots
Set the task to run independent of the user is logged.
Select the triggers tab
Here it is the most important detail:   This trigger will be executed Daily at 04:38:41 PM, will trigger every minute the SAPEVT for 12 min.   In short - This trigger will start 4:38pm and will stop 4:50pm
On the tab Actions, you must execute a program called as SAPEVT.exe. This program is located in your kernel folder.   Set as argument the name of your event and the name of your system following the standard <trigger's name> name=<SID>   example - Z_TASKSCHEDULER name=SE1

And that is! Your special schedule is set successfully on your SAP system. Keep in your mind from now the trigger is the Windows Task Scheduler instead the SAP by itself.

I hope this would help you and see ya next time!

Frederich Murador

SAP Basis administrator

Hi everybody,

    I would like to know if is possible change the SOAP runtime. I've develop some webservice from RFC functions and I check on soamanager and the transport binding type is SOAP 1.1 and my client has asked me to use SOAP 1.2 instead of 1.1

Thanks in advance.

Hello,

I am using SCM 7.0 EhP4 system (based on NW 7.5) and applying below 2 support packages using SPAM.

WEBCUIF 748: SP 0002

SAP_BS_FND 748: SP 0002

During the patch application its giving below errors during the IMPORT_PROPER phase,

=======

Error 208-Invalid object name '/SSB/CACHECONV'. when executing ADD-FIELD of

Error /SSB/CACHEDATA when executing ADD-FIELD of

      DB-ROLLBACK()

No DDL commands found for activation of /SSB/CACHEDATA

Error 208-Invalid object name 'scd.TSTMP_CURRENT_UTCTIME when executing ADD-FIELD of

Error  in DDL statement for when executing ADD-FIELD of

          DB-ROLLBACK()

No DDL commands found for activation of /SSB/CACHECONV

=======

Can someone please suggest on this issue.

Thanks in advance!

Regards,

CS

Hi all,

I am strangling to get access key for ABAP.

Can anyone help me to get this??

Thanks & Regards

Nikhil Kohli

Dear Experts,

this is a very practical question and it's much more OS-related, than SAP-related.

I am performing an action on a 64-bit HP-UX server. I wanted to start sapinst in a

way, that it will be independent on the connection and it won't interrupt its run, if

the connection will be disrupted.

So I have launched:

nohup ../SWPM/sapinst -nogui &

as this is the way, recommended by SAP.

Then, in order to follow the output, I did tail -f nohup.out

The first problem was - when I wanted to do something else in this window, I hit

Ctrl+C and it not only went out of tail, but it also terminated sapinst !!!!!!!!

How come ??? What's wrong with nohup in HP-UX ?

Then I left this window alone and I opened another putty session and started

sapinstgui there.

Now the second problem - I have selected the operation desired on the first screen,

hit next, I could see a couple of lines on the status bar about various .xml files being

generated and so on. Then I saw something like "Determining the SAP systems

installed" and that was it. I never got past that screen. Maybe just one time it went

through, maybe after 25 minutes waiting, but that was all. Once I have hit again

next, the button went grey and it never displayed the next screen.

Did anyone had similar disturbing experience and what could you advise ?

I can only think of requesting VNC next time from the OS guys, as I have been using

it before and it's very reliable.

Many thanks in advance for your suggestions and opinions!

Hello Experts,

Is there a best practice on how to setup network for a new SAP implementation. We are doing a s.4 hana implementation and never had sap before, so want to know if there is any such guide. Please share.

Thanks,

Jun

Hi all,

from today I have a problem when I try to execute ESR of SAP NetWeaver 7.40 from IE11. At certain point appear a form that report this title: "class "com.sap.guid.GUIDFormatException" does not match trust level of other classes in the same package"

I have this exception message:

java.lang.SecurityException: class "com.sap.guid.GUIDFormatException" does not match trust level of other classes in the same package

  at com.sun.deploy.security.CPCallbackHandler$ChildElement.checkResource(Unknown Source)

  at com.sun.deploy.security.DeployURLClassPath$JarLoader.checkResource(Unknown Source)

  at com.sun.deploy.security.DeployURLClassPath$JarLoader.getResource(Unknown Source)

  at com.sun.deploy.security.DeployURLClassPath.getResource(Unknown Source)

  at java.net.URLClassLoader$1.run(Unknown Source)

  at java.net.URLClassLoader$1.run(Unknown Source)

  at java.security.AccessController.doPrivileged(Native Method)

  at java.net.URLClassLoader.findClass(Unknown Source)

  at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source)

  at java.lang.ClassLoader.loadClass(Unknown Source)

  at com.sun.jnlp.JNLPClassLoader.loadClass(Unknown Source)

  at java.lang.ClassLoader.loadClass(Unknown Source)

  at java.lang.Class.getDeclaredMethods0(Native Method)

  at java.lang.Class.privateGetDeclaredMethods(Unknown Source)

  at java.lang.Class.privateGetMethodRecursive(Unknown Source)

  at java.lang.Class.getMethod0(Unknown Source)

  at java.lang.Class.getMethod(Unknown Source)

  at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)

  at com.sun.javaws.Launcher.run(Unknown Source)

  at java.lang.Thread.run(Unknown Source)

And I have also the following Startup information

<?xml version="1.0" encoding="UTF-8"?><jnlp spec="1.0+" codebase="http://sap03610.zeiss.org:54300/rep/">

    <information>

        <title>Enterprise Services Repository</title>

        <vendor>SAP AG</vendor>

        <homepage href="http://www.sap.com"/>

        <description type="one-line">Enterprise Services Repository</description>

        <description type="short">Enterprise Services Repository</description>

        <description type="tooltip">Enterprise Services Repository</description>

        <icon height="64" width="64" href="start/graphics/sap6464.gif" type="splash"/>

        <icon height="32" width="32" href="start/graphics/SAP3232.gif"/>

    </information>

    <security>

        <all-permissions/>

    </security>

    <resources>

   <j2se java-vm-args="-Xms32m -Xmx512m -XX:MaxPermSize=128m" version="1.6+" initial-heap-size="32m" max-heap-size="512m"/><!--

         &lt;j2se version=&quot;1.6+&quot; initial-heap-size=&quot;32m&quot; max-heap-size=&quot;512m&quot;/&gt;

  --><!-- ==================================================================

        ATTENTION: When modifying references in this file, remember to update

                   the corresponding files from the test-apps too!

                  (see repository_test.jnlp in &quot;_ibrep_test/webapp/start&quot; )

        =================================================================== --><!--Do not define parts or packages! This will be done automatically --><!-- XI jars -->

        <jar href="repository/com.sap.xpi.ibrep.client.jar" download="lazy" part="part-102"/>

        <jar href="repository/com.sap.xpi.ibrep.core.jar" download="lazy" part="part-102"/>

        <jar href="repository/com.sap.xpi.ibrep.rb.jar" download="lazy" part="part-102"/>

        <jar href="repository/com.sap.xpi.ib.client.jar" download="lazy" part="part-93"/>

        <jar href="repository/com.sap.xpi.ib.core.jar" download="lazy" part="part-93"/>

        <jar href="repository/com.sap.xpi.ib.rb.jar" download="lazy" part="part-93"/>

        <jar href="repository/com.sap.xpi.ib.mt.gui.lib.jar" download="lazy" part="part-114"/>

        <jar href="repository/com.sap.xpi.ib.mt.rb.jar" download="lazy" part="part-114"/>

        <jar href="repository/com.sap.xpi.ib.mt.util.lib.jar" download="lazy" part="part-114"/>

        <jar href="repository/com.sap.xpi.ib.mapping.lib.jar" download="lazy" part="part-110"/>

        <jar href="repository/com.sap.xpi.ib.upload.core.jar" download="lazy" part="part-116"/>

        <jar href="repository/com.sap.xpi.ib.upload.sap.jar" download="lazy" part="part-118"/>

        <jar href="repository/com.sap.xi.mapping.tool.lib_api.jar" download="lazy" part="part-114"/>

        <jar href="repository/com.sap.xi.flib.lib_api.jar" download="lazy" part="part-93"/>

        <jar href="repository/com.sap.aii.utilxi.core.jar" download="lazy" part="part-121"/>

        <jar href="repository/com.sap.aii.utilxi.gui.jar" download="lazy" part="part-132"/>

        <jar href="repository/com.sap.xpi.util.rb.jar" download="lazy" part="part-121"/>

        <jar href="repository/com.sap.aii.proxy.gen.jar" download="lazy" part="part-115"/>

        <jar href="repository/frog.jar" download="lazy" part="part-234"/>

        <jar href="repository/com.sap.xpi.ibrep.core.subn.jar" download="lazy" part="part-232"/><!-- Engine and other components -->

        <jar href="repository/jta.jar" download="lazy" part="part-304"/>

        <jar href="repository/ejb20.jar" download="lazy" part="part-301"/>

        <jar href="repository/sap.com~tc~sapxmltoolkit~sapxmltoolkit.jar" download="lazy" part="part-184"/>

        <jar href="repository/sap.com~tc~exception~impl.jar" download="lazy" part="part-225"/>

        <jar href="repository/sap.com~tc~logging~java~impl.jar" download="lazy" part="part-240"/>

        <jar href="repository/sap.com~tc~bl~guidgenerator~impl.jar" download="lazy" part="part-226"/>

        <jar href="repository/jperflib.jar" download="lazy" part="part-154"/>

        <jar href="repository/sap.com~tc~bl~ni~impl.jar" download="lazy" part="part-231"/><!-- required for CSN-connection -->

        <jar href="repository/sap.com~tc~je~clientlib~impl.jar" download="lazy" part="part-162"/>

        <jar href="repository/sap.com~tc~bl~jarm~jarm.jar" download="lazy" part="part-242"/><!-- Tensegrity Libs -->

        <jar href="repository/tenComposite.jar" download="lazy" part="part-268"/>

        <jar href="repository/tenGraph.jar" download="lazy" part="part-277"/>

        <jar href="repository/tenGraphics.jar" download="lazy" part="part-290"/>

        <jar href="repository/tenGenerics.jar" download="lazy" part="part-102"/>

        <jar href="repository/tenGui.jar" download="lazy" part="part-7"/>

        <jar href="repository/tenGuiResource.jar" download="lazy" part="part-292"/><!-- Maestro--><!--jar href=&quot;repository/maestro_ib.jar&quot; download=&quot;lazy&quot; /-->

        <jar href="repository/com.sap.xpi.ibrep.maestro.core.jar" download="lazy" part="part-102"/>

        <jar href="repository/com.sap.xpi.ibrep.maestro.model.jar" download="lazy" part="part-102"/>

        <jar href="repository/tenSkeleton.jar" download="lazy" part="part-249"/>

        <jar href="repository/tenLookAndFeel.jar" download="lazy" part="part-7"/>

        <jar href="repository/jaxb-api.jar" download="lazy" part="part-305"/>

        <jar href="repository/jaxb-impl.jar" download="lazy" part="part-0"/>

        <jar href="repository/jaxb-xjc.jar" download="lazy" part="part-0"/>

        <jar href="repository/jsr173_1.0_api.jar" download="lazy" part="part-306"/>

        <jar href="repository/activation.jar" download="lazy" part="part-244"/><!-- end Maestro--><!-- Aris Client -->

  <jar href="repository/jaxb-api-2.1.jar" download="lazy" part="part-305"/>

  <jar href="repository/jide-2.7.5.jar" download="lazy" part="part-47"/>

        <jar href="repository/JimiProClasses-1.0.0.jar" download="lazy" part="part-251"/>

        <jar href="repository/client.jar" download="lazy" part="part-14"/>

  <jar href="repository/jsr-1.7.3.jar" download="lazy" part="part-306"/>

  <jar href="repository/jxlayer-1.0.jar" download="lazy" part="part-313"/>

  <jar href="repository/filters-2.0.235.jar" download="lazy" part="part-43"/>

  <jar href="repository/y-reportdesigner-client-3.3.0-486419.jar" download="lazy" part="part-38"/>

  <jar href="repository/y-annotations-1.0.0-346691.jar" download="lazy" part="part-20"/>

  <jar href="repository/y-spellchecker-dictionaries-1.0.0-SNAPSHOT.jar" download="lazy" part="part-40"/>

  <jar href="repository/y-spellchecker-1.0.0-SNAPSHOT.jar" download="lazy" part="part-41"/>

  <jar href="repository/scptlang_en_help.jar" download="lazy" part="part-9"/>

  <jar href="repository/commons-digester-1.8.jar" download="lazy" part="part-312"/>

  <jar href="repository/commons-collections-3.2.2.jar" download="lazy" part="part-311"/><!-- Aris Core -->

  <jar href="repository/arismethod.jar" download="lazy" part="part-25"/>

        <jar href="repository/cl_locale.jar" download="lazy" part="part-14"/>

        <jar href="repository/cl_locale_de.jar" download="lazy" part="part-14"/>

        <jar href="repository/cl_locale_en.jar" download="lazy" part="part-14"/>

  <jar href="repository/mail-1.4.jar" download="lazy" part="part-254"/>

        <jar href="repository/jh-2.0_03.jar" download="lazy" part="part-249"/>

        <jar href="repository/js-1.7R2.jar" download="lazy" part="part-327"/>

        <jar href="repository/y-6.2.0.1.jar" download="lazy" part="part-27"/>

        <jar href="repository/y-reportexecution-3.0.0-474547.jar" download="lazy" part="part-37"/>

  <jar href="repository/y-reportdesigner-common-3.3.0-454947.jar" download="lazy" part="part-39"/>

  <jar href="repository/y-graphics-3.3.1-471587.jar" download="lazy" part="part-26"/>

        <jar href="repository/y-graphlayout-2.8.6-463383.jar" download="lazy" part="part-27"/>

  <jar href="repository/y-guiframework-6.21.52-738883.jar" download="lazy" part="part-26"/>

        <jar href="repository/y-lipo-1.1.2-416426.jar" download="lazy" part="part-35"/>

  <jar href="repository/y-utils-2.2.4-469928.jar" download="lazy" part="part-42"/>

        <jar href="repository/jdom-1.1.jar" download="lazy" part="part-10"/><!-- only for repository, when build is adapted

        &lt;jar href=&quot;repository/sapjco.jar&quot; download=&quot;lazy&quot; component=&quot;aris&quot;/&gt;

        &lt;nativelib href=&quot;repository/sap-rfc-windows.jar&quot; download=&quot;lazy&quot; component=&quot;aris&quot;/&gt;

        --><!-- end Aris --><!-- ssl libs -->

        <jar href="repository/iaik_jsse.jar" download="lazy" part="part-297"/>

        <jar href="repository/iaik_smime.jar" download="lazy" part="part-297"/>

        <jar href="repository/iaik_ssl.jar" download="lazy" part="part-297"/>

        <jar href="repository/w3c_http.jar" download="lazy" part="part-330"/>

        <property name="jnlp.log.initialConfiguration" value="FILE, SIMPLE"/>

        <property name="jnlp.com.sap.boot" value="rep,native"/>

  <property name="sun.java2d.d3d" value="false"/>

    <property name="jnlp.j2ee.dbhost.short" value="sap04388"/><property name="jnlp.com.sap.aii.ibdir.core.transport.autoDeploy" value="false"/><property name="jnlp.com.sap.aii.ibrep.core.cms.enableTransportWizard" value="false"/><property name="jnlp.com.sap.aii.ibrep.core.aris.ReleasedMethodOnly" value="true"/><property name="jnlp.com.sap.aii.ibrep.core.transport.enableCLNTupleTransport" value="false"/><property name="jnlp.com.sap.aii.ib.client.properties" value="com.sap.aii.ib.client.*, com.sap.aii.ib.core.*, com.sap.aii.util.xml.*, com.sap.aii.connect.*, com.sap.aii.repository.mapping.additionaltypes, com.sap.aii.docu.*, com.sap.aii.ibrep.core.*, com.sap.aii.ibdir.core.* , com.sap.aii.ibrep.client.*"/><property name="jnlp.com.sap.aii.ib.core.activation.changelist.enableNameCheck" value="false"/><property name="jnlp.com.sap.aii.connect.integrationserver.sld.name" value="is.44.sap03610"/><property name="jnlp.com.sap.aii.connect.landscape.contextroot" value="sld"/><property name="jnlp.com.sap.aii.connect.cr.name" value

jnlp file truncated after 10K

Someone can help me to fix this problem?

Thanks in advance for any help

Hello,

I have two questions about heterogeneous system copy.

First, is it necessary to open the SAP instances while exporting the source system?

Second, while installing the source system should i do the initial setup together with the existing export file or should the export file be implemented after completing the initial setup?

Best regards.

Hi everybody,

i try to monitor our SAP AS Java with JConsole locally from the server. When i start JConsole and try to connect locally, i get a JMX securityException and a classNotFoundException. JMX is already installed and i configured the server like explained in this tutorial.

http://wiki.sdn.sap.com/wiki/display/TechTSG/JMXRemoteport+configuration

regards

J2EE Engine not starting after i deploy LMSERVICE11P_5-20006622.zip and SAPJEE18_0-10006664.zip. There probably missing com/sap/security/core/util/imp/HashConverter class, but in which package is included, where i can download this?

std_server0.out:

ClassLoader name: [common:interface:tc~sec~destinations~interface;library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:signature_lib;library:tc.httpclient;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:tc~lm~nzdm~crrsrv;service:userstore]

Parent loader name: [Frame ClassLoader]

References:

   common:service:iiop;service:naming;service:p4;service:ts

   library:com.sap.ip.basecomps

   library:core_lib

   common:library:IAIKSecurity;library:activation;library:mail;library:tc~sec~ssl

   library:servlet

   library:sapxmltoolkit

   library:com.sap.mw.jco

   library:com.sap.util.monitor.jarm

   library:j2eeca

   library:opensql

   library:tc~bl~txmanager~plb

   library:tc~i18n~cp

   library:tc~lm~nzdm~crrfrmwrk

   interface:security

   interface:log

   interface:shell

   interface:keystore_api

   interface:tc~sec~certrevoc~interface

   library:ejb20

   library:compilation_lib

   interface:webservices

   library:com.sap.guid

   interface:appcontext

   interface:endpoint_api

   interface:resourceset_api

   interface:resourcecontext_api

   interface:ejbcomponent

   interface:container

   interface:visual_administration

   interface:transactionext

   interface:dsr_ejbcontext_api

   service:timeout

   library:tc~jmx

   interface:cross

   service:file

   service:locking

   library:tc~SL~UTIL

   service:memory

   library:antlr

   library:jdbdictionary

   library:opensqlextensions

Resources:

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\dbpool\dbpool.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_jaas.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\dbpool\sqljimpl.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.security.api.sda\com.sap.security.api.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\deploy\deploy.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\basicadmin\basicadmin.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_csi.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\jmx_notification\jmx_notification.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\userstore\userstore.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_https.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_jaas_test.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\basicadmin\jstartupimpl.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.security.core.sda\com.sap.security.core.tpd.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\webservices_lib\webservices_lib.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\tc.httpclient\httpclient.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\configuration\configuration.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_toolkit_core.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\jmx\jmx_sec.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\signature_lib\signature.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\webservices_lib\saaj-api.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\com.sap.security.core.ume.service\com.sap.security.core.ume.service.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.security.api.sda\com.sap.security.api.perm.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\basicadmin\jstartupapi.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\webservices_lib\jaxm-api.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\dbpool\opensqllib.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\security\security.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\adminadapter\adminadapter.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\keystore\keystore.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\connector\connectorimpl.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_ssf.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_util.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_service_api.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_userstore_lib.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_compat.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_xmlbind.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_toolkit_api.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\jmx\jmx.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_jaas.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\interfaces\tc~sec~destinations~interface\tc_sec_destinations_interface.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\tc~lm~nzdm~crrsrv\crrsrv.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.security.core.sda\com.sap.security.core.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\webservices_lib\jaxrpc-api.jar

Loading model: {parent,local,references}

---------------------------------------------------------------

  at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:382)

  ... 7 more

java.lang.NoClassDefFoundError: com/sap/security/core/util/imp/HashConverter

  at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:399)

  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:83)

  at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)

Caused by: java.lang.ClassNotFoundException: com.sap.security.core.util.imp.HashConverter

------------------------- Loader Info -------------------------

ClassLoader name: [common:interface:tc~sec~destinations~interface;library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:signature_lib;library:tc.httpclient;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:tc~lm~nzdm~crrsrv;service:userstore]

Parent loader name: [Frame ClassLoader]

References:

   common:service:iiop;service:naming;service:p4;service:ts

   library:com.sap.ip.basecomps

   library:core_lib

   common:library:IAIKSecurity;library:activation;library:mail;library:tc~sec~ssl

   library:servlet

   library:sapxmltoolkit

   library:com.sap.mw.jco

   library:com.sap.util.monitor.jarm

   library:j2eeca

   library:opensql

   library:tc~bl~txmanager~plb

   library:tc~i18n~cp

   library:tc~lm~nzdm~crrfrmwrk

   interface:security

   interface:log

   interface:shell

   interface:keystore_api

   interface:tc~sec~certrevoc~interface

   library:ejb20

   library:compilation_lib

   interface:webservices

   library:com.sap.guid

   interface:appcontext

   interface:endpoint_api

   interface:resourceset_api

   interface:resourcecontext_api

   interface:ejbcomponent

   interface:container

   interface:visual_administration

   interface:transactionext

   interface:dsr_ejbcontext_api

   service:timeout

   library:tc~jmx

   interface:cross

   service:file

   service:locking

   library:tc~SL~UTIL

   service:memory

   library:antlr

   library:jdbdictionary

   library:opensqlextensions

Resources:

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\dbpool\dbpool.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_jaas.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\dbpool\sqljimpl.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.security.api.sda\com.sap.security.api.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\deploy\deploy.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\basicadmin\basicadmin.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_csi.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\jmx_notification\jmx_notification.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\userstore\userstore.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_https.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_jaas_test.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\basicadmin\jstartupimpl.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.security.core.sda\com.sap.security.core.tpd.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\webservices_lib\webservices_lib.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\tc.httpclient\httpclient.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\configuration\configuration.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_toolkit_core.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\jmx\jmx_sec.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\signature_lib\signature.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\webservices_lib\saaj-api.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\com.sap.security.core.ume.service\com.sap.security.core.ume.service.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.security.api.sda\com.sap.security.api.perm.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\basicadmin\jstartupapi.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\webservices_lib\jaxm-api.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\dbpool\opensqllib.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\security\security.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\adminadapter\adminadapter.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\keystore\keystore.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\connector\connectorimpl.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_ssf.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_util.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_service_api.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_userstore_lib.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_compat.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_xmlbind.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_saml_toolkit_api.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\jmx\jmx.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\security.class\tc_sec_jaas.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\interfaces\tc~sec~destinations~interface\tc_sec_destinations_interface.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\services\tc~lm~nzdm~crrsrv\crrsrv.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.security.core.sda\com.sap.security.core.jar

   F:\usr\sap\R46\DVEBMGS00\j2ee\cluster\server0\bin\ext\webservices_lib\jaxrpc-api.jar

Loading model: {parent,local,references}

---------------------------------------------------------------

  at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:382)

  ... 7 more

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

May 17, 2016 3:18:51 PM             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.

Heap

par new generation   reserved 614400K, committed 614400K, used 66260K [0x000000007fff0000, 0x00000000a57f0000, 0x00000000a57f0000)

  eden space 409600K,   8% used [0x000000007fff0000, 0x00000000822e0368, 0x0000000098ff0000)

  from space 102400K,  29% used [0x000000009f3f0000, 0x00000000a11b4e30, 0x00000000a57f0000)

  to   space 102400K,   0% used [0x0000000098ff0000, 0x0000000098ff0000, 0x000000009f3f0000)

concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x00000000a57f0000, 0x00000000ffff0000, 0x00000000ffff0000)

concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 43658K [0x00000000ffff0000, 0x000000011fff0000,

Dear Experts,

I was thinking, that testing the migration key in advance isn't a bad idea. But I am really struggling

to perform this in practice. Looking through the different system copy guides and other documentation,

I can't find a real example on how exactly to do that, hence I am posting a couple of questions, to

which I didn't find the answers nowhere:

1) On what system one has to test the migration key ? Source or target ? (I think, on the target system)

2) Is it necessary to already have the export files ? Meaning - is it possible to test the migration key even

before performing the export of the source system ?

3) What is the EXACT COMMAND, meaning a REAL syntax example, without any placeholders like

<TASK_FILE>, etc. ?

4) If testing is performed on the target system, what do we need to have there, in order to test it ? Installed

database ? Unpacked R3load binary ? Unpacked kernel ? Installed NetWeaver system ? .CMD file ?

.TPL file ? Data file (.000), TEST_MIGKEY.CMD ?? Nobody says exactly what has to be done...

Many thanks for clarifying this to me!

Dear SAP Basis Gurus and SAP Abap Gurus,

I am executing a sap report to create business partner in SAP CRM system. Now i have used parallel processing methodology in this report for business partner creation.

This report works fine with 80% of total dialogue processors in the system(quality/development/testing sap servers) used with multiple batch jobs in parallel (example if total dialogue processes in system is 100 then i schedule this report with 10 batch jobs and 8 dialogue processor per batch job).

But in production system we have 12 application servers with (150 dialogue processors, 20 update 1, 10 update 2 and 30 batch processes) per application server. So total resource is

dialogue processor : 1800

update 1: 240

update 2 : 120

batch jobs available: 360

Now i am scheduling the business partner creation report with 84 batch jobs and assigned 17 dialogue processor per batch job.

But only 7-8 jobs are remaining active after scheduling and updating the database creating customer and rest of the jobs are finished in 1 second without updating anything (note: there is nothing wrong with data creation as we write application log for error while data creation and nothing has come up in application log). Now i reprocesses the rest of the batch jobs which completed in 1 second earlier and didn't update, again 7-8 jobs are remaining active and creating business partner and rest of them are finished in 1 second and so on.

This report is working fine in other sap systems like quality/development/testing, and this problem is only happening in production.

I am not at all familiar with basis configurations, So kindly help me out with this issue.

Thanks for your help

Sudipto

Dear Experts ,

We had received this error due to which we stopped the installation process.

Installation SAP Netweaver 7.0 SR3 ABAP

Oracle 10g

Windows Server 2K8 R2 64bit

Phase 10 : Create Database

TRACE      2016-04-21 15:19:14.958 (HOSTNAME\USERADMIN) [cguiengineimp.cpp:553]  CGuiEngineImp::showMessageBox()

<html> <head> </head> <body> <p> An error occurred while processing option <i>SAP NetWeaver 7.0 Support Release 3 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Assertion failed: in

function (role, readAccountData) {

    if (readAccountData === undefined) {

        readAccountData = true;

    }

    NWUSERADMINs.trace("NWUSERADMINs.getAccountData(", role, ")");

    this._initAccountData();

    ASSERT(arguments.callee, this.haveAccountData(role), "role " + role + " is not created yet.");

    var ad = this._readAccountDataFromKeydb(role);

    if (readAccountData) {

        ad = this._readAccountData(ad);

    }

    var masterpwd = this.getMasterPassword();

    if (ad.password == "" && this._useMasterPasswordForAccountData(ad) && ad.type == "USERADMIN" && masterpwd !== undefined && role != NWUSERADMINs.roles.J2EEGuest && !ad.locked) {

        ad.password = masterpwd;

    }

    NWUSERADMINs.trace("NWUSERADMINs.getAccountData(): ", dump_properties(ad));

    return ad;

}

: role ORA_SID_DBA is not created yet.)</i>. You can now: </p> <ul> <li> Choose <i>Retry</i><br>to repeat the current step. </li> <li> Choose <i>Log Files</i><br>to get more information about the error. </li> <li> Stop the option and continue later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW700/AS-ABAP/ORA/CENTRAL/. </p> </body></html>

TRACE      2016-04-21 15:19:14.958 (HOSTNAME\USERADMIN) [cguiengineimp.cpp:908] CGuiEngineImp::acceptAnswerForBlockingRequest

Waiting for an answer from GUI

Do I need to create this role manually or any modification to be done?

Please help me to resolve the issue.

Thank you.

Hi,

We are trying to deploy 1 DC but getting below mentioned error while trying to deploy the same on portal server (7.3).

Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: SOAObjectId type = CONSUMER_GROUP local = PI_WS ns = xx.com/xx~udi~dctm~interface processingState = INITIAL delete = false (processingTraceId=null, processingLogId=null) at com.sap.esi.esp.service.server.deploy.ws.WSDeploymentPlugin.onUpdate(WSDeploymentPlugin.java:102) at com.sap.engine.services.webservices.server.deploy.WebServicesNotificationHandler.sendEvent(WebServicesNotificationHandler.java:56) ... 21 more Caused by: com.sap.esi.esp.service.server.deploy.ActionException: com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: SOAObjectId type = CONSUMER_GROUP local = PI_WS ns = xx.com/xx~udi~dctm~interface processingState = INITIAL delete = false (processingTraceId=null, processingLogId=null) at

While checking application communication config in NWA, getting similar error as shown in screenshot.

Any suggestion like what is going wrong here.

Thanks.

In this document you will find the latest information about the SAP kernel such as

• Announcements of SP stack kernel deliveries
• Other news related to the development, maintenance and usage of the SAP kernel versions 72X (721, 721_EXT, 722, 722_EXT) and 74X (742, 745)

If you are interested in getting notifications when this document is updated, please activate the "Receive email notifications" feature. To unsubscribe from receiving notifications, click on "Stop email notifications".

News

18.05.2016: Kernel 722 PL 118 and 742 PL 412 revoked

There are issues with the RFC delta manager inside the kernel. External clients may get stuck. As a precaution the affected kernel patches have been revoked from ServiceMarketPlace.

28.04.2016: SP Stack Kernel 742 PL 400 released

SP stack kernel 742 PL 400 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2300406.

Information on known issues in the stack kernel 742 PL 400 can be found in Note 2294986. This note will be updated on a regular basis.

14.04.2016: WebGUI issue with Google Chrome Version 50

After updating Google Chrome from Version 49 to Version 50 the Easy Access Menu (start screen) remains empty. We are working on a kernel patch to circumvent this. For details see SAP Note 2305778.

12.04.2016: Potential Issue with Kernel 742 PL 311 - 321 and Kernel 745 PL 25 - 35

In edge cases a select statement may return an unexpected result. For details see SAP Note 2273425.
It is recommended to upgrade to SP Stack Kernel 745 PL 100 or Kernel 742 PL 329 which is the last release candidate before the upcoming SP Stack Kernel 742 PL 400.

17.03.2016: Kernel 745 Released as DCK to Kernels 740, 741 and 742

After an extended validation phase kernel 745 PL#100 has been released as a downward compatible kernel (DCK) to kernels 742, 741 and 740 and can be used instead of these with SAP NetWeaver 7.4. Refer to SAP Note 2251972 for details on installation and usage of kernel 742 as DCK. The release roadmap for 74* kernels is presented in SAP Note 1969546.

17.03.2016: SP Stack Kernel 722 PL 101 released

SP stack kernel 722 PL #101 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2292019.

Information on known issues in the stack kernel 722 PL #101 can be found in Note 2292017. This note will be updated on a regular basis.

18.12.2015: SAP Kernel 721 PL 618 and SAP Kernel 722 PL 20 and PL 21 revoked

As a precaution the Kernel (dw.sar) for 721 PL 618 and 722 PL 20 and 21 have been revoked from the SAP Support Portal.

For further details see SAP Note 2259736. We are working a patch highest priority.

13.11.2015: Heads up on Kernel 745 for NetWeaver 7.4

During Q1/2016 SAP Kernel 745 will be made available as Downward Compatible Kernel for SAP NetWeaver 7.4.

SAP Kernel 745 will eventually succeed SAP Kernel 742 (and 741 and 740).

SAP Kernel 742 will be retired in Q1/2017, one year later than the availability of SAP Kernel 745 as DCK. No more patches will be provided for SAP Kernel 742 after that date.

See also Understanding Kernel Releases for the SAP NetWeaver AS ABAP and SAP Note 1969546 - Release Roadmap Kernel 740

09.11.2015: SP Stack Kernel 742 PL#300 Released

SP stack kernel 742 PL #300 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2237353.

Information on known issues in the stack kernel 742 PL #300 can be found in SAP Note 2231749. This note will be updated on a regular basis.

16.10.2015: Kernel 722 PL14, PL15 and enserver PL 14 revoked

As a precaution Enqueue Server 722 PL 14 (enserver.sar) and Kernel (dw.sar) 722 PL 14 and PL 15 have been revoked from the SAP Support Portal.
The new patch of the Enqueue Server might not be 100% compatible to older clients (e.g. disp+work PL 13) and the newer disp+work starting PL 14 might not be 100% compatible with old Enqueue Servers (prior patch 14). Standard operations Enque, Dequeue and DequeueAll are NOT affected. Details can be found in SAP Note 2239931

13.10.2015: SP Stack Kernel 721 PL#600 Released

SP stack kernel 721 PL #600 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2214191.

Information on known issues in the stack kernel 721 PL #600 can be found in SAP Note 2214680. This note will be updated on a regular basis.

02.10.2015: issue with Oracle lib_DBSL 722 PL 13

Please do not use patch 13 for the 722 Oracle lib_DBSL

Further details can be found in note 2220724. A fix is expected early next week.

14.09.2015: SP Stack Kernel 741 PL#300 Released

The last SP stack kernel for the 741 kernel version has been released today. Kernel 741 PL #300 can be downloaded from the archive area of SAP Support Portal. Refer to release note 2207362 for information on fixes included in this stack kernel.

As announced previously, kernel 741 has reached its end of maintenance, see note 1969546 for more detail. Future 74* kernel corrections will be delivered through 742 kernel patches.

08.07.2015: SP Stack Kernel 742 PL#200 Released

SP stack kernel 742 PL #200 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2178917.

Information on known issues in the stack kernel 742 PL #200 can be found in Note 2176515. This note will be updated on a regular basis.

07.07.2015 SAP Kernel 741 maintenance

The SAP Kernel 741 reached its end of maintenance, see note 1969546. We will continue to deliver regression fixes during July and a final stack kernel 741 PL#300 in August. After that corrections will be delivered through kernel 742 patches.

12.06.2015 SAP Kernel Archive

SAP Kernels which are out of maintenance like SAP Kernel 720 can be found in the archive https://support.sap.com/software/patches/archive.html

For SAP Kernel 720 the last version is patch level 800. Please read the release note 2158874  - SAP Support Package Stack Kernel 7.20 (EXT) Patch Level 800. Corresponding note for regression found in the future is 2138737.

20.05.2015 SAP Kernel 722 Released

SAP kernel 722 has been released for customers today. The first shipment (Kernel 722 PL#4) can now be downloaded from SAP Support Portal. With this a new release cycle has been established for 72X kernel versions that can be used with all SAP NetWeaver releases 7.00-7.31:

• Kernel 720 reached its end of maintenance, no further corrections will be provided for this kernel version
• Kernel 721 becomes the standard kernel containing only corrections/bug fixes
• Kernel 722 replaces Kernel 721 in its role as Innovation Kernel. Besides regular corrections, new features/enhancements/improvements will be delivered with Kernel 722.

Refer to SAP Note 2133909 for general information on Kernel 722 including new features and current limitations. This note will be updated on regular basis.

Kernel 722 can be applied manually as a kernel patch, see Note 2115344 - Installation of Kernel 722 (EXT) for detailed instructions. Options to apply Kernel 722 during upgrade/update are outlined in Note 2133909.

04.05.2015: SP Stack Kernel 721 PL#500 Released

A new SP stack kernel 721 PL #500 is now available on SAP Support Portal.

SAP Note 2158856 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #402.

All regressions known in the PL #402 have been fixed.

Review SAP Note 2155366 for known issues in the stack kernel 721 PL #500. This note will be continuously updated.

14.04.2015: Kernel 742 Released as DCK to Kernels 740 and 741

After an extended validation phase kernel 742 PL#101 has been released as a downward compatible kernel (DCK) to kernels 741 and 740 and can be used instead of these with SAP NetWeaver 7.4. Refer to Note 2128122 for details on installation and usage of kernel 742 as DCK. The release roadmap for 74* kernels is presented in Note 1969546.

31.03.2015: SP Stack Kernels 741 PL#201 and 742 PL#101 are delivered

As announced previously, SP Stack kernels for 741 and 742 kernel versions have been updated. 741 PL#201 replaces 741 PL#200 and 742 PL#101 replaces 742 PL#100. New SP stack kernels can be now downloaded from SAP Support Portal, following fixes are included:

• Regression in the Oracle DBSL Library (Note 2118448, Point 2 - Termination during secondary database connection; LRAW length error) is removed.
• CommonCryptoLib has been updated to the version 8.4.35 (see Note 2134460.)

For more details on 741 PL#201 refer to Notes 2150081 - SAP Support Package Stack Kernel 7.41 Patch Level 201 and 2100429 - Known regressions in kernel 7.41 patch level 201.

Fixes and enhancements in the SP stack kernel 742 PL#101 are listed in the note 2145156. Information on known issues with this stack kernel can be found in the Note 2134238.

19.03.2015: Update on SP Stack Kernels 741 PL#200 and 742 PL#100

The latest SP stack kernels 741 (PL#200) and 742 (PL#100) contain a regression in the Oracle DBSL Library, see Note 2118448 -Termination during secondary database connection; LRAW length error, Point 2.

As a solution you may use the latest ORA lib_dbsl available on SAP Support portal. For kernel 741 on Windows, please be aware of the issue 2142073 - Application server in Windows NT with Oracle does not start.

Updated stack kernels will be provided as soon as possible.

11.03.2015: SP Stack Kernel 721 PL#402 Released

SP Stack kernel 721 PL #402 has been released and can be downloaded from SAP Support Portal. The issues from PL#400 (Note 2118382) and PL#401 (Note 2138260) are fixed.

Refer to Note 2138680 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 402 for overview of new features, enhancements and improvements added since PL#300. Known regressions are documented in Note 2138678.

09.03.2015: SP Stack Kernel 742 PL#100 Released

SP stack kernel 742 PL #100 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2136550.

Information on known issues in the stack kernel 742 PL #100 can be found in Note 2129327. This note will be updated on regular basis.

04.03.2015: SP Stack Kernel 721 PL#401 Revoked

SP Stack kernel 721 PL #401 has been revoked from SAP Support Portal for all platforms except for MS Windows because the kernel archives contained some files with wrong versions.

In most cases it is not necessary to replace the kernel in a system running with PL#401 because the issue has a limited impact and does not affect the kernel itself. Details are outlined in Note 2138260.

SP stack kernel PL#402 will be released as soon as possible; this document will be updated accordingly.

06.02.2015: SP Stack Kernel 741 PL#200 Released

A new SP stack kernel 741 PL #200 has been released today and can be downloaded from SAP Support Portal.

For a summary of enhancements and improvements included into this stack kernel, see SAP Note 2101802 - SAP Support Package Stack Kernel 7.41 Patch Level 200.

30.01.2015: SP Stack Kernel 721 PL#401 Replaces PL#400

Current SP stack kernel 721 PL#400 has been replaced with PL#401, see Note 2121693 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 401.

It fixes a file permission issue that has a very limited impact:

• It occurs with 721_EXT kernel on Windows platforms only
• It has no effect at runtime, only for future system maintenance
• Workaround is easy.

This means: even if above criteria apply, it is not always necessary to replace already installed 721 kernel PL#400. Refer to Note 2118382 for more information.

Note 2084437 contains the list of known regressions in the stack kernel 721 PL #401. This note will be continuously updated.

16.12.2014: SP Stack Kernel 721 PL#400 Released

A new SP stack kernel 721 PL #400 is now available on SAP Service Marketplace.

SAP Note 2101779 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #300.

All regressions known in the PL #300 have been fixed.

Review SAP Note 2084436 for known issues in the stack kernel 721 PL #400. This note will be continuously updated.

Hello,

I am trying to install TREX 7.1_62 on Linux server.

I put /sapmnt as my installation location in sapinst.

While installing TREX instance the installer is terminating with below log:

_install.log

Traceback (most recent call last):

  File "/sapsw/TREX_71_62/tx_trex_content/TX_LINUX_X86_64/support/setuplib.py", line 5013, in createLinked

    os.symlink(link[1], link[0])

OSError: [Errno 17] File exists

*******************************************************************************

Action: Creating directory structure for SAPSID D82, Instance 00 -- failed.

Exception description:

Traceback (most recent call last):

  File "/sapsw/TREX_71_62/tx_trex_content/TX_LINUX_X86_64/support/_install.py", line 1340, in installInstance

    self.memberInstallStatus.doItOrNot(self.memberSarTrek.createdirs)

  File "/sapsw/TREX_71_62/tx_trex_content/TX_LINUX_X86_64/support/setuplib.py", line 5857, in doItOrNot

    step(*args, **keyArgs)

  File "/sapsw/TREX_71_62/tx_trex_content/TX_LINUX_X86_64/support/setuplib.py", line 2542, in createdirs

    self.ds.createLinked()

  File "/sapsw/TREX_71_62/tx_trex_content/TX_LINUX_X86_64/support/setuplib.py", line 5016, in createLinked

    raise SetupException("failed to check/create link %s -> %s!" % (link[0], link[1]))

SetupException: >>>ERROR:failed to check/create link /usr/sap/D82 -> /sapmnt/D82!

*******************************************************************************

############ >>>ERROR:failed to check/create link /usr/sap/D82 -> /sapmnt/D82! - TREX setup cannot proceed.

Exception description:

Traceback (most recent call last):

  File "/sapsw/TREX_71_62/tx_trex_content/TX_LINUX_X86_64/support/_install.py", line 3562, in main

    Installer().mainTrexAction()

  File "/sapsw/TREX_71_62/tx_trex_content/TX_LINUX_X86_64/support/_install.py", line 703, in mainTrexAction

    self.installInstance(step)

  File "/sapsw/TREX_71_62/tx_trex_content/TX_LINUX_X86_64/support/_install.py", line 1379, in installInstance

    framework.error(str(e) + " - TREX setup cannot proceed.")

  File "/sapsw/TREX_71_62/tx_trex_content/TX_LINUX_X86_64/support/_install.py", line 3472, in error

    raise ErrorException(self.errorMarker + text,result=1)

ErrorException: <__main__.ErrorException instance at 0x7f4cfda6bd88>

*******************************************************************************

*                   ===  Script execution resumee  ===                        *

* Step 1: Preparation and checks before TREX system installation      : SUCCESS

* Step 2: TREX system installation                                    : FAILED

* Script execution terminated at 2015-04-03_08.33.35 with error 1

*******************************************************************************

I tried to use other locations like /usr/sap/D82 as installation location, inthat case it tries to create link like

/usr/sap/D82/D82 --> /usr/sap/D82

My server has /sapnt/D82 and /usr/sap/D82 as separate mount points.

/dev/mapper/vg_dd82-lvusapd82_3

                       47G  1.1G   46G   3% /usr/sap/D82

/dev/mapper/vg_dd82-lvusapd82_4

                      4.7G  139M  4.6G   3% /usr/sap/SMD/SMDA90

itsusravmdd05.jnj.com:/vol/itsusravmdd05_btb/btb_fsrf_sapmnt_d82

                       25G     0   25G   0% /sapmnt/D82

I dont understand why installer is trying to create a softlink between

/sapmnt/D82 and /usr/sap/D82

Please share any information you guys are having.

Thanks & Regards,

Tejas

Good day

We are busy implementing SAP Vendor Invoice Management system and i have been task to implement the VIM Approval Portal.

We would like to use our current SAP NetWeaver 7.3 Portal to deploy the VIM components. I have gone through the OpenText Vendor Invoice Management for SAP Solution Installation Guide but i can’t make out exactly what i need to do. I manage to copy the IM_APPROVAL_PORTAL7_5SP3.sca file onto our portal and ready to deploy/install using SUM.

But before i start, i would appreciate if anyone can outline the steps i need to take. maybe they will help me understand the Installation Guide better.

please let me know should you require more information.

thanks in advance

regards

Steven

Hi, we in the process of of upgrading our PI system from NW 7.02 to NW 7.4. The application runs on HP-UX, Oracle database. We are now is the execution phase and the AS Java stack is stuck in the step Execute Application Migration. its complaining about sap.com/com.sap.xi.repository(CSN component BC-XI-IBD) and sap.com/com.sap.xi.directory(CSN component BC-XI-IBC)

below is the complete logfile: EXECUTE-APPLICATION-MIGRATION_03.LOG

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/oracle/GRD/SUM/SUM/sdt/log/SWITCH/EXECUTE-APPLICATION-MIGRATION_03.LOG]/-->

<!--PATTERN[EXECUTE-APPLICATION-MIGRATION_03.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Mar 16, 2016 2:47:30 PM [Info  ]: Stopping instance number 0 on host grcdev with timeout of 10800 seconds.

Mar 16, 2016 2:47:30 PM [Info  ]: Process ID 975, name sapcontrol has been started.

Mar 16, 2016 2:47:30 PM [Info  ]:   Command line: /usr/sap/GRD/DVEBMGS00/exe/sapcontrol -nr 0 -host grcdev -user grdadm <SecureField> -function GetProcessList

Mar 16, 2016 2:47:30 PM [Info  ]:   Standard out: /oracle/GRD/SUM/SUM/sdt/tmp/SAPCONTROL_GETPROCESSLIST_0_32.OUT

Mar 16, 2016 2:47:30 PM [Info  ]: Process ID 975 has been started.

Mar 16, 2016 2:47:30 PM [Info  ]: Waiting for process ID 975, name sapcontrol to finish.

Mar 16, 2016 2:47:30 PM [Info  ]: Process ID 975, name sapcontrol has been finished, exit code 3.

Mar 16, 2016 2:47:30 PM [Info  ]: Stopping instance number 0 on host grcdev with timeout of 10800 seconds.

Mar 16, 2016 2:47:30 PM [Info  ]: Process ID 976, name sapcontrol has been started.

Mar 16, 2016 2:47:30 PM [Info  ]:   Command line: /usr/sap/GRD/DVEBMGS00/exe/sapcontrol -nr 0 -host grcdev -user grdadm <SecureField> -function Stop 0

Mar 16, 2016 2:47:30 PM [Info  ]:   Standard out: /oracle/GRD/SUM/SUM/sdt/tmp/SAPCONTROL_STOP_0_04.OUT

Mar 16, 2016 2:47:30 PM [Info  ]: Process ID 976 has been started.

Mar 16, 2016 2:47:30 PM [Info  ]: Waiting for process ID 976, name sapcontrol to finish.

Mar 16, 2016 2:47:31 PM [Info  ]: Process ID 976, name sapcontrol has been finished, exit code 0.

Mar 16, 2016 2:47:31 PM [Info  ]: Sent the stop command to instance number 0 on host grcdev with timeout of 10800 seconds.

Mar 16, 2016 2:47:31 PM [Info  ]: Process ID 977, name sapcontrol has been started.

Mar 16, 2016 2:47:31 PM [Info  ]:   Command line: /usr/sap/GRD/DVEBMGS00/exe/sapcontrol -nr 0 -host grcdev -user grdadm <SecureField> -function WaitforStopped 10800 5

Mar 16, 2016 2:47:31 PM [Info  ]:   Standard out: /oracle/GRD/SUM/SUM/sdt/tmp/SAPCONTROL_WAITFORSTOPPED_0_04.OUT

Mar 16, 2016 2:47:31 PM [Info  ]: Process ID 977 has been started.

Mar 16, 2016 2:47:31 PM [Info  ]: Waiting for process ID 977, name sapcontrol to finish.

Mar 16, 2016 2:48:16 PM [Info  ]: Process ID 977, name sapcontrol has been finished, exit code 0.

Mar 16, 2016 2:48:16 PM [Info  ]: The instance with number 0 on host grcdev was stopped after 45 seconds.

Mar 16, 2016 2:48:16 PM [Info  ]: Starting instance number 0 on host grcdev with timeout of 10755 seconds.

Mar 16, 2016 2:48:16 PM [Info  ]: Process ID 978, name sapcontrol has been started.

Mar 16, 2016 2:48:16 PM [Info  ]:   Command line: /usr/sap/GRD/DVEBMGS00/exe/sapcontrol -nr 0 -host grcdev -user grdadm <SecureField> -function GetProcessList

Mar 16, 2016 2:48:16 PM [Info  ]:   Standard out: /oracle/GRD/SUM/SUM/sdt/tmp/SAPCONTROL_GETPROCESSLIST_0_33.OUT

Mar 16, 2016 2:48:16 PM [Info  ]: Process ID 978 has been started.

Mar 16, 2016 2:48:16 PM [Info  ]: Waiting for process ID 978, name sapcontrol to finish.

Mar 16, 2016 2:48:16 PM [Info  ]: Process ID 978, name sapcontrol has been finished, exit code 4.

Mar 16, 2016 2:48:16 PM [Info  ]: Starting instance number 0 on host grcdev with timeout of 10755 seconds.

Mar 16, 2016 2:48:16 PM [Info  ]: Triggering an instance start by sapcontrol...

Mar 16, 2016 2:48:16 PM [Info  ]: Process ID 979, name sapcontrol has been started.

Mar 16, 2016 2:48:16 PM [Info  ]:   Command line: /usr/sap/GRD/DVEBMGS00/exe/sapcontrol -nr 0 -host grcdev -user grdadm <SecureField> -function Start

Mar 16, 2016 2:48:16 PM [Info  ]:   Standard out: /oracle/GRD/SUM/SUM/sdt/tmp/SAPCONTROL_START_0_12.OUT

Mar 16, 2016 2:48:16 PM [Info  ]: Process ID 979 has been started.

Mar 16, 2016 2:48:16 PM [Info  ]: Waiting for process ID 979, name sapcontrol to finish.

Mar 16, 2016 2:48:17 PM [Info  ]: Process ID 979, name sapcontrol has been finished, exit code 0.

Mar 16, 2016 2:48:17 PM [Info  ]: An instance start was triggered.

Mar 16, 2016 2:48:17 PM [Info  ]: Sent the start command to instance number 0 on host grcdev with timeout of 10755 seconds.

Mar 16, 2016 2:48:17 PM [Info  ]: Process ID 980, name sapcontrol has been started.

Mar 16, 2016 2:48:17 PM [Info  ]:   Command line: /usr/sap/GRD/DVEBMGS00/exe/sapcontrol -nr 0 -host grcdev -user grdadm <SecureField> -function WaitforStarted 10755 5

Mar 16, 2016 2:48:17 PM [Info  ]:   Standard out: /oracle/GRD/SUM/SUM/sdt/tmp/SAPCONTROL_WAITFORSTARTED_0_12.OUT

Mar 16, 2016 2:48:17 PM [Info  ]: Process ID 980 has been started.

Mar 16, 2016 2:48:17 PM [Info  ]: Waiting for process ID 980, name sapcontrol to finish.

Mar 16, 2016 3:04:34 PM [Info  ]: Process ID 980, name sapcontrol has been finished, exit code 0.

Mar 16, 2016 3:04:34 PM [Info  ]: The instance with number 0 on host grcdev was started after 977 seconds.

Mar 16, 2016 3:04:36 PM [Info  ]: Delete file /oracle/GRD/SUM/SUM/sdt/log/SWITCH/MigrationModulesReport.xml.

Mar 16, 2016 3:04:36 PM [Info  ]: Generating HTML evaluation file /oracle/GRD/SUM/SUM/sdt/log/SWITCH/MigrationModulesReport_03.html...

Mar 16, 2016 3:04:36 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Error while executing migration of the following application(s) sap.com/com.sap.xi.repository(CSN component BC-XI-IBD), sap.com/com.sap.xi.directory(CSN component BC-XI-IBC). <html>The following <b><a href="http://service.sap.com/~

form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1378048">SAP Note 1378048</a></b>  may contain solution for the problem.

.

i tried checking SAP note 1378048, but it was not very useful.

anyone who been stuck here before and have a solution. please help.....

thanks in advance

regards

Steven