DFS Reporting: Cannot connect to reporting DCOM server.

Discussion in 'File Systems' started by Thomas Kofler, Dec 25, 2006.

  1. Hi,

    we have a domain-based DFS (2 x Windows 2003 R2 servers).

    Replication and the namespace works fine.

    Reporting from Server1 also works fine (no errors, all reports green)
    But when we start the report from Server2 we get:

    Cannot connect to reporting DCOM server.
    Description: Access is denied.
    Last occurred: Monday, December 25, 2006 at 10:46:42 PM (GMT1:00)
    Suggested action: Verify that Windows Server 2003 R2 is installed on the
    server and that RPC traffic is not blocked by firewalls or port filtering.
    For information about troubleshooting RPC issues see RPC KB 839880.

    and (as a result)

    Cannot retrieve version vectors from this member.
    Description: Backlog calculations cannot be performed because an error
    occurred while the reporting mechanism attempted to retrieve version vectors
    from this member: Access is denied. . Version vectors are used to compare how
    up-to-date this server is compared to the reference server. If version
    vectors cannot be processed, then the backlog, if any, cannot be determined.
    Last occurred: Monday, December 25, 2006 at 10:46:43 PM (GMT1:00)
    Suggested action: For information about troubleshooting backlog problems,
    see The Microsoft Web Site.

    and under the topic "Servers unavailable for reporting"

    Cannot connect to reporting DCOM server.

    Both server are in the same domain and no firewall is between the two
    servers or activated on the server.
    The RPC bugfix and the fix for the December reporting bug are already
    installed on both servers.

    Any advice?,
    Thanks,
    Thomas
     
    Thomas Kofler, Dec 25, 2006
    #1
    1. Advertisements

  2. I had the same thing happen (See dcom error post from 12/06/2006). It ended
    up "fixing" itself. I attributed this "fix" to waiting 7 days, as Jill
    Zoeller explains in reply to my post on "sharing Violation" dated
    12/13/2006.

    If I had to guess this "version vector" also has no "anti event" fired and
    resolves itself after 7 days.

    Has it been 7 days since the event occurred?

    hth
    DDS
     
    Danny Sanders, Dec 26, 2006
    #2
    1. Advertisements

  3. Hi,

    thanks for your reply. Your posts regarding the same error were very
    interesting.
    The second server was installed at the 22nd of December.

    I will wait until the 2 of January and report back if the error disappeared.

    Thanks,
    Thomas
     
    Thomas Kofler, Dec 26, 2006
    #3
    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.