Archived from groups: microsoft.public.windowsxp.general (
More info?)
Amen!
"John Antonakos" <JohnAntonakos@discussions.microsoft.com> wrote in message
news:6BE57937-DB06-425A-8E65-AF92E51E930D@microsoft.com...
> First of all Mr Pegasus (MVP), i only mentioned hardware problem because a
> colleague who was investigating the issue for me, said he read some
article
> that mentioned the problem was linked to a hardware issue. Second, if you
sit
> down and think how Human Interface Device Service, a USB related handling
> service, can affect a scheduled event, then you can understand my hardware
> related worries. Anyway, i never accuse Dear Microsoft of bugs, you know
why
> sweetie ? ah? Because i have been programming for many years, and i know
well
> that any software in the world, especially one of the biggest software
> around, like Windows, will have bugs. At least Microsoft is very fast on
> fixing them. I feel really sorry for all the programmers at Seattle who
are
> working all day around to work on the most attacked software worldwide,
the
> Microsoft Windows series... Now lets close this stupid discussion, anyway,
> talking about the problem and looking into the schedule log, made me write
> the right search strings in Google and i found the article. That's the
whole
> story. I really feel sorry though for all those people out there,
> participating in forums daily, just to prove that they know SO MUCH about
> software. They make our life difficult, i am talking about the
professional
> programmers who are earning their living with what others play with. Enjoy
> your day!!!
>
> "Pegasus (MVP)" wrote:
>
> > Criticism noted. I am now waiting for your self-assessment
> > to explain how a hardware problem or a BIOS bug could
> > prevent a scheduled task from running. It's equivalent to
> > suggesting that you cannot join two tables because of an
> > incompatible video adapter.
> >
> >
> > "John Antonakos" <JohnAntonakos@discussions.microsoft.com> wrote in
message
> > news:929AFF57-1120-45C8-BF4D-7BB54F9ACBE6@microsoft.com...
> > > The workaround works just fine. Once you disable Human Interface
Device
> > > Access service (HID Input service) the scheduled tasks run even if
nobody
> > is
> > > logged in.
> > > I also checked all the PC`s that the scheduler was running normally
and i
> > > found out that this service was actually Disabled in those machines by
> > > default.
> > >
> > > Now, if a person like you cannot understand that an XP machine can
differ
> > > from another XP machine, i dont know why i even bother replying. I
really
> > > believe Microsoft should make the exams for Most Valuable Professional
> > more
> > > difficult.
> > > Its very easy for an anonymous to blame everyone else as
inexperienced.
> > >
> > > "Pegasus (MVP)" wrote:
> > >
> > > > That's a long shot, and yet to be proven.
> > > >
> > > >
> > > > "John Antonakos" <JohnAntonakos@discussions.microsoft.com> wrote in
> > message
> > > > news:3C9D1053-381C-4337-9CC1-4C314B2C315D@microsoft.com...
> > > > > Just look here, i found something:
> > > > >
> > > > >
http://support.microsoft.com/default.aspx?scid=kb;en-us;812400
> > > > >
> > > > > "Pegasus (MVP)" wrote:
> > > > >
> > > > > >
> > > > > > "John Antonakos" <John Antonakos@discussions.microsoft.com>
wrote in
> > > > message
> > > > > > news:E3C6055E-A0B3-44FB-A2A0-A2CD4BF14343@microsoft.com...
> > > > > > > I am trying to schedule an Event, using the XP Scheduler. I
want
> > this
> > > > > > > scheduled event to run, even when i am logged off, something
that
> > does
> > > > not
> > > > > > > happen in one specific PC. We have many pc's in the company,
one
> > of
> > > > them
> > > > > > is a
> > > > > > > DB Server. In this PC, which has Win XP Pro SP1, when no user
is
> > > > logged
> > > > > > on,
> > > > > > > then the scheduled event runs, but the related batch file DOES
> > NOT.
> > > > The
> > > > > > Last
> > > > > > > Result column has a value of 0x80 (some kind of error code),
> > instead
> > > > of
> > > > > > 0x0
> > > > > > > which appears on all other PC's after a successfull run.
> > > > > > >
> > > > > > > Has anybody seen this problem before ?
> > > > > > > Is it a hardware or BIOS problem ?
> > > > > > > Is there a workaround for this ?
> > > > > > > I searched a lot online, but no luck so far...
> > > > > > >
> > > > > > > Regards,
> > > > > > > John
> > > > > >
> > > > > > It's probably a bit premature to blame the BIOS or Microsoft
> > > > > > for a problem which most likely is caused by user error or
> > > > > > lack of experience. Your first step should be to gather
evidence,
> > > > > > post it here, then ask for advice. I suspect your batch file
runs
> > > > > > OK even though you're not aware of it. I suggest you modify
> > > > > > it like so:
> > > > > >
> > > > > > @echo off
> > > > > > echo %date% %time% Start of task > c:\test.log
> > > > > > echo User=%UserName%, Path=%path% >> c:\test.log
> > > > > > c:\Tools\YourTask.exe 1>>c:\test.log 2>c:\test.err
> > > > > > echo ErrorLevel of c:\Tools\YourTask.exe=%ErrorLevel% >>
c:\test.log
> > > > > > echo %date% %time% End of task >> c:\test.log
> > > > > >
> > > > > > Wait until the scheduler has invoked this job, then report
> > > > > > the contents of the two log files in your next post.
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >
Facebook
Twitter
Instagram