Event 1055 - Cluster File Share resource <> has failed a status ch

Discussion in 'Clustering' started by Mike Fife, Apr 19, 2006.

  1. Mike Fife

    Mike Fife Guest


    I am having this error occurring occasionally on either of the two nodes of
    an active/passive cluster using Windows 2003 server Enterprise edition.

    Source ClusSvc, Category Fil Share Resource, Type Error, Event ID 1055.

    Description: Cluster File Share resource <share name> has failed a status
    check. The error code is 64.

    The shares are published as normal shares but are part of a DFS the root of
    which is on and NT4 server.

    When this happens the groups belonging to the affected node appear to go off
    line and the cluster administration tool stops responding. The other node
    continues unaffected. The only way out of this situation so far is to reboot
    the affected node.
    the 'stalled' groups do not fail over.

    I have seen some articles which relate to DFS roots and clusters on 2003,
    but not to this configuration specifically.

    Has anyone experienced a similar error and is there a fix?

    Thanks in advance

    Mike Fife.
    Mike Fife, Apr 19, 2006
    1. Advertisements

  2. Error code 64 translates to: The specified network name is no longer

    Sounds like you might be having network issues on this node.

    John Toner [MVP], Apr 19, 2006
    1. Advertisements

  3. Mike Fife

    Mike Fife Guest


    this happens on either node, the network is fine and the nodes are pingable
    on all IP addresses that are supported by the owned group.

    The error is generated by the node into the system log on that node. The
    disks are attached via multipath SCSI and there are no errors indicating
    communications failures between the nodes and the disk resources.

    The console of the node is affected, it appears to freeze and becomes
    unresponsive. I don't think that this is a network issue.

    I think it is more akin to the issues that I have read about regarding the
    DFS root wizard in 2003 server.


    Mike Fife, Apr 20, 2006
  4. You can try increasing the Pending Timeout value for the fileshare from 180
    seconds to 360 seconds. To do this, start Cluster Administrator, right-click
    the resource that you want to change, click Properties, and then click the
    Advanced tab. Increase the Pending Timeout value to 360.

    John Toner [MVP], Apr 20, 2006
  5. Mike Fife

    Mike Fife Guest


    how will this affect the shared directory? I read this as an error internal
    to the node and not a failure to fail over.


    Mike Fife, Apr 21, 2006
    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.