Csngen_adjust_time: adjustment limit exceeded

Hello !
sun directory server patch 6
linux redhat 3.7
I have an error message on my master server :
[08/Dec/2008:21:00:58 +0100] - ERROR<38994> - CSN Generation - conn=-1 op=-1 msgId=-1 - Internal error csngen_adjust_time: adjustment limit exceeded; value - 39780731, limit - 86400
Master and Consumer are synchronized using ntp.
The problem is that someone has "played" a few weeks ago with the time of the server to make some tests.
I have tried to export / import the database using db2ldif/ldif2db but nothing repaired the directory.
I have deleted the changelog directory with no result too.
I have seen such a problem on this forum but nobody gave a concrete solution to it.
Does anyone experienced that ?
Any idea ?
thanks
Regards

Hallo ,
i have the same entry in the error-log. l havr no idea to fix.
do you fix it? What do you do?
we have directory server 5.2 P4

Similar Messages

Internal error csngen_adjust_time: adjustment limit exceeded ???

Hallo,
i have found this entries in our error-log in one of four servers. We use Sun Directory Server 5.2 P4. We use replication to all 4 servers. All Servers are configured as multimaster.
ERROR<38994> - CSN Generation - conn=-1 op=-1 msgId=-1 - Internal error csngen_adjust_time: adjustment limit exceeded; value - 2845858, limit - 86400
We use Sun Directory Server 5.2 P4. We use replication to 4 servers. All Servers are multimaster.

This can be a serious error which can prevent replication from working properly.
Please make sure all of your machines have synchronized times.
You may want to restart your servers as well.
I believe that a bug was fixed in 5.2patch4 regarding excessive CSN time adjustment. You may want to upgrade to this release if not done yet.
Regards,
Ludovic

PI 7.11 - SXI_CACHE Issue - SQL 0904 - Resource Limit Exceeded

Hi PI & IBM I Gurus,
We are having the SXI_CACHE issue in our PI 7.11 SPS04 system. When we try to do the delta cache refresh through SXI_CACHE, it is returning the error SQL 0904 - Resource limit exceeded. When we try to do the full cache refresh, it is getting the issue 'Application issue during request processing'.
We have cleaned up the SQL Packages with DLTR3PKG command, which did not resolve the issue. We recently performed a system copy to build the QA instance and I observed that the adapter engine cache for the development is presented in the QA instance and removed that cache from there.
I am not seeing the adapter engine connection data cache in our PI system. The adapter engine cache is working fine.
All the caches are working fine from the PI Administration page. The cache connectivity test is failing with the same error as I mentioned for the SXI_CACHE.
Please let me know if you have encountered any issue like this on IBM I 6.1 Platform.
Your help is highly appreciated.
Thanks
Kalyan

Hi Kalyan,
SQL0904 has different reason codes ...
Which one are you seeing ?
Is the SQL pack really at its boundary of 1GB ?
... otherwise, it is perhaps a totally different issue ... then DLTR3PKG cannot help at all ...
If you should see this big SQL Package, you should use PRTSQLINF in order to see if there is more or less over and over the same SQL in, just with different host variables or so ...
If the last point should be the case, I would open a message with BC-DB-DB4 so that they can check how to help here or to talk to the application people to behave a bit different ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

PI 7.11 - SXI_CACHE Issue - SQL0904 - Resource limit exceeded

Hi IBM I Gurus,
We are having the SXI_CACHE issue in our PI 7.11 SPS04 system. When we try to do the delta cache refresh through SXI_CACHE, it is returning the error SQL 0904 - Resource limit exceeded. When we try to do the full cache refresh, it is getting the issue 'Application issue during request processing'.
We have cleaned up the SQL Packages with DLTR3PKG command, which did not resolve the issue. We recently performed a system copy to build the QA instance and I observed that the adapter engine cache for the development is presented in the QA instance and removed that cache from there.
I am not seeing the adapter engine connection data cache in our PI system. The adapter engine cache is working fine.
All the caches are working fine from the PI Administration page. The cache connectivity test is failing with the same error as I mentioned for the SXI_CACHE.
Please let me know if you have encountered any issue like this on IBM I 6.1 Platform.
Your help is highly appreciated.
Thanks
Kalyan

Hi Kalyan,
SQL0904 has different reason codes ...
Which one are you seeing ?
Is the SQL pack really at its boundary of 1GB ?
... otherwise, it is perhaps a totally different issue ... then DLTR3PKG cannot help at all ...
If you should see this big SQL Package, you should use PRTSQLINF in order to see if there is more or less over and over the same SQL in, just with different host variables or so ...
If the last point should be the case, I would open a message with BC-DB-DB4 so that they can check how to help here or to talk to the application people to behave a bit different ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

RFC_ERROR_SYSTEM_FAILURE: Time limit exceeded. Connection Pool - JCO api

Hi Everyone
My Connection Pool parameters JCO api.
client=300
user=SISGERAL_RFC
passwd=******
ashost=14.29.3.120
sysnr=00
size=10
I have these parameters on my Connection Pool and sometimes appear these wrongs in my application:
1.
2006-01-07 13:20:37,414 ERROR com.tel.webapp.framework.SAPDataSource - ##### Time limit exceeded. LOCALIZED MESSAGE = Time limit exceeded. KEY = RFC_ERROR_SYSTEM_FAILURE GROUP = 104 TOSTRING = com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Time limit exceeded.
2.
2006-01-07 14:01:31,007 ERROR com.tel.webapp.framework.SapPoolConnectionManager - Timeout
Id like to know if is happening.
Are there something wrong with my connection pool?
What can be happening?
Thanks

Raghu,
Thanks for your response.
Yes, the pool connections are in place according to the sAP note mentioned above.
Regards,
Faisal

Memory Leak, Receiver Got Null Message & Consumer limit exceeded on destina

When running program that adds an Object message to a JMS queue and then recieves it. I get the following.
1) interminitent NULL messages recieved.
2) jms.JMSException: [C4073]: Consumer limit exceeded on destination interactionQueueDest. Even though only one receiver can be receiving via the supplied program.
3) After many message are added to the queue 1000's the Message Queue goes to Out Of Memory exception. It should swap to disk!!
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
RUN this program via a JSP call in the application server.
JSP
<%@ page language="java" import="jms.*"%>
<html>
<head>
<title>Leak Memory</title>
</head>
<body>
<hr/>
<h1>Leak Memory</h1>
<%
   LeakMemory leakMemory = new LeakMemory();
   leakMemory.runTest(10000,1000);
// NOTE will brake but slower with setting leakMemory.runTest(10000,100);
%>JMS resources must be created:
jms/queueConnectionFactory
jms/interactionQueue
must be created first.
Class:
package jms;
import javax.naming.*;
import javax.jms.*;
public class LeakMemory implements Runnable {
private QueueConnectionFactory queueConnectionFactory = null;
private Queue interactionQueue = null;
private boolean receiverRun = true;
private QueueConnection queueConnection;
private int totalMessageInQueue = 0;
public LeakMemory() {
    init();
   * initialize queues
public void init(){
    try {
      InitialContext context = new InitialContext();
      this.queueConnectionFactory = (QueueConnectionFactory)context.lookup("jms/queueConnectionFactory");
      this.interactionQueue = (Queue) context.lookup("jms/interactionQueue");
    catch (NamingException ex) {
      printerError(ex);
public void runTest(int messageCount, int messageSize){
    this.receiverRun = true;
    Thread receiverThread = new Thread(this);
    receiverThread.start();
    for (int i = 0; i < messageCount; i++) {
        StringBuffer messageToSend = new StringBuffer();
        for (int ii = 0; ii < messageSize; ii++) {
          messageToSend.append("0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789\n");
        QueueConnection queueConnectionAdder = null;
        QueueSession queueInteractionSession = null;
        QueueSender interactionQueueSender = null;
        try {
            //Get a queue connection
            queueConnectionAdder = this.getQueueConnection();
            queueInteractionSession = queueConnectionAdder.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
            interactionQueueSender = queueInteractionSession.createSender(this.interactionQueue);
            ObjectMessage objectMessage = queueInteractionSession.createObjectMessage(messageToSend);
            objectMessage.setStringProperty("PROPERTY", "" + System.currentTimeMillis());
            //Send object
            interactionQueueSender.send(objectMessage,DeliveryMode.PERSISTENT,5,0);
            totalMessageInQueue++;
            //Close Resources
            interactionQueueSender.close();
            queueInteractionSession.close();
            interactionQueueSender = null;
            queueInteractionSession = null;
        } catch (JMSException ex) {
           printerError(ex);
   * run
public void run() {
    while(this.receiverRun){
            try {
              QueueSession interactionQueueSession = this.getQueueConnection().createQueueSession(false, Session.CLIENT_ACKNOWLEDGE);
              QueueReceiver queueReceiver = interactionQueueSession.createReceiver(this.interactionQueue);
              ObjectMessage message = (ObjectMessage)queueReceiver.receive(100);
              if(message != null){
                StringBuffer messageRecived = (StringBuffer)message.getObject();
                //Simulate Doing Something
                synchronized (this) {
                  try {
                    Thread.sleep(400);
                  catch (InterruptedException ex1) {
                    //Can Safely be ignored
                message.acknowledge();
                totalMessageInQueue--;
              } else {
                printerError(new Exception("Receiver Got Null Message"));
              queueReceiver.close();
              interactionQueueSession.close();
              queueReceiver = null;
              interactionQueueSession = null;
            catch (JMSException ex) {
              printerError(ex);
    * Get's the queue Connection and starts it
    * @return QueueConnection The queueConnection
   public synchronized QueueConnection getQueueConnection(){
       if (this.queueConnection == null) {
         try {
           this.queueConnection = this.queueConnectionFactory.createQueueConnection();
           this.queueConnection.start();
         catch (JMSException ex) {
           printerError(ex);
     return this.queueConnection;
   private void printerError(Exception ex){
     System.err.print("ERROR Exception totalMessageInQueue = " + this.totalMessageInQueue + "\n");
     ex.printStackTrace();
}Is there something wrong with the way I'm working with JMS or is it just this unreliable in Sun App Server 7 Update 3 on windows?

1) interminitent NULL messages recieved.Thanks that explains the behavior. It was wierd getting null messages when I know there is messages in the queue.
2) jms.JMSException: [C4073]: Consumer limit exceeded
on destination interactionQueueDest. Even though only
one receiver can be receiving via the supplied
program. No other instances, Only this program. Try it yourself!! It works everytime on Sun Application Server 7 update 2 & 3
heres the broker dump at that error point
[14/Apr/2004:12:51:47 BST] [B1065]: Accepting: [email protected]:3211->admin:3205. Count=1
[14/Apr/2004:12:51:47 BST] [B1066]:   Closing: [email protected]:3211->admin:3205. Count=0
[14/Apr/2004:12:52:20 BST] [B1065]: Accepting: [email protected]:3231->jms:3204. Count=1 [14/Apr/2004:12:53:31 BST] WARNING [B2009]: Creation of consumer from connection [email protected]:3231 on destination interactionQueueDest failed:
B4006: com.sun.messaging.jmq.jmsserver.util.BrokerException: [B4006]: Unable to attach to queue queue:single:interactionQueueDest: a primary queue is already active
3) After many message are added to the queue 1000's
the Message Queue goes to Out Of Memory exception. It
should swap to disk!!The broker runs out of memory. Version in use
Sun ONE Message Queue                   Copyright 2002
Version: 3.0.1 SP2 (Build 4-a)              Sun Microsystems, Inc.
Compile: Fri 07/11/2003         All Rights ReservedOut of memory snippet
[14/Apr/2004:13:08:28 BST] [B1089]: In low memory condition, Broker is attempting to free up resources
[14/Apr/2004:13:08:28 BST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0021]: GREEN - current memory is 118657K, 60% of total memory
[14/Apr/2004:13:08:38 BST] WARNING [B2075]: Broker ran out of memory before the passed in VM maximum (-Xmx) 201326592 b, lowering max to currently allocated memory (200431976 b ) and trying to recover [14/Apr/2004:13:08:38 BST] [B1089]: In low memory condition, Broker is attempting to free up resources
[14/Apr/2004:13:08:38 BST] [B1088]: Entering Memory State [B0024]: RED from previous state [B0022]: YELLOW - current memory is 128796K, 99% of total memory [14/Apr/2004:13:08:38 BST] ERROR [B3008]: Message 2073-192.168.0.50(80:d:b6:c4:d6:73)-3319-1081944517772 exists in the store already [14/Apr/2004:13:08:38 BST] WARNING [B2011]: Storing of JMS message from IMQConn[AUTHENTICATED,[email protected]:3319,jms:3282] failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: Message 2073-192.168.0.50(80:d:b6:c4:d6:73)-3319-1081944517772 exists in the store already
[14/Apr/2004:13:08:38 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:38 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:39 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:39 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:39 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:39 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:40 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:40 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:40 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:40 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:41 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:42 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:42 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:42 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:42 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:43 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:43 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:43 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:43 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:44 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:44 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:44 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:45 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:45 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:46 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:46 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:47 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:47 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:47 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:47 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:48 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:49 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:49 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:49 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:49 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:50 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:50 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:50 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:50 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:51 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:51 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:51 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:51 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:52 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:52 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:53 BST] ERROR [B3107]: Attempt to free memory failed, taking more drastic measures : java.lang.OutOfMemoryError
[14/Apr/2004:13:08:53 BST] ERROR unable to deal w/ error: 1
[14/Apr/2004:13:08:53 BST] ERROR TRYING TO CLOSE [14/Apr/2004:13:08:53 BST] ERROR DONE CLOSING
[14/Apr/2004:13:08:53 BST] [B1066]:   Closing: [email protected]:3319->jms:3282. Count=0

Short dump "Time limit exceeded" when searching for Business Transactions

Hello Experts,
We migrated from SAP CRM 5.2 to SAP CRM 7.0. After migration, our business transaction search (quotation, sales order, service order, contract etc) ends with the short dump "Time limit exceeded" in class CL_CRM_REPORT_ACC_DYNAMIC, method DATABASE_ACCESS. The select query is triggered from line 5 of this method.
Number of Records:
CRMD_ORDERADM_H: 5,115,675
CRMD_ORDER_INDEX: 74,615,914
We have done these so far, but the performance is still either poor or times out.
1. DB team checked the ORACLE parameters and confirmed they are fine. They also checked the health of indices in table CRMD_ORDER_INDEX and indices are healthy
2. Created additional indices on CRMD_ORDERADM_H and CRMD_ORDER_INDEX. After the creation of indices, some of the searches(without any criteria) work. But it takes more than a minute to fetch 1 or 2 records
3. An ST05 trace confirmed that the selection on CRMD_ORDER_INDEX takes the most time. It takes about 103 seconds to fetch 2 records (max hits + 1)
4. If we specify search parameters, say for example a date or status, then again we get a short dump with the message "Time limit exceeded".
5. Observed that only if a matching index is available for the WHERE clause, the results are returned (albeit slowly). In the absence of an index, we get the dump.
6. Searched for notes and there are no notes that could help us.
Any idea what is causing this issue and what we can do to resolve this?
Regards,
Bala

Hi Michael,
Thanks. Yes we considered the note 1527039. None of the three scenarios mentioned in the note helped us. But we ran CRM_INDEX_REBUILD to check if the table CRMD_ORDER_INDEX had a problem. That did not help us either.
The business users told us that they mostly search using the date fields or Object ID. We did not have any problem with search by Object ID. So we created additional indices to support search using the date fields.
Regards,
Bala

Static credit check: credit limit exceeded for consignment issue delivery

Hi,
We are encountering a credit limit exceeded error in delivery creation for a consignment issue.
In SPRO config "Credit limit check for order types", no credit limit check is assigned to the order type. However, there is one assigned for the delivery type. Also, for CCAr/Risk cat./CG combination in OVA8 (Auto Credit Block Delivery), static credit check has been activated with error message reaction. Open orders and open deliveries were also activated. Customer exceeded credit exposure but user cannot release the order in any VKMx transactions as no credit limit check is assigned to the order type.
Given that this is the current setup, and the following conditions:
1. Credit limit for the customer cannot be increased
2. Oldest open item cannot be cleared just yet
Is there any way that we can proceed with delivery creation for this customer? The other order types have credit limit check so credit management team was able to release them. However, we are unsure on how to proceed with this consignment order. Kindly advise and thank you in advance for your help.

We are encountering a credit limit exceeded error in delivery creation for a consignment issue.
but user cannot release the order in any VKMx transactions as no credit limit check is assigned to the order type.
Looks contradictory and it may need to run report RVKRED77 to reorganization of open credit values. Try to run the report in test system and then run in production system. After running the report, the use must be able to release in VKM* transaction.
Regards,

Error while running query "time limit exceeding"

while running a query getting error "time limit exceeding".plz help.

hi devi,
use the following links
queries taking long time to run
Query taking too long
with hopes
Raja Singh

TIME LIMIT EXCEEDED ERROR WHILE EXECUTING DTP

Hi gurus,
I Have got an error while executing
The errors are as follows.
1.Time limit exceeded. No return of the split processes
2.Background process BCTL_DK9MC0C2QM5GWRM68I1I99HZL terminated due to missing confirmation
3.Resource error. No batch process available. Process terminated
Note: Iam not executing the DTP as a back ground job.
As it is of higher priority the answers Asap Is appreciated.
Regards
Amar.

Hi,
how is it possible to execute a DTP in dialog process. In my mind it is only possible for debugging...
In "Display Data Transfer Process" -> "Goto" -> "Settings for Batch Manger" you can edit settings like Number of Processes or Job Class.
Additional take a look at table RSBATCHPARALLEL and
http://help.sap.com/saphelp_nw04s/helpdata/en/42/f29aa933321a61e10000000a422035/frameset.htm
Regards
Andreas

Time Limit exceeded while running in RSA3

Hi BW Experts,
I am trying to pull 1 lakh data from CRM to BI System.
Before scheduling, i am trying to execute in RSA3.I am getting the error message as "Time Limit Exceeded".
Pls suggest, why it is happening like this.
Thanks in advance.
Thanks,
Ram.

Hi,
because huge data with in the stipulated time it is not executing and showing the all records ,so it is better to go any selection option by each document type or some else then u can add all the documents ,anyway in bw side we r running this job in background so no problem.if u want see all records at a time then u can discuss with ur basis people to extend the time for that.
Thanks & Regards
sathish

Time limit exceeded error

Hello All,
I am trying to execute a custom program with a variant, but I receive the Time limit exceeded error [TIME_OUT].
I am now trying to analyse why this error has occurred as I am a beginner. Any help shall be greatly appreciated.
Regards,
Arpita.
Moderator message: Welcome to SCN!
Moderator message: Please Read before Posting in the Performance and Tuning Forum
Edited by: Thomas Zloch on Oct 20, 2011 2:01 PM

Hi Ramya,
Your prog running in the back ground, so the time limit of the prog is exceded. Go to sm37 see the prog running time if exceded correct the time.
Regards
Srinu

Time Limit exceeded error in R & R queue

Hi,
We are getting Time limit exceeded error in the R & R queue when we try to extract the data for a site.
The error is happening with the message SALESDOCGEN_O_W. It is observed that whenever, the timelimit error is encountered, the possible solution is to run the job in the background. But in this case, is there any possibility to run the particular subscription for sales document in the background.
Any pointers on this would be of great help.
Thanks in advance,
Regards,
Rasmi.

Hi Rasmi
I suppose that the usual answer would be to increase the timeout for the R&R queue.
We have increased the timeout on ours to 60 mins and that takes care of just about everything.
The other thing to check would be the volume of data that is going to each site for SALESDOCGEN_O_W. These are pretty big BDOCs and the sales force will not thank you for huge contranns time
If you have a subscription for sales documents by business patrner, then it is worth seeing if the business partner subscription could be made more intelligent to fit your needs
Regards
James

Time Limit exceeded error in ALV report

I am gettting error "Time Limit Exceeded" when i execute ALV report. Can i run the program in background and how to do that?. I had already optimized my query in the program but even then i am facing the same issue.

You can process the alv in background by pressing F9...I guess that the output would be available as a spool in SP01.
You may need to re-check your query...And also, review the alv catalog and any events you are using....
Greetings,
Blag.

Time Limit Exceeded while executing Proxy Program

Hi all,
we are frequently facing Time Limit Exceeded problem in R/3 system while exceuting proxy program for large payloads (appx 5-7 MB). Sometimes we are able to successfully restart the message and sometimes we have to delete these messages. How can we resolve this issue.
Thanks,
Mayank

hi Joerg,
we are getting this error in inbound queue in R/3 system, also this is a async call, so no chance of any communication interruption b/w SAP systems. From PI system, message is succeccfully passed to R/3 system & Time Limit Exceeded is coming in R/3 system inboud queue (SMQ2). Is it poosible that timeout will happen within R/3 system.
Thanks,
Mayank

Csngen_adjust_time: adjustment limit exceeded

Similar Messages

Maybe you are looking for