SCE 2010 console has stopped working, CLR20r3
I have several Computer Groups listed in the Console and I can run a 'Group Summary Report' from all but 2 of the groups. The 'All Windows Computers' group has 392 members and the 'All Windows Clients' group has more than 300 members. When I right click and choose 'Group Summary Report' for these 2 groups the summary starts to run and then hangs and eventually I get the following: System Center Essentials has stopped working, details show Problem Event Name: CLR20r3. The other groups have less than 200 members each and the reports run without problem. Logged in with admin account, 2008 server and 2008 sql I think those numbers are within the limitations of Essentials.
April 24th, 2012 2:29pm
Hello, Here is an article which disscussed this issue: SCE 2007 Quick Fix: The admin console crashes when selecting a computer in the computers list http://blogs.technet.com/b/systemcenteressentials/archive/2011/02/28/sce-2007-quick-fix-the-admin-console-crashes-when-selecting-a-computer-in-the-computers-list.aspx Cause This can be caused by wrong information being reported by the video card driver. In this case, this happened because when SCE collected software and hardware inventory of that computer, the video card driver from that system reported an invalid value (e.g. a negative value) for the video card memory. For example, on a working computer it will show a value as 256 MB, but on a problem computer it may show a negative value such as -340473856 for Adapter RAM. This can be seen by running Hardware Inventory report (SCE console > Reporting pane) for that computer and selecting to see video card information. Resolution The ideal fix is to update the display driver on that computer or change it to a new one. An alternate option is to update WSUS. This problem occurs when using WSUS 3.0 Service Pack 1 (3.1.6001.65) as it stores values in SUSDB as it's received (i.e. negative values), but in WSUS 3.0 Service Pack 2 (WSUS 3.2.7600.226), it takes care of such negative values and does not store the invalid values in SUSDB. Once you update WSUS from SP1 to SP2, it updates SUSDB immediately, and then your SCE console will not crash anymore while trying to display information for that computer. Reports for deployment status will also start working fine once this is done. Thanks,Yog Li TechNet Community Support
April 25th, 2012 6:56am
WSUS 3.0 SP2 is currently installed. Could I remove (leaving the DB and log files and updated files) and reinstall? I guess I could start looking for a problem computer or computers. This is the full listing of the error Description: Stopped working Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: P3SJZHGV2N0OMVLLDUMEJI40FU144LYC Problem Signature 02: 7.0.2432.1 Problem Signature 03: 4bc66c1f Problem Signature 04: mscorlib Problem Signature 05: 22.214.171.124 Problem Signature 06: 4e154615 Problem Signature 07: 20c7 Problem Signature 08: 100 Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB OS Version: 6.0.6002.2.2.0.274.10 Locale ID: 1033 Read our privacy statement: http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409 Thanks
April 25th, 2012 2:31pm