Re: scheduler fails to start task five hours after session close

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Scheduled Tasks|Advanced|View Log may provide some details. If the job connects to another machine you may need to add the user/ group 'logon as batch job' rights (server side). Control Panel|Admin Tools|Local Security Policy\Local Policies\User Rights Assignments
"Log on as a batch job"

If the task completes but the job does not then there is a problem in the job itself. Remember that if it involves network resources to make sure the user account has permissions to the resources and also use UNC paths as mapped drives won't natively exist when no one is logged on.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"OBones" wrote:
Hi all,

I have a strange behavior on my servers where the scheduled tasks fail to start with message "Could not start". I looked around to find a more detailed explanation message, but was not able to locate any log file. Googling for similar terms did not help either so I did a bit of investigation. Here is the setup:

Servers are on a domain but are not the domain controller
I open sessions onto them using Terminal Services.
I logoff once I have finished a session, using the start menu.
I added one task every hour on the hour that calls the same batch file with the same credentials, those of the session I opened.

Here is what I observed:

If I keep the session opened, the tasks run fine.
If I close the session and open a new one more than 5 hours later, the first four tasks have run fine, but the last ones failed with the "could not start" message. For instance, I logoff at 9:05AM, log back in at 4:05PM, the tasks scheduled at 10, 11, 12, 1 and 2 worked but those at 3 and 4 failed with the "Could not start" message.

All the servers on which this happens are under Win2003 server with SP2 applied.

Could anyone help me with this?
Should I post this message on another group?

Thanks in advance for any help
Regards
Olivier

.

Relevant Pages

  • Reason 0.1.0 (New Nessus Client)
    ... Reason is an application/network security scanner client for Nessus and Nessus compatible servers. ... In addition to an improved user interface, it provides complete session management, templates, and report generation using XSLT. ...
    (Pen-Test)
  • Re: content static for 24hrs
    ... Largely content delivery, some of which will be subscription based. ... kind of session info would be required. ... The are single purpose servers. ...
    (microsoft.public.inetserver.asp.db)
  • Terminal Services Random Session Disconnections
    ... For about 3 weeks now we have been getting random sessions disconnections across our seven terminal servers They are all IBM Blades. ... Remote users are only affected - it is not users within the local lan that seem to be affected. ... problems when connecting to a new session. ...
    (microsoft.public.windows.server.networking)
  • Re: Connecting to TS Server
    ... you tried disabling any anti-virus or firewalls on the servers? ... because the user see's nothing on their end doesn't mean the session is ... Any errors in the logs on the server? ... user at a remote site logs out and then immediately tries to reconnect ...
    (microsoft.public.windows.terminal_services)
  • Update: Remote Desktop for Administration issue
    ... I logged in to one of my two problem servers from a workstation I never ... logged in from before and got a second session to open. ... allow a local connection as well as two remote connections as they should. ...
    (microsoft.public.win2000.general)