Re: Win2K Task Scheduler says running but it's not
From: Roger Abell [MVP] (mvpNoSpam_at_asu.edu)
Date: 09/17/05
- Previous message: Roger Abell [MVP]: "Re: Win2K Task Scheduler says running but it's not"
- In reply to: David Frankenbach: "Re: Win2K Task Scheduler says running but it's not"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 17 Sep 2005 14:13:48 -0700
Well, hopefully your people know what was pushed out
between 8/18 and 8/29 because there was nothing from MS.
I assumed the "non-application" status is only because it is in
a different Session ID and only the apps of the current show.
"David Frankenbach" <sendnospam@sendnospam.net> wrote in message
news:O5ahQD7uFHA.904@tk2msftngp13.phx.gbl...
> Roger,
>
>>> From the WindowsUpdate.log file the most recent updates it went through
>>> updates were on 7/26, 8/17, 8/18, 8/29, 9/6, 9/13 and 9/16.
>>
>> Well, turns out 6/28 is when the Update Rollup released in v1 (not July
>> as
>> I had said, which is actually when it got applied in our prod env) while
>> v2 came out this Tuesday (and would not install if v1 is there)
>> I have not yet chased into the new v2 release and ways to confirm
>> which one has installed, v1 or v2
>>
>>> Everything since the 8/29 update have been our attempts to resolve this
>>> task scheduler problem. Because the first failure to run that we had was
>>> the 9/3 run of the job.
>>>
>> you started trying to resolve the problem before the first time you
>> discovered it ?? Anyway, it sounds like the update rollup may have
>> been on the system for some time before the issue was noticed (?) if
>> that is the July service. However, if you search for schedule and/or
>> task in http://support.microsoft.com/kb/900345/ you will see that
>> there were certainly changes for task manager in the Update Rollup.
>
> No, the first failure of the job to run correctly was on 9/3. The 9/6
> through 9/16 hits in the updatelog were us making sure the box was up to
> date. I didn't go back further in time in the log to see what had happened
> before 7/26. I can if you think it'd be relevant. But I believe we've
> narrowed the problem do to what got pushed out between 8/18 and 8/29. The
> job had successful runs on 8/20 and 8/27.
>
> The guy in Australia's job ran every night and his first failure was on
> 8/29 I'm not sure if he was automatic update or not.
>
> I had been through that KB article, but nothing I saw about scheduler
> seemed relevant to this problem. Besides that it's rare for a Fixes KB
> article to predict what it's about to break *bg*
>
>> I cannot do that conveniently on a production box right now, but on
>> a fully serviced W2k server at office I just TS'd, defined sch'd task of
>> notepad short delay using a non-adm user account for the task but
>> while logged in with different account. Task started, but notepad did
>> not show, and looking at taskmanager it showed the process was in
>> session with different SessionID than that of my then current TS session,
>> in fact it was in Session ID 0. So, I tried again, with the current
>> login
>> account and saw the same result.
>>
>> Now, for my scheduled tasks this is not an issue that they are in
>> a different session than the (possibly existing) then current login
>> session, as my tasks do not have a dependency on interactive
>> session, etc.. However, this is as far as I can recall definitely a
>> behavior change if it is not all simply due to testing this within
>> a TS session. I will not be up to office where I have a box with that
>> version until Monday to test with TS not in the loop.
>
> I'm glad you are able to replicate the problem it's always the first step
> in figuring this kind of thing out.
>
> When I get back to the office on Monday I may try moving Spy++ over to
> that box and see if I can spelunk around and make sure that this now
> non-application status the exe is taking on is causing it to throw an
> error which has presented a dialog box to appear that we have no way of
> seeing. I'll probably create another couple of quick exes that do one
> specific detectable thing to a local file and and network file and connect
> to the database server to see if a very simple task can execute and
> terminate correctly.
>
>> I do not recall anything coming down the pipe in the 8/29 timeframe or
>> near before, and earlier this week I did do a review of the SUS and WSUS
>> to see what all had happened between the Aug and Sept patch Tuesdays.
>
> Thanks for all your help!
>
> --
> df - Microsoft MVP FoxPro http://www.geocities.com/df_foxpro
>
- Previous message: Roger Abell [MVP]: "Re: Win2K Task Scheduler says running but it's not"
- In reply to: David Frankenbach: "Re: Win2K Task Scheduler says running but it's not"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
