Error - Background Processing: Planning Run

Hey Guys,
I want to schedule a background planning run. The report /SCMTMS/CL_TS_VSR_BGD is terminated
because of the following error. Has anyone an idea how to solve this issue?
Kind reagards,
Christian
Error in the ABAP Application Program
The current ABAP program "/SCMTMS/VSR_OPT_BGD" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"/SCMTMS/CL_TS_VSR_BGD=========CP " in include
"/SCMTMS/CL_TS_VSR_BGD=========CI " in
line 42:
"Direct access to the components of the global interface /SCMTMS/IF_SRV"
"MGR_TYPES is not allowed (INTERFACE /SCMTMS/IF_SRVMGR_TYPES LOAD state"
"ment is missing)."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SANNG "
Error in the ABAP Application Program
The current ABAP program "/SCMTMS/VSR_OPT_BGD" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.

Can you refer the following SAP Notes will help you to resolve your problem.
1230638 Memory consumption for VSR planning run too high
1285772 Planning: Write application log from VSR batch reports
1279704 Planning: Various performance improvements

Similar Messages

Postprocessing - background processing - Still running!!!

Hi All
I think I am having a small problem with this task 'Postprocessing - background processing' during the Postprocessing Phase. Basically on previous runs, this task has finished quite quickly however during this next run it is taking hours. I have restarted this phase and it does not seem to finish.
I have checked SM66 to see if anything is running and there is nothing there. All of the other processes have finished successfully, just not sure about this one.
Has anyone had this issue before or can you give me an insight to what it is doing?
Thanks in advance
Phil

>
Phil Wade wrote:
> The process that are involved in the task are:
>
> Reset Internal Header Tables After the Transfer - Complete
> Postprocessing - background processing - This one has not completed
> Transfer of Number Range Intervals - Complete
> Reset Number Range and Table Buffers in Receiver System - Complete
> Delete Generated Views - Complete
> Adjust User Addresses - Complete
> Update SAPOffice - Complete
> Execute Initialization for POS Handling - Complete
> Change Logical System Names - Complete
> Unlock Users in Receiver System - Complete
> Refresh Data Selection Cluster of Current Transfer - Complete
> Phil
"Postprocessing - background processing" is not actually a task, it is there only to group the sub-tasks (from "Transfer of Number Range Intervals" to "Change Logical System Names"). When you execute it, it will run all the sub-tasks (in the Standard View this complexity is hidden, so you don't even see there are sub-tasks).
If the sub-tasks are all Complete then there is nothing left to do. It is normal that there is no State icon for that grouping task, or that Progress is 0. If you execute it again you are running all the sub-tasks once again (you probably received a pop-up to confirm that's what you wanted). In that case, the column "Exec No" in the sub-tasks probably shows that some were executed more than once (some are repeatable and some are not).
Hope this helps,
Rui Dantas

Error Mrp: Total Planning Run stopped due to 25 Terminations of 202 Matls

Hi
We are trying to run the Mrp Job I.e steps (RMMRP00) with variant PLVH_NETCHNG)..
I have 1 db server and 2 apps servers and it the starts to run for about 2 minutes and then crashes with the ffg error:
Total Planning Run stopped due to 25 Terminations (dumps)of 202 Matls.
Apps Guys says its a basis issue and i cant see an issue.
ANy help will be appreciated

Hi,
Please check the MRP setting some times we define mrp value upto 3-4 decimal and our setting upto 2 decimal points. If you send error log then that will be helpful for us to see the exact problem in the dump.
In case you want to send this by mail send [email protected]
Regards,
Anil

Error while production planning run

Hi,
I got this error "No gap for activity ||| found within the planning horizon" during production planning run.
Diagnosis
    There is not a large enough gap for the activity ||| on the mode
    1- in the planning period specified in the time profile.
System Response
    The system does not schedule or reschedule.
What could be the reason for this error ? Kindly help.

Hi,
   One reason could be the Time Bucket.
Please check your time series assigned for production planning run.
Check the PPMs and maintain the scheduling data .
Please let me know that whether you have transferred the data from R/3(Materials, WorkCenters, BOMs,PPMs) or you are doing manually in APO.
Let me know then i can tell you the right approach.
Regards,
Santosh

Front Row launches as background process when running second display

When I connect a second display, Front Row launches as a background process and hogs upwards of 90% of my CPU cycles. I've tried connecting things in various orders, but had no success in avoiding this.

try restarting and it will works. it happens to me some of the times or unplug your cable and plug it in again.

Error in Process flow running in SQL owb_run_own.wb_rt_api_exec.run_task

Hi all
We are having issue with owb_run_own.wb_rt_api_exec.run_task using Sql Plus
When i try to run through Warehouse Builder Process flow ran Successfully
When i try to run through SQL Plus using owb_run_own.wb_rt_api_exec.run_task We are getting error
ORA-20099: ORA-20003: Process Flow FailedSerious <PROCEDURE_NAME >unknown error
RPE-02018: Oracle Workflow schema OWF_MGR on host OWD2HOST cannot be accessed using service OWDX.XXXX.XXXX through port 1523. Please check the location details and try again.
Can any one help please
Thanks in Advance
Edited by: user1849 on May 5, 2009 9:56 AM

Hi all
We are having issue with owb_run_own.wb_rt_api_exec.run_task using Sql Plus
When i try to run through Warehouse Builder Process flow ran Successfully
When i try to run through SQL Plus using owb_run_own.wb_rt_api_exec.run_task We are getting error
ORA-20099: ORA-20003: Process Flow FailedSerious <PROCEDURE_NAME >unknown error
RPE-02018: Oracle Workflow schema OWF_MGR on host OWD2HOST cannot be accessed using service OWDX.XXXX.XXXX through port 1523. Please check the location details and try again.
Can any one help please
Thanks in Advance
Edited by: user1849 on May 5, 2009 9:56 AM

How to Check Error Log for Supply Planning Run

Hi All
I am getting error in supply planning run. I see the status under Excel Add-in >Supply Planning > Status. However there is no detailed error message here
How can I check the detailed log of this error to understand what is going wrong.
Can anybody guide on what can be probable causes of the error
Any help is highly appreciated
Thanks
Vijay

Hello Vijay, Wade
Can you run the Supply Planning in Simulation mode? Under the simulation drop-down you can also see 'Show Message'.
Open it after your planning run to see list of any data inconsistencies.
Thanks
Pramod

How do I run a background process which is under WLE control

Hello folks:
How can I run a background process that runs under WLE's control.
What I am looking for is a way to have a process that runs in an
infinite loop and polls the database to see if there is any background
work that needs to be done. But I still want the process to be managed
by WLE for fault tolerance.
Thanks,
Ram Ramesh
[email protected]

The easiest way to do this is to write a Tuxedo server (i.e., using only
ATMI and no CORBA stuff) that does the following:
1.) In tpsvrinit(), the last thing that it should do is a tpacall to the
service contained in this server (and nowhere else) with the TPNOREPLY
flag.
2.) In the method that implements the service, do your database work, sleep
for a little while, do another tpacall to itself with the TPNOREPLY flag,
and return.
Hope this helps,
Robert
Ram Ramesh wrote:
Hello folks:
How can I run a background process that runs under WLE's control.
What I am looking for is a way to have a process that runs in an
infinite loop and polls the database to see if there is any background
work that needs to be done. But I still want the process to be managed
by WLE for fault tolerance.
Thanks,
Ram Ramesh
[email protected]

Servlet background process on tomcat 4.0.2

i have 1 servlet which will run a thread, background process, whenever the init() on that servlet called. i tried on tomcat 3.3a and tomcat 3.2.3, and both tomcat will run my servlet's background process, will run the thread. but, when i run the servlet using tomcat 4, tomcat 4 will run the init(), but when it do not start the thread. what happen?... i used the same code, servlet, on tomcat 3.2.3, 3.3a and 4....
can anyone explain it to me?.....

my code look like this:
public class Discover extends HttpServlet implements Runnable
Thread t = null;
boolean running = false;
public void init()
t = new Thread(this);
t.start();
System.out.println("thread start");
public void doPost(HttpServletRequest request, HttpServletResponse response) throws
ServletException, IOException
response.setContentType("text/html");
PrintWriter out = response.getWriter();
out.println("discover=" + running);
public void run()
running = true;
System.out.println("thread running...");
* do some stuff here....
running = false;
System.out.println("thread stopped...");
i tried this servlet on tomcat 3.2.3 and 3.3a and the thread run. i can see the 'thread start', 'thread running' and 'thread stopped' on the tomcat console. but, when i use tomcat 4, i can only see 'thread start' on the console, which show that the run() is not execute...... y?... please help me.......

Background process zffd terminated due to missing confirmation

Hi all,
 In production system loading 2500000 lak data load to DSO when try to activate the DSO throwing below error. Kindly guide me on this.
Error:
Background process <ZASDFFF> terminated due to missing confirmation
Thanks

Hello,
To resolve this issue, you should make some adjustments to the DataStore
object parameters, then you should be able to activate the request.
Please make the following adjustments in transaction RSODSO_SETTINGS
(you can adjust this for each DataStore object):
1) Maximum package size (for activation).
 This you should reduce to 10000 (if the value is higher than that)
 Then the package processing will be less time consuming.
2) Maximum wait time for process (for activation)
 This could be increased to e.g. 600 (if the value is lower than this)
See SAP note 1118205 for further information.
Best Regards
Barry

Data load Error using Process chain

Hi,
In NW2004s when I schedule delta loads for 2LIS_11_VAITM using process chains, when there is zero delta, the manage screens of the infocubes show green light with zero records correctly whereas the process chain log display shows red. The details of the process monitor show zero records. Is this right? I assume that even if there is zero delta, the log must show green and all the subsequent processes like activation of ODS, deleting of PSA, construction of indexes must be carried out. Please confirm. Is this a bug?
Thanks.
Param

Hi Victor,
Can you please advice how you solved issue as we are having similar issue where it works fine when loaded manually but throws communication error when process chain runs, following is error message..
Communication error: call FM RSSDK_DATA_REMOTE_GET
Thanks in advance for your help!!
Sandeep

Recursion in planning run: product T-B104 location PL1000 to be planned twice

Dear experts,
Please advice regarding the following situation. I execute the Production Planning Run. After this, I check the log and I get the following error : "Recursion in planning run: product T-B104 location PL1000 to be planned twice". Based on previous posts regarding similar situations, I run the trx. /SAPAPO/SNPLLC to identify the existing cycles resulting in the recursion of the planning run. After this, in the log I have the following error: "no supply sources were found for the model 000".
Does anybody have a clue regarding the cause of this ?
Thank you,

Hi,
This should be probably master data - please check if you have all the master data in APO. ( for eg PDS)

Background Processing? how schedule job for "System Error" Message .

Hello everyone,
in sap help i have read.
http://help.sap.com/saphelp_nw04/helpdata/en/5a/f72040599a8f5ce10000000a155106/frameset.htm
PCK> Monitoring>Message Monitoring-->Background Processing
you can schedule jobs for various background processing:
●     Archiving of messages processed successfully
●     Deletion of messages that are not to be archived
●     Restarting of messages with errors
●     Rescheduling of lost messages
can anyone understand this docu?
give me some introduction, how can i define and schedule these jobs ?
thx in advance!!
best regards
Yaning

Background Processing
Prerequisites
You have started the message monitor on the initial screen of the PCK and are in Background Processing.
Features
Archiving
You require two archiving sessions to archive messages:
●     One session to write the messages to the archive
●     One session to delete the persisted messages that have been archived
To do this, you schedule an archiving job, which implicitly schedules the sessions to write to the archive and delete the archived messages.
You can define one or more rules for each archiving job; these rules contain conditions that a message must meet in order to be archived by the job. At least one of the defined rules must be met for archiving to take place.
All information that is displayed for a message in message monitoring is archived, in addition to the audit log for each message.
Deleting
A standard delete job is created automatically. It runs once a day. You can schedule additional delete jobs; however, you cannot define rules for them.
Restarting
Instead of restarting messages with errors manually with message monitoring, you can schedule a job to automatically restart these messages. This is possible for all messages for which the number of defined restart attempts has been exceeded (messages with the system error status).
You can define one or more rules for each job to restart messages; these rules contain conditions that a message must meet in order to be restarted by the job. At least one of the defined rules must be met for archiving to take place.
Rescheduling
A standard job to reschedule messages is created automatically. The job runs once a day and ensures that messages lost as a result of database failure, for example, are rescheduled. You can schedule additional rescheduling jobs; however, you cannot define rules for them.
Thx Aamir.
But I mean the messages with errors in Adapter Engine , not in Intergrations Engine.
the situation is like Naveen Pandrangi's WebLog
II. Errors in Adapter Engine [XI : How to Re-Process failed XI Messages Automatically|XI : How to Re-Process failed XI Messages Automatically]
I
Till now we have seen how to resubmit/restart message that failed in Integration Engine. One a message makes it from Integration Engine to Adapter Engine, the message is flagged as checked in Integration Engine. The status of the message in Adapter engine does not effect the processed state in Integration Engine. Now if this message was asynchronous, XI will by default try to restart the message 3 times at intervals of 5 minutes before the status of the message is changed from Waiting to System Error .
*how can i schedule a job to automatically restart these messages with errors?
best regards
Yaning
Edited by: Yaning Liu on Aug 18, 2008 1:43 PM

Error occurred during CTM planning run

Hi folks,
Appreciate your co-operations!
I am facing the problem while running the CTM with the profile DEMO2.
CTM Planning Run gives one error and alert.
Error: Error occurred during CTM planning run
Technical Data
Message type__________ A (Cancel)
Message class_________ /SAPAPO/CTM1 (CTM: Messgaes)
Message number________ 401
Problem class_________ 1 (very important)
Number________________ 1
Environment Information
CTM Action____________ G
Message type__________ A
Alert: Internal error has occurred (<!> Segmentation fault)
Technical Data
Message type__________ E (Error)
Message class_________ /SAPAPO/CTM1 (CTM: Messgaes)
Message number________ 571
Message variable 1____ <!> Segmentation fault
Number________________ 1
Environment Information
CTM Action____________ G
Message type__________ C
Log file display
 04:37:59 optsvr_main.cpp(1363) 'SuperVisor' => Commandline : 4 respected parameters ...
Args:
m0001006
sapgw04
28812935
IDX=1
 04:37:59 optsvr_main.cpp(645) 'SuperVisor' * SAP APO CTM Engine [CTM/ctmsvr]
 04:37:59 optsvr_main.cpp(646) 'SuperVisor' * Copyright u00A9 SAP AG 1993-2009
 04:37:59 optsvr_main.cpp(647) 'SuperVisor' *
 04:37:59 optsvr_main.cpp(648) 'SuperVisor' * Version : 7.0_REL SP05, 407661, Nov 25 2009 22:59:47
 04:37:59 optsvr_main.cpp(649) 'SuperVisor' * Platform : ntamd64/x64
 04:37:59 optsvr_main.cpp(650) 'SuperVisor' * Interface : 2.0
 04:37:59 optsvr_main.cpp(651) 'SuperVisor' * Build date : Nov 25 2009 22:59:47 [1259186387]
 04:37:59 optsvr_main.cpp(652) 'SuperVisor' * Build machine : PWDFM163
 04:37:59 optsvr_main.cpp(653) 'SuperVisor' * Latest change : 407661
 04:37:59 optsvr_main.cpp(654) 'SuperVisor' * NW release : 7100.0.3300.0
 04:37:59 optsvr_main.cpp(655) 'SuperVisor' * Perforce branch: 7.0_REL
 04:37:59 optsvr_main.cpp(656) 'SuperVisor' *
 04:37:59 optsvr_main.cpp(676) 'SuperVisor' * Hostname : m0001006
 04:37:59 optsvr_main.cpp(677) 'SuperVisor' * OS version : 5.2.3790 (WinServer2003, NTAMD64) SP2.0 (Service Pack 2), SERVER ENTERPRISE TERMINAL SINGLEUSERTS
 04:37:59 optsvr_main.cpp(678) 'SuperVisor' * PID : 6768
 04:37:59 optsvr_main.cpp(683) 'SuperVisor' * CWD : D:\usr\sap\SC6\DVEBMGS04\log
 04:37:59 optsvr_main.cpp(684) 'SuperVisor' *
 04:37:59 core_sysinfo.cpp(453) 'SuperVisor' * free disk space: 190433 MB
 04:37:59 core_sysinfo.cpp(454) 'SuperVisor' *
 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' * Memory information:
 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' * physical memory: 10238 MB total, 6511 MB available [63% free]
 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' * page file : 73212 MB total, 60889 MB available [83% free]
 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' * virtual memory : 8388607 MB total, 8388499 MB available [99% free]
 04:37:59 optsvr_main.cpp(693) 'SuperVisor' *
 04:37:59 optsvr_main.cpp(783) 'SuperVisor' * running in invoke mode
 04:37:59 optsvr_rfcconnection.cpp(871) 'MsgMgr' <RFC> RfcPing(RFC_HANDLE=1) received in thread#6912
 04:37:59 optsvr_rfcconnection.cpp(692) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PARAM_SET' for sending of parameters/options
 04:37:59 optsvr_rfcconnection.cpp(703) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PARAM_GET' for receiving of parameters/options
 04:37:59 optsvr_rfcconnection.cpp(712) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PROGRESS' for progress informations
 04:37:59 optsvr_rfcconnection.cpp(721) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_MESSAGE' for messages
 04:37:59 optsvr_rfcconnection.cpp(730) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_RESULT' for (intermediate) result informations
 04:37:59 optsvr_rfcconnection.cpp(739) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_SYSINFO' for system informations
 04:37:59 optsvr_rfcconnection.cpp(748) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PERFINFO' for performance informations
 04:37:59 optsvr_rfcconnection.cpp(1269) 'MsgMgr' <RFC> skipping empty profile value [GENERAL] sPROFILE_CUST_ID
 04:37:59 optsvr_rfcconnection.cpp(1835) 'MsgMgr'
Sender/Receiver RFC_HANDLE#1:
<RFC> * RFC connection attributes:
Own Host : m0001006
Partner Host: m0001006
Destination : OPTSERVER_CTM01
Program Name: SAPLRCC_COMM_ENGINE
SystemNr : 04 SystemId : SC6
Client : 700 User : MBATCHA
Language : E ISO Language: EN
CodePage : 1100 Partner CP : 1100
Kernel Rel. : 701 Partner Rel.: 701
Own Release : 711 CPIC ConvId : 28812935
Own Type : E PartnerType : 3
Trace : RFC Role : S
<RFC> * RFC statistic information:
number of calls : 7
number of received data: 10569
number of sent data : 1349
overall reading time : 9073
overall writing time : 162
 04:37:59 optsvr_main.cpp(1110) 'SuperVisor' * Starting MainScript ...
 04:37:59 optsvr_main.cpp(1445) 'SuperVisor'
***************************** OPTSVR - OPTIONS ***************************** *
[CTM_PROFILE]
nCTMENGINEPACKAGESIZE = 500
sCOMPONENT = SCM
sCTMLOGFILE = ctm.DEMO2.0000_0001.20091201043758.log
sCTMLOGFLAG = 0
sCTMPROFILE = DEMO2
sRELEASE = 700
[general]
bUNICODE = true
nSLOT_MAXIMUM = 1
nSLOT_MINIMUM = 1
nSLOT_RESERVED = 1
sAPO_RELEASE = 700
sAPPLICATION = CTM
sExeDir = d:\apoopt\ctm\bin
sExeName = ctmsvr.exe
sHOST = m0001006
sInvokeMode = invoke
sLANGU = E
sMANDT = 700
sPRODUCT_NAME = APO
sPRODUCT_PATCHLEVEL = 0001
sPRODUCT_RELEASE = 700
sPROFILE = DEMO2
sSESSION = tju5Bmz21}6WVG0Sn6pv3W
sSYSTEM = SC6
sUNAME = MBATCHA
[init]
sSECTION0001 = INIT
sSECTION0002 = GENERAL
sSECTION0003 = PASSPORT
sSECTION0004 = CTM_PROFILE
[PASSPORT]
bIS_REMOTE = false
nACTION_TYPE = 1
nSERVICE = 1
sACTION = /SAPAPO/CTMB
sPRE_SYSID = SC6
sSYSID = SC6
sTRANSID = 2205DEDE7A5BF16DA07D001CC46CF90E
sUSERID = MBATCHA
************************** OPTSVR OPTIONS - END **************************** *
 04:37:59 core_msgmgr.cpp(440) 'MsgMgr' * Sending progress number 802 to OutputInterface from []
 04:37:59 core_supervisor.cpp(728) 'SuperVisor' <M> Invoking module 'CTMModelGenerator' [6]->download
 04:37:59 core_msgmgr.cpp(440) 'MsgMgr' * Sending progress number 806 to OutputInterface from [MG]
 04:37:59 ctm_modelgen.cpp(166) 'CTMModelGenerator' ======================================================================
 04:37:59 ctm_modelgen.cpp(167) 'CTMModelGenerator' MG::download
 04:37:59 core_msgmgr.cpp(1110) 'MsgMgr' renaming tracefile
 04:37:59 core_msgmgr.cpp(1111) 'MsgMgr' old name: optsvr_trace20091201_043759_1a70.log
 04:37:59 core_msgmgr.cpp(1112) 'MsgMgr' new name: ctm.DEMO2.20091201_043759_1a70.log
logfile reopened : Tue Dec 01 04:37:59 2009
logfile name : ctm.DEMO2.20091201_043759_1a70.log
 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PRDAT_RFC_READ
 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PLPAR_RFC_READ
 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_LOC_RFC_READ
 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PPM_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_TRANS_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_RES_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_SSTCK_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_CAL_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PLPER_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_INCMD_RFC_READ
 04:38:03 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
 04:38:03 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_DEM_RFC_READ
 04:38:04 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_SUP_RFC_READ
 04:38:04 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_UCMAP_RFC_READ
 04:38:04 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
 04:38:04 core_msgmgr.cpp(440) 'MsgMgr' * Sending progress number 810 to OutputInterface from [MG]
 04:38:04 ctm_modelgen.cpp(735) 'CTMModelGenerator' MG::download done
 04:38:04 ctm_modelgen.cpp(736) 'CTMModelGenerator' ======================================================================
 04:38:04 core_supervisor.cpp(750) 'SuperVisor' <M> Returning from module 'CTMModelGenerator' [6]->download = success [ctx size : 1]
 04:38:04 core_supervisor.cpp(692) 'SuperVisor' <SCR> Starting script 'CTM Solve' with 9.22337e+012 seconds left
 04:38:04 core_supervisor.cpp(692) 'SuperVisor' <SCR> Starting script 'CTM Match' with 9.22337e+012 seconds left
 04:38:04 ctm_executionmanager.cpp(102) 'SuperVisor' ======================================================================
 04:38:04 ctm_executionmanager.cpp(103) 'SuperVisor' statistics:
 04:38:04 ctm_executionmanager.cpp(104) 'SuperVisor' number of demands: 7
 04:38:04 ctm_executionmanager.cpp(105) 'SuperVisor' ======================================================================
 04:38:04 ctm_executionmanager.cpp(107) 'SuperVisor' ======================================================================
 04:38:04 ctm_executionmanager.cpp(108) 'SuperVisor' parameters:
 04:38:04 ctm_executionmanager.cpp(118) 'SuperVisor' time continuous planning
 04:38:04 ctm_executionmanager.cpp(125) 'SuperVisor' backward scheduling
 04:38:04 ctm_executionmanager.cpp(184) 'SuperVisor' CBCLP enabled
 04:38:04 ctm_executionmanager.cpp(457) 'SuperVisor' ======================================================================
 04:38:04 core_supervisor.cpp(728) 'SuperVisor' <M> Invoking module 'CtmEngine' [7]->run
 04:38:04 ctm_executionmanager.cpp(523) 'SuperVisor' ======================================================================
 04:38:04 ctm_executionmanager.cpp(524) 'SuperVisor' EM::execute for packet 1
 04:38:04 ctm_executionmanager.cpp(1570) 'SuperVisor' EM::execute for packet 1 done
 04:38:04 ctm_executionmanager.cpp(1571) 'SuperVisor' ======================================================================
 04:38:04 core_supervisor.cpp(750) 'SuperVisor' <M> Returning from module 'CtmEngine' [7]->run = success [ctx size : 1]
 04:38:04 core_supervisor.cpp(728) 'SuperVisor' <M> Invoking module 'CTMModelGenerator' [6]->upload
 04:38:04 ctm_modelgen.cpp(1097) 'CTMModelGenerator' ======================================================================
 04:38:04 ctm_modelgen.cpp(1098) 'CTMModelGenerator' MG::upload of packet 1
<e> 04:38:05 ctmsvr_script.cpp(229) 'SuperVisor' <!> STRING EXCEPTION : <!> Segmentation fault
 04:38:05 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
 04:38:05 optsvr_main.cpp(1166) 'MsgMgr' Current check values:
[CHECK_EQUAL]
[CHECK_UPPERBOUND]
nPEAK_MEMORY_NTAMD64 = 45344
[CHECK_LOWERBOUND]
 04:38:05 optsvr_main.cpp(1209) 'MsgMgr' Performance values:
bSuccess false
nCPU_TIME 0
nPEAK_MEMORY 45344
nPEAK_VIRTUAL_BYTES 141844
nREAL_TIME 6
tracefile ctm.DEMO2.20091201_043759_1a70.log
 04:38:05 optsvr_main.cpp(1235) 'MsgMgr' Performance Monitor values:
ENGINE_VERSION 7.0_REL SP05, 407661, Nov 25 2009 22:59:47
nCPU_TIME 0
nHD_FREESPACE 190433
nPEAK_MEMORY 45344
nPEAK_VIRTUAL_BYTES 141844
nREAL_TIME 6
 04:38:05 optsvr_dsr.cpp(96) 'MsgMgr' <writeDSRdata> tracing not active => no DSR written
 04:38:05 optsvr_main.cpp(1256) 'SuperVisor'
Finished->FAILED ...
 04:38:05 core_memmgr.cpp(564) 'MsgMgr' transferring memory of heap 6912 to main heap
 04:38:05 core_memmgr.cpp(606) 'MsgMgr' finished transfer of heap 6912
 04:38:05 optsvr_rfcconnection.cpp(1835) 'MsgMgr'
Sender/Receiver RFC_HANDLE#1:
<RFC> * RFC connection attributes:
Own Host : m0001006
Partner Host: m0001006
Destination : OPTSERVER_CTM01
Program Name: SAPLRCC_COMM_ENGINE
SystemNr : 04 SystemId : SC6
Client : 700 User : MBATCHA
Language : E ISO Language: EN
CodePage : 1100 Partner CP : 1100
Kernel Rel. : 701 Partner Rel.: 701
Own Release : 711 CPIC ConvId : 28812935
Own Type : E PartnerType : 3
Trace : RFC Role : S
<RFC> * RFC statistic information:
number of calls : 116
number of received data: 420457
number of sent data : 39262
overall reading time : 5.30093e+006
overall writing time : 3831
 04:38:05 optsvr_main.cpp(1332) 'MsgMgr'
OptimizeServer says GOOD BYE
Please help me to resolve this issue.
Thanks & Regards,
Khadar

Hi Khadar,
1) The information you have provided is the CTM optimiser log.
Run the job in background and in sm37 and click on job log &
analyse the exact error happened. In case if you are not able
to do, please provide the error log.
2) Check the livecache is stable in its operations when the job
runs (check with basis team)
3) Run consistency check for master data before CTM run
4) Check for any struck queues and clear those and rerun
5) If you feel more inconsistencies in system, run livecache
consistency and rerun CTM run
Regards
R. Senthil Mareeswaran.

Error: The request could not be submitted for background processing

I'm getting an intermittent error in our custom reporting application using Crystal Reports Server XI R2 w/ SP1:
Error in File C:\WINDOWS\TEMP\{F6D30537-956A-458C-96D0-84ECB520D688}.rpt: The request could not be submitted for background processing.
I'm using the Report Application Server XI Release 2 .NET SDK. This is the code that produces the exception (The export type is pdf):
ByteArray ba = this.reportClientDocument.PrintOutputController.Export(ConvertExportReportTypeToCrystalReportExportType(),0);
The error is also logged by Business Objects in the crystalras log file:
ErrorLog 2007 12 3 12:24:56.531 6624 4872 (\servers\ras\dtsagent\reporthandler.cpp:11592): CReportHandler::buildReportViewerError: CSResultException thrown. ErrorSrc:"CRPE" FileName:"\servers\ras\dtsagent\reporthandler.cpp" LineNum:11588 ErrorCode:685 ErrorMsg:" Error in File C:\WINDOWS\TEMP\{F6D30537-956A-458C-96D0-84ECB520D688}.rpt:
The request could not be submitted for background processing." DetailedErrorMsg:""
This has been happening regularly about once a week, at which point the RAS fails and no more reports can be run until the CMS and RAS servers have been restarted.
Has anyone else had this problem, or have any ideas?
Thanks

It was not a bug (not in all cases anyhow), but it is one of those error message that might as well say; something went wrong. I wrote an article on the most likely cases for the error and the article can be downloaded from here;
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50a6f5e8-8164-2b10-7ca4-b5089df76b33
See if the above article will help you out. Please note that having the latest SP / FP is step one. The downloads page is here;
http://service.sap.com/sap/bc/bsp/spn/bobj_download/main.htm
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup

Error - Background Processing: Planning Run

Similar Messages

Maybe you are looking for