It ran properly, according to schedule the first day at 12noon, but it has
not ran since. (approximately 4 days ago).
The scheduled task (ShadowCopyVolume{3e8dee21-e3d3-11d7-8b36-505054503030})
appears in the "scheduled tasks" control panel applet , but when I attempt
to view the properties of the scheduled task, I get a Task scheduler error.
"General Page initialization failed. The specific error is 0x8007000d: The
data is invalid."
I click "OK" and I can see the schedule.
I can, however address the Volume's properties directly and Create shadow
copies manually without error.
Looks like a problem with the scheduler..
Any ideas?
TIA-
Rob
You are correct, this seems to be an issue with Task Scheduler (not
with shadow copies). We are looking into it. I have a couple of
questions:
1) Did you promote the machine to a domain controller, or demote it
recently?
2) If yes, when did you enabled shadow copies? Before or after
promoting to a DC?
Thanks, Adi
P.S. This posting is provided "AS IS" with no warranties, and confers
no rights.
"Rob Stewart" <rste...@com.yada> wrote in message news:<OfZm6Nif...@TK2MSFTNGP12.phx.gbl>...
It came up as a member, Shadow copies was enabled on E: then it was promoted
to a DC.
"Adi Oltean [MSFT]" <aol...@microsoft.com> wrote in message
news:151ad89d.0309...@posting.google.com...
"Rob Stewart" <rste...@com.yada> wrote in message
news:OE1fLwsf...@TK2MSFTNGP09.phx.gbl...
We are still trying to reproduce the problem.
In the meantime, a workaround would be to delete the schedule and
re-create it. Please let me know if this solves the issue that you are
seeing.
Steps:
1) Open the properties for the volume, select the Shadow Copies tab
2) select a volume and click "Settings"
3) click "Schedule..." and delete all the schedules. Press OK all the
way down.
4) Now, in the initial Shadow Copies property page the volume should
show as "Disabled". Press "Enable" to re-enable the volume.
5) Make sure that the scheduled tasks are working now.
Thanks, Adi
P.S. This posting is provided "AS IS" with no warranties, and confers
no rights.
"Rob Stewart" <rste...@com.yada> wrote in message news:<#qtwDJTg...@tk2msftngp13.phx.gbl>...
It likely had to do with the user account that the
schedule was stuck with, since VSC was implemented BEFORE
upgrading the machine to a DC.
There is a patch for this which will be released soon.
Thanks,
-RS
>.
>
We had the exact same problem on two new 2003 servers. Both were built
as fresh machines and DCPROMOed. After that we setup VSS and the
schedules never ran. We followed your below steps and got it to work.
Definately a bug.
Thanks
Mike
"Rob Stewart" <rste...@com.yada> wrote in message news:<082101c386ac$6963c930$a101...@phx.gbl>...
>.
>