Quantcast
Channel: SCN : All Content - SAP NetWeaver Application Server
Viewing all 2997 articles
Browse latest View live

STMS - default for "Leave Transport Request in Queue for Later Import"

0
0

Hi

 

Users/developers of a development system have asked to have the default value changed for "Leave Transport Request in Queue for Later Import". Presently this is by default selected, the users would like to have this changed, so that by default this option is NOT selected.

 

I cannot however find the right TP parameter to change for this...

 

Anyone know where to, if possible at all, to change the default setting of "Leave Transport Request in Queue for Later Import"  ???

 

Best Regards


How get instances information in cluster Java AS

0
0

I have arbitrary java claster Architecture.

I do solution to parse Java AS logs files and and further processing it. Files are in

/usr/sap/<SID>/J00/j2ee/cluster/server0/log/system


How can I get information about all AS instances in claster (hosts) to log in and read the files?

Now I use simple file to store hosts list but it is not convenient and it will extra work for SAP admin when add new AS instance (He can forget to add new host in file ).


I read about config tool but did not found simple way to get cluster hosts list. I use Java, where are some java, bapi, OS tools and utils to get it?

SAP Kernel: Important News

0
0

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

 

 

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:

 

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.

How can we stop only one Job server in Data Services

0
0

Hello all,

 

I'm not sure if this is the appropiate forum but anyway Im going to make my question.

I know how we can stop and start Job servers in a Data Service system.

 

The standard to stop and start job servers could be this:

 

cd $LINK_DIR/bin

. ./al_env.sh

./svrcfg

1   -> "Control job Service".

"o" -> "Stop Job Service".

"q" -> Quit.

 

But when you have more that one, How can you stop only one of them?


Thank you!

SGEN hangs sequential read TRDIR

0
0

After a  kernel upgrade from 7.01 to 7.21_ext in a SAP SCM 7.0 i have problems during execution of sgen.

I want to generate all objects of selected components....but when i arrive to choose the applications server where i want sgen has to run, and

pressing continue it remains in hang like the picture in attachment.

 

I see that it hangs in a sequential read in table trdir....that is a select * from REPOSRC.

This selection runs for hours until in next step i finally start the sgen.

I did statistics on table reposrc but the problem remains. Could it be a db problem? In other systems this phase is faster...only few minutes in worst of cases.

How can i solve this problem?

Thanks

Nickk

Error ICM in HTTPS connection in CRM

0
0

Hello,

 

I'm facing an problem when the user login on the CRM WEBUI using HTTPS protocol. The user use BCM to receive the calls from a 0800 number and the BCM software communicates with the CRM filling the customer's informations. When the user use HTTP protocol, the informations fills, but when the user use the HTTPS protocol, she can login (using a certificate or/and login manually), but the customer's informations don't fills.

 

I already update the certificate from BCM to CRM (in the STRUST).

 

My parâmeters for HTTPS in RZ10 is:

 

icm/HTTPS/verify_client                     2

icm/server_port_2                           PROT=HTTPS,PORT=443$$

ssl/ssl_lib                                 C:\usr\sap\CRP\DVEBMGS00\exe\sapcrypto.dll

sec/libsapsecu                              C:\usr\sap\CRP\DVEBMGS00\exe\sapcrypto.dll

ssf/ssfapi_lib                              C:\usr\sap\CRP\DVEBMGS00\exe\sapcrypto.dll

 

SMICM it's ok.

 

In the ICM logs i see a error (Atached on file erro_ICM_CHELEB_CERTIFICADOS).

 

CANOPUS, in the ICM logs error, is a virtual host that have two apps, in server CHELEB and CHERTAN, but the ICM errors appears only in CHELEB server. This is the CRM landscape.

 

Can you tell me if i need to do any configuration in CRM side? Or its like a infrastructure problem?

 

Thanks in advanced!!!!

 

Cleiton Folster Eli

System does not start post SAP JVM update

0
0

Hi,

 

We updated our SAP JVM  6 for EP 7.3 SP7 from patch 46 to patch 59 using JSPM.

The patch got deployed successfully; however, post deployment server0 refuses to start...stating the below cause:

 

Service [cross] start ================= ERROR =================

  CSN Component [BC-JAS-COR-RMT], DC Name [sap.com/cross]

java.lang.NoSuchFieldError: ipaddress

at com.sap.bc.proj.jstartup.fca.FCAProperties.init1(Native Method)

at com.sap.bc.proj.jstartup.fca.FCAProperties.init(FCAProperties.java:54)

at com.sap.engine.services.cross.fca.FCAConnectorImpl.<init>(FCAConnectorImpl.java:101)

at com.sap.engine.services.cross.CrossFrame.start(CrossFrame.java:82)

at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)

at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)

at com.sap.engine.frame.core.thread.Task.run(Task.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)

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

  Service [userstore] started. [187] ms / [15] CPU ms

FATAL: Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]


Please help...

 

Thanks a lot !

saba.


Full Active Active & HA without Hardware Clustering?

0
0

Hello,

 

I am currently working for a client who has some stringent HA requirements for up and coming releases. In a nutshell they are; fully resilient, instant mean time to repair, on Active Active, And we need some help in understanding what can be done within the constraints of their available infrastructure services.

 

The client is using Oracle Data Guard + other measures to provide HA throughout the stack and would like to run all SAP component Active Active. However, we understand this is not possible for ASCS/SCS, which are designed to run Active Passive. We also understood ASCS/SCS require hardware clustering for automatic failover. Unfortunately hardware clustering is not something available to the client for various reasons, thus, failover of ASCS/SCS would have to be manual, which is not acceptable.

 

This point is the crux of my question; is it possible to run a full Active Active including ASCS/SCS? Or can the ASCS/SCS failover being automated without hardware clustering?

 

The client currently has NW 7.31 ABAP and 7.4 JAVA for different software components and would like HA available on both.

 

Thanks in advance

Laurie


Strange License Expiry

TMS configuration - newly build PRD server

0
0

Hi Friends,

 

We build new PRD server copy of old PRD server

 

After system build, I would like to configure TMS.

 

Kindly let me know the steps to rebuild my STMS configuration.

Also please let me know how to take care of BG jobs and Printers?

 

 

Best Regards

Satya

Caught exception during application deployment from SAP J2EE Engine's deploy service

0
0

Hi, SAP Gurus.

 

Please help me with this error, show me when i tray to make deploy to DC's:


Caught exception during application deployment from SAP J2EE Engine's deploy service

java.rmi.RemoteException: Cannot deploy application corg.com/capexii~wd_ac_03_sg.. Reason: Clusterwide exception: Failed to deploy application corg.com/capexii~wd_ac_03_sg. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application corg.com/capexii~wd_ac_03_sg. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Error run report TMS_BCI_START_SERVICE

0
0

Hi,

 

I want activate the report TMS_BCI_START_SERVICE because  i need apply automaticly the transports request for Qas system, but run the report show the following message:

 

Internal error getting jobname, RC= 1

Message No. 2B010

Diagnosis

An internal error occurred.

System Response

The function terminates.

Procedure

Read the short text to see where the error occurred.

Procedure for System Administration

You can use the system log, database log and message server to analyze the error.

 

Please, can you help me with this error?

 

Best Regards,

Basis EDRS

History of free WP

0
0

Dear expert

 

There is a way to find history of  WP?

Forexample ifbetween 07 - 08  I had freewp?freeDIA?in SAP system.

 

 

 

Thanks

 

Naor

SCOT : Confirmation Message Receipt

0
0

Hello All,

 

SCOT -> Setting -> Mail Confirmation

 

When I look the jpg file, I understood, Except DEMISAS.COM.TR, I will receive confirmation  any internet mail .

 

Unfortunately, it is not working succesfully.

 

I am wondering, Did you use it ?

Is it succesfully ?

 

scotsample.jpg.jpg

 

Regards

 

Tanju

Fax via SMTP - replace + by international dialling code

0
0

Dear all,

 

We would like to change the standard format of our FAX via SMTP - the standard format looks like:

 

FAX=+<canonicalfaxnumber>@domain

 

This results in FAX=+32xxx@domain

 

We would like FAX=0032xx@domain where 0032 is the international dialling code for Belgium.

 

Is this possible?

 

Kind regards,

 

Lieselot


J2EE engine doesn't start - framework package jvmx.jar is not found

0
0

Hello,

 

I have a problem with the J2EE engine of Solution Manager 4.0 (Nw04s on linux-64bit), after an SPS12 and kernel 102 upgrade the application doesn't start. We have notice that the framework package jvmx.jar is not found.

 

what could be the problem?

 

Regards.

How to create a user in the local ume database when using write access to connected ldap

0
0

Hello,

I have to create a user in the local UME database of an SAP Portal where the userstore is also connected to a ldap source with write access.

Due to write access the ume always tries to create the user in the ldap directory, but I don't want this.

Is there any way to choose the destination of a newly created user?

 

Many thanks

 

Roland

SAP Kernel: Important News

0
0

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

 

 

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:

 

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.

Severe error(s) occurred in phase PREP_GENCHECKS/JOB_RSAUCHK_DUP!

0
0

Hi,

 

I am trying to upgrade CRM 7.0 EHP 1 to 7.0 EHP 3.

 

But I am getting below error now..Appreciate your help on this..

 

Severe error(s) occurred in phase PREP_GENCHECKS/JOB_RSAUCHK_DUP!


Last error code set: Cannot read l.1301 'D:\SUM\abap\mem\MEMProcSAPup.dat': Internal error: Read insert, got internally update for PID 3956

 

Environment:-WIndows Server 2012

DB:-SQL Server 2014

Software Update Manager Version: 1.0

Support Package Version: 13

Patch Level: 4

 

Thanks,

Mofizur

Failure occured in initialization of JMS queue 'jmsQueues/ISPEventQueue'

0
0

Hi guys

 

After Installing NW 7.5 Process Orchestration, under default trace, the following message is displayed repeteadly.

 

Functional Unit Wizard for Process Orchestration was completed, Its look a lack of permission but still unclear what is the reason behind this error.

 

 

Any help would be highly appreciated

 

Best

Martin

 

#2.#2015 11 13 14:55:11:114#0-300#Error#com.sap.jms.server.sc.UMESecurityProvider#

#BC-JAS-JMS#jms#C000AC1118921E9A0000000000007F16#1877050000742040##com.sap.jms.server.sc.UMESecurityProvider#PIAFPOD#0##28D3874D88D511E5897A005056A66387#28d3874d88d511e5897a005056a66387##0#Timeout Event Processor, id [5199], invocation [0]#Plain##

The username: PIAFPOD has not enough permissions. For more details see the exception.

[EXCEPTION]

javax.jms.JMSSecurityException: User: PIAFPOD has not permission: vpName: default, type: queue, action: produce, destination: ISPEventQueue

        at com.sap.jms.server.sc.UMESecurityProvider.checkPermission(UMESecurityProvider.java:217)

        at com.sap.jms.server.sc.UMESecurityProvider.checkDestinationProducePermission(UMESecurityProvider.java:112)

        at com.sap.jms.server.JMSVirtualProviderProcessor.producerCreate(JMSVirtualProviderProcessor.java:548)

        at com.sap.jms.client.session.JMSSession.createProducer(JMSSession.java:607)

        at com.sap.jms.client.session.JMSQueueSession.createSender(JMSQueueSession.java:56)

        at com.sap.engine.services.jmsconnector.cci.QueueSessionImpl.createSender(QueueSessionImpl.java:155)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper$PrivilegedCreateSender.run(PrivilegedActionHelper.java:112)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper$PrivilegedCreateSender.run(PrivilegedActionHelper.java:98)

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

        at javax.security.auth.Subject.doAs(Subject.java:422)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper.privilegedActionHelper(PrivilegedActionHelper.java:581)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper.createSender(PrivilegedActionHelper.java:664)

        at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.init(ISPEventSession.java:181)

        at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:342)

        at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:83)

        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

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

        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)

        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

 

 

#

 

 

#2.#2015 11 13 14:55:11:114#0-300#Error#com.sap.jms.server.JMSVirtualProviderProcessor#

#BC-JAS-JMS#jms#C000AC1118921E9A0000000100007F16#1877050000742040##com.sap.jms.server.JMSVirtualProviderProcessor#PIAFPOD#0##28D3874D88D511E5897A005056A66387#28d3874d88d511e5897a005056a66387##0#Timeout Event Processor, id [5199], invocation [0]#Plain##

 

 

[EXCEPTION]

javax.jms.JMSSecurityException: User: PIAFPOD has not permission: vpName: default, type: queue, action: produce, destination: ISPEventQueue

        at com.sap.jms.server.sc.UMESecurityProvider.checkPermission(UMESecurityProvider.java:217)

        at com.sap.jms.server.sc.UMESecurityProvider.checkDestinationProducePermission(UMESecurityProvider.java:112)

        at com.sap.jms.server.JMSVirtualProviderProcessor.producerCreate(JMSVirtualProviderProcessor.java:548)

        at com.sap.jms.client.session.JMSSession.createProducer(JMSSession.java:607)

        at com.sap.jms.client.session.JMSQueueSession.createSender(JMSQueueSession.java:56)

        at com.sap.engine.services.jmsconnector.cci.QueueSessionImpl.createSender(QueueSessionImpl.java:155)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper$PrivilegedCreateSender.run(PrivilegedActionHelper.java:112)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper$PrivilegedCreateSender.run(PrivilegedActionHelper.java:98)

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

        at javax.security.auth.Subject.doAs(Subject.java:422)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper.privilegedActionHelper(PrivilegedActionHelper.java:581)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper.createSender(PrivilegedActionHelper.java:664)

        at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.init(ISPEventSession.java:181)

        at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:342)

        at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:83)

        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

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

        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)

        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

 

 

#

 

 

#2.#2015 11 13 14:55:11:115#0-300#Error#com.sap.jms.client.session.JMSQueueSession#

#BC-JAS-JMS#jms#C000AC1118921E9A0000000200007F16#1877050000742040##com.sap.jms.client.session.JMSQueueSession#PIAFPOD#0##28D3874D88D511E5897A005056A66387#28d3874d88d511e5897a005056a66387##0#Timeout Event Processor, id [5199], invocation [0]#Plain##

Unable to create JMS message producer for destinationId: 97, for JMS session with sessionID: 171 for connectionId: 1877172.

[EXCEPTION]

javax.jms.JMSSecurityException: User: PIAFPOD has not permission: vpName: default, type: queue, action: produce, destination: ISPEventQueue

        at com.sap.jms.server.sc.UMESecurityProvider.checkPermission(UMESecurityProvider.java:217)

        at com.sap.jms.server.sc.UMESecurityProvider.checkDestinationProducePermission(UMESecurityProvider.java:112)

        at com.sap.jms.server.JMSVirtualProviderProcessor.producerCreate(JMSVirtualProviderProcessor.java:548)

        at com.sap.jms.client.session.JMSSession.createProducer(JMSSession.java:607)

        at com.sap.jms.client.session.JMSQueueSession.createSender(JMSQueueSession.java:56)

        at com.sap.engine.services.jmsconnector.cci.QueueSessionImpl.createSender(QueueSessionImpl.java:155)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper$PrivilegedCreateSender.run(PrivilegedActionHelper.java:112)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper$PrivilegedCreateSender.run(PrivilegedActionHelper.java:98)

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

        at javax.security.auth.Subject.doAs(Subject.java:422)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper.privilegedActionHelper(PrivilegedActionHelper.java:581)

        at com.sap.aii.af.utilxi.jms.auth.PrivilegedActionHelper.createSender(PrivilegedActionHelper.java:664)

        at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.init(ISPEventSession.java:181)

        at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:342)

        at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:83)

        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

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

        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)

        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

 

 

#

 

 

#2.#2015 11 13 14:55:11:115#0-300#Error#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent#

#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1118921E9A0000000300007F16#1877050000742040##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout()#Guest#0##28D3874D88D511E5897A005056A66387#28d3874d88d511e5897a005056a66387##0#Timeout Event Processor, id [5199], invocation [0]#Plain##

Exception occured during timer callback - Failure occured in initialization of JMS queue 'jmsQueues/ISPEventQueue' for message processing.#

Viewing all 2997 articles
Browse latest View live




Latest Images