FRSdiag error explanation

Discussion in 'File Systems' started by Antknee, Dec 14, 2004.

  1. Antknee

    Antknee Guest

    Hi. I would to know if there is an advanced resource that will tell the
    explanation and causes of FRS errors.
    For instance, I ran frsdiag and received this error: WS
    RPC_S_SERVER_TOO_BUSY. Well, googling it didn't help much as the links didn't
    pertain to FRS.
    This has been the case with many errors or warnings I have seen from frsdiag
    or related tools.
    It's great it tells me there is a problem, but what the heck does it mean?
    Antknee, Dec 14, 2004
    1. Advertisements

  2. Antknee

    Glenn L Guest

    Unfortunately there is not a published resource (that I know of) that
    explains the internal error codes FRS generates.
    However, this one at least can get you started in the right direction.
    This is a problem either establishing or maintaining an RPC session with a
    replication partner. The error should have the partners server name around
    it somewhere,
    You should have a FRS 13508 related to this which tells the replication
    partners name. Do you get a corresponding 13509 at some point indicating
    replication is working again?

    Simultaneous network tracing (at each replica member involved in the event)
    when reproducing this error is typically necessary to get to the bottom of
    what is going on.
    RPC errors are all too often network related.
    Glenn L, Dec 15, 2004
    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.