User name & password preventing progress

[Pegasus [MVP]]

.. . . and here is the missing code:

@echo off
echo Working - please wait.
set dest=%UserProfile%\Desktop\test.txt
path 1>"%dest%"
dir /s "%SystemRoot%\net.exe*" 1>>"%dest%" 2>>&1
echo\ >> "%dest%"
net start "Task Scheduler" 1>>"%dest%" 2>>&1
notepad "%dest%"

 

[bm]

The plot thickens . . . I suggest you now do this:
- Right-click bm.bat, then click Edit.
- Copy the code below, then paste it into bm.bat. Do NOT
retype it - this would most likely result in typing errors and
further confusion.
- Save and close the file.
- Double-click it to execute it.
- Copy and paste the result into your reply.

Sorry I don't know where to get bm.bat in order to right click it

 

[Pegasus [MVP]]

Sorry I don't know where to get bm.bat in order to right click it

Sorry, if you are unable to locate a file that you previously ran then it
would be best if you asked a computer-savvy friend to assist you in
resolving your main problem (which we haven't even come close to examining).

 

[Jose]

Sorry I don't  know where to get bm.bat in order to right click it

If Task Scheduler is running in Services, stop it.

Navigate to c:\windows and rename/delete the schedlgu.txt file (the ST
log file). It is a simple text file. You can't delete the log if
the TS service is running. Delete it, start over, troubleshoot, fix,
repeat as necessary.

Go back to Services and start the Task Scheduler. If it does not
start, look at the new schedlgu.txt log file for clues. You can only
delete the log file if the service is not running. The answers to
problems come from looking at the log file and understanding it - not
guessing or trying things.

You should not have to get to a command prompt to start the TS
service, download anything, type anything in or run a batch file - it
should start/stop just fine from Services. If the TS service is set
to Automatic, it should start when XP starts. If it does't work
right, fix it. It the TS service is working properly then fix the
individual tasks.

All of the attempts to stop/start the service or STs will be in the
log - success/failure/why not. If it gets to crowded, stop the
service and delete the log file. Get one task at a time to run
manually or fix it if it doesn't.

Look in c:\windows\tasks for your tasks, look at the columns of useful
information (Last Run Time, Last Result), right click each task of
interest and try to run the task manually, look in columns for success/
failure messages and the log file and then fix the afflicted task if
needs fixing.

 

[bm]

Sorry, if you are unable to locate a file that you previously ran then it
would be best if you asked a computer-savvy friend to assist you in
resolving your main problem (which we haven't even come close to
examining).

You are right although I was learning it must have been a pain to you
But many thanks for you help
Blair

 

[bm]

. . . and here is the missing code:

@echo off
echo Working - please wait.
set dest=%UserProfile%\Desktop\test.txt
path 1>"%dest%"
dir /s "%SystemRoot%\net.exe*" 1>>"%dest%" 2>>&1
echo\ >> "%dest%"
net start "Task Scheduler" 1>>"%dest%" 2>>&1
notepad "%dest%"

Although this is dated earlier than your last message it looks like a final
help. If that is the case how can I| use it?
Blair

 

[bm]

Sorry I don't know where to get bm.bat in order to right click it

If Task Scheduler is running in Services, stop it.

Navigate to c:\windows and rename/delete the schedlgu.txt file (the ST
log file). It is a simple text file. You can't delete the log if
the TS service is running. Delete it, start over, troubleshoot, fix,
repeat as necessary.

Go back to Services and start the Task Scheduler. If it does not
start, look at the new schedlgu.txt log file for clues. You can only
delete the log file if the service is not running. The answers to
problems come from looking at the log file and understanding it - not
guessing or trying things.

You should not have to get to a command prompt to start the TS
service, download anything, type anything in or run a batch file - it
should start/stop just fine from Services. If the TS service is set
to Automatic, it should start when XP starts. If it does't work
right, fix it. It the TS service is working properly then fix the
individual tasks.

All of the attempts to stop/start the service or STs will be in the
log - success/failure/why not. If it gets to crowded, stop the
service and delete the log file. Get one task at a time to run
manually or fix it if it doesn't.

Look in c:\windows\tasks for your tasks, look at the columns of useful
information (Last Run Time, Last Result), right click each task of
interest and try to run the task manually, look in columns for success/
failure messages and the log file and then fix the afflicted task if
needs fixing.

I checked the Windows set up and found that the Scheduler was not active and
when I pressed Start now I got the following message The task scheduler
service is not running. Fault OX80041315
I searched for the schedlgu.txt file but only found a file called schedlgu
with no txt.attached. It listed dozens of failed files.. Should I delete all
of these?

 

[Jose]

You are right although I was learning it must have been a pain to you
But many thanks for you help
Blair

Is your Task Scheduler service running or not? If not or it won't
start, post a fresh c:\windows\schedlgu.txt log file showing attempts
to start it from today. This will take about 1 minute to do.

Here is what mine looks like after starting and stopping the service:

"Task Scheduler Service"
Started at 10/27/2009 9:52:40 AM

"Task Scheduler Service"
Exited at 10/27/2009 9:52:50 AM
[ ***** Most recent entry is above this line ***** ]



If your existing STs will not run manually, post the clean log file of
the attempt to manually start the task. This will take about 1 minute
to do.

Look in the c:\windows folder for the schedlgu.txt file, open it with
notepad, copy/paste the relevant parts back here. Delete the log file
so it starts over.

STs are not hard to figure out when the information requested is
presented. There is nothing to download, nothing to type, no batch
files to create, etc.

Why do things you do not need to do when you have everything you need
already?

 

[Pegasus [MVP]]

Although this is dated earlier than your last message it looks like a
final
help. If that is the case how can I| use it?
Blair

This is the batch file that I neglected to attach to my most recent post. I
corrected my oversight within 20 minutes, after which you reported that you
were unable to locate the batch file bm.bat on your own machine. This is why
I said that your chances of fixing your problem without on-site help are
slim because you do need to carry out a number of instructions that go
somewhat beyond the experience level of someone unused to maintaining
Windows.

 

[bm]

You are right although I was learning it must have been a pain to you
But many thanks for you help
Blair

Is your Task Scheduler service running or not? If not or it won't
start, post a fresh c:\windows\schedlgu.txt log file showing attempts
to start it from today. This will take about 1 minute to do.

Here is what mine looks like after starting and stopping the service:

"Task Scheduler Service"
Started at 10/27/2009 9:52:40 AM

"Task Scheduler Service"
Exited at 10/27/2009 9:52:50 AM
[ ***** Most recent entry is above this line ***** ]



If your existing STs will not run manually, post the clean log file of
the attempt to manually start the task. This will take about 1 minute
to do.

Look in the c:\windows folder for the schedlgu.txt file, open it with
notepad, copy/paste the relevant parts back here. Delete the log file
so it starts over.

STs are not hard to figure out when the information requested is
presented. There is nothing to download, nothing to type, no batch
files to create, etc.

Why do things you do not need to do when you have everything you need
already?

I have already ascertained that Task Scheduler is not running and when I
tried to start it I got the message "The Task Scheduler service is not
running" Fault OX80041315

I opened schedlgu and it is filled with entries. Here is an example

"User_Feed_Synchronization-{AD194F03-5854-4F80-8E01-91FDDE91D2B8}.job"
(msfeedssync.exe) 24/07/2008 14:15:00 ** ERROR **
The attempt to retrieve account information for the specified task failed;
therefore, the task did not run. Either an error occurred, or no account
information existed for the task.
The specific error is:
0x8004130f: No account information could be found in the Task Scheduler
security database for the task indicated.
"User_Feed_Synchronization-{AD194F03-5854-4F80-8E01-91FDDE91D2B8}.job"
(msfeedssync.exe) 24/07/2008 14:20:00 ** ERROR **
The attempt to retrieve account information for the specified task failed;
therefore, the task did not run. Either an error occurred, or no account
information existed for the task.
The specific error is:
0x8004130f: No account information could be found in the Task Scheduler
security database for the task indicated.
"User_Feed_Synchronization-{AD194F03-5854-4F80-8E01-91FDDE91D2B8}.job"
(msfeedssync.exe) 24/07/2008 14:25:00 ** ERROR **
The attempt to retrieve account information for the specified task failed;
therefore, the task did not run. Either an error occurred, or no account
information existed for the task.
The specific error is:
0x8004130f: No account information could be found in the Task Scheduler
security database for the task indicated.

If I can't open the scheduler I am a bit stuck
Blair

 

[Jose]

You are right although I was learning it must have been a pain to you
But many thanks for you help
Blair

Is your Task Scheduler service running or not?  If not or it won't
start, post a fresh c:\windows\schedlgu.txt log file showing attempts
to start it from today.  This will take about 1 minute to do.

Here is what mine looks like after starting and stopping the service:

"Task Scheduler Service"
Started at 10/27/2009 9:52:40 AM

"Task Scheduler Service"
Exited at 10/27/2009 9:52:50 AM
[ ***** Most recent entry is above this line ***** ]

If your existing STs will not run manually, post the clean log file of
the attempt to manually start the task.  This will take about 1 minute
to do.

Look in the c:\windows folder for the schedlgu.txt file, open it with
notepad, copy/paste the relevant parts back here.  Delete the log file
so it starts over.

STs are not hard to figure out when the information requested is
presented.   There is nothing to download, nothing to type, no batch
files to create, etc.

Why do things you do not need to do when you have everything you need
already?

I have already ascertained that Task Scheduler is not running and when I
tried to start it I got the message "The Task Scheduler service is not
running" Fault OX80041315

I opened schedlgu and it is filled with entries. Here is an example

"User_Feed_Synchronization-{AD194F03-5854-4F80-8E01-91FDDE91D2B8}.job"
(msfeedssync.exe) 24/07/2008 14:15:00 ** ERROR **
 The attempt to retrieve account information for the specified task failed;
therefore, the task did not run. Either an error occurred, or no account
information existed for the task.
 The specific error is:
 0x8004130f: No account information could be found in the Task Scheduler
security database for the task indicated.
"User_Feed_Synchronization-{AD194F03-5854-4F80-8E01-91FDDE91D2B8}.job"
(msfeedssync.exe) 24/07/2008 14:20:00 ** ERROR **
 The attempt to retrieve account information for the specified task failed;
therefore, the task did not run. Either an error occurred, or no account
information existed for the task.
 The specific error is:
 0x8004130f: No account information could be found in the Task Scheduler
security database for the task indicated.
"User_Feed_Synchronization-{AD194F03-5854-4F80-8E01-91FDDE91D2B8}.job"
(msfeedssync.exe) 24/07/2008 14:25:00 ** ERROR **
 The attempt to retrieve account information for the specified task failed;
therefore, the task did not run. Either an error occurred, or no account
information existed for the task.
 The specific error is:
 0x8004130f: No account information could be found in the Task Scheduler
security database for the task indicated.

If I can't open the scheduler I am a bit stuck
Blair

I missed that part before with all the other stuff happening.

In your explorer under Virew, enable Show hidden files and folder,
uncheck Hide extensions for know file types so you can locate
schedlgu.txt easily.

If you have a schedlgu.txt file, it was running at some point. Look
at the dates in your log file - do those look right? Is your system
date set to 2008?

When do you see this OX80041315 message - is it in the log?

What are the properties of Task Scheduler in Services?

%SystemRoot%\system32\services.msc /s

Is it set to Automatic and running?

If it is running, stop it, rename or delete the schedlgu.txt file -
you can't edit it or delete it if the service is running.

Change it to Automatic, start it, check the log, reboot and check it
and the log again.

Your existing jobs may not be fixable, but they can be recreated. Get
the service running, we'll make a simple task to test it, then get
your other STs recreated. You will probably not be able to get the
existing ones to run.

If ST still will not start, cut and paste your STs to another folder
so there are no STs in c:\windows\tasks then try the service. One/
all of the tasks is broken. If just one is brokwn in a certain way,
nothing will work right.

The error you see is well known, but first you need to get the TS
service working reliably. Forget about getting your old Tasks to run
for now.

and send information about your configuration:

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste
the information back here.

There will be some personal information (like System Name and User
Name), and whatever appears to
be private information to you, just delete from the pasted
information.

This will minimize back and forth Q&A and eliminate guesswork and
assumptions.

 

[Jose]

I have a new external HD from Lacie which comes with it's own backup
software. Every time I try to backup I am asked for my user name & password.
I have never used a password in Windows but since their system demands itI
added a password for Windows XP.
The message I get is "Failed to set Scheduled User name or password. Please
retype them"
I am wondering if there is some procedure I have missed in creating my user
name & password in XP
Is there some way of checking the correctness of them?
Blair

It is not recommended to run a ST with Windows using an account that
has no PW.

Either add a PW to your account or create a new account with a PW for
your STs and change the properties of the STs to use the account that
has a PW.

Here is an idea for your Lacie product to somehow override the
recommendation

http://en.kioskea.net/faq/sujet-1794-request-password-in-scheduled-tasks

 

[bm]

I have a new external HD from Lacie which comes with it's own backup
software. Every time I try to backup I am asked for my user name &
password.
I have never used a password in Windows but since their system demands it
I
added a password for Windows XP.
The message I get is "Failed to set Scheduled User name or password.
Please
retype them"
I am wondering if there is some procedure I have missed in creating my
user
name & password in XP
Is there some way of checking the correctness of them?
Blair

It is not recommended to run a ST with Windows using an account that
has no PW.

Either add a PW to your account or create a new account with a PW for
your STs and change the properties of the STs to use the account that
has a PW.

Here is an idea for your Lacie product to somehow override the
recommendation

http://en.kioskea.net/faq/sujet-1794-request-password-in-scheduled-tasks

This looks like a good solution. If I do this will I also have to carry out
your previous instruction as well?
I am extremely grateful to you for your help
Kind regards
Blair

 

[Jose]

It is not recommended to run a ST with Windows using an account that
has no PW.

Either add a PW to your account or create a new account with a PW for
your STs and change the properties of the STs to use the account that
has a PW.

Here is an idea for your Lacie product to somehow override the
recommendation

http://en.kioskea.net/faq/sujet-1794-request-password-in-scheduled-tasks

This looks like a good solution. If I do this will I also have to carry out
your previous instruction as well?
I am extremely grateful to you for your help
Kind regards
Blair

I would try the link first. I found it later when I started looking
specifically at STs and Lacie stuff.

I do not have any Lacie components and I don't know why they would do
things this way, but since they even have such an option tells me they
must have encountered it before.

I would still encourage you to understand how the schedlgu.txt file
works, where it is, how to start it anew, etc. so troublshooting STs
will be easier later, or if this problem persists. Still work on
stopping and starting the ST service manually, deleting the log file
in between so only a start is in the log file, etc. THEN start
troubleshooting afflicted tasks.

You want your clean log to look something like this when you start the
TS service:

"Task Scheduler Service"
Started at 10/28/2009 8:12:09 AM
[ ***** Most recent entry is above this line ***** ]

Nobody wants to look at some huge log file with a bunch of old garbage
in it - a brand new log with just relevant information is much better!

Please go ahead and post up the msinfo32 information.

 

[bm]

It is not recommended to run a ST with Windows using an account that
has no PW.

Either add a PW to your account or create a new account with a PW for
your STs and change the properties of the STs to use the account that
has a PW.

Here is an idea for your Lacie product to somehow override the
recommendation

http://en.kioskea.net/faq/sujet-1794-request-password-in-scheduled-tasks

This looks like a good solution. If I do this will I also have to carry
out
your previous instruction as well?
I am extremely grateful to you for your help
Kind regards
Blair

I would try the link first. I found it later when I started looking
specifically at STs and Lacie stuff.

I do not have any Lacie components and I don't know why they would do
things this way, but since they even have such an option tells me they
must have encountered it before.

I would still encourage you to understand how the schedlgu.txt file
works, where it is, how to start it anew, etc. so troublshooting STs
will be easier later, or if this problem persists. Still work on
stopping and starting the ST service manually, deleting the log file
in between so only a start is in the log file, etc. THEN start
troubleshooting afflicted tasks.

You want your clean log to look something like this when you start the
TS service:

"Task Scheduler Service"
Started at 10/28/2009 8:12:09 AM
[ ***** Most recent entry is above this line ***** ]

Nobody wants to look at some huge log file with a bunch of old garbage
in it - a brand new log with just relevant information is much better!

Please go ahead and post up the msinfo32 information.

I have attempted to answer your points but I may still be muddled

I ran the schedlgu file and it had numerous entries all on the 27/10/08. You
said delete them which I did
(My pc is set to the correct date) TS services are set Automatic but the
system is shown as stopped
When I pressed the Start button I get the error message ox80041315
%Systemroot%\system32\services.msc shows Automatic but stopped
Deleted all the ST in the list and created a new one.. Result message; New
task created but will not run because the account is not set. Error
ox80041315
I am not worried about keeping any readings as I am just starting backups
with this new HD.
So I can create an ST but because ST is not running nothing will happen.
How do I get ST to run?
Finally I ran msinfo32 but got the reply "Can't collect information.
Windows management may have moved or missing"
Sorry not to able to do more
I need further instruction
Blair

 

[Pegasus [MVP]]

Although this is dated earlier than your last message it looks like a
final
help. If that is the case how can I| use it?
Blair

I note that you do not seem to make a lot of progress. In desperate cases
like these I sometimes suggest a drastic measure: That you open up your
machine for me to find out what's wrong. If you're interested in finding out
how this might work, send a note to pegasus_fnlATyahooDOTcom.

 

[bm]

I note that you do not seem to make a lot of progress. In desperate cases
like these I sometimes suggest a drastic measure: That you open up your
machine for me to find out what's wrong. If you're interested in finding
out how this might work, send a note to pegasus_fnlATyahooDOTcom.

Yes I am interested. But how do I send a message ?
"pegasus_fnlATyahooDOTcom." is not an email address
Blair

 

[Bob I]

Yes I am interested. But how do I send a message ?
"pegasus_fnlATyahooDOTcom." is not an email address
Blair

Replace "AT" with "@" and "DOT" with "."

 

[bm]

Replace "AT" with "@" and "DOT" with "."

Many thanks Bob- I should have thought of that!!
Blair

 

[Pegasus [MVP]]

A remote access connection to the OP's PC revealed the following:
- The Task Scheduler service was NOT running.
- Attempts to start it resulted in the error message "File not found".
Windows failed to say which file it could not fine. Very helpful . . .
- Attempts to start other services (e.g. Windows Time) were successful.
- Re-installing IE7 did not fix the problem.
- A closer examination of the Task Scheduler service in the registry
revealed that the ImagePath entry was wrong. It read
C:\WINDOWS\system32\drivers\services.exe
instead of
%SystemRoot%\System32\svchost.exe -k netsvcs

I suspect malware or maybe a poorly written installation program for two
reasons:
a) The entry reads "c:\Windows" instead of "%SystemRoot%". I believe that
"%SystemRoot%" is the usual coding method.
b) The file C:\WINDOWS\system32\drivers\services.exe does not exist. It
resides in c:\windows\system32.

The OP does not have the skills to make such a change by himself.

Problem solved, thread closed.