Re: vssadmin list writers

From: Mark Chila (MarkChila_at_discussions.microsoft.com)
Date: 01/15/05


Date: Sat, 15 Jan 2005 14:05:05 -0800

I have resolved the issue. I needed a second hot fix for Shadow Copy which
resolved the issue.

Thanks,
M-

"Marina Roos [SBS-MVP]" wrote:

> Hi Mark,
>
> Are you using the SBS Backup wizard? To what are you backing up? At what
> time?
>
> --
> Regards,
>
> Marina
> Microsoft SBS-MVP
> One of the Magical M&M's
>
> "Mark Chila" <Mark Chila@discussions.microsoft.com> schreef in bericht
> news:F1100C29-FFCF-4854-A9A7-5CD325DB533E@microsoft.com...
> > I am having a problem wiht list writetrs, see below. I've applied Hot Fix
> for
> > Microsoft Knowledge Base article number Q826936 and they are still
> generating
> > errors, see below....
> >
> > Microsoft Windows [Version 5.2.3790]
> >
> > (C) Copyright 1985-2003 Microsoft Corp.
> >
> >
> >
> > C:\Documents and Settings\Administrator>vssadmin list writers
> >
> > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
> >
> > (C) Copyright 2001 Microsoft Corp.
> >
> >
> >
> > Waiting for responses.
> >
> > These may be delayed if a shadow copy is being prepared.
> >
> >
> >
> > Writer name: 'TermServLicensing'
> >
> > Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
> >
> > Writer Instance Id: {ff6f38c7-02ab-4a9c-afdf-e689a5594194}
> >
> > State: [9] Failed
> >
> > Last error: Retryable error
> >
> >
> >
> > Writer name: 'Dhcp Jet Writer'
> >
> > Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
> >
> > Writer Instance Id: {d5bb4410-d22d-4921-a025-12f32f6f7760}
> >
> > State: [9] Failed
> >
> > Last error: Retryable error
> >
> >
> >
> > Writer name: 'WINS Jet Writer'
> >
> > Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
> >
> > Writer Instance Id: {7c25fd1e-c415-40e5-8806-6370612ff0eb}
> >
> > State: [9] Failed
> >
> > Last error: Retryable error
> >
> >
> >
> > Writer name: 'NTDS'
> >
> > Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
> >
> > Writer Instance Id: {c30805e0-1d58-4d50-b92d-13b46429a31e}
> >
> > State: [9] Failed
> >
> > Last error: Retryable error
> >
> >
> >
> > Writer name: 'IIS Metabase Writer'
> >
> > Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
> >
> > Writer Instance Id: {54b241fb-3720-489f-bb73-427c2f831aca}
> >
> > State: [9] Failed
> >
> > Last error: Retryable error
> >
> >
> >
> > Writer name: 'WMI Writer'
> >
> > Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
> >
> > Writer Instance Id: {b8256d4b-31f7-4ad3-8513-892ed28187bf}
> >
> > State: [9] Failed
> >
> > Last error: Retryable error
> >
> >
> >
> > Writer name: 'BITS Writer'
> >
> > Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
> >
> > Writer Instance Id: {eb2d43f1-ee18-449b-9272-4fd654cad9dd}
> >
> > State: [9] Failed
> >
> > Last error: Retryable error
> >
> >
> >
> > Writer name: 'Removable Storage Manager'
> >
> > Writer Id: {5d3c3e01-0297-445b-aa81-a48d7151e235}
> >
> > Writer Instance Id: {9ed6b845-ef4e-445a-841c-794799515a23}
> >
> > State: [9] Failed
> >
> > Last error: Retryable error
> >
> >
> >
> > Writer name: 'System Writer'
> >
> > Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
> >
> > Writer Instance Id: {2ee9fe20-0757-44be-b6af-bfe22c6cf3f0}
> >
> > State: [5] Waiting for completion
> >
> > Last error: No error
> >
> >
> >
> > Writer name: 'MSDEWriter'
> >
> > Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
> >
> > Writer Instance Id: {8d86fca4-089d-47fe-abe1-b107f15b1e8c}
> >
> > State: [1] Stable
> >
> > Last error: No error
> >
> >
> >
> > Writer name: 'FRS Writer'
> >
> > Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
> >
> > Writer Instance Id: {dceecf28-a4f3-4812-8abd-07d9260b0aa1}
> >
> > State: [5] Waiting for completion
> >
> > Last error: No error
> >
> >
> >
> > Writer name: 'Event Log Writer'
> >
> > Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
> >
> > Writer Instance Id: {ec7e1fd9-4981-43aa-88b8-2baf4b73c9f2}
> >
> > State: [1] Stable
> >
> > Last error: No error
> >
> >
> >
> > Writer name: 'Registry Writer'
> >
> > Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
> >
> > Writer Instance Id: {5c786011-88ca-4dc7-bf41-1e8b885db134}
> >
> > State: [1] Stable
> >
> > Last error: No error
> >
> >
> >
> > Writer name: 'COM+ REGDB Writer'
> >
> > Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
> >
> > Writer Instance Id: {f19a93a1-1259-455e-a571-06bb46cc867e}
> >
> > State: [1] Stable
> >
> > Last error: No error
> >
> >
> > Please advise... Thanks!
>
>
>



Relevant Pages

  • Re: Why did my font shadow color change?
    ... This site provides more info on color schemes: ... Geetesh Bajaj, Microsoft PowerPoint MVP ... to a white shadow. ... Can someone tell me why this happened and how to fix it? ...
    (microsoft.public.powerpoint)
  • Re: RGPs most popular pins
    ... John wrote: ... Thanks Rudy, I'll fix that. ... I found the Shadow already, ...
    (rec.games.pinball)
  • Re: pop up
    ... This could be the fix for you. ... "May your shadow be found in happy places." ... (Native American) ... Prev by Date: ...
    (microsoft.public.publisher)
  • Shadow Copy: Initilization Failed
    ... I wanted to share this Shadow Copy failure fix that worked for me. ... Command-line: 'C:\WINDOWS\system32\vssadmin.exe Create Shadow ... regsvr32 /s /i swprv.dll ...
    (microsoft.public.windows.server.general)
  • Re: RGPs most popular pins
    ... Thanks Rudy, I'll fix that. ... I found the Shadow already, ... Let me know if you spot something else. ...
    (rec.games.pinball)