--- David E Jones <[EMAIL PROTECTED]> wrote: > > Hmmm.... I've never heard of anything like this > happening before. > > There may be some errors that can get a scheduled > service record in a > bad state, but it's pretty rare. > > The thing to do is send over some more details, like > the service > definition, and the most recent records in the > JobSandbox table for > the job in question. > > -David > >
I haven't personally witnessed this happen with the JobSandbox, but I have witnessed it with the UserLogin routines. User can't login because MySql has cut off the connection to the database and so the UserLoginHistory can't be entered and therefore the user login fails. The service that calls the simple-method I included in the previous message has prevented the user login failure from occurring in our deployment.
