Dear Freinds,
When I check into the st06 during our pic hours the idle time is very low.
Even I checked the top 40 CPU processes, the users are as below
<sid>adm
ora<sid>
ora<sid>
ora<sid>
<sid>adm
daaadm
<sid>adm
root
<sid>adm
orapnc
sapadm
root
root
ora<sid>
ora<sid>
root
root
root
Can anyone tell how to analyze further to increase the CPU idle time of the system.
Regards,
Hi All,
We are trying to redirect the user to a different URL when SAP ECC AS is down.
User is interacting with the application through a simple HTML Based web application(No Enterprise Portal/WDA).
After doing a lot of research, i found out that we should configure the Web Dispatcher as Reverse Proxy to achieve this. But, i am only getting information on these in context of SAP Enterprise Portal.
Kindly, share some resources or suggestions in case of only SAP NW ECC and External Web Application related landscapes.
Thanks
Sahil
Hi I have Installed new ms-office 2016 and facing error in transaction smartforms "compile error in hidden module" please find screen shot attached.
Dear All,
We have the below scenario .
Webdispatcher (WEP) > EP > Webdispatcher (WSR) > SRM .
1. Both the webdispatchers are installed as HA along with the SCS and ASCS server .
2. We would like to configure the End to end scenario . Basically we want the flow to use the same app server at the backend hence we are using the sticy mask parameter as mentioned in note (255.255.240.0) at both the WD's and ICM as PROT = ROUTER .
3 . WD at the EP is not of primary important but the one in between EP and SRM as when using the message server the request was distributed to the different app sever when coming back and forth and its not serving our purpose .
4 Now when I use the https://WDhost:WDport (SRM) I am getting the certificate error warning which arises from one of the app server . I did exported ABAP certificate from SRM and imported the same into WSR . Both the certs are CA signed
Am I missing something . Please help .
Regards
Satish
Hi,
We are trying to build ECP (Enhanced Client or Proxy) authentication to SAP Netweaver(7.31 support pack18) application server.
We notice that there is an extra redirect which breaks the ECP authentication flow. Is there any specific ECP Url, that should be used?
Looking for help, if anyone has implemented ECP authentication to SAP Netweaver, and if so, how did you get past this issue.
On further debug, we are getting the following error:
2016-06-18 20:30:54,797 - ERROR [org.opensaml.saml.common.binding.security.impl.ReceivedEndpointSecurityHandler:200] - Message Handler: SAML message intended destination endpoint 'https://xyz.com/idp/profile/SAML2/POST/SSO' did not match the recipient endpoint 'https://xyz.com/idp/profile/SAML2/SOAP/ECP'
Thanks,
Hi Experts,
Anybody explain the functionalities of tcode sm13 and sm14.
Thanks &Regards,
Ram Pulagam.
Dear Experts,
This is regarding below two errors in log viewer belonging to component BC-XI-IBD
1) No hostname and Http port defined in Exchange profile sld.<SID>.<hostname>
2) Creating CIM client failed. Parameter password is empty.
SAP Process Orchestration system 7.40 on Oracle 11
This system was recently upgraded to 7.40 and we saw the first error mentioned above "No hostname and http port defined...." in D, Q and P system.
Hence we applied note 2198240, in which it says to change property of usage_type setting from XPI to CE
After we applied the change throughout the landscape the error "No hostname and http port..." were NOT occurring in systems
But we found strange thing ONLY in production system, we started receiving the second error "Creating CIM client failed. Parameter password is empty"
For the second error we found note 1638667, which says to change usage_type setting property from CE to XPI.
We want to get rid of this reoccurring errors everday.
Kindly let me know your expert views.
regards,
Trever
Hi All,
I am facing with SECUDIR path identification by secondary servers of same SID.
As a part of SNC implementation for RFC connections, I am enabling SNC with activation of sap cryptolibrary certificate from STRUST.
System is Netweaver 7.4.
Steps:
1. I implamented parameters reqiored for SNC communication except snc/enable=0.
2. Restarted the system and the created SNC cryptolib certificate from STRUST.Certificate got created in OS level at /usr/sap//sec in promary & secondary servers.
3. I enabled SNC using snc/enable =1
4. I faced an issue that my primary server was trying to read certificates from HOME i.e. /global/adm, so I set parameter SETENV03 = SECUDIR=$(DIR_INSTANCE)/sec in primary instance. I restarted the instance & it worked.
5. But for secondary instance, even if I have set profile parameter SETENV for SECUDIR, it still looks for certificate at home directory.
Please see logs below:
case1- SECUDIR is taken correctly in one instance
SncInit(): Initializing Secure Network Communication (SNC) N IBM RS/6000 with AIX (mt,ascii,SAP_UC/size_t/void* = 16/64/64) N UserId="adm" (1304), envvar USER="adm" N SncInit(): found snc/data_protection/max=3, using 3 (Privacy Level) N SncInit(): found snc/data_protection/min=2, using 2 (Integrity Level) N SncInit(): found snc/data_protection/use=3, using 3 (Privacy Level) N SncInit(): found snc/gssapi_lib=/sapmnt//exe/libsapcrypto.so N File "/sapmnt//exe/libsapcrypto.so" dynamically loaded as GSS-API v2 library. N N Sun Jun 19 06:36:09 2016 N SECUDIR="/usr/sap//DVEBMGS05/sec" (from $SECUDIR) N The internal Adapter for the loaded GSS-API mechanism identifies as: N Internal SNC-Adapter (Rev 1.1) to CommonCryptoLib N Product Version = CommonCryptoLib (SAPCRYPTOLIB) Version 8.4.43 pl40 (Oct 8 2015) MT-safe N SncInit(): found snc/identity/as=p:CN=SAP/KerberosN SncInit(): Accepting Credentials available, lifetime=Indefinite N SncInit(): Initiating Credentials available, lifetime=Indefinite M ***LOG R1Q=> p:CN=SAP/Kerberos [thxxsnc.c 301] M SNC (Secure Network Communication) enabled
case 2-SECUDIR is taking from HOME for this instance
SncInit(): Initializing Secure Network Communication (SNC) N IBM RS/6000 with AIX (mt,ascii,SAP_UC/size_t/void* = 16/64/64) N UserId="adm" (1304), envvar USER="adm" N SncInit(): found snc/data_protection/max=3, using 3 (Privacy Level) N SncInit(): found snc/data_protection/min=2, using 2 (Integrity Level) N SncInit(): found snc/data_protection/use=3, using 3 (Privacy Level) N SncInit(): found snc/gssapi_lib=/sapmnt//exe/libsapcrypto.so N N Sun Jun 19 07:16:53 2016 N File "/sapmnt//exe/libsapcrypto.so" dynamically loaded as GSS-API v2 library. N SECUDIR="/home/adm/sec" (from HOME) N The internal Adapter for the loaded GSS-API mechanism identifies as: N Internal SNC-Adapter (Rev 1.1) to CommonCryptoLib N Product Version = CommonCryptoLib (SAPCRYPTOLIB) Version 8.4.43 pl40 (Oct 8 2015) MT-safe N SncInit(): found snc/identity/as=p:CN=SAP/KerberosN SncInit(): Accepting Credentials available, lifetime=Indefinite N SncInit(): Initiating Credentials available, lifetime=Indefinite M ***LOG R1Q=> p:CN=SAP/Kerberos [thxxsnc.c 301] M SNC (Secure Network Communication) enabled Thanks, Devendra
Dear All,
When we are testing SAP OSS RFC it is giving below error.
recently we have renewed the certificate of the sap router.
Every entries OSS1 and RFC connection are fine and router is running fine.
Please help me to solve this.
Regards,
Jeyaganesh.
Dear Experts,
We have configured terminating SSL on SAP webdispatcher. It is working fine. We are able to acces portal through webdispatcher host name and port but when the users launch the webdynpro iviews thats connects to the backend ABAP system we get a IE security warning on each iview. Backend ERP and SRM systems are not configured for HTTPS.
I would like to know is ther any way to avoid this or we have to configure SSL on backend application systems as well ?
Please advice
Regards,
Abdul
Hi Experts,
I am new for SAP ,while trying update records update process taking too much for updating.
can any one help how to trouble shoot this problem with brief explanation.
Thnks&Regards,
Ram pulagam
Hi Experts,
I am using a REST Web Service( Created in SICF ) to be consumed directly(using the URI) via external applications. We have Load Balancing configured in our landscape.
In the table RZLLITAB, the message server group is configured and is assigned to respective app servers.
Currently, we don't have a Web Dispatcher configured in our system, and i wanted to use the Message Server as a Load Balancer.
Since, REST Services are stateless, do i really need to install the Web Dispatcher in this case.?
Thanks
Sahil
Dear all,
we are currently preparing the upgrade of our AS JAVA production system and are facing a small challenge there:
We want to perform the upgrade in parallel with the ABAP part, UME of AS JAVA is stored in ABAP system. Therefore i am not able to log on AS JAVA part during ABAP downtime (because UME is not accessible). We dont want to change the UME configuration due to risk of unexpected issues.
1. Is there any kind of emergency user available for AS JAVA part (which is independant of UME) ? Is this user able to perform an upgrade or am i forced to use "j2ee_admin" ?
2. Is there any other possibility to perform the upgrade without available UME ?
Many thanks in advance !
Hello Experts,
we have newly created a project which dealing a new message flow from SAP PI to SAP HCM system.
HCM system receiving inbound messages which are not processing automatically. all the messages are reaching HCM system and showing as ready status. we are manually pushing messages when ever flow happening.
we would like to flow happen automatically instead of manually trigger.
Kindly provide your suggestions what are area need to check to fix issue.
Regards
Prabhakaran
SAP BASIS consultant
Dear All,
When we clicking sap gui login it will taking too much time.I think,It will taking more then 15mins.How we solve this problem.
Thanks & Regards,
Jeyaganesh.
In this document you will find the latest information about the SAP kernel such as
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".
SP stack kernel 745 PL #201 is now available on SAP Support Portal.
It fixes two important regressions, which affected all previous Kernel 745 versions lower than PL 211 (excluding 201). Details are outlined in SAP Note 2340627.
Information on known issues in the stack kernel 745 PL #201 can be found in SAP Note 2341597. This note will be updated on a regular basis.
SP stack kernel 745 PL #200 is now available on SAP Support Portal.
It contains various improvements and enhancements that are outlined in detail in SAP Note 2299971.
Information on known issues in the stack kernel 745 PL #200 can be found in SAP Note 2317428. This note will be updated on a regular basis.
1. when common crypto lib starting 8.4.31 till (including) 8.4.34 is in place, upgrade runs into error. For details see item 4 in SAP Note 2200230.
2. On Windows 2008 (w/o R2) on Haswell CPU the SAP Kernel 745 can crash. For details see SAP Note 2330836.
By mistake SAPEXE and SAPEXEDB archives have been available for Kernel 742 PL 414 on the support portal for a short time. As PL 414 is supposed to be only a regular patch (and not a stack kernel for which SAPEXE, SAPEXEDB will be published), these packages have been revoked meanwhile and replaced by the corresponding DW packages. Sorry for any inconvenience this may have caused.
SP stack kernel 742 PL #401 is now available on SAP Support Portal. It fixes several known issues with the previous version PL 400. For details see SAP Note 2324879.
Information on known issues in the stack kernel 742 PL #401 can be found in SAP Note 2324928. This note will be updated on a regular basis.
SP stack kernel 721 PL #700 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2316471.
Information on known issues in the stack kernel 721 PL #700 can be found in SAP Note 2316429. This note will be updated on a regular basis.
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. The correction causing the issue has been retracted. A new version of Kernel 722 PL 118 with compile time on May 19th as well as Kernel 742 PL 413 has been published.
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.
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.
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.
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.
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.
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.
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
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.
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
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.
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.
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.
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.
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.
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.
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:
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.
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.
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.
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:
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.
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.
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.
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.
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.
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.
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:
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.
Hi experts,
I get the following on executing r3trans:
2EETW169 no connect possible: "DBMS = SYBASE --- "
So it seems like DBMS is not set correctly, right?
How can I set the SID there?
