SMD: E2E_CONTROLLER jobs do not schedule in SM37

Hi!
I fighting with set up of SMD functions Workload Analysis, Change Analysis in SAP Solution Manager.
The set up of all the steps (SMD for Managing System, SMD for Managed system are in status "green", Wily 8 is installed, SMD agent is running) run succesfully. 
Unfortunately I cannot detect valid E2E_CONTROLLER jobs in SM37. As a result no current data are available.
I recently updated my SOLMAN from SP18 to EhP1 and Wily Introscope from version 7.2. to 8.
Questions:
Are there any changed regarding the E2E_CONTROLLER jobs with SOLMAN 7.0 EHP1?
Is it possible to re schedule the E2E_CONTROLLER jobs in order to see current data in tabs WA and CA?
Thank you very much!
regards
Jürgen

Hi Jürgen,
with EhP1 the Extractor Framework has been changed, there is a new job "EFWK Resource Manager" which takes care of the ressources used for data extraction. You can use the "Extractor Framework Administration" in the Root Cause Analysis Workcenter to check if the extractors are running.
More information can be found in the Workload Analysis User Guide for EhP1 under:
http://service.sap.com/diagnostics --> User Guides --> Workload Analysis.
Best regards
Michael

Similar Messages

  • BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED

    Hello,
    To generate the log report, /VIRSA/ZVFATBAK program is scheduled on hourly basis but some time report doesn't get generated and if we see the background job then it shows sucessfully finished.
    If we see the maually the log report for FFID then below error message is displayed.
    " BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED"
    Can anyone guide me to solve the issue.
    Thanks in advance.
    Best Regards,
    Prashant Dubey

    Hi,
    once chk the status of the job by selecting that and check job status(cltr+shift_f12)
    since it was periodically scheduled job there will be a RELEASED job after every active job..
    so try to copy that into another job using copy option and give some new name which u have to remember...
    the moment u copy u can find the same copied job in SCHEDULED status...
    from here, try to run it again on hourly basis....
    After copying the job u can unschedule the old released job to scheduled otherwise 2 will run at a time...
    rgds,

  • GRC FF 5.1 BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED

    I've had FF installed in prod for 4 days. I just now got around to running the /VIRSA/ZVFATBAK job. However it only generates the logs for the last 24 hours. I know when you schedule the batch run to run hourly this will be resolved but I wanted to run the /VIRSA/ZVFATBAK job manually the first time because I knew it would take longer than an hour. Is there a variant I can use in SE38 to get these earlier logs generated?
    thanks for your help
    Dave wood

    You can create your variants in SE38. It does not come up with the programs. For Spools, you can get upto 3 days of logs while for the work logs, it will be a week max. But, i think you can change the system parameters in such a way you can retrieve the logs of the jobs for more than a week.
    Thanks
    Sudhan Shan

  • Charms :  Background job not scheduled (normal correction) ?

    Hi,
    I am trying to run a dry cycle for normal correction but when i go to task plan in any ticket to release a request. When i schedule this job " release a request" , i dont see any job running in background in SM37. I think job is not gettin sceduled properly.
    Please help me out

    Hi,
    All right. We need to dig this one
    I guess you schedule the import by going the the tasklist
    and you get a red flag for this activity in the calendar ? do you have any error message ?
    If the messagein the task-list is not self-explanatory you can check the SLG1 log in SOLMAN. Which error message do you get there. (select the correct time frame, the log could be big)
    My guess is that some S_RFC authorisation is still missing there
    This authorisation is outside SAP_ALL and is often the cause of this kind of issue
    Tell me the error message and we will hopefully  fix this (I had the same kind of issue when I started last year)
    best regards Xavier

  • Schduling background jobs not showing in sm37

    Hi,
      I scheduled the  jobs : Z_MM_INVENTORY_REPORT, RM07MLBS on daily basis from 03/22/2011.Its running successfully upto 03/26/2011 daily,after that when iam checking on SM37 from 03/27/2011 to 03/31/2011 it showing schduled on 03/27/2011 not running. and remaining dates 28,29,30,31 not showing any thing(means not scheduling).
    what could may be the reason for not running that jobs.
    Thanku

    What is the status of the Job in SM37 ?
    and on
    and remaining dates 28,29,30,31 not showing any thing(means not scheduling).
    The periodical jobs create the next job, when the current job changes is status from Released to Active. Since your Job on 27th is having some issue, the Job for 28th has not been created, simillarly the rest.
    Regards,
    Sanujit

  • Some background jobs not shown in SM37

    Dear Friends,
    Some of my background jobs are not shown or visible in SM37. But, it is available in TBTCO, TBTCP & TBTCS tables. These jobs are scheduled in daily basis. These tables having records for all days of missed jobs.
    I dont know, why it is not comming in SM37. I tried in many search parameters in SM37 like prog. name, date and so on.
    These missed background jobs are not comes in spooler (SP01) also.
    Kindy, suggest me to find out the missed background jobs.
    Thanks in advance
    Regards,
    Rajagopal
    Chennai - INDIA.

    Hi rajagopalan,
    Normally this should not happen. Make sure the following in sm37:
    a. The start date is :  01.01.1800
    b. The end date is : 31.12.9999
    c. All the checkboxes (six checkboxes) are ticked.
    d. username = your username
    e. jobname = *
    SM37 gets records from the view V_OP (containing TBTCO and TBTCP)
    and filters for username using the field SDLUNAME.
    So you can basically cross-check if the count is atleast correct or the jobs were of different user (fieldname in the view/table) etc. (From SM37, you can export to excel and check the count)
    regards,
    amit m.

  • Scheduled jobs are not running DPM 2012 R2

    Hi,
    Recently upgraded my dpm 2012 sp1 to 2012 R2 and upgrade went well but i got 'Connection to the DPM service has been lost.(event id:917 and other event ids in the eventlog errors ike '999,997)'. Few dpm backups are success and most of the dpm backups consistenancy
    checks are failed.
    After investigating the log files and found two SQL server services running in the dpm 2012 r2 server those are 'sql server 2010 & sql server 2012 'service. Then i stopped sql 2010 server service and started only sql server 2012 service using (.\MICROSOFT$DPM$Acct).
    Now 'dpm console issue has gone (event id:917) but new issue ocurred 'all the scheduled job are not running' but manully i can able to run all backup without any issues. i am getting below mentioned event log errors 
    Log Name:      Application
    Source:        SQLAgent$MSDPM2012
    Date:          7/20/2014 4:00:01 AM
    Event ID:      208
    Task Category: Job Engine
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      
    Description:
    SQL Server Scheduled Job '7531f5a5-96a9-4f75-97fe-4008ad3c70a8' (0xD873C2CCAF984A4BB6C18484169007A6) - Status: Failed - Invoked on: 2014-07-20 04:00:00 - Message: The job failed.  The Job was invoked by Schedule 443 (Schedule 1).  The last step to
    run was step 1 (Default JobStep).
     Description:
    Fault bucket , type 0
    Event Name: DPMException
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: TriggerJob
    P2: 4.2.1205.0
    P3: TriggerJob.exe
    P4: 4.2.1205.0
    P5: System.UnauthorizedAccessException
    P6: System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal
    P7: 33431035
    P8: 
    P9: 
    P10: 
    Log Name:      Application
    Source:        MSDPM
    Date:          7/20/2014 4:00:01 AM
    Event ID:      976
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      
    Description:
    The description for Event ID 976 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event: 
    The DPM job failed because it could not contact the DPM engine.
    Problem Details:
    <JobTriggerFailed><__System><ID>9</ID><Seq>0</Seq><TimeCreated>7/20/2014 8:00:01 AM</TimeCreated><Source>TriggerJob.cs</Source><Line>76</Line><HasError>True</HasError></__System><Tags><JobSchedule
    /></Tags></JobTriggerFailed>
    the message resource is present but the message is not found in the string/message table
    plz help me to resolve this error.
    jacob

    Hi,
    i would try to reinstall DPM
    Backup DB
    uninstall DPM
    Install DPM same Version like before
    restore DPM DB
    run dpmsync.exe -sync
    finished
    Seidl Michael | http://www.techguy.at |
    twitter.com/techguyat | facebook.com/techguyat

  • Scheduled jobs do not run as expected after upgrading to 10.2.0.3 or 4

    FYI, we've had a ticket open for several days because our scheduled jobs (dbms_scheduler) would no longer run as scheduled after an upgrade to 10.2.0.4 on HPUX, couldn't find the solution by searching in metalink, nor did I find it here or using Google - obviously I wasn't searching correctly. There is a note id that references a set of steps that appears to have resolved our problem. I am putting this note out here so that if you encountered the same difficulty you may come across this note earlier in your troubleshooting efforts rather than later. The full title of the note is: 'Scheduled jobs do not run as expected after upgrading to either 10.2.0.3 or 10.2.0.4'. The Doc ID is: 731678.1.

    Thanks - our ticket should be getting closed out on it (our dba will be updating it), the scheduler has been running reliably since we took the steps in the doc mentioned.

  • F110 APP run - Payment run has been scheduled, but job was not released

    Dear Friends,
    We have made payment parameters, payment proposal, edit payment proposal and it was working fine upto that stage.
    Parameters have been entered
    Payment proposal has been created
    Payment proposal has been edited
    But when we selected payment run, immediately it showed the below status:
    Payment run has been scheduled 17.01.08 12:59:55
    Job was not released
    Also I'm not able to delete the Payment run made, fields are in disabled mode.
    Please guide me how to resolve this issue.
    Thanks in advance for your help.
    Regards,
    Dwarak.

    Dear Supriya,
    Thanks a lot for your immediate response.
    Still the same problem is existing even after one and half hours.
    ie.,
    Payment run has been scheduled 17.01.08 12:59:55
    Job was not released
    Could you please let me know which Tcode we have to go to release this inorder to solve this issue.
    As it is in the production client, it would be really helpful if you could let me know the details at the earliest.
    Thanks again.
    Regards,
    Dwarak.

  • BPM - Background Job for Reorganization = Not Scheduled

    Good afternoon, first of all thank you very much for the support they can provide. I have developed a JDBC interface -> BPM (Multimapping) which works well. Modify a Message Mapping in the BPM that I use for an RFC Lookup, I have added the Configurable Parameters in the BPM and Integration Directory and everything works fine at design time. But when running the interface at run time the message reaches the BPM and the error "error in BPE inbound Permanent processing".
    I have reviewed the Business Process Engine in the RWB and the item is Red Schedule Background Job for Reorganization and detail reads: "Background Job for Reorganization = Not Scheduled".
    As I can solve this problem. Thank you very much.

    Re: Importing trans request failed
    Re: Transports Erroring
    Re: What is RDDIMPDP .....
    have a look it may help you
    Message was edited by:
            Vinod Udapudi
    Message was edited by:
            Vinod Udapudi

  • SQL Server Agent Job is not running as per schedule

    I have a job that is supposed to run every 6 AM.  It was running last week but not this morning. 
    The big problem is that there are no error messages what so ever. I checked Agent History, SQL server logs and Windows system logs.
    I checked the schedule and it is set to run everyday and there are no limits on how long it is supposed to run and it is enabled.
    Did anyone get this problem before?

    Hi,
    Sometimes there are valid reasons a job will NOT kick-in on the scheduled time. Sometime ago, our database full backup job didn't start on time and in fact just
    got skipped over. Upon further investigation, a idiot started doing defragging on the target (destination) server without informing anybody in the enterprise and the previous days backup was running over 24+ hours instead of 2 hours. Sometime people cheat
    and try to enable/disable jobs and in those cases you may want to add notification if something like this happens. http://www.mssqltips.com/sqlservertip/1803/auto-alert-for-sql-agent-jobs-when-they-are-enabled-or-disabled/
    Sankar Reddy
    Blog: http://SankarReddy.com/
    Twitter: http://twitter.com/SankarReddy13/

  • Scheduled GridControl jobs get not executed

    Hello,
    I have a really strange behaviour lately with the GridControl jobs:
    We have several GridControl jobs which are scheduled (e.g. from monday til friday at 05:00 am). In usual, they get executed at the scheduled time. But some of them
    don't get executed anymore from one day to the other (and don't appear in the "job activity" tab anymore). When looking up these jobs in the job library, the scheduled
    time is still correct. The agent on the target node hasn't stopped or dind't report any errors. It's just like someone has deleted these jobs (which is not the case).
    That's real bad since we rely on those jobs...
    Does anybody know this behaviour? It looks like a bug to me...
    Rgds
    JH

    Please refer the note 457792.1

  • Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.

    Dear Guru's,
                     I am having a problem during transportation. i am not able to transport to quality system.And the tp system logs shows following error messages:-
    WARNING: System GNQ. Warning.        20071105123442 :
    ERROR:       Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.
    ERROR:       I'm waiting 100 sec (Count: 1).
    WARNING:       (This warning is harmless if no further warnings follow.)
    Please help.
    Regards
    Akif

    Re: Importing trans request failed
    Re: Transports Erroring
    Re: What is RDDIMPDP .....
    have a look it may help you
    Message was edited by:
            Vinod Udapudi
    Message was edited by:
            Vinod Udapudi

  • Scheduled Brio/IR Jobs are not running as expected in EPM 11.1.2.2

    Hi All,
    We are observing some scheduled jobs are not running as expected,they are not running on the scheduled time.
    Given below are more details.
    We have 2 Jobs running at 6:00 AM daily based on single Recurring Time Event and it is observed that this jobs are not running on time(ex: 6:06 AM EST).
    I tried verifying Consolidate Job Status in workspace admin options and the v8_RecurtimeEvent table for any miss in the 'Next Run Time',
    but they were having the scheduled date/time of run.No clue from EPM Logs.
    Interesting observation is the same jobs are running after updating the schedule time a little bit further(ex: 6:06 AM to 6:07 AM),but again after some days
    the updated job(6:07 AM ) will stop running.
    Thanks,

    Put the IR job logs in TRACE:32 mode which will give more information in the logs . Refer this document link to put in TRACE mode :http://docs.oracle.com/cd/E17236_01/epm.1112/epm_install_troubleshooting_1112200.pdf
    Thanks,
    KK

  • Scheduled java job seems not to be started

    Hello,
    relying on the Composition Environment CE 7.1.1 SP2 I have created a custom Java job according to this tutorial: https://cw.sdn.sap.com/cw/docs/DOC-102724
    I have succesfully deployed my job and scheduled a task to execute the job every hour. However, the job does not seem to be started at all. I cannot find any clue that the task has been executed.
    What can I do about this?
    Kind regards
    Alexander

    Revoked question.

Maybe you are looking for