Troubleshooting Cmdlet Issues

Occasionally you might have a problem when you run a cmdlet. The following are some common issues and solutions for them.
  • The Group Management IP is not set.

    Solution: Execute the Set-Configuration cmdlet to set the IP and credentials for the Windows user who runs the cmdlet.

  • The cmdlet is run as a Local Administrator account in a Windows cluster.

    Solution: Always run the cmdlet using a DOMAIN\Administrator level account.

  • In a cluster, the cmdlet needs to communicate Windows Management Instrumentation (WMI) to other nodes, but is blocked by a firewall..

    Solution: Make sure that the firewall allows inbound and outbound TCP ports. Use port 135 for RPC and port 445 for WMI.

  • Slow operations have been observed after multiple cycles of Invoke, Remove, and Disconnect cmdlets have been run.

    Solution: Windows keeps track of disconnected disk devices as phantom devices. Download and run the Microsoft DevNodeClean utility from the Microsoft web site.