Caling fm with "update task"

hi frnds,
the requirement is one RFC fm (fm1) is called in back ground mode and one more function module (fm2) is called inside fm1 in update task.
the desired result is as soon as the fm1 is completed executed in background, (the commit work will happen) after then the fm2 should get executed and result can be seen in a transaction.
but the fm fm2 does not seem to be executing, (i am not getting the desired result) but if i execute the fm fm2 using se37 i am able to see the results in transaction.
the below code explains the exact flow.
code
function fmxx.
call function fmyy in update task
table = table1.
endfunction.
call function fmxx
in background
destination "XXYY010"
table = table2.
*****code
settings that have been made is FM2 is
1. radio button "update task" (X)
2. radio button "immediate start" (X)
could anyone please let me know why i am not getting the desired result.
my doubt is that
when the fm1 is executed in background, whether the fm2 will be sucessfully executed after the database provoke happens or not?
many thanks in advance.
regards,
Karthick C

just call the funtion do not use update task. The background task function will get executed only after a commit work so I guess it should be OK.
call function fmyy "no update task

Similar Messages

Running Function Module in Background with Update Task is not working

Hello Friends,
I have a "Z" Report Program where I am running this Report in Background using JOB_OPEN, JOB_SUBMIT, JOB_CLOSE. I am calling this in BADI.
In this Report I am calling another Function Module PRICES_POST which is a standard Function Module and in this FM there is another FM 'CKML_UPDATE_MATERIAL_PRICE IN UPDATE TASK'. Now when I am running the BADI these values are not being updated.
Friends I would like to know whether can we run Function Modules which are included with UPDATE TASK as Background Job program?
Kindly help me in providing your valuable suggestions in proceeding further.
Thanks and Regards
Pradeep Goli

Usually the sequence of CALLs in your report should look like
CALL FUNCTION 'CM_F_INITIALIZE'
 EXPORTING
 msg_on_screen = c_x.
CALL FUNCTION 'CKMS_BUFFER_REFRESH_COMPLETE'.
CALL FUNCTION 'PRICES_CHANGE'
 EXPORTING
 actual_bdatj = f_matpr-pp-bdatj
 actual_poper = f_matpr-pp-poper
 bukrs = p_bukrs
 budat = p_date
 xblnr = p_xblnr
 TABLES
 t_matpr = t_matpr.
READ TABLE t_matpr WITH KEY pp-xerror = ' '
 TRANSPORTING NO FIELDS.
IF sy-subrc <> 0.
 MESSAGE i046(ckprch).
ELSE.
 CALL FUNCTION 'PRICES_POST'
 EXPORTING
 i_bktxt = p_bktxt
 bukrs = p_bukrs
 lis_update = 'X'
 TABLES
 t_matpr = t_matpr.
ENDIF.
COMMIT WORK.
If you forget the COMMIT-WORK each and every FM called in UPDATE TASK will not be triggered.
Regards,
Raymond

Help with Update task

Hi friends,
In the below am trying to update a custom table using a call function in update task. I dont see the table getting updated can someone take a look at it and let me knw what the problem is? I have the commit work statement and also marked the function module as an update one in the attribute. Please help me . Thanks in advance! kathy
*& Include ZINBOUND_TEST
Report: ZINBOUND_TEST.
DATA: l_dest TYPE REF TO if_bgrfc_destination_inbound,
 l_unit TYPE REF TO if_trfc_unit_inbound,
 l_inb_dest TYPE bgrfc_main_i_dst,
 lv_matid TYPE /sapapo/matid,
 lv_matnr TYPE /sapapo/matnr,
 lv_maktx type /SAPAPO/MAKTX,
 lv_langu TYPE LANGU.
data: lt_product type STANDARD TABLE OF ZUPDATE,
 ls_product type ZUPDATE.
lv_matid = '123'.
lv_langu = 'E'.
lv_maktx = 'Materia1'.
CALL FUNCTION 'Z_TEST' IN UPDATE TASK
EXPORTING
 iv_matid = lv_matid
 iv_maktx = lv_maktx
 iv_langu = lv_langu .
COMMIT WORK.
select * from zupdate into corresponding fields OF TABLE lt_product.
if sy-subrc <> 0.
write 'no records added'.
else.
loop at lt_product into ls_product.
 write: / ls_product-MATID,
 ls_product-MAKTX.
endloop.
endif.
FUNCTION Z_TEST.
*"*"Update Function Module:
*"*"Local Interface:
*" IMPORTING
*" VALUE(IV_MATID) TYPE /SAPAPO/MATID
*" VALUE(IV_MAKTX) TYPE /SAPAPO/MAKTX
*" VALUE(IV_LANGU) TYPE LANGU
data: itab type standard table of zupdate,
wa_itab type zupdate.
wa_itab-matid = iv_matid.
wa_itab-maktx = iv_maktx.
wa_itab-langu = iv_langu.
append wa_itab to itab.
update zupdate from table itab .
ENDFUNCTION.
Edited by: ka reddy on Sep 24, 2009 4:14 PM
Edited by: ka reddy on Sep 24, 2009 4:15 PM
Edited by: ka reddy on Sep 24, 2009 4:16 PM
Edited by: ka reddy on Sep 24, 2009 4:17 PM
Edited by: ka reddy on Sep 24, 2009 4:21 PM

Hey Naimesh thanks for the reply. yeah i read that document way before and i started taking a stab at implementing it.
I started with update task to see how it behaves and then wanted to go with BGRFC tats when i had the update issue.
Now that am done with update i want to implement BGRFC.
I have modified the earlier prgm...Can you give me some ideas how to extend this? Thanks!
*& Include ZBGRFC_INBOUND_TEST
Report: ZBGRFC_INBOUND_TEST.
DATA: l_dest TYPE REF TO if_bgrfc_destination_inbound,
 l_unit TYPE REF TO if_trfc_unit_inbound,
 l_inb_dest TYPE bgrfc_main_i_dst,
 lv_matid TYPE /sapapo/matid,
 lv_matnr TYPE /sapapo/matnr,
 lv_maktx type /SAPAPO/MAKTX,
 lv_matid1 TYPE /sapapo/matid,
 lv_matnr1 TYPE /sapapo/matnr,
 lv_maktx1 type /SAPAPO/MAKTX,
 lv_langu1 TYPE LANGU,
 lv_langu TYPE LANGU.
data: lt_product type STANDARD TABLE OF ZUPDATE,
 ls_product type ZUPDATE.
lv_matid = '125'.
lv_langu = 'E'.
lv_maktx = 'Materia3'.
**--Get the inbound destination for BGRFC.
IF l_inb_dest IS INITIAL.
 SELECT SINGLE * FROM bgrfc_main_i_dst INTO l_inb_dest.
 ENDIF.
 l_dest = cl_bgrfc_destination_inbound=>create( l_inb_dest-destination ).
 l_unit = l_dest->create_trfc_unit( ).
CALL FUNCTION 'Z_TEST' IN BACKGROUND UNIT l_unit
EXPORTING
 iv_matid = lv_matid
 iv_maktx = lv_maktx
 iv_langu = lv_langu .
select * from zupdate into corresponding fields OF TABLE lt_product.
if sy-subrc <> 0.
write 'no records added'.
else.
loop at lt_product into ls_product.
 write: / ls_product-MATID,
 ls_product-MAKTX.
endloop.
endif.
Edited by: ka reddy on Sep 24, 2009 5:16 PM

Function module with UPDATE TASK

All,
Have a look at the below code. While debugging the control is not going inside the function module called using call function ...... in update task statement.
I believe the function module is not executed immediately, but is scheduled for execution in a special work process (update work process). For this purpose, the name of the function module including the passed actual parameters is stored as a log record in the database table VBLOG. If the statement is executed during the update task, the addition IN UPDATE TASK is ignored.
The actual execution is triggered by the statement COMMIT WORK which is not happening in this case. The formal parameters of the function module receive the values of the actual parameters from table VBLOG. How can I read the entries in VBLOG? Why the function module is not executed? Please suggest.
PERFORM bte_publish ON COMMIT LEVEL 9.
* syncron update
 COMMIT WORK AND WAIT.
* Publish business transaction events. The function module have
* to call as last update module!
FORM bte_publish.
IF NOT gvt_nodes IS INITIAL.
 CALL FUNCTION 'CUSTOMER_HIERARCHY_THROW_BTE' IN UPDATE TASK
 EXPORTING
 ffi_valid_on = knvh-datab
 fti_event_list = gvt_nodes
 fti_event_listx = gvt_nodesx.
ENDIF.
ENDFORM. " BTE_PUBLISH
Thanks,

Right Naren. But I need to check inside the update function module, whether it is calling the BTE function module I had configured and the code which I had put in it. Any ideas?
The COMMIT WORK is returning 4 and hence I believe it is not popping up another debuggin session in which the update FM runs.
Thanks,
Message was edited by: Somen

IN UPDATE TASK problem with CRM_ORDER_SAVE

Hello,
I'm trying to write a program to update one field on CRM order documents,
but i need to run it in background with update task.
- I created a function module and called CRM_ORDER_MAINTAIN and CRM_ORDER_SAVE functions
in this function module consequently,
- I set the tick "Update Module" and "Start.immed." in attributes of this function module,
- I called the function module with IN UPDATE TASK additon in a program
- I used COMMIT WORK command after calling this function module.
if I use IN UPDATE TASK addition ,
function is not working and not updating table VBLOG
and no return message in my workplace.
But same coding is working perfectly if I don't use IN UPDATE TASK.
Is there way to understand what's wrong, or a trace possibility?
Thanks in advance.
Bulent

Hello Bulent,
The entry in VBLOG is retained if the there is any error during the update work process otherwise it is removed from VBLOG.
Why don't you check the behavior of your FM in "update debugging"? That should throw more light on how the FM works in update work process.
@Ravi:
You can check with SO01 transaction if any error occurs
If there is an error during the update the record in VBLOG updated again. Check the online documentation on [UPDATE TASK|http://help.sap.com/abapdocu_702/en/abapcall_function_update.htm].
BR,
Suhas

What is Update Task Capability of a Function Module

Hi Folks,
My client wants me to create a function module with Update Task Capability.
Can you please know what is this and how to use this? I am completely new to this Update Task part. So please guide me accordingly.
Thanks in advance,
Siddarth

Hi Sir,
Please have a look below to understand update task capability of FM.
Plz do reward if useful
Thankx.
Why do we use this " In Update Task " ??
The main update technique for bundling database changes in a single database LUW is to use CALL FUNCTION... IN UPDATE TASK.
How do we Use ??
A typical R/3 installation contains dialog work processes and at least one update work process. The update work processes are responsible for updating the database. When an ABAP program reaches a COMMIT WORK statement, any function modules from CALL FUNCTION... IN UPDATE TASK statements are released for processing in an update work process. The dialog process does not wait for the update to finish. This kind of update is called asynchronous update.
What is the Use... ??
Asynchronous update is useful when response time from the transaction is critical, and the database updates themselves are so complex that they justify the extra system load
Real time scenario.
Suppose a user wants to change an entry in a database table, or add a new one. He or she enters the necessary data, and then starts the update process by choosing Save. This starts the following procedure in the ABAP program:
Firstly, the program locks the database entry against other users, using the enqueue work process (or the message server in the case of a distributed system). This generates an entry in the lock table. The user is informed whether the update was successful, or whether the lock could not be set because of other users.
If the lock is set, the program reads the entry that is to be changed and modifies it. If the user has created a new entry, the program checks whether a record with the same key values already exists.
In the current dialog work process, the program calls a function module using CALL FUNCTION... IN UPDATE TASK, and this writes the change details as an entry in table VBLOG.
When the program is finished (maybe after further dialog steps), a COMMIT WORK statement starts the final part of the SAP LUW. The work process that is processing the current dialog step starts an update work process.
Based on the information passed to it from the dialog work process, the update work process reads the log entries belonging to the SAP LUW from table VBLOG.
The update work process passes this data to the database for updating, and analyzes the return message from the database. If the update was successful, the update work process triggers a database commit after the last database change and deletes the log entries from table VBLOG.
If an error occurred, the update work process triggers a database rollback, leaves the log entries in table VBLOG, flags them as containing errors, and sends a SAPoffice message to the user, who should then inform the system administrator.
The corresponding entries in the lock table are reset by the update work process.
The system logs your request and executes the function module when the next COMMIT WORK statement is reached. The parameter values used to execute the function module are those current at the time of the call.
a = 1.
CALL FUNCTION 'UPD_FM' IN UPDATE TASK EXPORTING PAR = A...
a = 2.
CALL FUNCTION 'UPD_FM' IN UPDATE TASK EXPORTING PAR = A...
a = 3.
COMMIT WORK.
Here, the function module UPD_FM is performed twice in the update task: the first time, with value 1 in PAR, the second time with value 2 in PAR.
Check the SAP Help :
http://help.sap.com/saphelp_nw04s/helpdata/en/41/7af4bfa79e11d1950f0000e82de14a/frameset.htm

I need to have COMMit WORK with in a FM, which is calling in UPDATE task

Hello
I am sending out the custom IDOC from SAP to partner application by writing a custom my_OB_IDOC_FM, well.
With in this my_OB_IDOC_FM, for some functionality, i am using a standard SAP FM and I need to use a COMMIT WORK immediately after this standard SAP FM call.
But, all my IDOC is calling in update task, so once am triggering IDOC (inturn my_OB_IDOC_FM is calling in UPDATE task) am getting dump because of that inside used COMIT WORK statement!
So, pls. let me know how can replace this COMMIT WORK or hoe can i fix my issue? can i do like CALL FUNCTION standard_SAP_FM in background task/seperate task? so that i can use COMMIT WORK?
Thank you

I've dealt with something similar before.
You could make a new z-program and run in a background job... like this:
* create the job
CALL FUNCTION 'JOB_OPEN'
      EXPORTING
          JOBNAME          = mv_JOBNAME
      IMPORTING
          JOBCOUNT         = mv_JOBCOUNT
      EXCEPTIONS
          CANT_CREATE_JOB = 1
          INVALID_JOB_DATA = 2
          JOBNAME_MISSING = 3
          OTHERS           = 4.
* submit the program to the job
    SUBMIT ZPROGRAM
      WITH i_ebeln in mr_ebeln
      WITH updall = 'X'
      WITH wq_simul = ''
      TO SAP-SPOOL
        DESTINATION sv_output_device
        IMMEDIATELY ''
        KEEP IN SPOOL 'X'
        WITHOUT SPOOL DYNPRO
      USER sy-uname
      VIA JOB mv_jobname NUMBER mv_jobcount
      AND RETURN.
* submit the job
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
        JOBCOUNT             = mv_JOBCOUNT
        JOBNAME              = mv_JOBNAME
        STRTIMMED            = 'X'
    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.

In update task option with class methods ??

Hi,
In my case, I have written a BADI and in it's method I will be updating a custom table. In the earlier approach I was updating the custom table in a function module which was invoked in update task as
CALL FUNCTION 'Z_XXX'
IN UPDATE TASK
EXPORTING
Do we have a similar update task concept w.r.t class methods ? So that whatever i have written in the FM I will copy into the method but that code must execute in update task !!
thks

Thanks Krishna, I too thought of the same initially but this looks like too many layers involved...
BTW, I came across a document in SAP help,
http://help.sap.com/saphelp_nw04/helpdata/EN/fa/f23c15330411d5992100508b6b8b11/content.htm
Any idea on this ? Will this be of any help ?
thks

SCCM 2012 - Maintenance Windows Issue with Update Deployment using Task Sequence

Hi Guys,
I have a question for you!!
We use a Task Sequence to deploy "Patch Tuesday" security fix; we use the integrated step "Install Software Update" and the Task Sequence run during Maintenance Windows (1 hour).
We notice that the time remaining is not recalculated on every software update installation occur (http://blogs.technet.com/b/csloyan/archive/2010/10/24/maintenance-window-calculations-explained.aspx);
it's correct?
The formula indicated in the link above is not considered in this type of software update deployment (Install Software Update task sequence step)?
Thanks a lot.
David

Hi,
Any update?
Is the time remaining recalculated after each update is installed when using the Software Update Group directly as Torsten said?
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Issues with Approval Task IN IDM 7.1

Hi,
I have been facing issues with Approval task.
Firstly,
I have created an Approval task with 'Mskeyvalue' and 'Mxref_mx_privilege' as attributes.
I am having a problem in the Approvers workflow UI where, we see these approvals.
It not only displays the requested privilege,but also the already provisioned privileges of the enduser to the approver.
He will not be able to recognize which privilege has been requested.
Is this an already known issue which has been sorted out in recently updated patches?
If not can you suggest me a solution for this.
Secondly,
The privilege requested by the end-user is getting provisioned to the backend,even before it is Approved.
Since Provisioning tasks are mapped through repository,privileges are getting provisioned as soon as
an entry is made into the Identity Stores.
But,Ideally the requested privilege should not be proviosioned to the backend until it is approved by the Approver.
Is this an already known isuue which has been sorted out in recently updated patches?
If not can you suggest me a solution for this.
Thanks and Regards,
Joel
Edited by: Joel Sundararajan Davis on Jul 16, 2009 11:04 AM

Joel,
I'm afraid the approval process is not quite this simple. You are correct, if you have provisioning setup on the repository for a privilege it will be assigned immediately. The approval task as you are using it works as an 'interrupt' to a process - nothing more.
There is an entry type called pending value that you would need to leverage in order to have privileges requested route for approval. This pending value object is created by default for role requests in 7.1, but I'm not sure how to create a pending value for a privilege.
Which brings to mind a question - is there a reason you want users to request privileges instead of roles? In general I think the security model is setup so that users are assigned roles which contain one or more privileges.
If you do choose to use a role instead of privilege, simply set the attribute MX_APPROVAL_TASK to the id of the approval task you want to use and the system will do the rest. The display you referenced in the first part of your question will always display the current values of the attributes you select for the user, so don't try to display the roles there - just display the user id, name, whatever else is helpful and when the approver clicks on the user id they will get the approval details which will include the requested role.
Also, please note that if you would like to assign a role directly anywhere (bypass approvals) you can use the switch: {direct_reference=1}
-Geoff

How do I SUBMIT from a user exit which is called in an update task?

I want to send an idoc each time there is a goods movement. So, in the user exit of MB_POST_DOCUMENT I am calling IDOC_OUTBOUND_WRITE_TO_DB. This creates an idoc of status 30. However, in order to send the idoc I want to SUBMIT RSEOUT00. I get an ABAP dump on the SUBMIT because MB_POST_DOCUMENT is called in the update task, where SUBMIT is not allowed. Do you know any other way I can execute RSEOUT00 at this moment without having to call it later in batch?
Thanks!!
Joy

Hi Naren,
Your reply is VERY helpful!! Thank you so much.
I added CALL FUNCTION 'RSAP_IDOC_EINBUCHEN_VOM_BIW_4' IN BACKGROUND TASK. I am no longer getting the dump, but my idoc is still a status 03 and not a status 30. Should I expect to see it turn to a status 30? I ran this function directly in SE37 -> Test with the same parameters and it ran perfectly and turned the idoc to a status 03. Is there anything else I need to do in the code?
Thanks again,
Joy

Update tasks - Transfer Order creation.

I have an issue in our production environment where in some situations a Transfer Order (TO) is created with missing storage handling unit information. This only happens intermittently, and when the TO is cancelled and re-created, it is created with the correct storage unit information.
I have looked at the TO creation function l_to_create_int and it is called from within an update function module l_communication_to_create. The l_to_create_int function is not called within an update task. The function within l_to_create_int which creates the storage handling unit is an update function module (function L_TA_HINZUFUEGEN).
So my question is, what happens when you have a combination of function modules called as an update and function modules called normally? Will the updates in the function called normally update outside of the update task commit? I'm beginning to think that the problem may be caused by inconsistencies in when updates are completed by the program.
I'd greatly appreciate any help or guidance regarding this issue.
Kind regards,
James Mandikos.

Hi James,
You are correct, a function module must be explicitly be called in 'UPDATE TASK' for it to be executed in the update task (regardless of the settings flagged in SE37).
If, however, it is called in UPDATE TASK there are four possible settings you can have in SE37 which each behave differently (as of the release I am looking at at the moment - R/3 4.7).
Here is my understanding of how the settings behave:
Start immed.
Will run in a V1 update process together with all other update functions called in the same LUW with Start immed. flagged.
Immediate start, no restart
As above, but cannot be reprocessed via transaction SM13 in the case of error (but can be viewed).
Start delayed
Will run in a V2 update process individually.
Coll.run
Will run in a V2 update process toegether with all other update functions called in the same LUW with Coll.run flagged.
So given the data you have provided both your function modules should be running in a collective V1 process, and therefore if one failed then the whole transaction should have been rolled back (and hence this does not explain your problem).
BUT what may be happening is that for whatever reason the transaction fails (maybe due to heavy system load) and either your system admin (or an autmated job) is pushing through the error in SM13. As the function L_TA_HINZUFUEGEN is flagged as immediate start, no restart then it will not be processed and the L_TO_CREATE_INIT will be. This could exactly explain your problem.
Hope that makes things clearer.
Cheers,
Brad

OIM Design Console Internal error while updating task attributes

Hi All,
I have installed OIM9101 on jboss, the set up is running fine. I am in the process of integrating a OID connector following steps given OID connector guide. In design console(Administration-->Task Scheduler) while modifying "OID Group Lookup Reconciliation Task" attributes, attribute value is not getting saved. When i click on save option it shows a pop up windows saying "problem in updating task attributes. update failed."
Any solution for this??.. Please help.
Thanks in Advance.
Edited by: VAYANAKA on Nov 26, 2010 10:48 PM

Thank you for the reply..I have tried to create a new scheduled task. But while saving it again an Internal error pop up window comes saying " Description:Could not execute database read.The database encountered a problem with the specified SQL Query.Remedy: Check the database query.Contact your system administrator."..
Is it any problem with my database.? I have checked database, its up and running??
Thanks In advance.

OIM: Error while updating Task Attributes

Hi All,
I am trying to use PeopleSoft User Management using OIM connector.
I am facing an error saying "problem in updating Task Attributes" while scheduling a task on OIM design Console. I am trying to update and save PSFT Base Non Trusted User Reconciliation. following is the log message displayed in server command prompt.
ERROR,11 Apr 2008 05:02:53,287,[XELLERATE.SERVER],Class/Method: tcTSA/eventPostU
pdate encounter some problems: problem in updating Task Attributes
com.thortech.xl.scheduler.exception.SchedulerGenericException: problem in updati
ng Task Attributes
at com.thortech.xl.scheduler.core.quartz.QuartzSchedulerImpl.updateTaskA
ttributes(Unknown Source)
at com.thortech.xl.scheduler.ejb.SchedulerControllerBean.updateTaskAttri
butes(Unknown Source)
at com.thortech.xl.scheduler.beans.SchedulerControllerSession.updateTask
Attributes(Unknown Source)
at com.thortech.xl.scheduler.beans.SchedulerController_z4f4d2_EOImpl.upd
ateTaskAttributes(SchedulerController_z4f4d2_EOImpl.java:478)
at com.thortech.xl.scheduler.beans.SchedulerController_z4f4d2_EOImpl_CBV
.updateTaskAttributes(Unknown Source)
at com.thortech.xl.dataobj.tcTSA.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.ejb.databeansimpl.tcDataObjectBase.save(Unknown Sourc
e)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl.save(tcTSA_u3xmy2_EOImp
l.java:1437)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl_WLSkel.invoke(Unknown S
ource)
at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(Activata
bleServerRef.java:90)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by [Nested Exception]:
java.lang.NullPointerException
at com.thortech.xl.scheduler.core.quartz.QuartzSchedulerImpl.updateTaskA
ttributes(Unknown Source)
at com.thortech.xl.scheduler.ejb.SchedulerControllerBean.updateTaskAttri
butes(Unknown Source)
at com.thortech.xl.scheduler.beans.SchedulerControllerSession.updateTask
Attributes(Unknown Source)
at com.thortech.xl.scheduler.beans.SchedulerController_z4f4d2_EOImpl.upd
ateTaskAttributes(SchedulerController_z4f4d2_EOImpl.java:478)
at com.thortech.xl.scheduler.beans.SchedulerController_z4f4d2_EOImpl_CBV
.updateTaskAttributes(Unknown Source)
at com.thortech.xl.dataobj.tcTSA.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.ejb.databeansimpl.tcDataObjectBase.save(Unknown Sourc
e)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl.save(tcTSA_u3xmy2_EOImp
l.java:1437)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl_WLSkel.invoke(Unknown S
ource)
at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(Activata
bleServerRef.java:90)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
ERROR,11 Apr 2008 05:02:53,287,[XELLERATE.SERVER],Class/Method: tcDataObj/save E
rror :Data Update Failed
ERROR,11 Apr 2008 05:02:53,302,[XELLERATE.DATABASE],Class/Method: tcDataBase/rol
lbackTransaction encounter some problems: Rollback Executed From
java.lang.Exception: Rollback Executed From
at com.thortech.xl.dataaccess.tcDataBase.rollbackTransaction(Unknown Sou
rce)
at com.thortech.xl.dataobj.tcDataObj.rollback(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.doRollback(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.ejb.databeansimpl.tcDataObjectBase.save(Unknown Sourc
e)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl.save(tcTSA_u3xmy2_EOImp
l.java:1437)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl_WLSkel.invoke(Unknown S
ource)
at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(Activata
bleServerRef.java:90)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
I am facing above error when try to update any task in the task scheduler.
Can anyone please suggest me where i am going wrong?
Thanks,
Uma.

I would assume you are missing the jar file for your scheduled tasks. Try and create a new scheduled task with the same class name, if it won't let you save, this is your answer. You'll want to make sure you have the connector scheduled task file in the ScheduleTask folder in your OIM directory.
-Kevin

Install Updates task not working during Build and Capture in SCCM 2012

Working with a new SCCM 2012 installation.
We are trying to get a Build and Capture TS to install all updates for Win7SP1.
All packages are deployed to DP, build and cap machine is in a collection with all updates deployed to it. Agent installation parameters include "SMSMP" "SMSSLP" parameters. Machine is not being attached to the domain during OS install.
Updates can be pushed to existing domain machines, so obviously the updates themselves are working.
The task sequence works correctly to install the image, but "Install Updates" task just sits there and eventually times out. (No indication of updates being installed.) If this task is working, shouldn't I see a Downloading Updates progress bar, or was that
eliminated from 2012?

Same issue for me except I'm running 2012 R2 my B&C runs forever on Install Software Updates, eventually just rebooting and coming back to the login screen of Windows 7 without ever finishing the Install Updates.
Been working on it litteraly for weeks.
1- Tried adding .Net 4.52 as an application installation thinking maybe it would resolve the issue
2- Tried installing via Run Command Line + DISM all hotfixes that require 2 reboots as per (https://support.microsoft.com/en-us/kb/2894518)
3- Tried to simply REMOVE the same hotfixes from my Software Update Groups alltogether.
4- Injected all applicable software updates through Offline Servicing in the SCCM Console (Schedule Updates) on the Windows 7 DVD wim file. That way my logic was that once it would hit the Software Updates, there would be a lot less to install.
I'm at the point where I had to open a case with Microsoft Premier Support as of yesterday. So, nothing new to report yet. But yes, this is a true pain in the ***.
For the sake of comparison, I am running 4 Update Groups: one containing patches up to 2012. Another one for 2013, 2014 and 2015. I have patches for Windows 7 + Office of all categories except Service Packs.
If someone has any ideas, feel free to chime in.

Caling fm with "update task"

Similar Messages

Maybe you are looking for