Task Scheduler - general page initialization failed

Could someone out there email me the systaskfix.exe utility as well.
I would appreciate it.

Dmazck wrote:

Could someone out there email me the systaskfix.exe utility as well.
I would appreciate it.


Accepting and running an executable file sent to you by a stranger on a
listserv would be a very foolhardy thing to do.Most of the time, what you
got would undoubtedly be fine, but there are crazy people out there, and the
risk of getting something malicious is just too great.

Also, posting your real E-mail address, unmunged, on a listserv is just an
invitation to get spam. In the future, if you must do this, modify the
address, and provide instruction to fix it. Say somethink like
(remove shoes to send mail.)

--
Ken Blake - Microsoft MVP Windows: Shell/User
Please reply to the newsgroup

Al Marklinwrote:
Sorry you had to reinstall, Jan. In my case, the problem came from a
forced
demotion from an AD server, which could no longer synchronize with
the other
servers. Rejoining the domain after a manual clean up worked fine,
except for
the AT System account problem, but deleting that folder referenced
below
fixed the problem like a charm.

"jschulenburg via WindowsKB.com" wrote:

Al,

I solved the problem by reïnstalling the server. The problem was
that i
changed the AT service account before i ran dcpromo to convert the
server to
a DC. After promoting the server, the AT service account cannot be
accessed
anymore and jobs scheduled using AT/SOON fail to run.

The right installation sequence is:
- install the server
- add it to the domain (if necessary)
- run dcpromo
- alter the AT service account

--
Kind regards,

Jan Schulenburg

Message posted via WindowsKB.com
http://www.windowskb.com/Uwe/Forums....owsxp/200607/1
[/quote:e5da68bb43]

HI All,

I am in a similar situation. Would someone please forward the
systaskfix.exe tool to me as well.. thanks in advance!!!!

Hi i have the same problem but i can't find SysTaskFix in internet.
please give me it truth email the link or tool diretcly.
Please!! i am desperate.!!


--
LZ


"Vincent Xu [MSFT]" wrote:

Hi ,

Thanks for sending me the MPS report.

After research, I think that we can use the systaskfix.exe tool to reset
the task scheduler database. HINT: I have sent the tool to your email box
at .

To use this tool, follow these steps:

1. Run "SysTaskFix.exe /fix" (without the quotation marks) from the command
line.

2. Click "Start", and then click "Control Panel".

3. Double-click "Scheduled Tasks".

4. Right-click on the task and then click "Properties".

5. In the "Run as" box on the "Task" tab, enter the username and password
or "NTAUTHORITY\SYSTEM".

6. Click "OK".

In Windows XP, we may try to use the SCHTASKS.EXE tool to run the task with
the system account to see if the task can run properly. For details on how
to use the SCHTASKS.EXE tool, type "SCHTASKS.EXE /?" in a command line.
HINT: To change the user account to run a task, you can use the following
command:

Schtasks /change /U user /P password /RU SYSTEM /TN Task name

Hope this helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

================================================== ====
Get Secure! - www.microsoft.com/security
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====



--------------------
X-Tomcat-ID: 81024859
References:


MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: (Vincent Xu [MSFT])
Organization: Microsoft
Date: Tue, 16 May 2006 06:08:31 GMT
Subject: Task Scheduler - general page initialization failed
X-Tomcat-NG: microsoft.public.windowsxp.general
Message-ID:
Newsgroups: microsoft.public.windowsxp.general
Lines: 91
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windowsxp.general:1507447
NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122

Hi,

I suggest you collect some system information using Microsoft
Configuration
Capture Utility , and please send the CAB (Zip) file to me.

Please download the tool:

http://download.microsoft.com/downlo...fe5-a579-30b0b
d9
15706/MPSRPT_SETUPPerf.EXE

For more information and overview, please refer to link below:

KB818742 Overview of the Microsoft Configuration Capture Utility
(MPS_REPORTS)

http://support.microsoft.com/?id=818742

Note: The CAB file will be generated for your convenience in the
%systemroot%\MPSReports\Setup\Report\Cab directory called
%COMPUTERNAME%_MPSReports_.CAB. The CAB file will contain the reports
generated by the MPS Reporting Tool. If the CAB file isn't produced,
please
compress all of the result files under
%systemroot%\MPSReport\Setup\Report
as a Zip file. (Note: %systemroot% is the folder where you install
Windows.)

Please send me the CAB file via the email :


Thanks.

Best regards,

Vincent Xu
Microsoft Online Partner Support

================================================ ======
Get Secure! - www.microsoft.com/security
================================================ ======
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================ ======
This posting is provided "AS IS" with no warranties,and confers no
rights.
================================================ ======



--------------------
Thread-Topic: Task Scheduler - general page initialization failed
thread-index: AcZ4R27bZJ/576YtT2u0dZAkHamtlA==
X-WBNR-Posting-Host: 198.146.154.32
From: =?Utf-8?B?Sm9zaCBLZWxsZXk=?=
References:

Subject: Task Scheduler - general page initialization failed
Date: Mon, 15 May 2006 10:46:02 -0700
Lines: 30
Message-ID:
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windowsxp.general
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windowsxp.general:1507153
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windowsxp.general

"Vincent Xu [MSFT]" wrote:

"The attempt to retrieve account information for the specified task
failed"
error message when you use Task Scheduler to schedule volume shadow
copy to
run in Windows Server 2003
http://support.microsoft.com/?id=822904

These are Windows XP computers, so that article does not apply.

If it doesn't apply, I have following suggestions:

Suggestoin 1:
=================
remove the problematic computer from domain and create a new local
user
account to see the result.

I tried this, and it did not help. (As I mentioned, we're trying to
run
tasks under NT AUTHORITY\System rather than under any particular user's
account.)

Suggestion 2:
=====================
We may use Clean Boot to eliminate third party interference. To boot
into
Clean Boot environment:

This didn't help either.

Any other ideas?

Josh Kelley

I met the same problem, and I can't find the systaskfix.exe everywhere. Would
someone forward the systaskfix.exe tool to me as well please?

Many thanks!

" wrote:

Al Marklinwrote:
Sorry you had to reinstall, Jan. In my case, the problem came from a
forced
demotion from an AD server, which could no longer synchronize with
the other
servers. Rejoining the domain after a manual clean up worked fine,
except for
the AT System account problem, but deleting that folder referenced
below
fixed the problem like a charm.

"jschulenburg via WindowsKB.com" wrote:

Al,

I solved the problem by reïnstalling the server. The problem was
that i
changed the AT service account before i ran dcpromo to convert the
server to
a DC. After promoting the server, the AT service account cannot be
accessed
anymore and jobs scheduled using AT/SOON fail to run.

The right installation sequence is:
- install the server
- add it to the domain (if necessary)
- run dcpromo
- alter the AT service account

--
Kind regards,

Jan Schulenburg

Message posted via WindowsKB.com
http://www.windowskb.com/Uwe/Forums....owsxp/200607/1
[/quote:e5da68bb43]

HI All,

I am in a similar situation. Would someone please forward the
systaskfix.exe tool to me as well.. thanks in advance!!!!

On Sep 27, 11:51*pm, Jason wrote:
I met the same problem, and I can't find the systaskfix.exe everywhere. Would
someone forward the systaskfix.exe tool to me as well please?

Many thanks!



" wrote:
Al Marklinwrote:
Sorry you had to reinstall, Jan. In my case, the problem came from a
forced
demotion from an AD server, which could no longer synchronize with
the other
servers. Rejoining the domain after a manual clean up worked fine,
except for
the AT System account problem, but deleting that folder referenced
below
fixed the problem like a charm.

"jschulenburg via WindowsKB.com" wrote:

Al,

I solved the problem by reïnstalling the server. The problem was
that i
changed the AT service account before i ran dcpromo to convert the
server to
a DC. After promoting the server, the AT service account cannot be
accessed
anymore and jobs scheduled using AT/SOON fail to run.

The right installation sequence is:
- install the server
- add it to the domain (if necessary)
- run dcpromo
- alter the AT service account

--
Kind regards,

Jan Schulenburg

Message posted via WindowsKB.com
http://www.windowskb.com/Uwe/Forums....owsxp/200607/1
[/quote:e5da68bb43]

HI All,

I am in a similar situation. Would someone please forward the
systaskfix.exe tool to me as well.. thanks in advance!!!!

What exactly is the problem again? That original post is pretty old.

When you checked out the Google results for systaskfix.exe, what did
you find?

If your problem is 0x8007000d and you searched for that, were those
solutions unable to resolve the issue?

Do any of those situations apply to you

It doesn't make sense (to me) to try to download one program to try to
fix another program that should be working properly in the first
place, but not everybody shares this opinion.

No, my error is: 0x80090016: Keyset does not exist

"Jose" wrote:

On Sep 27, 11:51 pm, Jason wrote:
I met the same problem, and I can't find the systaskfix.exe everywhere. Would
someone forward the systaskfix.exe tool to me as well please?

Many thanks!



" wrote:
Al Marklinwrote:
Sorry you had to reinstall, Jan. In my case, the problem came from a
forced
demotion from an AD server, which could no longer synchronize with
the other
servers. Rejoining the domain after a manual clean up worked fine,
except for
the AT System account problem, but deleting that folder referenced
below
fixed the problem like a charm.

"jschulenburg via WindowsKB.com" wrote:

Al,

I solved the problem by reïnstalling the server. The problem was
that i
changed the AT service account before i ran dcpromo to convert the
server to
a DC. After promoting the server, the AT service account cannot be
accessed
anymore and jobs scheduled using AT/SOON fail to run.

The right installation sequence is:
- install the server
- add it to the domain (if necessary)
- run dcpromo
- alter the AT service account

--
Kind regards,

Jan Schulenburg

Message posted via WindowsKB.com
http://www.windowskb.com/Uwe/Forums....owsxp/200607/1
[/quote:e5da68bb43]

HI All,

I am in a similar situation. Would someone please forward the
systaskfix.exe tool to me as well.. thanks in advance!!!!

What exactly is the problem again? That original post is pretty old.

When you checked out the Google results for systaskfix.exe, what did
you find?

If your problem is 0x8007000d and you searched for that, were those
solutions unable to resolve the issue?

Do any of those situations apply to you

It doesn't make sense (to me) to try to download one program to try to
fix another program that should be working properly in the first
place, but not everybody shares this opinion.

On Sep 28, 9:57*pm, Jason wrote:
No, my error is: 0x80090016: Keyset does not exist



"Jose" wrote:
On Sep 27, 11:51 pm, Jason wrote:
I met the same problem, and I can't find the systaskfix.exe everywhere. Would
someone forward the systaskfix.exe tool to me as well please?

Many thanks!

" wrote:
Al Marklinwrote:
Sorry you had to reinstall, Jan. In my case, the problem came from a
forced
demotion from an AD server, which could no longer synchronize with
the other
servers. Rejoining the domain after a manual clean up worked fine,
except for
the AT System account problem, but deleting that folder referenced
below
fixed the problem like a charm.

"jschulenburg via WindowsKB.com" wrote:

Al,

I solved the problem by reïnstalling the server. The problem was
that i
changed the AT service account before i ran dcpromo to convert the
server to
a DC. After promoting the server, the AT service account cannot be
accessed
anymore and jobs scheduled using AT/SOON fail to run.

The right installation sequence is:
- install the server
- add it to the domain (if necessary)
- run dcpromo
- alter the AT service account

--
Kind regards,

Jan Schulenburg

Message posted via WindowsKB.com
http://www.windowskb.com/Uwe/Forums....owsxp/200607/1
[/quote:e5da68bb43]

HI All,

I am in a similar situation. Would someone please forward the
systaskfix.exe tool to me as well.. thanks in advance!!!!

What exactly is the problem again? *That original post is pretty old.

When you checked out the Google results for systaskfix.exe, what did
you find?

If your problem is 0x8007000d and you searched for that, were those
solutions unable to resolve the issue?

Do any of those situations apply to you

It doesn't make sense (to me) to try to download one program to try to
fix another program that should be working properly in the first
place, but not everybody shares this opinion.

Here is an old article that I read that some folks say works fine with
XP.

I cannot recreate the error right now, but it is easy to check it out.

http://support.microsoft.com/?id=246183

Thanks for your reply, but I had alreay tried these steps before, and it
didn't work to my XP.

"Jose" wrote:

On Sep 28, 9:57 pm, Jason wrote:
No, my error is: 0x80090016: Keyset does not exist



"Jose" wrote:
On Sep 27, 11:51 pm, Jason wrote:
I met the same problem, and I can't find the systaskfix.exe everywhere. Would
someone forward the systaskfix.exe tool to me as well please?

Many thanks!

" wrote:
Al Marklinwrote:
Sorry you had to reinstall, Jan. In my case, the problem came from a
forced
demotion from an AD server, which could no longer synchronize with
the other
servers. Rejoining the domain after a manual clean up worked fine,
except for
the AT System account problem, but deleting that folder referenced
below
fixed the problem like a charm.

"jschulenburg via WindowsKB.com" wrote:

Al,

I solved the problem by reïnstalling the server. The problem was
that i
changed the AT service account before i ran dcpromo to convert the
server to
a DC. After promoting the server, the AT service account cannot be
accessed
anymore and jobs scheduled using AT/SOON fail to run.

The right installation sequence is:
- install the server
- add it to the domain (if necessary)
- run dcpromo
- alter the AT service account

--
Kind regards,

Jan Schulenburg

Message posted via WindowsKB.com
http://www.windowskb.com/Uwe/Forums....owsxp/200607/1
[/quote:e5da68bb43]

HI All,

I am in a similar situation. Would someone please forward the
systaskfix.exe tool to me as well.. thanks in advance!!!!

What exactly is the problem again? That original post is pretty old.

When you checked out the Google results for systaskfix.exe, what did
you find?

If your problem is 0x8007000d and you searched for that, were those
solutions unable to resolve the issue?

Do any of those situations apply to you

It doesn't make sense (to me) to try to download one program to try to
fix another program that should be working properly in the first
place, but not everybody shares this opinion.

Here is an old article that I read that some folks say works fine with
XP.

I cannot recreate the error right now, but it is easy to check it out.

http://support.microsoft.com/?id=246183