WS ERROR_ACCESS_DENIED

Discussion in 'File Systems' started by joegrab, Mar 19, 2006.

  1. joegrab

    joegrab Guest

    ------------------------------------------------------------
    FRSDiag v1.7 on 3/19/2006 8:34:52 AM
    ..\ADSERVER05 on 2006-03-19 at 8.34.52 AM
    ------------------------------------------------------------

    Checking for errors/warnings in FRS Event Log .... passed
    Checking for errors in Directory Service Event Log .... passed
    Checking for minimum FRS version requirement ... passed
    Checking for errors/warnings in ntfrsutl ds ... passed
    Checking for Replica Set configuration triggers... passed
    Checking for suspicious file Backlog size... passed
    Checking Overall Disk Space and SYSVOL structure (note: integrity is not
    checked)... passed
    Checking for suspicious inlog entries ... passed
    Checking for suspicious outlog entries ... passed
    Checking for appropriate staging area size ... passed
    Checking for errors in debug logs ...
    ERROR on NtFrs_0002.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
    2872: 877: S0: 18:49:48> :SR: Cmd 00c49f48, CxtG ddaa00c5, WS
    ERROR_ACCESS_DENIED, To ADServer04.kemco.local Len: (380) [SndFail - rpc
    call]
    ERROR on NtFrs_0002.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
    2868: 877: S0: 18:50:38> :SR: Cmd 00c72ff0, CxtG ddaa00c5, WS
    ERROR_ACCESS_DENIED, To ADServer04.kemco.local Len: (380) [SndFail - rpc
    call]
    ERROR on NtFrs_0002.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
    2868: 877: S0: 18:51:38> :SR: Cmd 00c93910, CxtG ddaa00c5, WS
    ERROR_ACCESS_DENIED, To ADServer04.kemco.local Len: (380) [SndFail - rpc
    call]

    Found 10 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above

    ......... failed with 10 error entries
    Checking NtFrs Service (and dependent services) state...passed
    Checking NtFrs related Registry Keys for possible problems...passed
    Checking Repadmin Showreps for errors...passed


    Final Result = failed with 10 error(s)
     
    joegrab, Mar 19, 2006
    #1
    1. Advertisements

  2. Hi Joe

    The below errors come from the 02 debug logs - normally there are 5 with the
    latest being 5. So it looks like there was a tempoary problem using RPC
    between this server and ADServer04. To find out the date check the last
    change timestamp on the 02 debug log file in c:\windows\debug.
    Monitor this behaviour and the event log messages (I suspect that there may
    also be 13508 messages). Check for patterns - e.g. is the server restarted
    during the times this error is logged (or was the WAN/ router down etc.)

    Hope this helps
    Roland
     
    rnitsch [msft], Mar 21, 2006
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.