Hi Team,

I have installing the add on onapsis on portal 740.

Got below error:

\Incorrect credentials error.

I have corrected the passwords on host, restarted SUM.  still the issue.

can you help here. I am debugging further.

Hello all!

we're preparing our nw systems for unicode conversion. One of these steps are running UCCHECK for checking that customer modified Sap programs and z-programs are abap 6.10 compliant.

Our systems have never been any lower than NW 7.0 version, do you guys know if we can skip this step?

Thanks!

m.

Hi Guys,

What is the exact difference between SAP Netweaver and SAP Netweaver AS ABAP.

If anybody wants to create ODATA services through Netweaver Gateway then what should be installed Netweaver of Netweaver AS ABAP.

Thanks

Hi,

     I am trying to install ABAP application server with netweaver gateway trial version. While installing some jobs were failed.

java version "1.8.0_51"

Java(TM) SE Runtime Environment (build 1.8.0_51-b16)

Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

Import Monitor jobs: running 1, waiting 5, completed 28, failed 0, total 34.

Import Monitor jobs: running 2, waiting 4, completed 28, failed 0, total 34.

Import Monitor jobs: running 3, waiting 3, completed 28, failed 0, total 34.

Loading of 'SAPSLOAD' import package: ERROR

Import Monitor jobs: running 2, waiting 3, completed 28, failed 1, total 34.

Loading of 'D010INC' import package: ERROR

Import Monitor jobs: running 1, waiting 3, completed 28, failed 2, total 34.

Loading of 'D010TAB' import package: ERROR

Import Monitor jobs: running 0, waiting 3, completed 28, failed 3, total 34.

Import Monitor jobs: running 1, waiting 2, completed 28, failed 3, total 34.

Import Monitor jobs: running 2, waiting 1, completed 28, failed 3, total 34.

Loading of 'SAPSLEXC' import package: ERROR

Import Monitor jobs: running 1, waiting 1, completed 28, failed 4, total 34.

Loading of 'WBCROSSGT' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 28, failed 5, total 34.

How to resolve these failed jobs? I think because of these errors I am getting another error saying "Migration monitor exits error 103".

Could any body suggest me how to resolve those errors.

Thanks and Regards,

Teja.

Hi Admins,

What are well know issues of SAP Installation on Windows or UNIX system.

Regards,

Ratnakar B

Hi Admins,

What are the types of installation of SAP system and what are the consequences of these approaches.

Regards,

Ratnakar B

Hello together,

we started a System measurement in our Landscape but  some JOBs of the program  RSUVM007 canceled . So we can't download the results of the measurement. I can't find any dumps our entries in the syslog.  Only in SM37 :  Job canceled

The error is:

Our release is SAP NW 7.40 SP 9

I've checked the SAPNOTE:  1625363 - Job RSUVM007 canceled with databaseerror

but this Note is always to release 7.31

Anyone an idea to fix this Problem?

Best regards,

Mathias

Dear Experts,

I have a little weird situation here and I'd kindly like to ask for your help and advice.

There is a NetWeaver 7.4 system at SPS10, which suprisingly is dual stack!

Now I need to apply SPS12 to it and the result is weird:

While on the ABAP stack everything seems to be OK, there is a strange situation

with Java. Just 5 components are showing version 7.40.12:

All the other components, down to the bottom are 7.40.11. Now the question is,

whether this is normal behaviour and MOPZ is checking compatibility and only

SP11 of those components is released and compatible with SPS12 ABAP, or

there is something wrong with the Solution Manager and MOPZ is calculating

nonsense ?

I also did an experimental MOPZ transaction to SPS14 and it calculates those

5 listed components as SPS13 and all the others as SPS12.

The only problem I could think of, was the CIM content and it's pretty old, from

april 2015, but I am not allowed to update it (yet).

Please kindly advise on how to proceed!

Just in case, I downloaded SP12 for all the other components and I am ready

to patch the system once again, but, as I said, my question is, whether this is

really needed and SPS12 really means having all the components at SP12, or

MOPZ knows what it's doing and if it calculates SP11, then this has been tested

by SAP and is guaranteed to run without issues.

Many thanks in advance!

Hi Admins ,

How do i become a quick learner of SAP BASIS and Net weaver. What are the best ways to learn and practice the SAP administration.

Regards,

Ratnakar B

Hi Admins,

I am installing SAP ECC6 on my development machine, I come to know across the several points in my mind i.e. why I am following these steps and how it could be used by the application server instance.

1. How port numbers are used by the application.

2. How the JAVA_HOME path environment variable used by the application.

3. How the size of virtual memory to be defined and how it will be used by the application or other services (DVEMG..etc)

4. Why do I entering the Host name in host file, if I does not enter what would be the impact.

5. Why these installation ports 21212 and 21213 are kept open.

6. 3200, 3300, 3600, 4700 are kept open (DVEBMGS uses these ports) can I use any other ports here if the above reserved for other things.

Please provide your available inputs on the same.

Thanks in advance,

Ratnakar B

Hi ,                                                                                                                                                                                                                                            What are the error code standards which is followed by SAP.

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 there,

I recently changed the name and domain of a PI 7.0 server under windows server 2003 and sql 2005.

The problem is that I from time to time there is a communication call between the new server and the old server. Both are still on line.

How do I know?  I am running netstat command in new server to check.

Command:

netstat -5 -an | findstr "old_IP_address"

Result:

TCP "new_IP_address":"any_port" "old_IP_address":"139" TIME_WAIT

TCP "new_IP_address":"any_port" "old_IP_address":"445" TIME_WAIT

The different results are shown at different time.

I need to identify where is this configuration set pointing to the old_server_name.

And of course how to stop it.

This usually happens when I start SAP from SAP Management Console.

Thanks for your help.

Luis.

Hi everyone,

I'm new in SAP. I wanted to install SAP Application Server ABAP Trial Version 7.02. Installation is stuck in "Import ABAP" phase as the following photo. I'm still waiting for next phase.

My system properties:

According to import_monitor.log :

INFO: 2016-06-15 00:37:02 -> First line

Import Monitor is started.

....

TRACE: 2016-06-15 01:48:28 com.sap.inst.migmon.LoadTask processPackage -> Last line

Loading of 'D010INC' import package into database:

If you help me, I'll be grateful.

Thanks in advance,

Tugce

Hello,

What type of SAP NetWeaver (Portal, R/3 or ECC) license will be required for the architecture of the application listed below

1. Application will be hosted on an internet facing Portal and accessed by the following user types
   • N number of anonymous users
   • Users created in user store (LDAP or MS ADS) linked to the SAP Portal i.e. users that don't have a SAP ECC login)
2. Application will used ABAP Dictionary tables (Standard or Custom Tables) as the data store
3. Application's business logic to perform CRUD operations on the ABAP Dictionary tables will be contained in remote enabled ABAP function modules
4. Application related function modules will have corresponding OData services created in SAP Gateway
5. Application related OData services will be consumed in SAPUI5 based user interface
6. Application's SAPUI5 projects will be imported and activated on ABAP stack

Thank you

Regards

Abhishek

Hi,

For our standalone Java system (EP), we use a third party monitoring tool.

I have activated from Visual Admniistrator the monitoring leaf:

Services->Monitoring---> /Kernel/Licensing Manager/License Validity Period/J2EE-Engine_ORA

for both server and dispatcher.

However, after every system restart this gets deactivated and I get a ticket from the monitoring tool that the license expired. I have a choice of deactivating this monitoring or make the activated changes saved and not get deactivated.

Is there a way to keep this leaf green permanently?

I copied a local wdp project into the DC (through src folder). I could build the new DC successfully but when I try to deploy the same I get the following error:

Exception while trying to deploy

[ERROR CODE DPL.DCAPI.1027] DeploymentException.

Reason: An error occurred while deploying the deployment item 'demo.sap.com_migratelocal'.; nested exception is:

     com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of demo.sap.com_migratelocal. Cannot deploy it.

Can somebody please let me know where is the problem?

I am using NetWeaver IDE 7.1 CE.

NB : Points will be awarded promptly

Best Regards

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

17.06.2016: SP Stack Kernel 745 PL 200 released

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.

16.06.2016: NW 7.4 upgrade issues on Windows

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.

15.06.2016: Kernel 742 PL 414 is not a SP Stack Kernel

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.

14.06.2016: SP Stack Kernel 742 PL 401 released

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.

07.06.2016: SP Stack Kernel 721 PL 700 released

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.

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. 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.

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.

Hi Team, I need to check the DB02, what I need to check and what are the details required. Regards, Ankit

Hello Experts,

I have installed a new system via system copy on hana DB. THis is a sandbox system installed on linux plateform. TMS has been set up and is consistent.

The follwoing is the requirement. Anyone has any idea how to implement this.

1) TR's transported to PRD system will have to be auto transported to this new sandbox system as well.

2) I have to cover all transports being moved to PROD from the point in time backup has been taken for the new sandbox system to the sandbox system.

Regards

Vishwanath B