Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
General failure in sheduling engine in CRM 2013 Online RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I have a retrieve plugin registered (async) on appointments, whenever i open any appointment, i get the following error messagae in notificaiton bar "General failure in sheduling engine".

    If the plugin step is registered as sync everthing works fine without error message.

     

    Does anyone have any ideas as to why this could be occurring?

    Thanks and Regards,

    Nishant Rana

    http://nishantrana.wordpress.com https://twitter.com/#!/nishantranacrm

    Wednesday, June 17, 2015 7:29 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    What does your plugin do ?

    Have you tested with an empty plugin that does nothing - i.e. is the issue just with having a plugin registered to run Async on the Retrieve, or is it specific to the code in the plugin ?

    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Wednesday, June 17, 2015 8:19 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi David,

    Yes it is the issue just with having a plugin registered to run Async on the Retrieve.

    Regards,

    Nishant Rana

    http://nishantrana.wordpress.com https://twitter.com/#!/nishantranacrm

    Wednesday, June 17, 2015 9:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am curious about your requirements.  Generally a retrieve or retrievemultiple plugin is designed to modify the data that is being displayed in real time, and therefore does not make sense in an async operation.  I think if the appointment has not already been scheduled successfully the UI is designed to trap this error and render a friendly message for it in the UI when the record is displayed.  Seems like the problem in your case may be the fact that in async mode the UI can no longer natively trap the error, but it is now bubbling up to the more generic 'Business Process Error' level, which is the message you are seeing.
    Wednesday, June 17, 2015 7:59 PM