> Glad to read that it doesn't imapct the actual backup.
>
> Personally, I would ignore the errors you see in the Event Log, Thomas.
> They are
> non-critical and informational.
> However, you should feel free to contact support on it.
>
> -steve
>
> "Thomas R Grassi Jr" <thomasgrassi[ at ]hotmail.com> wrote:
>
>>Steve
>>
>>Good to hear from you again
>>
>>Yes tyhe backups run to a successfull end
>>
>>I have it setup to run every day at 6:00 AM
>>
>>Today I took notice the errors were there.
>>
>>I ran it again to see if I was right about it being WLOC
>>and it occured again.
>>
>>I just tested it by making the Windows Shadow Copy service disabled
>>
>>This time I got different VSS errors
>>
>>As I stated before I looked up the errors codes and Microsoft does not
>>have
>>any fixes for these errors they are only referencing Windows Servers
>>
>>I believe the WLOC does use VSS the problem I had in the past with VSS
>>errors was it was backing up SQL database files and VSS did not work so I
>>excluded in my WLOC backup the folder that SQL databases are in
>>I did check and the settings are still intact.
>>
>>I hope we can figure this one out
>>
>>Should I contact Microsoft on this one?
>>
>>
>>Thanks for your help
>>
>>Tom
>>
>>I hope we can figure something out on this one.
>>"StephenB" <sboots[ at ]mvps.org> wrote in message
>>news:9640l41rcqmj6gtitht3tuib58rtbsjcqo[ at ]4ax.com...
>>> Did backup complete?
>>> These errors are for Windows Volume Shadow Copy Service, which is used
>>> by
>>> Windows to make copies of files for restore if you use Business or
>>> Ultimate
>>> editions of OneCare. VSS is also used if you are connected to and using
>>> Windows
>>> Home Server for full PC backup. I don't think OneCare uses VSS, but I
>>> could b
>>> wrong, based on your experience with this happening during a OneCare
>>> backup.
>>> What it appears is that the drive was literally not available to VSS to
>>> perform
>>> its magic. Perhaps what happened is that OneCare locked the drive or
>>> files
>>> to
>>> perform the backup and VSS was trying to access that same drive.
>>> -steve
>>>
>>> "Thomas R Grassi Jr" <thomasgrassi[ at ]hotmail.com> wrote:
>>>
>>>>Today these errors started popping up while backup was running
>>>>
>>>>Event Type: Error
>>>>Event Source: VSS
>>>>Event Category: None
>>>>Event ID: 12305
>>>>Date: 12/22/2008
>>>>Time: 6:01:25 AM
>>>>User: N/A
>>>>Computer: TGKW001
>>>>Description:
>>>>Volume Shadow Copy Service error: Volume/disk not connected or not
>>>>found.
>>>>Error context:
>>>>CreateFileW(\\?\Volume{d48d3a68-65b1-11dd-b0f2-0013201992d2},0xc0000000,0x00000003,...).
>>>>
>>>>For more information, see Help and Support Center at
>>>>
http://go.microsoft.com/fwlink/events.asp.>>>>Data:
>>>>0000: 49 4e 43 49 43 48 4c 48 INCICHLH
>>>>0008: 32 30 35 00 00 00 00 00 205.....
>>>>0010: 53 50 52 44 49 46 46 43 SPRDIFFC
>>>>0018: 39 36 00 00 00 00 00 00 96......
>>>>
>>>>Event Type: Error
>>>>Event Source: VSS
>>>>Event Category: None
>>>>Event ID: 5013
>>>>Date: 12/22/2008
>>>>Time: 6:01:47 AM
>>>>User: N/A
>>>>Computer: TGKW001
>>>>Description:
>>>>Volume Shadow Copy Service error: Shadow Copy writer
>>>>RemovableStorageManager
>>>>called routine OpenNtmsSessionW which failed with status 0x80070015
>>>>(converted to 0x800423f3).
>>>>
>>>>For more information, see Help and Support Center at
>>>>
http://go.microsoft.com/fwlink/events.asp.>>>>Data:
>>>>0000: 57 53 48 43 4f 4d 4e 43 WSHCOMNC
>>>>0008: 32 32 39 32 00 00 00 00 2292....
>>>>0010: 57 53 48 52 53 4d 43 00 WSHRSMC.
>>>>0018: 35 32 30 00 00 00 00 00 520.....
>>>>
>>>>
>>>>any ideas or thoughts on this
>>>>
>>>>Thanks
>>>>
>>>>Tom
>>>>
>>>
>>> --
>>> Stephen Boots sboots[ at ]mvps.org
>>> Microsoft MVP - Windows Live
>>> Windows Live OneCare Forum Moderator
>>>
http://forums.microsoft.com/windowsonecare/default.aspx?siteid=2>>
>
> --
> Stephen Boots sboots[ at ]mvps.org
> Microsoft MVP - Windows Live
> Windows Live OneCare Forum Moderator
>
http://forums.microsoft.com/windowsonecare/default.aspx?siteid=2