Storage Foundation and High Availability Solutions 7.4 HA and DR Solutions Guide for Microsoft Exchange 2010 - Windows
- Section I. Introduction and Concepts
- Introducing Storage Foundation and High Availability Solutions for Microsoft Exchange Server
- How VCS monitors storage components
- Introducing the VCS agent for Exchange 2010
- Introducing Storage Foundation and High Availability Solutions for Microsoft Exchange Server
- Section II. Configuration Workflows
- Configuring high availability for Exchange Server with InfoScale Enterprise
- Reviewing the HA configuration
- Reviewing a standalone Exchange Server configuration
- Reviewing the Replicated Data Cluster configuration
- Reviewing the disaster recovery configuration
- Disaster recovery configuration
- Notes and recommendations for cluster and application configuration
- Configuring disk groups and volumes for Exchange Server
- About managing disk groups and volumes
- Configuring the cluster using the Cluster Configuration Wizard
- Using the Solutions Configuration Center
- Configuring high availability for Exchange Server with InfoScale Enterprise
- Section III. Deployment
- Installing Exchange Server 2010
- Configuring Exchange Server for failover
- Configuring the service group in a non-shared storage environment
- Configuring campus clusters for Exchange Server
- Configuring Replicated Data Clusters for Exchange Server
- Setting up the Replicated Data Sets (RDS)
- Configuring a RVG service group for replication
- Configuring the resources in the RVG service group for RDC replication
- Configuring the RVG Primary resources
- Adding the nodes from the secondary zone to the RDC
- Verifying the RDC configuration
- Deploying disaster recovery for Exchange Server
- Reviewing the disaster recovery configuration
- Setting up your replication environment
- Configuring replication and global clustering
- Configuring the global cluster option for wide-area failover
- Possible task after creating the DR environment: Adding a new failover node to a Volume Replicator environment
- Testing fault readiness by running a fire drill
- About the Fire Drill Wizard
- About post-fire drill scripts
- Prerequisites for a fire drill
- Preparing the fire drill configuration
- Running a fire drill
- Deleting the fire drill configuration
- Section IV. Reference
- Appendix A. Using Veritas AppProtect for vSphere
- Appendix B. Troubleshooting
- Appendix A. Using Veritas AppProtect for vSphere
Exchange Service agent error messages
The following table lists the Exchange Service agent error messages and their descriptions.
Table: Exchange Service agent error messages
Message | Description |
---|---|
Failed to find the service object. Please check the 'Service' attribute. | The value specified for the "Service" attribute is incorrect. Solution: Provide a valid value for the Lanman resource. If the value is correct, see error type and error code for further information. |
Failed to open the service object.(Service = service name). Error Type, Error Code. | The agent failed to open the service object. Solution: See the associated Windows error type and error code for more information. |
Failed to get the state of the service (service name). Error Type, Error Code. | The agent failed to retrieve the state of the service. Solution: See the associated Windows error type and error code for more information. |
Failed to start the service (service name) Error Type, Error Code. | The agent failed to start the specified service. Solution: See the associated Windows error type and error code for more information. |
Failed to stop the service (service name). Error Type, Error Code. | The agent failed to stop the service. Solution: See the associated Windows error type and error code for more information. |
Failed to kill the service (service name) Error Type, Error Code. | The agent failed to terminate the service. Solution: See the associated Windows error type and error code for more information. |
Configuration error. 'Service' attribute is not configured. | No value specified for the "Service" attribute. Solution: Specify a valid value for the attribute. |
Configuration error. 'LanmanResName' attribute is not configured. | No value specified for the "LanManResName" attribute. Solution: Specify a valid value for the attribute. |
Failed to set the virtual environment for service: (service name). Error Type, Error Code. | The agent failed to set the environment block for the service. The agent needs to set the environment block for starting the service in the context of the virtual server name. Solution: See the associated Windows error type and error code for more information. |
Failed to remove virtual environment for Service = (service name). Error Type, Error Code. | The agent failed to remove the environment block for the service. While taking the resource offline, the agent stops the service and removes the environment block. Solution: See the associated Windows error type and error code for more information. |
Configuration error. \"LanmanResName\" attribute is not configured. | No value specified for the "LanmanResName" attribute. Solution: Specify a valid value for the attribute. |
Configuration error. DetailMonitoringInterval attribute is greater than zero but DBList is empty. No database is specified for detail monitoring. | Detail monitoring for databases is enabled and the monitoring interval (DetailMonitor attribute) is also specified. But there are no databases selected. The DBList attribute is empty. Solution: Select the databases for the detail monitoring. |
FaultOnMountFailure flag is true.\"Auto Mount\" on database: (database names) is enabled but database is dismounted. Agent will return status as offline." | The attribute FaultOnMountFailure is set to True for databases that are set to mount automatically on startup. But these databases are dismounted. So the agent will fault the service group. |
\"Auto Mount\" on database: (database names) is enabled but database is dismounted. Agent will return status as Unknown. | Databases that are set to mount automatically on startup are dismounted. If these databases are selected for detail monitoring, the agent will return an Unknown status and appropriate administrative action is required. |
Failed to add computer account to 'Exchange Servers' group Error Type, Error Code. | Unable to add the computer account to the Exchange Servers group. Solution: Make sure that the user has permissions to add computer accounts to the Exchange Servers group. If the user has those permissions, see the error type and error code for further information. |