"Task Scheduler" in w3k3 cluster failover
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
"Task Scheduler" in w3k3 cluster failover

 
Post new topic   Reply to topic    Windows Server Forum Index -> Clustering
Author Message
Bcn
Guest
Posted: Mon Feb 14, 2005 6:19 pm    Post subject: "Task Scheduler" in w3k3 cluster failover Reply with quote
Hi,

I would like to know if is possible to set up a Task Scheduler service in a
cluster failover?

Thanks in advance
Back to top
Rodney R. Fournier [MVP]
Guest
Posted: Mon Feb 14, 2005 6:53 pm    Post subject: Re: "Task Scheduler" in w3k3 cluster failover Reply with quote
I have never tried it, but you could do it as a Generic Service.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog

"Bcn" <Bcn@discussions.microsoft.com> wrote in message
news:C820E15E-2E26-472C-B13F-21C17485CE53@microsoft.com...
Quote:
Hi,

I would like to know if is possible to set up a Task Scheduler service in
a
cluster failover?

Thanks in advance
Back to top
Mike Rosado [MSFT]
Guest
Posted: Mon Feb 14, 2005 8:08 pm    Post subject: Re: "Task Scheduler" in w3k3 cluster failover Reply with quote
Hi BCN,

See if the following works for you. Many Generic Services have registry
values that are outside the Cluster database (registry hive). In these
cases, it is necessary to sync the registry keys between the nodes for
consistency, and modify the registry so that common information is available
to both nodes.

Although the Generic Service resource can be used as an effective temporary
solution, it is not a good long term solution because the Generic Service
resource does not contain specific code to test if that particular service
is online. The Generic Service resource only checks with the Service Control
Manager to get a state for the service. The proper long term solution is to
write a service-specific resource dynamic-link library (.dll) file.

The Generic Service resource calls the same function for both isalive and
looksalive. The function calls the QueryServiceStatus function to get the
current state of the service. If the service is either not running, or is in
a start-pending state, the LooksAlive or IsAlive function is returned as
"failed."

In several cases we located the registry keys, modified them so that shared
job information is stored on the shared disk, and then added the registry
keys to the
Registry Replication properties for the generic service.

The following steps should work for you:

1. The scheduled job information is located in c:\%systemroon%\tasks
subdirectory.

- create a tasks directory on the shared disk

2. Modify the following registry key so that the TasksFolder location is
pointed to the tasks subdirectory on the shared disk.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SchedulingAgent

This key has the following value: TasksFolder reg_expand_sz
%SystemRoot%\Tasks (change this path to task directory on the shared disk)

3. Add "software\microsoft\schedulingagent" (minus the quotes) to the
Registry Replication tab for the Generic Service properties.

NOTE: We have had customers trying to perform the work and test from a
Terminal Server session and the jobs were initially failing. We had them
log off and back on (see KB232276) and then the jobs worked OK.

232276 Drive Letter Not Visible or Drive Letter Changed to Question Mark or
http://support.microsoft.com/?id=232276

NOTE: The security credentials for each job are contained in the Protected
Storage Database on the local node and not with the job. So in order for a
job to work on both nodes we need to refresh the credentials of the job on
each node. To do that, create the job on first node, set the credentials.
Move the Generic Service resource to the 2nd node and enter the credentials
for the job again. This issue is discussed in the following KB317529:

317529 Scheduled task does not run after you push the task to another
computer
http://support.microsoft.com/?id=317529

--
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
<http://www.microsoft.com/info/cpyright.htm>

-----Original Message-----

"Bcn" <Bcn@discussions.microsoft.com> wrote in message
news:C820E15E-2E26-472C-B13F-21C17485CE53@microsoft.com...
Quote:
Hi,

I would like to know if is possible to set up a Task Scheduler service in
a
cluster failover?

Thanks in advance
Back to top
BCN
Guest
Posted: Tue Feb 15, 2005 8:15 pm    Post subject: Re: "Task Scheduler" in w3k3 cluster failover Reply with quote
Thaks was helpful

"Mike Rosado [MSFT]" wrote:

Quote:
Hi BCN,

See if the following works for you. Many Generic Services have registry
values that are outside the Cluster database (registry hive). In these
cases, it is necessary to sync the registry keys between the nodes for
consistency, and modify the registry so that common information is available
to both nodes.

Although the Generic Service resource can be used as an effective temporary
solution, it is not a good long term solution because the Generic Service
resource does not contain specific code to test if that particular service
is online. The Generic Service resource only checks with the Service Control
Manager to get a state for the service. The proper long term solution is to
write a service-specific resource dynamic-link library (.dll) file.

The Generic Service resource calls the same function for both isalive and
looksalive. The function calls the QueryServiceStatus function to get the
current state of the service. If the service is either not running, or is in
a start-pending state, the LooksAlive or IsAlive function is returned as
"failed."

In several cases we located the registry keys, modified them so that shared
job information is stored on the shared disk, and then added the registry
keys to the
Registry Replication properties for the generic service.

The following steps should work for you:

1. The scheduled job information is located in c:\%systemroon%\tasks
subdirectory.

- create a tasks directory on the shared disk

2. Modify the following registry key so that the TasksFolder location is
pointed to the tasks subdirectory on the shared disk.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SchedulingAgent

This key has the following value: TasksFolder reg_expand_sz
%SystemRoot%\Tasks (change this path to task directory on the shared disk)

3. Add "software\microsoft\schedulingagent" (minus the quotes) to the
Registry Replication tab for the Generic Service properties.

NOTE: We have had customers trying to perform the work and test from a
Terminal Server session and the jobs were initially failing. We had them
log off and back on (see KB232276) and then the jobs worked OK.

232276 Drive Letter Not Visible or Drive Letter Changed to Question Mark or
http://support.microsoft.com/?id=232276

NOTE: The security credentials for each job are contained in the Protected
Storage Database on the local node and not with the job. So in order for a
job to work on both nodes we need to refresh the credentials of the job on
each node. To do that, create the job on first node, set the credentials.
Move the Generic Service resource to the 2nd node and enter the credentials
for the job again. This issue is discussed in the following KB317529:

317529 Scheduled task does not run after you push the task to another
computer
http://support.microsoft.com/?id=317529

--
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/info/cpyright.htm

-----Original Message-----

"Bcn" <Bcn@discussions.microsoft.com> wrote in message
news:C820E15E-2E26-472C-B13F-21C17485CE53@microsoft.com...
Hi,

I would like to know if is possible to set up a Task Scheduler service in
a
cluster failover?

Thanks in advance


Back to top
Mario
Guest
Posted: Thu Oct 13, 2005 8:50 pm    Post subject: Re: "Task Scheduler" in w3k3 cluster failover Reply with quote
I try your procedure but the error is: 0x80070002 The system cannot find the
file specified.
Thanks for help,
Mario

"Mike Rosado [MSFT]" wrote:

Quote:
Hi BCN,

See if the following works for you. Many Generic Services have registry
values that are outside the Cluster database (registry hive). In these
cases, it is necessary to sync the registry keys between the nodes for
consistency, and modify the registry so that common information is available
to both nodes.

Although the Generic Service resource can be used as an effective temporary
solution, it is not a good long term solution because the Generic Service
resource does not contain specific code to test if that particular service
is online. The Generic Service resource only checks with the Service Control
Manager to get a state for the service. The proper long term solution is to
write a service-specific resource dynamic-link library (.dll) file.

The Generic Service resource calls the same function for both isalive and
looksalive. The function calls the QueryServiceStatus function to get the
current state of the service. If the service is either not running, or is in
a start-pending state, the LooksAlive or IsAlive function is returned as
"failed."

In several cases we located the registry keys, modified them so that shared
job information is stored on the shared disk, and then added the registry
keys to the
Registry Replication properties for the generic service.

The following steps should work for you:

1. The scheduled job information is located in c:\%systemroon%\tasks
subdirectory.

- create a tasks directory on the shared disk

2. Modify the following registry key so that the TasksFolder location is
pointed to the tasks subdirectory on the shared disk.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SchedulingAgent

This key has the following value: TasksFolder reg_expand_sz
%SystemRoot%\Tasks (change this path to task directory on the shared disk)

3. Add "software\microsoft\schedulingagent" (minus the quotes) to the
Registry Replication tab for the Generic Service properties.

NOTE: We have had customers trying to perform the work and test from a
Terminal Server session and the jobs were initially failing. We had them
log off and back on (see KB232276) and then the jobs worked OK.

232276 Drive Letter Not Visible or Drive Letter Changed to Question Mark or
http://support.microsoft.com/?id=232276

NOTE: The security credentials for each job are contained in the Protected
Storage Database on the local node and not with the job. So in order for a
job to work on both nodes we need to refresh the credentials of the job on
each node. To do that, create the job on first node, set the credentials.
Move the Generic Service resource to the 2nd node and enter the credentials
for the job again. This issue is discussed in the following KB317529:

317529 Scheduled task does not run after you push the task to another
computer
http://support.microsoft.com/?id=317529

--
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/info/cpyright.htm

-----Original Message-----

"Bcn" <Bcn@discussions.microsoft.com> wrote in message
news:C820E15E-2E26-472C-B13F-21C17485CE53@microsoft.com...
Hi,

I would like to know if is possible to set up a Task Scheduler service in
a
cluster failover?

Thanks in advance


Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Clustering All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB