Announcement

Collapse
No announcement yet.

DCOM Error when I run Get-OabVirtualDirectory

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

  • DCOM Error when I run Get-OabVirtualDirectory

    Hi

    I have noticed if I run

    Get-OabVirtualDirectory (or get-owavirtualdirectory etc..) from an exchange powershell on the mailbox server it returns the correct data but 2 events are logged in the mailbox servers Event Viewer -> Custom Views -> Server roles -> Administrative Events

    The 2 events are

    DCOM was unable to communicate with the computer CAS02.xxxx.com using any of the configured protocols.

    DCOM was unable to communicate with the computer CAS01.xxxx.com using any of the configured protocols.

    We have 2 cas servers, cas01 and cas02 - no events are logged on them when I run the command

    I have checked connectivity from mailbox server to cas01 and cas02, I can ping, resolve DNS etc.., I have stopped the firewall temporarily on both CAS servers but whenever I run the command I get the 2 errors logged.

    I tried to use DTCping to trouble shoot but when I start it on the mailbox server I get this in the log file

    Cluster Environment detected
    12-06, 13:54:38.218-->DTC resource not found

    the mailbox server is part of a DAG setup.

    All operating systems are exchange 2008 r2 and exchange is 2010 sp2 update 4 v2

    Anyone have any suggestions on where to look next?

    Kind Regards

    Paul


  • #2
    Re: DCOM Error when I run Get-OabVirtualDirectory

    Apologies for replying to my own post, just wanted to add somethings ive tried in the last few days - none have worked.

    I can duplicate the DCOM error at will from pretty much any machine talking to the CAS servers.

    E.g. If I open an Exchange Managment shell on a hub transport server and type Get-OAB-VirtualDirectory I get the following event logged

    Event ID: 10009 - DCOM was unable to communicate with the computer CAS02.xxxxxxxxx.com using any of the configured protocols.

    However I do get the correct response and no error in the exchange shell.

    cas02 is resolvable to the correct IP.

    I have tried disabling the firewall on both cas02 and hub02

    I managed to get dtcping.exe to run on on both servers, they were able to communicate fine and no errors (output below)

    RPC server is ready
    12-12, 14:54:13.735-->RPC server:CAS02 received following information:
    Network Name: CAS02
    Source Port: 59600
    Partner LOG: HUB24660.log
    Partner CID: 80110545-624D-46B1-B8D7-DD03C2EE3C4E
    ++++++++++++Validating Remote Computer Name++++++++++++
    12-12, 14:54:18.137-->Start DTC connection test
    Name Resolution:
    hub2-->192.168.1.232-->hub2.xxxxxxxxx.com
    12-12, 14:54:18.137-->Start RPC test (CAS02-->hub2)
    RPC test is successful
    Partner's CID:80110545-624D-46B1-B8D7-DD03C2EE3C4E
    ++++++++++++RPC test completed+++++++++++++++
    ++++++++++++Start DTC Binding Test +++++++++++++
    Trying Bind to hub2
    12-12, 14:54:18.168-->CAS02 Initiating DTC Binding Test....
    Test Guid:AA28D761-86DB-4DFB-A9F1-0BB18A6AD5FB
    Received reverse bind call from hub2
    Network Name: CAS02
    Source Port: 59600
    Hosting Machine:CAS02
    Binding success: CAS02-->hub2
    ++++++++++++DTC Binding Test END+++++++++++++
    ++++++++++++Start Reverse Bind Test+++++++++++++
    Received Bind call from hub2
    Network Name: CAS02
    Source Port: 59600
    Hosting Machine:CAS02
    12-12, 14:54:18.215-->Trying to Reverse Bind to hub2...
    Test Guid:80110545-624D-46B1-B8D7-DD03C2EE3C4E
    Name Resolution:
    hub2-->192.168.1.232-->hub2.xxxxxxx.com
    Reverse Binding success: CAS02-->hub2
    ++++++++++++Reverse Bind Test ENDED++++++++++
    Session idle timeout over, tearing down session
    Session is shuting down

    I also tried adding a dword value "IgnoreDelegationFailure" to HKLM\Software\Policies\Microsoft\Windows NT\Rpc - I only did this on the CAS server as the hub transport did not have HKLM\Software\Policies\Microsoft\Windows NT\Rpc

    Does anyone else have any more suggestions? things seem to be working ok but I dont like leaving problems that might bite me in the future.

    Thanks

    Paul

    Comment

    Working...
    X