Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
CSV no longer available - STATUS_CONNECTION_DISCONNECTED(c000020c)

Answered CSV no longer available - STATUS_CONNECTION_DISCONNECTED(c000020c)

  • Saturday, December 08, 2012 3:12 PM
     
     
    Sign In to Vote
    0

    Hi,

    we have a 4 node Hyper-V Server 2008 R2 SP1 Cluster with a few VMs. Since this week on monday we have problems while accessing CSVs from some nodes.

    NodeNames:

    130
    131
    132
    133

    For example: If Node 133 owns all three CSVs everything is working fine.

    If I transfer the ownership to Node 130 the following ocourrs:
    Node 130 (the owner itself), 131 and 133 can access the volume. 132 cannot.

    If I transfer the ownership to Node 132 the following ocourrs:
    Node 132(the owner itself), 131 and 133 can access the volume. 130 cannot.

    Also what we see:

    If I open on Node 130 Hyper-V Manager I can connect to 131 and 133 but not to 132. I will get an RPC error

    If I open on Node 132 Hyper-V Manager I can connect to 131 and 133 but not to 130. I will get an RPC error

    We already have checked/done the following:

    Disabled TCP Chimney

    Hotfixes installed:
    Windows6.1-KB2494016-x64
    Windows6.1-KB2639032-x64
    Windows6.1-KB2674551-x64
    Windows6.1-KB2685891-x64

    KB-Article checked:
    Unable to access ClusterStorage folder on a passive node in a server 2008 R2 cluster
    http://support.microsoft.com/kb/2008795/en-us

    The above KB article is exactly what we are seeing but the recommended actions are already in place.

    Do you have any further Idea what we can try to get the problem solved?

    Peter Forster | MVP Virtual Machine 2002-2011 | Austria |



    • Edited by Peter Forster Saturday, December 08, 2012 3:16 PM wording
    •  
     

All Replies

  • Monday, December 10, 2012 6:12 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,

    > If I open on Node 130 Hyper-V Manager I can connect to 131 and 133 but not to 132. I will get an RPC error
    >     If I open on Node 132 Hyper-V Manager I can connect to 131 and 133 but not to 130. I will get an RPC error

    That’s the reason why you encounter such issue. When accessing a CSV volume from a passive (non-coordinator) node, the disk I/O to the owning (coordinator) node is routed through a 'preferred' network adapter and requires SMB be enabled on that network adapter.

    This issue is caused by network problem, which kind of anti-virus software are you using. If possible, temporary disable it and check the result.

    Also you may refer to following article to troubleshoot RPC unavailable issues:

    Troubleshooting "The RPC server is unavailable"
    http://social.technet.microsoft.com/wiki/contents/articles/4494.troubleshooting-the-rpc-server-is-unavailable-en-us.aspx

    For more information please refer to following MS articles:

    Requirements for Using Cluster Shared Volumes in a Failover Cluster in Windows Server 2008 R2
    http://technet.microsoft.com/en-us/library/ff182358(v=WS.10).aspx
    Hyper-V: Why does Hyper-V Manager not always work over VPN connection? Access Denied or RPC server unavailable errors.
    http://blogs.technet.com/b/jhoward/archive/2008/08/07/hyper-v-why-does-hyper-v-manager-not-always-work-over-vpn-connection-access-denied-or-rpc-server-unavailable-errors.aspx

    Hope this helps!

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Lawrence

    TechNet Community Support

     
  • Tuesday, December 11, 2012 8:13 PM
     
     Answered
    Sign In to Vote
    0

    Hi,

    I've run those disable tasks:

    Netsh int tcp set global RSS=Disabled
    Netsh int tcp set global chimney=Disabled
    Netsh int tcp set global autotuninglevel=Disabled
    Netsh int tcp set global congestionprovider=None
    Netsh int tcp set global ecncapability=Disabled
    netsh int ip set global taskoffload=disabled
    Netsh int tcp set global timestamps=Disabled
    netsh int tcp set global autotuning=disabled

    And currently it looks like that the error is gone. I will check the system the next days if the error happens again.

    Thanks!

    Peter Forster | MVP Virtual Machine 2002-2011 | Austria |

     
  • Thursday, December 13, 2012 9:08 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    I would like to confirm what is the current situation? Have you resolved the problem or do you have any further progress?

    If there is anything that we can do for you, please do not hesitate to let us know, and we will be happy to help.

    Lawrence

    TechNet Community Support

     
  • Thursday, December 13, 2012 8:40 PM
     
     
    Sign In to Vote
    0

    Hi,

    currently we do not see any issue. If an error will pop up again I will create a new thread for that.

    Thanks!

    Peter Forster | MVP Virtual Machine 2002-2011 | Austria |