Administrator Guide
Figure 37. Data Consistency Master Report
The report indicates a status of either "Succeeded" or "Inconsistencies Detected."
d If there are inconsistencies that were detected, expand the category for more details. To repair inconsistencies, do the following:
NOTE: You can run repair operations when there is live trac on the system. However, with live trac,
repair may take longer.
• To perform automatic recovery of as many issues as possible, run the Invoke-DataConsistency runbook with AllowRepair
set to Yes, and Subsystem set to VMProvider.
• For issues that cannot be automatically recovered, see the following section of this guide, Troubleshooting data consistency
issues.
Troubleshooting data consistency issues
There are some issues that the data consistency runbooks cannot automatically repair.
This section provides troubleshooting steps that you can follow to try to resolve these issues. If troubleshooting steps are not listed or do
not resolve the issue, contact support.
Troubleshooting steps are organized by report categories. In addition, there is information about how to manually recover access to tenant-
created objects.
Table 30. Virtual Machine Provider
Error Cause/Resolution
Cloud not found in VMM
Cause:
This issue occurs if a Windows Azure Pack plan is congured with a
cloud, but the cloud does not exist in VMM.
Resolution:
Follow these steps as a VMM administrator:
1 In the VMM console, verify that a valid cloud exists, or create a cloud if
applicable.
2 In the Windows Azure Pack management portal for administrators, open
the plan properties.
3 Select a valid cloud.
4 Save the plan settings.
StampCannotBeFound = The SPF stamp {0} cannot
be found. This issue is not automatically recoverable.
Cause:
This issue occurs if the stamp that is referenced by a Windows Azure
Pack plan no longer exists in the SPF database. This would only occur if the
stamp ID was manually deleted in the SPF database.
94 Operations