Hello All,

Please direct me if there are any specific guidelines to migrate batch job log files from one server to another.

Two servers are different Operating systems, we have performed a OS/DB migration just wanted to check the possibility of batch job log files stored at OS level.

I have identified few batch jobs which are in both source and target servers physically copied the job log files in the respective directory, still in the target am not able to view those batch job log files.

Please throw some light here

Hello,

I would like to known some other information about "Certificate Expiration Notification " http://help.sap.com/saphelp_nw70ehp1/helpdata/en/d4/5b1140d72dc442e10000000a1550b0/content.htm

Do you known how can I activate this in CCMS. Under DISP ->Services a have not "Certificate Expiration Notification " in RY20 ...:-(

Thanks a lot.

Best regards

Capek Martin

I am looking to configure CCMS alert for certificate expire. Please help me to identify the MTE for certificate expiry for ABAP.

Option 1: SSFALRTEXP is intended for certificates that expire within the AutoABAP concept, that is, this report is automatically processed each day from about 3 o'clock; A prerequisite for this is that the AutoABAP mechanism has not been deactivated. This report only generates the aforementioned warnings. But warning should be shown in CCMS. So which MTE class isolates certificate expiry ?

Option 2 : SSF_ALERT_CERTEXPIRE is a report with an online and background list output that can be scheduled as a replacement for the SSFALRTEXP report (as a daily background job). If you are using this report as a replacement for the SSFALRTEXP report, the start time must be before 3 o'clock. If this is not possible. This report only generates the aforementioned warnings. But warning should be shown in CCMS. So which MTE class isolates certificate expiry ?

Regards

Manjunath

Hi

I am installing solman 7.1 SR1, and in the 26th step Start Instance it gives following error -

An error occurred while processing option SAP Solution Manager 7.1 Support Release 1 > SAP Systems > MaxDB > Central System > Central System( Last error reported by the step: ABAP processes of instance XXX/DVEBMGS00 [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up.). You can now:

• Choose Retry to repeat the current step.
• Choose Log Files to get more information about the error.
• Stop the option and continue with it later.

Log files are written to C:\Program Files/sapinst_instdir/SOLMAN71/SYSTEM/ADA/CENTRAL/AS.    

While investigating through logs I found below mentioned details -

From sapstartsrv -

WIN-Q8BOMFF2BOJ\Administrator is starting SAP System at 2014/02/04  8:20:04

SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [sapwinha.cpp, line 213]

SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 920]

From dev_ms -

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

trc file: "dev_ms", trc level: 1, release: "720"

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

 

 

[Thr 5060] Tue Feb 04 08:20:04 2014

[Thr 5060] ms/http_max_clients = 500 -> 500

[Thr 5060] MsSSetTrcLog: trc logging active, max size = 52428800 bytes

systemid   562 (PC with Windows NT)

relno      7200

patchlevel 0

patchno    101

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

pid        968

 

 

[Thr 5060] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 968) [msxxserv.c   2278]

[Thr 5060] load acl file = D:\usr\sap\XXX\SYS\global\ms_acl_info.DAT

[Thr 5060] MsGetOwnIpAddr: my host addresses are :

[Thr 5060]   1 : [10.203.136.14] WIN-Q8BOMFF2BOJ.ec2.internal (HOSTNAME)

[Thr 5060]   2 : [127.0.0.1] WIN-Q8BOMFF2BOJ (LOCALHOST)

[Thr 5060] MsHttpInit: full qualified hostname = WIN-Q8BOMFF2BOJ

[Thr 5060] HTTP logging is switch off

[Thr 5060] set HTTP state to LISTEN

[Thr 5060] *** HTTP port 8101 state LISTEN ***

[Thr 5060] *** I listen to internal port 3901 (3901) ***

[Thr 5060] *** HTTP port 8101 state LISTEN ***

[Thr 5060] CUSTOMER KEY: >B1166352916<

[Thr 5060] build version=720.2011.10.26

From SAPinst -

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

msg_server.EXE, MessageServer, GREEN, Running, 2014 02 04 08:47:07, 0:10:09, 2464

disp+work.EXE, Dispatcher, GRAY, Stopped, 2014 02 04 08:47:07, 0:00:06, -1

igswd.EXE, IGS Watchdog, GREEN, Running, 2014 02 04 08:47:07, 0:10:09, 4212

 

 

ERROR 2014-02-04 08:57:16.966

CJS-30149  ABAP processes of instance SM1/DVEBMGS00 [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up.

 

 

ERROR 2014-02-04 08:57:17.153

FCO-00011  The step start with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CI_Instance|ind|ind|ind|ind|ci|0|NW_CI_Instance_Start|ind|ind|ind|ind|start|0|start was executed with status ERROR ( Last error reported by the step: ABAP processes of instance XXX/DVEBMGS00 [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up.).

 

 

INFO 2014-02-04 08:57:17.543

Creating file C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\ADA\CENTRAL\AS\__instana_tmp.xml.

I fail to understand the reason for disp+work.exe to stop, need your suggestions/pointers to proceed ahead.

Thanks & Regards

Jeetendra

Hi

We have installed a SAP Netweaver 2004s system on AIX box.

We have installed the J2EE + ABAP Engine.

While creating the user from the portal we get the following error:

#1.5#1E656000400200710000008E000890AC00042D27C0FEBD4D#1175548671736#com.sap.security.core.persistence.datasource.imp.R3PersistenceBase#sap.com/tc_wddispwda#com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.getPrivateIDPart()#J2EE_ADMIN#25759##punlparidm06.bmc_E60_602784150#J2EE_ADMIN#81b977c0e15f11dbc9551e6560004002#SAPEngine_Application_Thread[impl:3]_15##0#0#Error#1#/System/Security/Usermanagement#Java#An exception was thrown in the UME/ABAP user management connector. Message: .##An exception was thrown in the UME/ABAP user management connector. Message: .

[EXCEPTION]

#2#Cannot create user QM?MVZ_{IMONY in ABAP backend system. Reason: The UME/ABAP adapter has recognized that the communication user is only assigned to the read-only role SAP_BC_JSF_COMMUNICATION_RO (or no role at all) in the backend system. Therefore UME was set to read-only mode for users from the backend system. See SAP Note 908911 for further information.#com.sap.security.core.persistence.datasource.PersistenceException: Cannot create user QM?MVZ}IMONY in ABAP backend system. Reason: The UME/ABAP adapter has recognized that the communication user is only assigned to the read-only role SAP_BC_JSF_COMMUNICATION_RO (or no role at all) in the backend system. Therefore UME was set to read-only mode for users from the backend system. See SAP Note 908911 for further information.

        at com.sap.security.core.persistence.datasource.imp.R3Persistence.getPrivateIDPart(R3Persistence.java:2521)

        at com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.bindNewPrincipalDatabag(DataSourceBaseImplementation.java:340)

        at com.sap.security.core.persistence.datasource.imp.R3Persistence$Transaction.bindNewPrincipalDatabag(R3Persistence.java:8727)

        at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.bindNewPrincipalDatabag(PrincipalDatabagFactoryInstance.java:4640)

        at com.sap.security.core.persistence.imp.PrincipalDatabag.getIDParts(PrincipalDatabag.java:1034)

What can be the problem here.

AM i missing any step.

Best Regards

Manoj

Hi everyone,

we try to configure Single Sign-On for the users with SAP GUI for Windows.

The ABAP application server has been configured, and I think the config is OK, since in the log file I see:

N  SncInit(): Initializing Secure Network Communication (SNC)

N        AMD/Intel x86_64 with Linux (st,ascii,SAP_UC/size_t/void* = 16/64/64)

N        UserId="sidadm" (1002), envvar USER="sidadm"

N  SncInit():   found snc/data_protection/max=3, using 3 (Privacy Level)

N  SncInit():   found snc/data_protection/min=1, using 1 (Authentication Level)

N  SncInit():   found snc/data_protection/use=3, using 3 (Privacy Level)

N  SncInit(): found  snc/gssapi_lib=/usr/lib64/snckrb5.so

N    File "/usr/lib64/snckrb5.so" dynamically loaded as external SNC-Adapter.

N    The SNC-Adapter identifies as:

N    External SNC-Adapter (Rev 1.0) to Kerberos 5/GSS-API v2

N  SncInit():   found snc/identity/as=p/krb5:SAPServiceSID/sapsid.intranet.ufz.de@INTRANET.UFZ.DE

N  SncInit(): Accepting  Credentials available, lifetime=Indefinite

N  SncInit(): Initiating Credentials available, lifetime=07h 37m 16s

So, I think there is no error on the server side. But whenever a user tries to log in, he/she gets an error in SAP GUI:

---snip---

GSS-API(maj): Miscellaneous Failure

GSS-API(min): SSPI u2u-problem: please add Service principal for targe

target="p:myuser@INTRANET.UFZ.DE"

Error in SNC

---pins---

What's wrong here? Do I have to execute the "setspn" command for each user? And how would this look like? On the command line, the output of "setspn -l myuser" is empty, "setspn -l myuser@INTRANET.UFZ.DE" results in an error.

The entry in the Network tab in the SAP GUI reads either "p/krb5:myuser@INTRANET.UFZ.DE" or "p:myuser@INTRANET.UFZ.DE" or simply "P:myuser", the error remains always the same.

Can someone please help me?

Werner

Hi,

We're doing SAP DB Migration from MaxDB to MSSQL in my environment. We're in the phase of taking source system export, during the export its checking SAP release (getSAPReleaseFromDB) its throwing timeout error on getSAPReleaseFromDB.log. We're able to get xuser list and also able to login using these users control,superdba and sapsid. We searched a lot for a note to resolve this issue but didn't get any.

SWPM trying to execute this command "sqlcli -U DEFAULT -Q "SELECT "RELEASE","EXTRELEASE" FROM "SAPSID"."CVERS" WHERE COMPONENT='SAP_BASIS'" and output throws a timeout error.

Few logs has been provided below.

Did anyone faced this kind of issue means, please let us know the resolution.

Logs:

GetSAPReleaseFromDB.log

* -10709: Connection failed (RTE:[3] connect timeout)

sapinst.log

INFO 2015-07-06 00:19:02. 253 (hostname\sidadm)

Execution of the command "sqlcli -U DEFAULT -Q "SELECT "RELEASE","EXTRELEASE" FROM "SAPSID"."CVERS" WHERE COMPONENT='SAP_BASIS'" finished with return code 0. Output: * -10709: Connection failed (RTE:[3] connect timeout)

Thanks & Regards,

Guna

Dear all,

I faced with error "Found contradicting entries in profile '/usr/sap/SID/SYS/profile/SID_DVEBMGS00_host'" during SPS15 update using SUM. Icheked all logs and instance profile, but i cant find contradacting entries in profile. Guide me please, how can i find contradacting entries in profile?

Hi,

What is happend: after a simple ST-A/PI update I restarted SAP (DEV). On an other system (QAS) I restarted the whole system. Just a simple restart .. not a bit of it! After the restart, I started the DB and tried to start SAP via MMC, but the MMC just showed the Process List and Access Points and SAP doesn't came up!

Windows 2008 R2 SP1

Oracle 11.2.0.4

SAP ERP 6.07 (nuc)

So I restarted the Service SAP<SID>_00, nothing changed.

I reinstalled it, nothing.

In the work directory the sapstartsrv.log shows the following entries, nothing to worry about:

---------------------------------------------------
trc file: "sapstartsrv.log", trc level: 0, release: "741"
---------------------------------------------------
pid 2660
[Thr 2744] Mon Sep 15 16:42:09 2014
HistoryLog_Init: logfile (D:\usr\sap\<SID>\DVEBMGS00\work\history.glf) already exists, check parameter
SAP HA Trace: SAP Microsoft Cluster library '741, patch 47, changelist 1517710' initialized
CCMS agent initialization: WARNING: cannot recognize instance type, checking profile parameter "system/type".
CCMS agent initialization for instance type ABAP: return code 0.
CCMS agent start: return code 0.
Initializing SAPControl Webservice
[Thr 2896] Mon Sep 15 16:42:14 2014
Auto PSE update thread started
Starting AutoRestart thread
SapSSLInit failed => https support disabled
AutoRestart thread started, version check is enabled
Starting WebService Named Pipe thread
Starting WebService thread
Webservice named pipe thread started, listening on port \\.\pipe\sapcontrol_00
Webservice thread started, listening on port 50013
SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [D:/depot/bas/741_REL/src/proj/sapha/sapwinha.cpp, line 214]
SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [D:/depot/bas/741_REL/src/proj/sapha/sapwinha.cpp, line 936]
swhsap\<SID>adm is starting SAP System at 2014/09/15 16:47:52
SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [D:/depot/bas/741_REL/src/proj/sapha/sapwinha.cpp, line 214]
SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [D:/depot/bas/741_REL/src/proj/sapha/sapwinha.cpp, line 936]

sapstart.log

SAP-R/3-Startup Program
Starting at 2014/09/15 16:47:57
Startup Profile: "D:\usr\sap\<SID>\SYS\profile\<SID>_DVEBMGS00_<HOST>"
Starting Programs

So I checked also:

- Environment variables

- Filesystem accessibility

- Windows Events

- reinstalled Redistributable Package

- Kernel Update 741.47

- MMC Update

If I start the SAP system manually, I get the system without any problems up:

D:\usr\sap\<SID>\SYS\exe\nuc\NTAMD64\sapcpe.EXE pf=\\<HOST>\sapmnt\<SID>\SYS\profile\<SID>_DVEBMGS00_<HOST>
D:\usr\sap\<SID>\SYS\exe\nuc\NTAMD64\strdbs.cmd <SID>
D:\usr\sap\<SID>\DVEBMGS00\exe\msg_server.EXE pf=\\<HOST>\sapmnt\<SID>\SYS\profile\<SID>_DVEBMGS00_<HOST>
D:\usr\sap\<SID>\DVEBMGS00\exe\disp+work.EXE pf=\\<HOST>\sapmnt\<SID>\SYS\profile\<SID>_DVEBMGS00_<HOST>
D:\usr\sap\<SID>\DVEBMGS00\exe\igswd.EXE -mode=profile pf=\\<HOST>\sapmnt\<SID>\SYS\profile\<SID>_DVEBMGS00_<HOST>

The strange thing is, after I don't find anything about it, I tried a restart on an other system and guess what, exactly the same problem!

No error messages in the logs .. and a manual start works.

I think the SAPSTARTSRV service doesn't start properly without any error messages!

So, does anyone got an idea? Maybe it's just simple and I don't get it. I just want to ask you before I open an OSS message ..

Thanks!

Best regards,

Tobias

Hi Guys

I am held in this phase Checks after phase MAIN_NEWBAS/PARCONV_UPG were negative, what could be the solution

A Part of Log

2 EGT055XRequest: Delete and recreate "Index /B364/ECPFP_R01-P (DDIC/08.07.15/04:10)"

4 EGT281 sql:

4 EGT231      "DROP INDEX '/B364/ECPFP_R01~P'"

4 EDA093 "DDL time(___1):" "........72" milliseconds

3WEDT510 Index "/B364/ECPFP_R01"-"P" completely contains the fields of index "020"

2 EDT502 Index "/B364/ECPFP_R01"-"P" must be created in the database

4 EDT520 Index "/B364/ECPFP_R01"-"P" was successfully activated

4 EGT281 sql:

4 EGT291   "CREATE UNIQUE INDEX '/B364/ECPFP_R01~P' ON""'/B364/ECPFP_R01'"" "" "

4 EGT231      "('KEY_CPFP_R01T',"

4 EGT231      "'KEY_CPFP_R011',"

4 EGT231      "'KEY_CPFP_R012',"

4 EGT231      "'KEY_CPFP_R013',"

4 EGT231      "'KEY_CPFP_R014',"

4 EGT231      "'KEY_CPFP_R015',"

4 EGT231      "'KEY_CPFP_R01U',"

4 EGT231      "'KEY_CPFP_R01P')"

4 EGT231      "PCTFREE 10"

4 EGT231      "INITRANS 002"

4 EGT231      "TABLESPACE PSAPSR3FACT"

4 EGT231      "NOCOMPRESS"

4 EGT231      "STORAGE (INITIAL 0000000000 K"

4 EGT231      "NEXT 0000000000 K"

4 EGT231      "MINEXTENTS 0000000000"

4 EGT231      "MAXEXTENTS 0000000000"

4 EGT231      "PCTINCREASE 0000"

4 EGT231      "FREELISTS 001)"

2 ED0314 ORA-02220: invalid MINEXTENTS storage option value

4 EDA093 "DDL time(___1):" "........57" milliseconds

2EEGT236 The SQL statement was not executed

2EEDI006 Index " " could not be created completely in the database

2EEGT082 "Index" "/B364/ECPFP_R01-P" could not be created

Dear team,

The system has recurrent job running every 15 minutes. It creates the following dump in ECC system.

DATA_OFFSET_LENGTH_TOO_LARGE    

Invalid subfield access: Offset and length too large...

Please help on this.

it shows issue with table FP_L_I_COUNTER field L_V_CHAR it seems.

Could anybody please help.

Regards,

Arthur

Purpose

The purpose of this document is to list all the undeployment options available to undeploy .SDA (Software Deployment Archive), .SCA (Software Component Archive), .EAR (Enterprise Archive) or .WAR (Web Archive) files on SAP J2EE servers Netweaver release: 7.1/7.2/7.3, 7.4 and the upcoming 7.5 version. For a similar knowledge base article for the deployment of these components, check my SAP KBA document : http://service.sap.com/sap/support/notes/1715441
(How to deploy .SCA/ .SDA/ .EAR/ .WAR files on J2EE servers on Netweaver release 7.1, 7.2, 7.3 and 7.4).

In earlier SAP releases (version 6.40 and 7.00) the Software Deployment manager (SDM) tool could have been easily used for this. However, it has depreciated in the latter releases. For more information, check: Undeploying Components - Using Java - SAP Library

NOTE: Undeployment as such is not supported and should be used only in cases where the SAP Basis admin is well versed with the system landscape and the repercussions of this activity very well. If unknowingly a component is deployed, the best option would be to restore the system to the previous state it was before the deployment was triggered. Hence, you should always take a full offline backup before commencing deployment.

Option 1

The best option to use is the J2EE TELNET "UNDEPLOY" command.

1) Open telnet connection and run the below commands:

> lsc (to list the available server nodes)

> jump <server node> (usually jump 0)

> add deploy

> undeploy -h (to get the command syntax and all the available options. For more information, check http://wiki.sdn.sap.com/wiki/display/TechTSG/(JSTSG)(Telnet)DeployController+Commands

For example: >undeploy name=com.sap.pct.mdm.tech.wizards vendor=sap.com name= on_undeploy_error=stop

If you wish to undeploy multiple SDAs , use the "list" option to supply an XML file as argument. Here is the syntax to run that command from telnet:

undeploy list=D:\usr\sap\UndeployItems.xml

on_undeploy_error=skip_depending on_prerequisite_error=skip_depending

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

The XML file has to be EXACTLY in the below format (including the case and spaces)

<Components>

  <DevelopmentComponentLine vendor="sap.com" name="MyApp"/>

  <DevelopmentComponentLine vendor="sap.com" name="MyService"/>

</Components>

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

NOTE: This will not calculate the dependencies though. If the operation fails, the logs will give you an idea on the dependency involved and then you can make a call on whether you wish to undeploy them in that order as well. Once all the SDAs related to the SCA are removed, then the "undeploy_empty_sca" command can be used to delete the empty SCA from the server.
This is extremely useful in cases where the SCA in question has many SDAs, like the GP-CORE SCA that has more than 102 deployed components and undeploying one by one can be a cumbersome affair.

Option 2

The Netweaver Developer Studio undeploy view can also be used to this purpose. Firstly navigate to NWDS -> window -> preferences and maintain the j2ee server details:

Now open the undeploy view by clicking on Window -> show view -> other

and select the undeploy view:

Once this is done, you can select the DC components that are part of the SCAs that need to be undeployed. It is also possible to select the whole SCA file using this technique:

Also do check:  http://help.sap.com/saphelp_nwce10/helpdata/en/44/70655c200812d2e10000000a422035/frameset.htm

Option 3

The guiconsole.bat in the location /usr/sap/<SID>/J<nr>/j2ee/console is a script that will inturn open the telnet application and you can commence undeployment as mentioned in option 1.

Option 4

ANT scripts can be used for undeployment of SDAs. For more information on this, check: http://help.sap.com/saphelp_nwce711/helpdata/en/46/150746f21914dce10000000a155369/content.htm.

NOTE: From SUM version SP14 (which will be released soon), the SUM tool also has an option to undeploy files.

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 (720, 720_EXT, 721, 721_EXT) and 74X (741, 742)

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

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.

14.10.2014: SP Stack Kernel 741 PL#100 Released

With kernel 741 PL #100 a new SP stack kernel has been released for the 741 kernel version.

SAP Note 2077824 contains the list of enhancements and most important fixes included into this stack kernel.

14.10.2014: SP Stack Kernel 720 PL#700 Released

A new SP stack kernel 720 PL #700 is now available on SAP Service Marketplace. Refer to SAP Note 2077789 for more detail on corrections and improvements delivered with this patch.

Please note that the kernel 721 will replace the kernel 720 as standard kernel in Q1 2015 as stated in SAP note 1975687. There is only one more SP stack kernel 720 planned to be delivered before this milestone is reached.

When trying to import the certificate response into the SSL server Standard PSE (or another PSE), an error might happen, informing that the "Verification of Certificate chain failed".

It is possible that a wrong intermediate and/or root certificate is being used.

This post will show how to extract the intermediate and the root certificates using the Windows Crypto Shell Extension.

First step

Double click the certificate response file (<filename>.cer):

Go to "Certification Path" (third tab):

Double click in the intermediate certificate (a new popup will be displayed):

Click in "Details" (second tab):

Click in "Copy to File..." to start a wizard. Select "Base-64 encoded X.509 (.CER)" to export the file.

Next step

Repeat the first step for the root certificate

Now it is possible to combine:

certificate response +

intermediate certificate +

root certificate

and paste them into the dialog box:

displayed after clicking in the "Import Cert. Response" button ("Own Certificate" section of the PSE):

Introduction

In the past I always worked with saprouter without understanding the mechanism of the saprouter-rules completely. Thus resulted a saproutertab with lots of useless entries and the inflationary use of *. In order to be able to use a short saproutertab it is necessary to understand the effectiveness of a saprouter entry.

     This BLOG is not a full documentation of the saprouter tool! For details please take a look at: http://sap.help.com

saproutertab entries

The saprouter controls connections. He permits or disables connection. This behavior depends on the rules defined in the saproutertab. A rule consists of 4 parts:

Part 1          Part 2                    Part 3                  Part4

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

D or P          Hostname of         Hostname of          Port

                   a starting point      an ending point

                   of a connection.     of a connection.

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

In Part 1: D stands for disable and P for permit. If you want to permit a connection from  server1 to server2 with port 3255 than the rule is:

          P    server1        server2        3255

In my sap router tab I always disable all connections with:

         D    *    *    *

I put this rule to the end of the saprotertab because it would kill all P rules if it is the first rule. Every P rule after D * * * is ignored.  Then I allow each connection I want to use.

So far it is very simple. But what rules are needed to allow a connection passing several saproutes? For this scenario I use an example with 3 saprouter hops for a connection. I describe how to maintain the saproutertab and how to test the connection with niping. In order to understand the mechanism of the following scenario it is crucial to know, the saprouters communicate with other saprouters via the standard saprouter port (3299).

Scenario Port 1442

We want to communicate from Server A with Server B via port 1442. In the following picture you can see the path of communication and the Names and hostnames of each saprouter.

Now let's consider how to maintain the saproutertab:

We know:

     1.    The saprouter communicate with other saprouter via standard saprouter port (in this case 3299).

     2.    The saprouter disables/permits connections.

     3.    The port of the addressed server is used.

With this 3 points we can maintain the saproutertab of every saprouter:

Saprouter 1

P    Host_A    Host_2        3299

D    *         *             *

Saprouter 2

P    Host_1     Host_3       3299

D    *          *            *

Saprouter 3

P    Host_2    Host_B        1442

D    *         *             *

For the rules the port used on the destination host is important. For the rule in saprouter 1 the port is 3200 because saprouter 2 communicates with saprouter 1 via port 3299.

With niping you can test your saproutertab entries. For the simulation of a server use:

     niping -s -I 0 -S 1442 -R -P

And for the corresponding client use:

     niping -c -H /H/Host_1/H/Host_2/H/Host_3/H/Host_B -S 1442 -R -P

I like to use the niping in raw mode, because in raw mode I can simulate communication with any port I want.

Testing with niping

niping tests the connection via the saprouter and gives an error message, when a communication is not possible. Lets change the rule in saprouter 2 from

     P Host_1 Host_3     3299      to

     P Host_1 nonsense   3299

Now

     niping -c -H /H/Host_1/H/Host_2/H/Host_3/H/Host_B -S 1442 -R -P

Now niping will throw the following error:

The error states the information you need to repair the wrong saproutertab configuration:

     Error     Host_2: route permission denied ( Hoste_1 to

               Host_3, 3299)

The error states the saproutertab entry needed to permit the connection.

     P Host_1 Host_3     3299

And this was the rule we changed!

Scenario Port 3200

Now, we want to connect to a sap system via the tree saprouters. The following picture shows this:

The 32<SysNr.> Port is the SAP Dispatcher port, used by SAP GUI. SysNr. is the Systemnumber of the sap system. In this case the systemnumber is 00 and we use 3200.

In Saprouter 1 we have to add the rule (this rule is going to overrule the entry P     Host_A     Host_2     3299):

     P     *               Host_2     3299

This rule is necessary because we want to login with every frontend with a sap-gui. If you want to login only with one frontent Forntend_1 you have to add rule:

     P     Frontend_1      Host_2     3299

In Saprouter 2 we don't have to add a new rule because the communication between the saprouters was not changed. In the last saprouer we have to add the rule for the communication via port 3200:

     P     Host_2          Host_B     3200

The configuration of the saproutertabs is:

Saprouter 1

P    *         Host_2        3299

P    Host_A    Host_2        3299

D    *         *             *

Saprouter 2

P    Host_1     Host_3       3299

D    *          *            *

Saprouter 3

P    Host_2    Host_B        3200

P    Host_2    Host_B        1442

D    *         *             *

In order to test the connection we make the following entry in the sap logon:

If there is an error in the configuration of the saproutertabs you are will get an error like this:

In this case the error can only be located in the 1st or second saprouter (because of port 3299). If the entry in the last saprouter is wrong you get an error with port 3200.

If there is no error you get the login screen.

Hope you enjoy this blog.

Usefull links

Portmapping

http://www.easymarketplace.de/saprouter.php

SAProuter Strig

https://help.sap.com/saphelp_nw04/helpdata/de/4f/992dd7446d11d189700000e8322d00/content.htm

nipping als Portprüfung (RAW-Mode)

http://darrylgriffiths.blogspot.de/2014/01/network-port-test-using-sap-niping.html

OSS zu niping

500235 - Network Diagnosis with NIPING

Configure SNC saprouter

http://www.erpgenie.com/sapgenie/docs/SAP%20SNC%20CONFIGURATION.pdf

Hi,

Can we do remote client copy between R3 system and BW system?

When I am trying to activate DB connect data source it is giving Invalid parameter leng. Could not find the parameter length please any once help me on this

Dear all,

In my production system following situation, a largenumber of processes busy with report from sapsys "<RPC(GENERATE ABAP (CLI WP <WP NUMBER>))>"

Tell me please, what is this report do? I canceled this processes,because thereare no remaining processes for business users.

Hi everyone,

we try to configure Single Sign-On for the users with SAP GUI for Windows.

The ABAP application server has been configured, and I think the config is OK, since in the log file I see:

N  SncInit(): Initializing Secure Network Communication (SNC)

N        AMD/Intel x86_64 with Linux (st,ascii,SAP_UC/size_t/void* = 16/64/64)

N        UserId="sidadm" (1002), envvar USER="sidadm"

N  SncInit():   found snc/data_protection/max=3, using 3 (Privacy Level)

N  SncInit():   found snc/data_protection/min=1, using 1 (Authentication Level)

N  SncInit():   found snc/data_protection/use=3, using 3 (Privacy Level)

N  SncInit(): found  snc/gssapi_lib=/usr/lib64/snckrb5.so

N    File "/usr/lib64/snckrb5.so" dynamically loaded as external SNC-Adapter.

N    The SNC-Adapter identifies as:

N    External SNC-Adapter (Rev 1.0) to Kerberos 5/GSS-API v2

N  SncInit():   found snc/identity/as=p/krb5:SAPServiceSID/sapsid.intranet.ufz.de@INTRANET.UFZ.DE

N  SncInit(): Accepting  Credentials available, lifetime=Indefinite

N  SncInit(): Initiating Credentials available, lifetime=07h 37m 16s

So, I think there is no error on the server side. But whenever a user tries to log in, he/she gets an error in SAP GUI:

---snip---

GSS-API(maj): Miscellaneous Failure

GSS-API(min): SSPI u2u-problem: please add Service principal for targe

target="p:myuser@INTRANET.UFZ.DE"

Error in SNC

---pins---

What's wrong here? Do I have to execute the "setspn" command for each user? And how would this look like? On the command line, the output of "setspn -l myuser" is empty, "setspn -l myuser@INTRANET.UFZ.DE" results in an error.

The entry in the Network tab in the SAP GUI reads either "p/krb5:myuser@INTRANET.UFZ.DE" or "p:myuser@INTRANET.UFZ.DE" or simply "P:myuser", the error remains always the same.

Can someone please help me?

Werner

Dear Experts

we are trying to open MSS pages in HCM  Portal it throws igs cummunication error then i found some documents related to this by which i went al11 and open DIR_PROFILE = /usr/sap/SID/SYS/profile from there i went start profile of particular instance i found the IGS server line in commented

Kindly find the attachment for the same and suggest some thing on this our dev and qua werver IGS server works properly but in PRD it throws error

Prd Application server IGS

Prd Central server IGS

Quality server IGS where IGS working

Kindly give me some suggestions to rectify the issue..

Regards