Summary: After you upgrade to Microsoft Systems Management Server (SMS) 2003 Service Pack 3 (SP3), you run a report that is based on the v_Add_Remove_Programs view. However, the report stops responding, and the process uses 100 percent of the CPU resources.
For example, reports such as the "Computers with specific software registered in Add Remove Programs" report stop responding, and the process uses 100 percent of the CPU resources.
Solution: Fixing Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 SP3 errors is a really difficult task for most computer users. To solve Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 SP3 problems effectively and efficiently, install a good Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 SP3 Error Removal Tool is a smart solution. It's an amazing software which is designed for users to troubleshoot Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 SP3 errors efficiently..
Download the Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 SP3 repair tool
In order to repair Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 SP3 error, use the SmartPCFixer software program. This system optimizer software is already proven to locate, identify, and remove Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 SP3 errors. Speed up your PC with SmartPCFixer at once
Method for Advanced Users
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SMS 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
PrerequisitesTo apply this hotfix, you must have SMS 2003 SP3 installed.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.File nameFile versionFile sizeDateTimePlatformInvcollectiontask.dll2.50.4253.310647,61601-Aug-200708:25x86Sms2003ac-sp3-kb939872-x86.mspNot applicable340,99201-Aug-200708:25Not applicable
Hotfix installation informationBecause of new architecture in SMS 2003, you must create a new package and a new program to advertise this hotfix to the advanced client computers. We recommend that you let the software installation wizard do this automatically. You have to create the package, the program, the collection, and the advertisement on the site at the top of the hierarchy.
After the hotfix is installed on an 32-bit SMS 2003 SP3 advanced client, the advanced client will no longer report data for the Win32Reg_AddRemovePrograms64 class during its next hardware inventory cycle. Therefore, the previously reported data will be removed from the associated table in the SMS database.
To apply this hotfix, follow these steps:
Note Silent installations do not create the SMS package and programs. See the SMS Installation Directory\Logs\KB939872\ACReadme.txt file for instructions that you can use to manually update the SMS advanced clients.
Note You must have Windows Installer version 3.0 or a later version.
The product code for the English version of SMS 2003 SP3 advanced client is 4A39A27F-005B-407E-8CF5-F4D8065658E4.The PatchGUID for the English version of SMS 2003 SP3 advanced client is AB136A5F-6EB5-46A3-9283-13616362BC31.
If LCase(installer.ProductInfo(productCode, "ProductName")) = LCase(productName) Then Exit For Next If IsEmpty(productCode) Then Wscript.Echo "Product is not registered: " & productName : Wscript.Quit 2 WScript.Echo "ProductCode = " & productCode
How to manually update the v_Add_Remove_Programs viewAfter you apply this hotfix, you can manually update the v_Add_Remove_Programs view to increase performance. To do this, run the following statement against the SMS database by using SQL Query Analyzer:if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[v_Add_Remove_Programs]') and OBJECTPROPERTY(id, N'IsView') = 1) drop view [dbo].[v_Add_Remove_Programs] GO SET QUOTED_IDENTIFIER ON GO SET ANSI_NULLS ON GO CREATE VIEW dbo.v_Add_Remove_Programs AS SELECT MachineID AS 'ResourceID', InstanceKey AS 'GroupID', RevisionID, AgentID, TimeKey AS 'TimeStamp', ProdID00 AS 'ProdID0', DisplayName00 AS 'DisplayName0', InstallDate00 AS 'InstallDate0', Publisher00 AS 'Publisher0', Version00 AS 'Version0' FROM dbo.Add_Remove_Programs_DATA UNION ALL (SELECT arp64.MachineID, arp64.InstanceKey, arp64.RevisionID, arp64.AgentID, arp64.TimeKey, arp64.ProdID00, arp64.DisplayName00, arp64.InstallDate00, arp64.Publisher00, arp64.Version00 FROM Add_Remove_Programs_64_DATA arp64 LEFT JOIN Add_Remove_Programs_DATA arp32 ON arp64.ProdID00 = arp32.ProdID00 AND arp64.MachineID = arp32.MachineID WHERE arp32.ProdID00 IS NULL) GO SET QUOTED_IDENTIFIER OFF GO SET ANSI_NULLS ON GO Grant select on v_Add_Remove_Programs to smsschm_users Go Grant select on v_Add_Remove_Programs to webreport_approle Go
What Else Does SmartPCFixer Offer You?
SmartPCFixer™ is not only able to troubleshoot Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 SP3 error, but also help identify and fix Windows' invalid registry entries. By running Scan & Cleaner as part of scheduled maintenance, it will keep your PC from freezing or frequent crashes . Using it will reduce the probability of you getting a "blue screen", program not responding or lock up.
SmartPCFixer provides you with Registry Backup, System Backup, Favorites Backup and Folder Backup. In addition, the new built-in function of Restore Point enables you to create a system store point so you can recover your system to a previous state if you do not like the changes you have made. This ensures the safety of your system when you run the registry repair process.
Related: No Music In 3D Pinball In Windows Me,Internet Explorer Does Not Check For Newer Versions Of Web Pages,Non-critical Error Attempting To Install TCP/IP After RAS,Manual Workflow Rules Are Not Sorted Alphabetically When You Try To Apply The Manual Workflow Rules By Using The Microsoft CRM Web Client Or By Using The Outlook Client,PPT7: Clipart Gallery 2.0a Update For Windows NT Users
Read More: ,FIX: INSERT..SELECT with IGNORE_DUP_ROW on a Clustered Index Stops Responding,FIX: An object data source may not appear in the Website Data Sources window when you try to set the object data source for a SQL Server 2005 Reporting Services report in Visual Studio 2005,How to Disable Write Caching for the 32-Bit File System,How to customize or reset a menu in an Office for Mac program,FIX: Your WinFX application crashes when you try to use the FileRecordSequence.WriteRestartArea method that is included in the WinFX SDK