Some Resource Groups (Azure) are not visible inside MCS wizard while catalog creation

When creating MCS catalog for Azure, master image need to be selected from its Resource Group.

While doing this, some Resource Groups are visible, and some others are not. All visible and non-visible Resource Groups were created manually and they all were working fine during initial deployment. But some of them are not visible on Studio anymore after some days.

The affected Resource Groups are neither visible in Studio nor in PoSh SDK (image.folder location in XDHyp: Posh drive). However, if we know the Resource Group name, can browse to them by typing the name manually in PoSh SDK. Subscription scope service principal is used for all Resource Groups, and we are also able to browse to them in PoSh SDK. So it is not an access related issue.

If we create new Resource Groups, they are all visible on Studio for master image selection.


  • No Related Posts

Cluster resource ‘%1’ in Resource Group ‘%2’ failed.

Product: Windows Operating System
Event ID: 1069
Source: ClusSvc
Version: 5.2
Message: Cluster resource ‘%1’ in Resource Group ‘%2’ failed.

The Cluster service reported that the indicated resource failed. The Cluster service will attempt to restart the resource or fail it over, but the causes of this message should be investigated.

Possible causes include:

  • The dependencies or other properties for the resource are not configured correctly in the cluster.
  • There is a hardware problem, such as a disconnected cable, incorrect termination of a SCSI bus, or failure of a device.
  • The application associated with the resource failed or became unavailable.
User Action

If the Cluster service continues to log this error, do the following:

If the resource is a disk:

  • Verify that the cables are connected correctly.
  • Check the termination of the SCSI bus.
  • Review the log files for all cluster nodes to determine whether other problems are indicated.

For other resources:

  • Check and correct problems with the application or service associated with the resource. If the application or service cannot start within reasonable time limits, diagnose and resolve the issues that might be causing the slow start.
  • Verify that the resource is configured correctly.
  • Verify that all dependent resources are configured correctly.
  • If the diagnostic log is enabled, check it for corresponding status codes.

For more information about the ClusSvc 1069 event, see related KB articles by searching the Microsoft Knowledge Base for Cluster and 1069 in the Search for box.