October 10, 2005 at 9:36 am
Hello,
I would like to inform you of a new Microsoft bug with Job Scheduler on Windows 2003 server.
The hotfix is developed but is not tested and is not posted yet, it is by request. But the situation is so common so I decided to alert you in case you get similar cases.
THE ISSUE: If a user logged to Windows 2003 server using Terminal services AND a non-interactive job is scheduled to run on the same account this job will not run.
See the article that was just posted a couple of days ago:
http://support.microsoft.com/default.aspx?scid=kb;en-us;843280
"Non-interactive At.exe tasks do not run in Windows Server 2003"
Basically what it says is: you have an account on Windows 2003 server (admin, localadmin, sqladmin, jobadmin - up to your imagination) and you use this account to login to the server AND you use this account to run jobs then if the job is Non-Interactive (where did you see Interactive jobs ???) then when you are logged in through Terminal Services or just left your session running then your jobs would not run.
There are a lots of workarounds: do not leave unattended sessions, schedule jobs on its own account etc, but we have at least know that this situation may happen.
Yelena
Regards,Yelena Varsha
October 10, 2005 at 11:04 am
Odd issue, but thanks for posting
October 10, 2005 at 11:26 am
It happens more often then you think. In most of the enterprises Data Centers are locked and servers are accessed in Terminal Services remote Administration mode. That is when it happens.Creating (or be given by an administrator) a local server account and using it for everything is a favorite for most developers and consultants (who usually are given one account). X-ing (clicking on the X) out of Terminal Services connection is a common mistake and the session stays. Logging off Terminal Services correctly and leaving right away not making sure "can not end the application..." will still keep your session running is another mistake. Just leaving your session because you have something running for many hours is yet another case.
Regards,Yelena Varsha
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply