Something here might help.
https://social.technet.microsoft.com/Forums/lync/en-US/abcae273-5b09-4d6e-b0dd-7df5e06e5845/wmi-error-invalid-namespace?forum=winserverManagement
--please don't forget to Accept as answer if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Server 2012 r2 Domain controller.
WMI diag gives the following errors:
Root/aspnet, 0x8004100E - (WBEM_E_INVALID_NAMESPACE) Namespace specified cannot be found.
Then 118 error 0x80070002 saying it can't open registry keys.
DISM scanhealth showed no errors.
What should I do to resolve this issue or is a WMI rebuild necessary? What steps are needed to rebuild WMI?
Thanks
Something here might help.
https://social.technet.microsoft.com/Forums/lync/en-US/abcae273-5b09-4d6e-b0dd-7df5e06e5845/wmi-error-invalid-namespace?forum=winserverManagement
--please don't forget to Accept as answer if the reply is helpful--
Thanks for the reply.
They said they tried to rebuild the repository (didn't include steps) and didn't help.
The blog link in there goes to a general page now.
I only have 1 server so can't copy repositories.
SFC scan didn't help.
Might give this one a go.
https://techcommunity.microsoft.com/t5/ask-the-performance-team/wmi-repository-corruption-or-not/ba-p/375484
--please don't forget to Accept as answer if the reply is helpful--
Hi,
If you suspect WMI or repository corruption, rebuilding repository is the last thing you should do. Deleting and rebuilding the repository can cause damage to the system or to installed applications. You could first try some steps(instructed below) to check the issue details.
Reference link:
https://techcommunity.microsoft.com/t5/ask-the-performance-team/wmi-rebuilding-the-wmi-repository/ba-p/373846
Thanks,
Jenny
Thanks for the replies.
The objects.data is only 29MB.
I'm getting a notification during the pre-install check for Veritas Backup Exec. It says problems in WMI could prevent SQL express from installing correctly.
A previous version of this software froze during install but seemed to work fine after a reboot after aborting the install.
The time has come to install a newer version again.
Are there any known issues with re registering WMI components, as listed in JennyYam's link or this link from Veritas?
https://www.veritas.com/support/en_US/article.100017778
The only WMI error in event viewer is a TPM-WMI 1794 error. Not sure how to resolve this. Link with supposed info to fix this error: Link
Looks like there are 2 2012 r2 updates further down the page. Install those?
Thanks!