Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

ShadowCopyVolume{1d9b67f1-1a01-11dc-ab86-00c09f40f098}.job Task warning in log

Posted on 2008-10-14
4
Medium Priority
?
2,485 Views
Last Modified: 2010-04-21
I am getting the following error logged in the Scheduled Task log for Volume Shadow Copy jobs.

"ShadowCopyVolume{1d9b67f1-1a01-11dc-ab86-00c09f40f098}.job" (vssadmin.exe) 10/10/2008 12:00:00 PM ** WARNING **
      Invalid working directory..
      The specific error is:
      0x00000003: The system cannot find the path specified.
      Verify that the directory exists and try again.

This warning is followed by a sucessfull start and finish entry:

"ShadowCopyVolume{1d9b67f1-1a01-11dc-ab86-00c09f40f098}.job" (vssadmin.exe)
      Started 10/10/2008 12:00:00 PM
"ShadowCopyVolume{1d9b67f1-1a01-11dc-ab86-00c09f40f098}.job" (vssadmin.exe)
      Finished 10/10/2008 12:00:08 PM
      Result: The task completed with an exit code of (0).

I have verified Shadow Copies are successful and can restore files to previous versions.  Seems to be a false error.
I would like to resolve because I monitor the log file for Errors and Warnings and notify via email.

Thanks for any insight!
0
Comment
Question by:innproc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 80

Expert Comment

by:arnold
ID: 22715450
Look in the scheduled task to see what the job is/does.
Check the working directory to which the scheduled task points.
i.e. the working directory reflected there might no longer exist.
0
 

Author Comment

by:innproc
ID: 22720778
I have 2 Dell PowerVault 745N.  I enable Volume Shadow Copies for the entire D drive.  D is the storage and share drive.  In the case of the first NAS the shadow copy points back to the d drive as the storage volume.  The second NAS's shadow copies point to a SAN attached volume (E:).

In both cases the default Shadow Copy settings and schedules were used.  Both storage targets also have more than 80% capacity free.

Properties of the task:

Run: C:\WINDOWS\system32\vssadmin.exe Create Shadow /AutoRetry=5 /For=\\?\Volume{1d9b67f1-1a01-11dc-ab86-00c09f40f098}\

Start in: %systemroot%\system32

Schedule:
every day of the week at 5:00 AM and 12:00 PM

Again, the task was automatically created when I enabled Volume Shadow Copy for the volume.  I used all default settings for the job.

The above warning happens on both servers for each scheduled Shadow Copy job, but ultimately the shadow copies are successful.

Hope this clarifies my issue.

Thanks
0
 
LVL 80

Accepted Solution

by:
arnold earned 300 total points
ID: 22723780
Try removing the entry in the start in box.  This seems to be what the message deals with.
0
 

Author Closing Comment

by:innproc
ID: 31505969
Had to open a Microsoft support case to resolve root problem, but arnold solution also stops this error entry in the Task Log.
0

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

INTRODUCTION The purpose of this document is to demonstrate the Installation and configuration of the Data Protection Manager product. Note that this demonstration was prepared on the basis of Windows OS is 2008 R2 and DPM 2010. DATA PROTECTI…
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

618 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question