Posted on December 13th, 2007 by thehabgroup
Cluster File Share ‘%1′ could not be found.
Description: The Event ID 1054 description does not normally have an error code associated. This error can happen if no dependency on the physical disk resource so the cluster service attempts to enumerate a share prior to the disk coming online, or, the physical disk has failed.
To Resolve:
- Ensure you add the physical disk to the dependency list of the file share resource.
- Verify the physical disk where the file share directory is located is ONLINE.
- Verify the file share resource and the physical disk where the file share directory is located is in the same resource group.
- Verify the directory has not been deleted.
Cluster Cluster File Share event id: 1054Cluster Cluster File Share event id: 1054
No Comments »
Filed under: Cluster
Posted on September 26th, 2007 by thehabgroup
Here is an example Cluster Log entry:
ERR Volume Manager Disk Group <Shadow Copy Disk Group>: LDM_RESLooksAlive: *** FAILED for Shadow Copy Disk Group, status = 0, res = 0, dg_state = 22
To get the proper error below, take the code in the log (decimal value) and convert it to text and then refer to below:
#define DG_SUCCESS 0×0000
#define DG_FAIL_NO_DG 0×0001
#define DG_FAIL_NO_DISK 0×0002
#define DG_FAIL_NO_MAJORITY 0×0003
#define DG_FAIL_START_RES 0×0004
#define DG_FAIL_STOP_RES 0×0005
#define DG_FAIL_STOP_THREAD 0×0006
#define DG_FAIL_IMPORT 0×0007
#define DG_FAIL_DEPORT 0×0008
#define DG_FAIL_DGNAME_EXISTED 0×0009
#define DG_FAIL_INVALID_DRIVE_LETTER 0×0010
#define DG_FAIL_NO_MEM 0×0011
#define DG_FAIL_UNEXPECTED 0×0012
#define DG_FAIL_INVALID_ARG 0×0013
#define DG_FAIL_INITIALIZE 0×0014
#define DG_FAIL_UNINITIALIZE 0×0015
#define DG_FAIL_VOL_LOCKED 0×0016
#define DG_FAIL_SHARING_VIOLATION 0×0017
#define DG_FAIL_VXIO_FAILURE 0×0018
#define DG_DEPORT_WITH_ACTIVE_IO 0×0019
#define DG_FAIL_REQ_RECOVERY 0×0020
#define DG_FAIL_NOT_CLUSTER_DG 0×0021
#define DG_RES_OK 0×0021
#define DG_RES_MAJORITY_LOST 0×0022
#define DG_RES_NONE 0×0023
#define DG_VOL_OK 0×0024
#define DG_VOL_FAIL_REDUNDENCY 0×0025
#define DG_VOL_FAILED 0×0026
#define DG_NO_CLUS_SUPPORT 0×0027
#define DG_FAIL_MORE_DATA 0×0061
#define DG_FAIL_NO_GUID 0×0062
#define DG_FAIL_NO_VOL 0×0063
#define DG_FAIL_INVALID_HANDLE 0×0064
The State is 22, which translates to DG_RES_MAJORITY_LOST means the Dynamic Disk group does not contain a majority of the disks, so it fails.
ClusterCluster
No Comments »
Filed under: Cluster
Posted on August 31st, 2007 by thehabgroup
All printer information is stored under the following registry key:
HKLM\Cluster\Resources\ResourceGUID\
All printer, driver, port information, spool directory, job completion tiemout is stored in separate keys under the following parameters key:
HKLM\Cluster\Resources\ResourceGUID\Parameters
Structure necessary for other Windows based print clients under the following key:
HKLM\Cluster\Resources\ResourceGUID\Parameters\Environments
Monitor information, TCP/IP ports, port address, name and SNMP information under the following key:
HKLM\Cluster\Resources\ResourceGUID\Parameters\Monitors
The same printer information as stored in a non clustered HKLM\System\CCS\Control\Print key is stored under the following key:
HKLM\Cluster\Resources\ResourceGUID\Parameters\Printers
The printer share is still populated under
HKLM\System\CurrentControlSet\services\LanmanServer\Shares
Cluster PrintingCluster Printing
No Comments »
Filed under: Printing, Cluster
