Unable to Read Existing Resultant Wua Policy. Error = 0x80070002.
Consulting Services
Need help with your SCCM infrastructure ? Consult our fixed cost consulting plans to come across our rates or contact us for a custom quote.
As an SCCM ambassador, it's important to acquire the concept of troubleshooting a Configuration Manager client installation. By targeting the SCCM customer installation error codes, you will have a better idea of what is happening during client installation. The mistake codes is not an exact science, they can defer depending on the state of affairs. For a ameliorate understanding about error codes, read this great post from Jason Sandys.
These codes appear in ccmsetup logs, located on in C:\windows\ccmsetup\logs. During the installation procedure, monitor theccmsetup.log using cmtrace.exe and locate each mistake codes.
In that location are other logs, on which the SCCM customer installation relates. If you don't observe plenty information in the ccmsetup.log, scan all related log files in c:\windows\ccm\logs .Utilize the control line net helpmsg,for more than data about your return fault code.
SCCM Console
You tin can besides add theLast Installation Errorin the SCCM console:
- Open the SCCM panel and navigate toAssets and Compliance /Devices
- In the devices view, correct-click on the header and selectLast Installation Error
At that place are chances that the last mistake code returns an empty value for a device.
SCCM Client Installation Error Codes
This mail from Technet Forums(Thanks to Charlie Hawkins),has inspired united states of america to set a listing of all fault codes, that can happen during the SCCM client installation. Some errors have been added based on our personal experiences.
Experience free to send usa any new error codes, this listing will be updated based on your comments.
| ID | Source | Description | Solution |
|---|---|---|---|
| 2 | The system cannot find the file specified This error occur when the WMI service is corrupt | Technet Resolution WMI Repair | |
| v | Access denied | Make sure that the installation account is fellow member of the Ambassador Grouping | |
| 7 | Reboot Required | ||
| 8 | Setup Already Running | ||
| 9 | Prerequisite evaluation failure | ||
| 10 | Setup manifest hash validation failure | ||
| 52 | Yous were not connected considering a duplicate proper name exists on the network | Cheque for indistinguishable proper noun in DNS (IP) | |
| 52 | You were not connected because a duplicate name exists on the network | Check for duplicate proper noun in DNS (IP) | |
| 53 | Unable to locate Cannot connect to admin$ Computer Browser not started | Add File & Print sharing to Exceptions in Firewall Turn file and print on KB920852 | |
| 58 | The specified server cannot perform the requested operation | ||
| 64 | Windows | The specified network name is no longer bachelor | |
| 67 | Network proper name cannot exist establish | Check if client has a DNS entry or invalid DNS | |
| 86 | Incorrect network configuration | ||
| 112 | Not enough disk space | Complimentary some space on the computer | |
| 1003 | Cannot complete this office | ||
| 1053 | The service did not respond to the start or command asking in a timely fashion | ||
| 1068 | The dependency service or group failed to start | ||
| 1130 | Windows | Not enough server storage is available to procedure this command | |
| 1203 | The network path was either typed incorrectly, does not exist, or the network provider is not currently available Please endeavor retyping the path or contact your network administrator | ||
| 1208 | Windows | An extended error has occurred | |
| 1305 | The revision level is unknown | ||
| 1396 | Login Failure | The target account name is wrong | Check for indistinguishable proper noun in DNS (IP) NBTSTAT -a reverse lookup |
| 1450 | Windows | Insufficient system resources exist to complete the requested service | |
| 1603 | CCMExec could not be stopped | Reboot and install the client as ambassador | |
| 1618 | MSI | This error is cause by a multiple client.msi installation at the same fourth dimension | Cease all related MSI install procedure |
| 1789 | The trust relationship between this workstation and the primary domain failed | KB2771040 | |
| 12002 | Failed to transport HTTP Request | Check firewall ports | |
| 8007045D | MSI | Setup was unable to create the WMI namespace CCM | Delete all SCCM folders and rebuilt wmi Repository |
| 800706BA | WMI | Unable to connect to WMI on remote machine | Prajwal Desai post |
| 80041001 | MSI | Setup was unable to create the WMI namespace CCM Warning 25101. Setup was unable to delete WMI namespace CIMV2\SMS | WMI Repair |
| 8004103B | WMI | Unable to create the WMI Namespace | Rebuild WMI Repository |
| 80070070 | Setup failed due to unexpected circumstances | Rebuild WMI Repository | |
| 87D0029E | WMI | CCMSetup Failed | Prajwal Desai post |
| 2147023174 | The RPC server is unavailable | Check out firewall or AntiVirus | |
| 2147024891 | Access is denied | ||
| 2147749889 | WMI | Generic failure | |
| 2147749890 | WMI | Not found | WMI Repair |
| 2147749904 | WMI | Invalid class | |
| 2147749908 | WMI | Initialization failure | |
| 2147942405 | Admission is Denied | Missing Firewall rules MacAfee-HIPS | |
| 2147944122 | The RPC server is unavailable | KB899965 Dcom is miss-configured for security | |
| 2148007941 | Server Execution Failed | ||
| Technet Forums Sources |
Don't forget to put emphasis on the prerequisites of the SCCM client, this volition increment your success percentage during client installation. You can also check the listing of client commands list, as an additional help for troubleshooting your SCCM clients.
SCCM Client Installation Mistake CodesReporting
Knowing the client installation condition from reports reduces the number of devices without SCCM client installed in your It infrastructure. It likewise increases your effectiveness, when information technology's fourth dimension to tackle all unhealthy clients.
One of our custom SSRS reports is made specially for the Configuration Manager Client. This report now shows the last SCCM client installation error codes, including the description of the installation deployment country. This report will help you achieve the *almost* 100% client installation, that your project manager loves to come across.
Source: https://systemcenterdudes.com/sccm-client-installation-error-codes/
0 Response to "Unable to Read Existing Resultant Wua Policy. Error = 0x80070002."
Postar um comentário