Error occured in background job......

Hi,
SUDDENLY ALL THE BACK GROUND JOBS  STATUS  ARE SHOWING CANCELLED. WHAT CAN BE REASONS?
ashutosh

sir,
Actually what happend,  all background job  automatic   showing their status been canceld due to unknow problem.
what's should be the reasons?
ASHUTOSH

Similar Messages

  • Internal error occurs in background job scheduling

    Hi Experts,
    We are facing an error message "Internal error occurs in background job scheduling" while trying to execute a custom report(Z report) in background in SA38.
    Please find the following observation on our side on this message.
    1) This message is not coming for only one report not for others.
    2) SU53 screen shot shows that SE38 check is failed, but the weird thing is not happening for other report.
    3) Persons having SE38 auhtorization are able to run this report.
    Please advise.
    Thanks in advance,
    Viven

    What is the message ID and number? Have you tried OSS search and debugging?
    What does this program do, in a nutshell?

  • An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))

    We are using DPM Version: 4.1.3465.0 with System Center 2012 Service Pack 1 to back up VMs in our Hyper V Cluster. We have a total of 37 VMs with a combination of 2008r2 servers and 2012 servers. One of our 2012 servers will not backup, and we consistently
    get the message "An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))". I have seen this error message when I Googled it, but cannot get past it. I have deleted the Protection Group and
    data and tried to re-create, but get the same errors. I also thought the the server might be mis-reporting the data size, but I expanded that to cover the replication data. I have also tried to perform consistancy checks multiple times with no luck. I have
    not seen a difinitive answer from my Google searches, so was hopeful someone has seen this also, and have had success in resolving. Currently this server has no backup recovery points, so I am worried if it does crash. I think I have the rollups installed
    as well.

    Hi Kelly,
    does the issue still persists?

  • Error in triggering background job

    HI, I've been facing an error which a background job is being scheduled. The scenario is something like this ...
    1) A third party schedulling system triggers a SAP job and monitors the progress
    2) In SAP, the master job is been copied with a different user name and then released for processing.
    3) There are multiple jobs which get triggered but there is one job which is causing a problem.
    4) The job makes a copy an stays in a scheduled status without getting released. While i try to manually release the job it give me an error that cannot create record in the database.
    5) Upon checking the system log it gives me this -  Error: INSERT background sched. table(job $$$$).
    There is already an entry for the specified job in the table TBTCS.
    6) While checking the TBTCS table i've found multiple entries out there. Should this table be empty or have information about the runtime of this job.
    Please help as this background job is causing concerns in archiving processess defined.
    Thankx in advance for your help.
    Arvind.

    the earlier problem of background job was solved by changing the  output device assigned to user wf-batch .
    regarding the transport request :
    when i was trying to execute the step : "Schedule bakgrd for missed deadlines " MANUEL it was giving me an option of SAVE AND SCHEDULE . which was creating the transport request . but when i executed it automatically it worked fine without asking a request to me ... i don't know why )-: ... probablly we can specify a different interval then the standard of three minutes and which will be transported (it's just a guess) . i have  executed it  automatically ...
    well thanks all for u r help

  • An unexpected error occurred while the job was running. (ID: 104)

    I'm getting this error in the event logs when trying to run a consistency check / sync with one of our file servers.
    This server was working fine, but w needed to migrate the data to a new partition (GPT) to allow it to expand past the 2TB limit of MBR partitions.  I added a new 3TB disk migrated the data and changed the drive letter to what the old partition was
    prior.  Since then we seem to get this error.
    I have installed the update roll up on both the server and the agent side.  I have also removed the server from the protection group then re-added it.  I've also removed and reinstalled the agent on the file server.
    Any help is appreciated!  Here's the full error from the DPM server:
    The replica of E:\ on server is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3106)
    An unexpected error occurred while the job was running. (ID: 104)

    Server Version is Windows 2012 R2 STD.  DPM is 4.2.1235.0 (DPM 2012 R2).  I expanded the production file server.  All that server does is host up file shares.
    I suspected the fact that I created a new volume and changed drive letter back to the original to be the source cause of the issue.  What I ended up doing is blowing away the backups from this server on disk and re-adding it to the protection group. 
    It now runs much longer, but still times out at random with the error mentioned above.
    Vijay:  The error was copied from Event Viewer.  Not sure what else you require?  Event ID is 3106 from DPM-EM.
    The DPM logs say:
    Affected area: E:\
    Occurred since: 2015-01-05 2:04:38 AM
    Description: The replica of Volume E:\ on servername is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery
    points, but new recovery points cannot be created until the replica is consistent.
    For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
     An unexpected error occurred while the job was running. (ID 104 Details: The semaphore timeout period has expired (0x80070079))
    Date inactivated: 2015-01-05 7:03:04 AM
    Recommended action: No action is required because this alert is inactive.
    Affected area: E:\
    Occurred since: 2015-01-05 2:04:38 AM
    Description: The replica of Volume E:\ on servername is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing
    recovery points, but new recovery points cannot be created until the replica is consistent.
    For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
     An unexpected error occurred while the job was running. (ID 104 Details: The semaphore timeout period has expired (0x80070079))

  • An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057)) After DPM 2012 SP1 to R2 Upgrade

    Hi,
    We have upgraded DPM 2012 SP1 to DPM 2012 R2 and OS is Windows 2012 standard.
    Now in File Protection Group, we receive error
    "An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))".
    This happens to only one Drive(X: Drive) of the PG server, other drive(Z: Drive) backup is working fine.
    We tried,
    Deleted entire protection group and recreated ,
    Ran consistency job 2 to 3 times.
    Ran Synchronize with consistency check.
    But every time It failed. Before upgrade it was working fine.
    Thanks

    Hi
    I would suggest opening a new case with MS to allow the DPM team to further look into the issue. Also the DPM 2012 R2 RollUp which addresses the (0x80070057)
    issue is Rollup 1 and the private will not be needed after applying Rollup 1. The Roll up is found here
    http://support.microsoft.com/kb/2904687/en-us
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your
    question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

  • ORA-20000 error when executing background jobs in BI System

    Hello Experts,
    We newly installed NW2004s System. Few BI related background jobs are showing Error no: 4 or Error no: 3 in SM50. Also few BI related background jobs are giving error "ORA-20000 occurred when executing SQL statement (parse error offset=0)". Please let me know what does Error 4 or 3 mean in SM50 and how to resolve Ora-20000 error?
    Thanks

    This may be to do with insufficient authorization for the user (for creating statistics for example). Check OSS note 963760.

  • Error while scheduling Background Job for User/Role Full Synchronization

    Hi all,
    We have installed RAR 5.3 Component and uploaded the authorization data & established the connectors to the backend system.
    We have performed all the post installation activities and everything is complete.
    When we have scheduled User -Full Synchronization with the Back End system as  a part of Post Installation Activity we are receiving the below error message
    "Error while executing the Job:Cannot assign an empty string to host variable 2."
    Also the VIEW LOG/ Terminate Job buttons are disabled  in this screen.
    Can somebody please help us in resolving the above issue
    Thanks and Best Regards,
    Srihari.K

    Hi,
    We are copy pasting the error log (Part as it is huge) below here. We could able to do Full Synch for Roles and also for Profiles. Only for User Synch we are getting this error and none of the users are sychronized to RAR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WILSONA of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WINDC of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WLADICHJ of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WUK of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user ZENGS of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user ZHENGL of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: All System Flag:false=====Last Batch Flag:true
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis loadUserData
    INFO: @@@ User sync completed for params true: Syskey List is [HL2-QAHR]
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob run
    WARNING: *** Job Exception: Cannot assign an empty string to host variable 2.
    com.sap.sql.log.OpenSQLException: Cannot assign an empty string to host variable 2.
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
         at com.sap.sql.types.VarcharResultColumn.setString(VarcharResultColumn.java:57)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:511)
         at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setString(PreparedStatementWrapper.java:355)
         at com.virsa.cscext.dao.CSCDAO.updateIgnoredUserData(CSCDAO.java:1388)
         at com.virsa.cscext.dao.CSCDAO.populateGenObjUser(CSCDAO.java:1169)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.populateGenObj(BatchRiskAnalysis.java:868)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.insertBAPIUserData(BatchRiskAnalysis.java:142)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.loadUserData(BatchRiskAnalysis.java:390)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1275)
         at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
         at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob setStatus
    INFO: Job ID: 13 Status: Error
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
    FINEST: --- @@@@@@@@@@@ Updating the Job History -
    2@@Msg is Error while executing the Job:Cannot assign an empty string to host variable 2.
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
    INFO: -
    Background Job History: job id=13, status=2, message=Error while executing the Job:Cannot assign an empty string to host variable 2.
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
    INFO: -
    Complted Job =>13----
    Please let us know how to resolve this error
    Thanks and Best Regards,
    Srihari.K

  • Error in Schedule Background Job for Deadline Monitoring of swu3

    While Auto Customization swu3 i am getting error message 'Output device "" not known' in 'Schedule Background Job for Deadline Monitoring'
    Please advice what could be cause of it

    the earlier problem of background job was solved by changing the  output device assigned to user wf-batch .
    regarding the transport request :
    when i was trying to execute the step : "Schedule bakgrd for missed deadlines " MANUEL it was giving me an option of SAVE AND SCHEDULE . which was creating the transport request . but when i executed it automatically it worked fine without asking a request to me ... i don't know why )-: ... probablly we can specify a different interval then the standard of three minutes and which will be transported (it's just a guess) . i have  executed it  automatically ...
    well thanks all for u r help

  • Write the Error log from background Job to the Spool request

    Hi ,
    I have a situation where in i need to capture the error log of a Z program which runs as a background job and write that log into the spool request. My Z program calls runs RSEINB00 program using the SUBMIT statement. When this Job fails the error log can be seen in SM37. But i need this error log to be sent in to a spool.
    I can read the error log using the BP_JOBLOG_READ FM and can also create a spool using the RSPO_SPOOL_OPEN FM.
    The problem is, when the Submit statement executes, due to internal valdation in the RSEINB00 program the program terminates. Due to this it is not able to perform the SY-SUBRC Check and thus doesn't read the log.
    Can anybody suggest me how to overcome this problem. I am attaching the code for your refernece.
    SUBMIT RSEINB00
           USING SELECTION-SET 'TEST2'
                           TO SAP-SPOOL
                           LIST NAME 'LOCL'
                           IMMEDIATELY space
                           KEEP IN SPOOL 'X'
           AND RETURN.
    <b>If sy-subrc <> 0.</b>           
                 CALL FUNCTION 'BP_JOBLOG_READ'
                  EXPORTING
                    CLIENT                      = SY-MANDT
                    JOBCOUNT                    = i_tbtco-jobcount
                    JOBLOG                      = i_tbtco-joblog
                    JOBNAME                     = i_tbtco-jobname
                   TABLES
                     JOBLOGTBL                   = l_joblog
                 IF SY-SUBRC <> 0.
                 else.
                    message i002 with l_joblog-msgv1.
                 ENDIF.
    <b>
    ENDIF.</b>
    Rgds,
    Kewal
    P.S. : any other approach to solve this problem will be appreciated too and the points will be rewarded suitably.

    If I select a job in SM37 and I click on "spool" I get a list with separate spool entries for each of the steps, e. g.
    Programmname/Kommand   Programmtyp   Spoolliste
    Z_MM_STAT_UPDATE_WERK  ABAP             1707445
    ZSLEEP                 Ext. Kommando
    Z_MM_STAT_UPDATE_WERK  ABAP             1707459
    ZSLEEP                 Ext. Kommando
    Z_MM_STAT_UPDATE_MARA  ABAP             1721423
    ZSLEEP                 Ext. Kommando
    Z_MM_STAT_UPDATE_WERK  ABAP             1721437
    Z_MM_STAT_UPDATE_MARA  ABAP             1721446
    Z_MM_STAT_UPDATE_WERK  ABAP             1721447
    Z_MM_STAT_UPDATE_VKORG ABAP             1721471
    ZSLEEP                 Ext. Kommando
    Z_MM_STAT_UPDATE_VKORG ABAP             1721521
    ZSLEEP                 Ext. Kommando
    Z_MM_STAT_UPDATE_VKORG ABAP             1721816
    It's in German but I'm sure you get the idea. For each Z_MM_STAT_UPDATE and variant I have a separate spool list that I can display.
    Markus

  • Error messege in Background Job(SM37) -  Please enter a valid date

    Hi all,
    background job which is scheduled in sm37 is giving error for dated 01.01.2009 to 30.01.2009.
    But before 31.12.2008 it was working fine
    error messege-
    This is happening in Production and developement  client.
    While running the report it showing the error messege- Please enter a valid date
    One function module is used in the report for geting fiscal year from date.
    it is showing the following error messege for perticular date range- 01.01.2009 to 30.01.2009.
    GM_GET_FISCAL_YEAR
    Error
    Fiscal year variant V3 not defined or maintained for date 01.01.2009
    Thanks
    Susanta

    Hi,Because this datein the past

  • Error occurs in background work process.

    Respected Guru's,
    error occurs in two background work process, i have displayed the trace files of both the bgd work process.
    How to rectify this error ?
    Further, can you please help me in identifying the problem, please suggest me good material which gives steps for troubleshooting such error in the developer's and system trace.
    Thank you.
    Dayanandan.a
    Developer trace file for BGD WP 1
    trc file: "dev_w12", trc level: 1, release: "620"                                             
    ACTIVE TRACE LEVEL           1                                                             
    ACTIVE TRACE COMPONENTS      all, M                                                        
    M  systemid   560 (PC with Windows NT)                                                        
    M  relno      6200                                                                            
    M  patchlevel 0                                                                               
    M  patchno    251                                                                             
    M  intno      20020600                                                                        
    M  pid        2864                                                                            
    M                                                                               
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc12 2864) [dpxxdisp.c   1016]                      
    M  <EsNT> Memory Reset enabled as NT default                                                  
    M  calling db_connect ...                                                                     
    M  db_connect o.k.                                                                            
    M  rdisp/reinitialize_code_page -> 0                                                       
    M                                                                               
    M Tue Jul 30 10:22:53 2002                                                                    
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD    
    M                                                                               
    M Tue Jul 30 10:22:55 2002                                                                    
    M  *** ERROR => SlicLockSema: sema locked [slicshm.c    89]                                   
    M  *** ERROR => SlicShmInit: SlicLockSema failed [slicshm.c    231]                           
    M  *** ERROR => SlicValBufInit: cannot initialize SHM [slicshm.c    299]                      
    M  *** ERROR => SlicValBufRead: license buffer not initialized [slicshm.c    329]             
    M  *** ERROR => SlicCheckBuf: some error reading license buffer contents [slicshm.c    419]   
    M                                                                               
    M Wed Jul 31 00:00:49 2002                                                                    
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD    
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD    
    M Thu Aug 01 00:00:49 2002                                                                               
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD                       
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD                       
    M                                                                               
    M Fri Aug 02 00:00:49 2002                                                                               
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD                       
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020802.AUD                       
    M                                                                               
    M Fri Aug 02 00:14:09 2002                                                                               
    M  *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c  235]  
    M  ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   10641]                                           
    M  ***LOG R18=> ThPrivCommit, ThICommit () [thxxhead.c   11307]                                                  
    M  in_ThErrHandle: 1                                                                               
    M  *** ERROR => ThPrivCommit: ThICommit (step 4, th_errno 9, action 2, level 1) [thxxhead.c   8277]              
    M                                                                               
    M  Info for wp 12                                                                               
    M                                                                               
    M    stat = 4                                                                               
    M    reqtype = 4                                                                               
    M    act_reqtype = 4                                                                               
    M    tid = 12                                                                               
    M    mode = 0                                                                               
    M    len = 24                                                                               
    M    rq_id = 6638                                                                               
    M    rq_source = 1                                                                               
    M    last_tid = 12                                                                               
    M    last_mode = 0                                                                               
    M    rfc_req = 0                                                                               
    M    report = >                                        <                                                         
    M    action = 16                                                                               
    M    tab_name = >                              <                                                                 
    M   
    M                                      
    M  Modeinfo for User T12/M0            
    M                                      
    M    tm state = 2                      
    M    uid = 13                          
    M    term type = 0x0                   
    M    display = 0x0                     
    M    cpic_no = 0                       
    M    cpic_idx = -1                     
    M    usr = >SAPUSER     <              
    M    terminal = >                    < 
    M    client = >800<                    
    M    conversation_ID = >        <      
    M    appc_tm_conv_idx = -1             
    M    imode = 3                         
    M    mode state = 0x42                 
    M    th_errno = 9                      
    M    async_receives = 0                
    M    cpic_receive = 0                  
    M    em handle = 2                     
    M    roll state = 4                    
    M    abap state = 4                    
    M    em state = 3                      
    M    eg state = 1                      
    M    lock = 0                                                                               
    Developer's trace file for BGD WP 2
    trc file: "dev_w13", trc level: 1, release: "620"                                             
    ACTIVE TRACE LEVEL           1                                                             
    ACTIVE TRACE COMPONENTS      all, M                                                        
    M  systemid   560 (PC with Windows NT)                                                        
    M  relno      6200                                                                            
    M  patchlevel 0                                                                               
    M  patchno    251                                                                             
    M  intno      20020600                                                                        
    M  pid        2872                                                                            
    M                                                                               
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc13 2872) [dpxxdisp.c   1016]                      
    M  <EsNT> Memory Reset enabled as NT default                                                  
    M                                                                               
    M Tue Jul 30 10:21:44 2002                                                                    
    M  calling db_connect ...                                                                     
    M  db_connect o.k.                                                                            
    M                                                                               
    M Tue Jul 30 10:22:25 2002                                                                    
    M  rdisp/reinitialize_code_page -> 0                                                       
    M                                                                               
    M Tue Jul 30 10:22:53 2002                                                                    
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD    
    M                                                                               
    M Wed Jul 31 00:00:52 2002                                                                    
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD    
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD    
    M                                                                               
    M Thu Aug 01 00:00:49 2002                                                                    
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD    
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD                      
    M                                                                               
    M Fri Aug 02 00:00:51 2002                                                                               
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD                      
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020802.AUD                      
    M                                                                               
    M Fri Aug 02 00:14:09 2002                                                                               
    M  *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c  235] 
    M  ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   10641]                                          
    M  ***LOG R18=> ThPrivCommit, ThICommit () [thxxhead.c   11307]                                                 
    M  in_ThErrHandle: 1                                                                               
    M  *** ERROR => ThPrivCommit: ThICommit (step 4, th_errno 9, action 2, level 1) [thxxhead.c   8277]             
    M                                                                               
    M  Info for wp 13                                                                               
    M                                                                               
    M    stat = 4                                                                               
    M    reqtype = 4                                                                               
    M    act_reqtype = 4                                                                               
    M    tid = 13                                                                               
    M    mode = 0                                                                               
    M    len = 24                                                                               
    M    rq_id = 6643                                                                               
    M    rq_source = 1                                                                               
    M    last_tid = 13                                                                               
    M    last_mode = 0                                                                               
    M    rfc_req = 0                                                                               
    M    report = >                                        <                                                        
    M    action = 16                                                                               
    M    tab_name = >                              <                                                                
    M                                                                               
    M  Modeinfo for User T13/M0                                                                               
    M                                                                               
    M    tm state = 2                      
    M    uid = 14                          
    M    term type = 0x0                   
    M    display = 0x0                     
    M    cpic_no = 0                       
    M    cpic_idx = -1                     
    M    usr = >SAPUSER     <              
    M    terminal = >                    < 
    M    client = >800<                    
    M    conversation_ID = >        <      
    M    appc_tm_conv_idx = -1             
    M    imode = 3                         
    M    mode state = 0x42                 
    M    th_errno = 9                      
    M    async_receives = 0                
    M    cpic_receive = 0                  
    M    em handle = 3                     
    M    roll state = 4                    
    M    abap state = 4                    
    M    em state = 3                      
    M    eg state = 1                      
    M    spa state = 3                     
    M    enq state = 0                     
    M    next hook = T-1/U-1/M255          
    M    master hook = T-1/U-1/M255        
    M    slave hook = T-1/U-1/M255         
    M    debug_tid = -1                    
    M    mode type = 0x1                   
    M    debug = 0                         
    M    lock = 0                          
    M                                      
    M                                      
    M Sat Aug 03 00:00:55 2002
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020803.AUD
    M                                                                               
    M Sun Aug 04 00:00:49 2002                                                                
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020803.AUD
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020804.AUD
    M                                                                               
    M Mon Aug 05 00:00:49 2002                                                                
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020804.AUD
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020805.AUD
    M                                                                               
    M Tue Aug 06 00:00:49 2002                                                                
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020805.AUD
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020806.AUD

    Thank you, Bhaskar,
    I have performed consistency check for temse objects and all the comments are displayed in red color.
    Does it mean that objects are inconsistent. But, no comments states that object are inconsistent.
    I have attached the comments displayed,
    Consistency check of table TST01 / TemSe objects
    This comment occurs repeatedly, Unable to access the related file           Length = 0
    Incorrect number of data lines in TST03              
    Object with part number 1 missing
    Object reset                     Length = 0
    The related file has an incorrect length
    Consistency check of table TST03 / TemSe data
    No object found in TST01
    May i delete all objects, as all the comments are red in color.
    Dayanandan.A

  • Error in active background jobs

    Hi All,
    i facing problem while cosing the job
    i have written the code
          IF NOT p_imm IS INITIAL.
            CALL FUNCTION 'JOB_CLOSE'
              EXPORTING
                jobcount             = l_f_jobcount
                jobname              = l_f_jobname
                strtimmed            = l_flg_start_sofort
              EXCEPTIONS
                cant_start_immediate = 1
                invalid_startdate    = 2
                jobname_missing      = 3
                job_close_failed     = 4
                job_nosteps          = 5
                job_notex            = 6
                lock_failed          = 7
                OTHERS               = 8.
    COMMIT WORK .
    and it is not showing any error and it should finished the job in sm37 but i am always getting the ststus active rather than finished.
    please suggest what could be the reason
    Thanks,
    Madhu

    hi all,
    please help me on this..
    when there is no data then background job finish the job and in the job log it shows thst no valid data for selection. but if there si any data ... the job status stil active and it never get finished.... and finaly it get cancelled.
    even while dubugging it never shows sy-subrc value other than 0. even when i run the background job manually for the submit sdt program it finish the job. I don't understand the reason why it is in active stage while executing id dialog.
    Please mention if there is any parameter value missing ..
    my code as follows..
    do n times.  "n muber of jobs
    Start Immediately
          IF NOT p_imm IS INITIAL.
    l_flg_start_sofort = 'X'.
    (1)Open the job
          CALL FUNCTION 'JOB_OPEN'
            EXPORTING
              jobname          = l_f_jobname
            IMPORTING
              jobcount         = l_f_jobcount
            EXCEPTIONS
              cant_create_job  = 1
              invalid_job_data = 2
              jobname_missing  = 3
              OTHERS           = 4.
          IF sy-subrc <> 0.
            MESSAGE e032(sxmsf) WITH l_f_jobname.
          ENDIF.
    (2)Report start under job name
          SUBMIT (g_c_prog_c1_lo)
                 WITH s_partn IN r_partn
                 WITH s_parro IN s_parro
                 WITH s_grvsy IN s_grvsy
                 WITH s_lgreg IN s_lgreg
                 WITH p_updab = p_updab
                 WITH p_updbi = p_updbi
                 WITH p_enqal = p_enqal
                 TO SAP-SPOOL WITHOUT SPOOL DYNPRO
                 VIA JOB l_f_jobname NUMBER l_f_jobcount AND RETURN.
    *(3)Job closed when starts Immediately
          IF NOT p_imm IS INITIAL.
            CALL FUNCTION 'JOB_CLOSE'
              EXPORTING
                jobcount             = l_f_jobcount
                jobname              = l_f_jobname
                strtimmed            = l_flg_start_sofort
              EXCEPTIONS
                cant_start_immediate = 1
                invalid_startdate    = 2
                jobname_missing      = 3
                job_close_failed     = 4
                job_nosteps          = 5
                job_notex            = 6
                lock_failed          = 7
                OTHERS               = 8.
          COMMIT WORK .
          ADD 1 TO g_cnt_job.
          l_r_tbtcjob-jobcount = l_f_jobcount.
          l_r_tbtcjob-jobname = l_f_jobname.
          l_r_tbtcjob_previous = l_r_tbtcjob.
          IF NOT l_flg_first_job IS INITIAL.
            g_v_tbtcjob_first = l_r_tbtcjob.
          ENDIF.
          CLEAR: l_flg_first_job.
        ENDDO.
    thanks

  • Error handling in background jobs

    Dear All,
    I have a program to update certain tables which I schedule as a background job.
    I need to find a way to handle errors and communicate the update status to the administrator/ job monitor.
    Some of the methods I can think of are:
    1. Use write statements in the program to write the status. Admin/ Job monitor can look up the job spool in SM37 and get the status.
    2. Store the status against each updated table in a custom table. Admin / Job monitor can check thru SE16.
    Is there any other way to communicate the job status.
    Thanks and Regards,

    I used the option :
    Use write statements in the program to write the status. Admin/ Job monitor can look up the job spool in SM37 and get the status. The same has been implemented in production by now.
    Cheers.
    Ashwin

  • Print error scheduling a background job

    HI
    I am using
    Transaction F110 – Automatic Payment.
    When I am scheduling job for printing in background,I am getting error
    The error <Status Text in spool > states front end unavailable.
    Any inputs asap pls

    You are getting the error because, the printer selected to print the output trying to use front end default printer. You might have selected LOCL as the printer. Chage the printer.
    Regards
    Sridhar

Maybe you are looking for