Announcement

Collapse
No announcement yet.

NTDS Writer is missing HELP !!!

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • NTDS Writer is missing HELP !!!

    Hi
    I am having trouble Backup the system state on my 2003 STD DC.

    after doing some checking i notice that the NTDS writer is missing when i enter the command VSSADMIN LIST WRITERS .

    after restart everything is OK for a week or two and then its start all again.

    i installed a patch from microsoft that should fix this problem but it didn't.

  • #2
    Re: NTDS Writer is missing HELP !!!

    is this not a service that can be restart manually or by the options under services on error to restart?

    if the above is not the case i am lost and by wat you say u seem to be taking the right approach

    Comment


    • #3
      Re: NTDS Writer is missing HELP !!!

      No, this is not a service (other than the volume shadow copy service). there will be several writers on the server based on what roles the server performs and what components are installed. You can run vssadmin list writers from a command prompt to see a list of writers on the server and there status. Have you googled the problem?

      Comment


      • #4
        Re: NTDS Writer is missing HELP !!!

        i googled there is noting there

        here is my "vssadmin list writers " output from my DC server
        notice that the NTDS Writer is missing

        Need Help !




        vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
        (C) Copyright 2001 Microsoft Corp.

        Writer name: 'FRS Writer'
        Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
        Writer Instance Id: {915123d3-1a29-49a7-9ff2-894f8ca002ca}
        State: [1] Stable
        Last error: No error

        Writer name: 'System Writer'
        Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
        Writer Instance Id: {ff849de7-1ff6-4bd7-a431-010e03545593}
        State: [1] Stable
        Last error: No error

        Writer name: 'MSDEWriter'
        Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
        Writer Instance Id: {959f4c8b-39c4-49b4-a913-6d56b5cf6769}
        State: [1] Stable
        Last error: No error

        Writer name: 'IIS Metabase Writer'
        Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
        Writer Instance Id: {c8e69c4d-9614-4859-8650-c96975ff53d5}
        State: [1] Stable
        Last error: No error

        Writer name: 'Registry Writer'
        Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
        Writer Instance Id: {bbc5b9dd-6f6f-4910-be9c-ff98577af38b}
        State: [1] Stable
        Last error: No error

        Writer name: 'COM+ REGDB Writer'
        Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
        Writer Instance Id: {cf845cb0-983e-4ddf-ade2-b43c1900a261}
        State: [1] Stable
        Last error: No error

        Writer name: 'WMI Writer'
        Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
        Writer Instance Id: {3d55d702-0b5e-4771-8852-bd7f8f8810d3}
        State: [1] Stable
        Last error: No error

        Writer name: 'Event Log Writer'
        Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
        Writer Instance Id: {c674e693-bbf0-44b7-a22f-0d4ef87a1d52}
        State: [1] Stable
        Last error: No error

        Writer name: 'BITS Writer'
        Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
        Writer Instance Id: {14fa77e8-eba5-44b0-bbea-0fd32f80efa7}
        State: [1] Stable
        Last error: No error

        Comment

        Working...
        X