Archived from groups: microsoft.public.win2000.general,microsoft.public.win2000.security (
More info?)
inlined . . .
"David Frankenbach" <sendnospam@nospam.com> wrote in message
news:OFhHw6vuFHA.4020@TK2MSFTNGP12.phx.gbl...
> Roger,
>
> Since this machine is a running process box as part of a much larger
> network, no, we don't have automatic updates turned on. Machines go
> through scheduled maintence cycles where updates are applied. I just
> checked the box right now and there are no high priority updates to
> install. DirectX 9.0c and Windows Media Player 9 are the only available
> updates to install and they are not likely to ever be installed because
> this is a server not a desktop machine.
That sounds much like my servers . . .
> 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.
> How can I tell if the v2 rollup was applied?
>
> The real task has a Run As user which is the same user that is always
> logged into the machine.
>
> When I run the exe from explorer it is running as the currently logged in
> user.
>
> Can you try setting up a brand new task to launch notepad, either schedule
> it to run in a couple of minutes or right click and select run and see
> what happens?
>
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 not sitting at the machine itself it's in a server room in another
> building, I connect to it via Remote Desktop from an XP Pro machine over
> our network. I use the same user to connect to the machine I don't use my
> login.
>
> I posted this same message in the universalthread.com before here and
> another user in Australia has confirmed that since 8/29 his tasks are
> failing in this same fashion.
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.
>
> df (MVP Visual FoxPro)
>
> "Roger Abell [MVP]" <mvpNoSpam@asu.edu> wrote in message
> news:eyvPfcvuFHA.3252@TK2MSFTNGP10.phx.gbl...
>> Dave,
>>
>> Microsoft did not send out any patches at the end or August, nor any
>> three weeks ago. There were patches on the second Tuesday of Aug,
>> which was the 9th. If you patching schedule is a little lagging, then
>> you
>> may have also installed the W2k post SP4 Update Rollup at that time
>> even though it was release mid-July.
>> That v1 release of the rollup did have some issues, but I do not recall
>> hearing of any issue similar to your description. A v2 release was made
>> this Tuesday.
>>
>> On my W2k systems that are fully up-to-date patch-wise I am not
>> experiencing issues with scheduled tasks (other than the GUI reporting
>> of last result status still being blank, something that happened quite
>> some time ago).
>>
>> Have you logged in with the account that is used for the scheduled task
>> and run the exe ? I know you said you can run it without issue but it
>> was not clear that was with the scheduled account.
>
>
Facebook
Twitter
Instagram