Build Revoked best practices report from SPDocKit determines whether one or more servers in the environment is running the SharePoint binaries that are revoked due to a critical issue.
This check determines whether one or more servers in the environment is running the SharePoint binaries that are revoked due to a critical issue.
A SharePoint farm can be scaled to contain one or more SharePoint servers, hosting one or more SharePoint components per server. This model provides scalability and it can also provide high availability. Environments supporting a high number of users and hosting large amounts of content are usually scaled in such a way that various SharePoint components have dedicated hardware or a set of resources allocated to them.
All components in a SharePoint environment should be on the same patch level in order to provide maximum compatibility, stability, and supportability. Also, SharePoint should run on the latest Service Pack level in order to get the latest stable bug fixes and new features.
There are numerous examples, however, where Microsoft has issued a faulty service pack containing a critical issue. Such packages and builds are then revoked and new packages are reissued shortly after the bug gets fixed.
Check all SharePoint servers in the environment. Make sure that SharePoint servers are not running the revoked build. If so, please consult the SharePoint Updates page (listed under Additional information section) to get the information about particular build and how to solve the issue. In some cases, you may need to consult Microsoft Support to resolve the issue.
To verify installed SharePoint Server updates, start Control Panel, go to Programs > Programs and Features and click View installed updates. Control Panel, however, will only show installed binaries. Installing SharePoint binaries is only a part of the patching process. To verify the upgrade status of the SharePoint Farm and servers in the farm, open the Central Administration, and in the Upgrade and Migration section, click Check upgrade status.
Additional information can be found in the following TechNet articles: