Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a task, which runs fine while launching it with "Right click / Run" in the scheduler, but fails with a weird "SQL Server login fail" due to bad login while ran automatically at specified time.

Login for SQL Server is internal SQL Server account, not a "Trusted connection" Windows account. I know the login (and all others parameters) are good. Also, I've got some other tasks launched on the same server which runs fine. This one is the only exception. Nothing in the task requires an opened session.

Like I said previously I can't figure why it's ok to launch it by the "Run" command in scheduler but not at specified time. And of course I'm sure my DB server is always available.

Does somebody know if there are significant differences between launching the task by "Right click / Run" and awaiting for it to be started automatically ?

As I don't have this behavior with other tasks I'm pretty sure it's a bug in scheduler but I can't even guess what happens here.

share|improve this question
Procmon.exe – Mathias R. Jessen Sep 24 '13 at 8:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.