Scheduling Engine Failure
Mark Braithwaite
We have recently started receiving the 'General Failure in Scheduling
Engine' error when scheduling service activities. The error occurs after a
resource is selected and a user clicks save.
We receive the 'SQL Server Error, Contact your System Administrator' message
and when we close the window we see the 'General Failure in Scheduling
Engine' error.
I have done a bit of research around this, we have installed Update Rollup 1
and we have not removed the Status Reason field from the Appointment or
Service Activity forms.
Does anyone have any ideas as to why this could be occurring? Our service
department is getting quite irritated with this and a solution would be
really appreciated.
Many Thanks
Mark
Tim VonDerHaar
There is information from the past that KB917010 fixed a similar problem, but
this fix was packaged in rollup #1 which we are well past. We are up to
rollup #3, so it sounds like a new bug.
Tim
Guatelli Francoise
regarding account.
If i save the appointment under another account that the one that give the
issue, the appointment is saved without problem. If i update this appointment
by putting the previous account that give problem, the appointment is saved
normally.
I have no idea yet how to figure out the problem, any proposal will be
welcome.
Guatelli Francoise
account.
Removing the sharing solve the issue
Tim VonDerHaar
two issues.
1) We were missing some permissions under Service management. Make sure
your calendar has append and append to permissions as well as have your my
work hours across the board set to organization level
2) Above fixed most of the problems, but we also found that a hotfix, I
believe that was part of rollup3 has an issue, actually was bad and created
this new bug. Microsoft just developed a limited release hotfix under
KB950119 to address the problem of p_GrantAccessBulkForCreate failing under
appointments. Doing a search on the hotfix doesn't show very much yet, so
you will need to contact Microsoft.
Chris Lefsrud
The issue manifests when any record is assigned to the Regarding field, be
it an account or contact or Order or whatever. Also, it is possible to
create a Service Activity without populating the Regarding field; then the
record can be reopened, assigned a Regarding value (Account, Order, etc.),
and successfully saved. Permissions not an issue, we experience this with
Administrator access.
In our situation, we have a dev database where this error is absent, and a
production database that only gets customizations via import, and where the
error is present. This may suggest that it is a data issue.
--
HCL
Nevitt@discussions.microsoft.com Andrew Nevitt
has been most helpful. We went as far as changing the Append privilege
against the Calandar entity to Organisation-wide and this solved the problem
straight away. In our case, the issue was with a user creating appointments
for other users.
andrew....@gmail.com
Nev...@discussions.microsoft.com> wrote:
> Thank you for this post - we had a similar issue with a client so this blog
> has been most helpful. We went as far as changing the Append privilege
> against the Calandar entity to Organisation-wide and this solved the problem
> straight away. In our case, the issue was with a user creating appointments
> for other users.
>
>
>
> "Tim VonDerHaar" wrote:
> > I think we have finally solved the problem just yesterday. We actually had
> > two issues.
>
> > 1) We were missing some permissions under Service management. Make sure
> > your calendar has append and append to permissions as well as have your my
> > work hours across the board set to organization level
>
> > 2) Above fixed most of the problems, but we also found that a hotfix, I
> > believe that was part of rollup3 has an issue, actually was bad and created
> > this new bug. Microsoft just developed a limited release hotfix under
> > KB950119 to address the problem of p_GrantAccessBulkForCreate failing under
> > appointments. Doing a search on the hotfix doesn't show very much yet, so
> > you will need to contact Microsoft.
>
> > "Guatelli Francoise" wrote:
>
> > > Same issue with one of our user, it seems that the problem is link to the
> > > regarding account.
> > > issue, theappointmentis saved without problem. If i update thisappointment
> > > by putting the previous account that give problem, theappointmentis saved
> > > normally.
>
> > > I have no idea yet how to figure out the problem, any proposal will be
> > > welcome.
>
> > > "Tim VonDerHaar" wrote:
>
> > > > I have a user that has just begun to experience this very same problem.
> > > > There is information from the past that KB917010 fixed a similar problem, but
> > > > this fix was packaged in rollup #1 which we are well past. We are up to
> > > > rollup #3, so it sounds like a new bug.
>
> > > > Tim
>
> > > > "Mark Braithwaite" wrote:
>
> > > > > Hi
>
> > > > > We have recently started receiving the 'General Failure in Scheduling
> > > > > resource is selected and a user clicks save.
>
> > > > > and when we close the window we see the 'General Failure in Scheduling
> > > > > Engine'error.
>
> > > > > I have done a bit of research around this, we have installed Update Rollup 1
> > > > > and we have not removed the Status Reason field from theAppointmentor
> > > > > Service Activity forms.
>
> > > > > Does anyone have any ideas as to why this could be occurring? Our service
> > > > > department is getting quite irritated with this and a solution would be
> > > > > really appreciated.
>
> > > > > Many Thanks
>
> - Show quoted text -
I'm not sure if you guys are referring to v3 or v4 - in my case it
worked fine in v3 but I have run into the problem with v4.
I found the same as Chris above, i.e. the appointment creation fails
of you have a value in the regarding field, but works fine if you
create the apponitment without the regarding field and then update the
regarding field afterwards. This happens even as system administrator,
so it is not a permissions issue in my case.