Hi all, the last few installs of SCCM 2007 SP1 R2 on windows 2008 x64 ive had an issue where statview.exe uses 99% CPU for 180 seconds.Basically i go into component or site sytem status, show messages... and play the waiting game...i havent been able to find anything on this as yet and was wondering if anyone else has run into this or has a fix ?

You will want to filter your messages, it is attempting to load all status messages in the system which is very CPU and memory intensive. Consider using reports or status message queries with filters to get at the messages you are interested in.Stan

its not a filter issue mate.When displaying messages statview goes to 99% CPU immediately- irrelevant of if there is 1 or 100000 messages being viewed- i have since found out that if i change the priority of the statview process to "below normal" - the statview window and associated logs are displayed immediately

I am having this same behavior ... thanks for the tip to set the process priority lower, because that does work.I'm running ConfigMgr SP2 with R2 on Windows 2008 x64 SP2. Any ideas?Cheers,Trevor Sullivan

I wrote a small utility to run in the background, to get around this meanwhile, since lowering the priority speeds it up quickly. Here is the c# source code (not sure where I can actually post the binary file). You should be able to easily compile this with Visual Studio 2008 as a console application, targeting the .NET 2.0 framework. Once I had the compiled .NET assembly,I just wrote a small batch file that calls it with a single parameter:SetProcessPriority statviewC# Sourceusing System;using System.Diagnostics;using System.Threading;using System.Windows.Forms; namespace SetProcessPriority{ class Program { static void Main(string[] args) { if (args.Length != 1) return; string procname = args[0]; while (1 == 1) { try { Process[] procs = Process.GetProcessesByName(procname); foreach (Process proc in procs) { proc.PriorityClass = ProcessPriorityClass.BelowNormal; } } catch { } Thread.Sleep(2000); } } }}End C# SourceCheers,Trevor SullivanConsultant | 1E Inc.http://trevorsullivan.wordpress.com

I wrote a small utility to run in the background, to get around this meanwhile, since lowering the priority speeds it up quickly. Here is the c# source code (not sure where I can actually post the binary file). You should be able to easily compile this with Visual Studio 2008 as a console application, targeting the .NET 2.0 framework. Once I had the compiled .NET assembly, I just wrote a small batch file that calls it with a single parameter: SetProcessPriority statview C# Source using System; using System.Diagnostics; using System.Threading; using System.Windows.Forms; namespace SetProcessPriority { class Program { static void Main(string[] args) { if (args.Length != 1) return; string procname = args[0]; while (1 == 1) { try { Process[] procs = Process.GetProcessesByName(procname); foreach (Process proc in procs) { proc.PriorityClass = ProcessPriorityClass.BelowNormal; } } catch { } Thread.Sleep(2000); } } } } End C# Source Cheers, Trevor Sullivan http://trevorsullivan.net

I wrote a small utility to run in the background, to get around this meanwhile, since lowering the priority speeds it up quickly. Here is the c# source code (not sure where I can actually post the binary file). You should be able to easily compile this with Visual Studio 2008 as a console application, targeting the .NET 2.0 framework. Once I had the compiled .NET assembly, I just wrote a small batch file that calls it with a single parameter: SetProcessPriority statview C# Source using System; using System.Diagnostics; using System.Threading; using System.Windows.Forms; namespace SetProcessPriority { class Program { static void Main(string[] args) { if (args.Length != 1) return; string procname = args[0]; while (1 == 1) { try { Process[] procs = Process.GetProcessesByName(procname); foreach (Process proc in procs) { proc.PriorityClass = ProcessPriorityClass.BelowNormal; } } catch { } Thread.Sleep(2000); } } } } End C# Source Cheers, Trevor Sullivan http://trevorsullivan.net

thanks trevor - its always nice when someone else atcually gets what your saying! :-) <instead of getting dismissed with a "nothing" answer!>thanks for the small prgram.... i will give it a try.

Today, I ran into this same issue with a clean install of a SCCM 2007 with SP2 and applied R2. SCCM is installed on a Windows server 2008 R2 with SQL 2008 Std SP1.Basically, Statview.exe utilizes CPU at %99 - %100 and SQLServer doesn't get a chance to execute the query in a timely manner and it takes forever to finish the query execution.Any update from MS on this issue?

I recently started having this issue as well.My lab and our production server are both SCCM R2 SP2. The lab server is having the issue, the production server is not...Lowering the priority of the statview process as Ben suggested clears up the problem right away.I have no idea why that works... Is there an 'official' fix for this yet? Otherwise, is there a way to take off the 'anwered' status on this thread?

yer - you'd think that the fact that it wasnt even taken seriously - let alone answered would preclude it from being marked as answered - but, unfortunately it seems to be a common occurance in these forums.I have no had any indication that this has even been recognised as an issue.

Unfortunately, forum entries aren't an official way to report issues and get hotfixes. The only way I'm aware of to get an issue officially acknowledged, and a hotfix created (if one doesn't already exist) would be to open a Microsoft support case, so they can get all of the relevant log files and details about your configuration.If this is an ongoing issue, I strongly encourage you to open a support case, so you can get an official response.Standardize. Simplify. Automate.

Hi Sherry,Support cases are expensive. I'm all for getting the info to microsoft (log files etc...) but in my case, I don't have a support contract.If any MS folks are interested in looking into this I will be happy to provide log files or do whatever I can to grease the wheels (except provide a credit card # ;-) ) This does appear to be a bug...-Karl M

Experiencing same issue in a vm test lab. (virtualbox) (x64) AD 2008, SQL 2008, SCCM 2007 SP2 w R2 all on the same VM. Looks like this hasn't been fixed in over a year? Thanks to Ben_22 for the fix.

(x64) AD 2008, SQL 2008, SCCM 2007 SP2 w R2 all on the same VM. It's not recommanded, ConfigMgr/SQL should not be installed on the domain controller machine !!! Move ConfigMgr/SQL on other machine with Windows 2008/2008R2 (full patched) and see if the problem still exists.Bechir Gharbi. MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront (Time Zone : GMT+1)

I have the same error with SCCM 2007 R2 on SQL 2008 SP1 and Windows Server 2008 R2. When I want to open some Advertisment status then statview.exe goes to 100% and it take time to open the log file. If I put this process in tTask Manager to Low priority it open it immediatelly. Any experience with this?

For now I found that if I change mmc.exe to low priority in Task Manager it will make SCCM console to work normally and do not have statview.exe CPU 100%.

I have tried to report this as a bug at connect.microsoft.com. I will update once I get some sort of feedback. OHM

Out of curiosity.... are these virtual servers? John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Yes, these are Hyper-V virtual servers.

Yes, these are Hyper-V virtual servers. With local SQL? I haven't run SCCM on Hyper-V but I have heard it's better than VMWare. I can tell you SCCM on VMWare will have problem with high CPU though. On physical hardware when I would run statview it was no problem at all. On virtual it pegs the CPU at 100% for awhile and I only display since midnight. If you try to display more it will kill the server. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Yes, I have local SQL Server 2008. Except the issue with statview.exe CPU 100% everything else is working fine. I'm forced every time when I open SCCM console to go in Task Manager and to change mmc.exe priority to low.

New blog post: http://tinyurl.com/32rtl3e - Fixing the statview 100% cpu issue on Windows Server 2008. Enjoy. #in"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm