Quota violation could just be not enough memory for WMI to load everything. It could also mean WMI corruption too.
Try this: winmgmt /verifyrepository You could also run a ccmrepair.exe to see if that fixes anything, I am pretty sure that wont fix site WMI issues, just the client though. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Owen Sent: Friday, January 10, 2014 9:36 AM To: [email protected] Subject: Re: [mssms] Can't connect to Primary site in 2012 R2 with CAS, any thoughts? Hmm, have to admit that I've never seen this one before! This happens when I attempt step c. as seen here: 1. Click Enum Classes, click Recursive, and then click OK. [Inline image 1] On Fri, Jan 10, 2014 at 9:15 AM, Stephen Owen <[email protected]<mailto:[email protected]>> wrote: I'm able to connect to other sites from this server, including the primary. I'm about to start testing local WMI, as listed in this article. http://schadda.blogspot.com/2012/08/how-to-fix-issues-related-with_7.html [..]6. Verify namespace connectivity * On the computer where the SMS Provider is installed, click Start, click Run, and then type wbemtest. * Click Connect, type \\<siteserver>\root\sms<file:///\\%3csiteserver%3e\root\sms>, and then click Login. * Click Enum Classes, click Recursive, and then click OK. * In the Query Result list, double-click SMS_ProviderLocation. * Click Instances, and then double-click the line that contains the target site code. For example, SMS_ProviderLocation.SiteCode="ABC." * In the Properties section, locate the NamespacePath line. You might have to double-click this line to see the whole line. * Copy the NamespacePath value to the clipboard. For example, copy the following value: * \\Server1\root\sms\site_ABC<file:///\\Server1\root\sms\site_ABC>[..] On Fri, Jan 10, 2014 at 9:10 AM, Niall Brady <[email protected]<mailto:[email protected]>> wrote: do you get the error when starting the console only ? if so try specify the fqdn On Fri, Jan 10, 2014 at 3:07 PM, Daniel Ratliff <[email protected]<mailto:[email protected]>> wrote: Looks like an SMS provider failure. I am not sure how to fix though. [38, PID:10184][01/10/2014 14:56:26] :Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.GetInstance(String objectPath) Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Stephen Owen Sent: Friday, January 10, 2014 9:03 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Can't connect to Primary site in 2012 R2 with CAS, any thoughts? Hi all, I've got a 2012 R2 env with three primaries and a CAS, and I am able to connect to the CAS, and two of the three primaries. However, on one primary I get the message that ConfigMgr is unable to connect to the site. I've checked Remote Activation and DCOM and that all looks fine. Do you all see anything I should double-check, based on this log? The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
<<inline: image001.png>>
