Prev: Need SP2 Installation Instructions
Next: Advice regarding an unusual "event" report
From: Swifty on 13 Nov 2009 15:28
Jose wrote:
> If a ST will not run, there is always a reason given and the given
> reason is in the log file which on most systems is:
>
> c:\Windows\SchedLgU.Txt
>
> What does it say about your afflicted STs?

That's really handy to know, thank you!

Unfortunately, it tells me nothing, because I was forced to reboot a
short while ago. This fixes most of my problems, and then that log soon
wraps around because I have a scheduled task running every 5 minutes (in
an attempt to catch the cause of the underlying problem; it must have
been something which has run since the last reboot, but before the
scheduled task stopped running).

--
Steve Swift
http://www.swiftys.org.uk/swifty.html
http://www.ringers.org.uk
From: Ross on 16 Nov 2009 12:10
Thanks for the suggestion, Steve. I'll try it today as it seems to be
a much more widespread problem than we previously thought.

Jose - there is no scheduled task log. It occurs to me that the
system user might not have credentials to write to the windows
directory (IE, our security policy is shooting us in the foot), but
then the problem would presumably be everywhere, not just on a handful
of servers. (Our security policy - really, the servers in general -
should be homogeneous. All of the servers are created from the same
image, get the same patches, windows updates, and so on.)

Could this also be a problem with the users themselves? The error
seems like it might be something corrupt with the user profiles, or
something wrong with how users are retrieved. The "unspecified" COM-
esque error makes me think something is wrong with the how, not the
what, but the task of determining where the problem resides is
daunting at best. Short of throwing on process explorer and crossing
my fingers, I'm not really sure how to start. I'm certainly open to
suggestions.

Thanks again,
Ross

On Nov 13, 2:28 pm, Swifty <Steve.J.Sw...(a)gmail.com> wrote:
> Jose wrote:
> > If a ST will not run, there is always a reason given and the given
> > reason is in the log file which on most systems is:
>
> > c:\Windows\SchedLgU.Txt
>
> > What does it say about your afflicted STs?
>
> That's really handy to know, thank you!
>
> Unfortunately, it tells me nothing, because I was forced to reboot a
> short while ago. This fixes most of my problems, and then that log soon
> wraps around because I have a scheduled task running every 5 minutes (in
> an attempt to catch the cause of the underlying problem; it must have
> been something which has run since the last reboot, but before the
> scheduled task stopped running).
>
> --
> Steve Swifthttp://www.swiftys.org.uk/swifty.htmlhttp://www.ringers.org.uk

From: Ross on 16 Nov 2009 12:20
On Nov 16, 11:10 am, Ross <rosshink...(a)gmail.com> wrote:
> Thanks for the suggestion, Steve.  I'll try it today as it seems to be
> a much more widespread problem than we previously thought.
>
> Jose - there is no scheduled task log.  It occurs to me that the
> system user might not have credentials to write to the windows
> directory (IE, our security policy is shooting us in the foot), but
> then the problem would presumably be everywhere, not just on a handful
> of servers.  (Our security policy - really, the servers in general -
> should be homogeneous.  All of the servers are created from the same
> image, get the same patches, windows updates, and so on.)
>
> Could this also be a problem with the users themselves?  The error
> seems like it might be something corrupt with the user profiles, or
> something wrong with how users are retrieved.  The "unspecified" COM-
> esque error makes me think something is wrong with the how, not the
> what, but the task of determining where the problem resides is
> daunting at best.  Short of throwing on process explorer and crossing
> my fingers, I'm not really sure how to start.  I'm certainly open to
> suggestions.
>
> Thanks again,
> Ross
>
> On Nov 13, 2:28 pm, Swifty <Steve.J.Sw...(a)gmail.com> wrote:
>
> > Jose wrote:
> > > If a ST will not run, there is always a reason given and the given
> > > reason is in the log file which on most systems is:
>
> > > c:\Windows\SchedLgU.Txt
>
> > > What does it say about your afflicted STs?
>
> > That's really handy to know, thank you!
>
> > Unfortunately, it tells me nothing, because I was forced to reboot a
> > short while ago. This fixes most of my problems, and then that log soon
> > wraps around because I have a scheduled task running every 5 minutes (in
> > an attempt to catch the cause of the underlying problem; it must have
> > been something which has run since the last reboot, but before the
> > scheduled task stopped running).
>
> > --
> > Steve Swifthttp://www.swiftys.org.uk/swifty.htmlhttp://www.ringers.org.uk

No deal. Since user information can't be retrieved, I can't edit the
user information or whether or not it's run only if the user is logged
on.

Square one.

I'll keep picking away at it.

-Ross
First  |  Prev  | 
Pages: 1 2
Prev: Need SP2 Installation Instructions
Next: Advice regarding an unusual "event" report