SMS: Client Logging Improvements in APM and ODP to Help with Troubleshooting

Article translations Article translations
Article ID: 327999 - View products that this article applies to.
This article was previously published under Q327999
This article has been archived. It is offered "as is" and will no longer be updated.

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Expand all | Collapse all

On This Page

SYMPTOMS

It may be difficult to troubleshoot Available Programs Manager (APM) and Offer Data Provider (ODP) logs on clients because the logs contain so much data that the information in the logs may wrap quickly.

RESOLUTION

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Systems Management Server 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
288239 How to Obtain the Latest Systems Management Server 2.0 Service Pack

WORKAROUND

Logging in the Smsapm32.log, Odpsys32.log, Odpusr32.log, and associated .lo_ files has been changed to include only relevant information (with fewer lines of information).

These changes take effect on clients that have version 2.00.1493.4134 or later of the following components installed:
Available Programs Manager Win32
SMS Client Base Components
Software Distribution
These log files contain fewer lines of information, which means that information is retained in the log files longer. This depends on the number of advertisements that are available and on the client polling cycles for new advertisements.

Modify the Logging Level

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

You can change the logging to the original logging level by modify the registry:
  1. Start Registry Editor.
  2. Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Available Programs Manager Win32\Logs\Masks
  3. Click any of the following keys, point to New on the Edit menu, click DWORD, type 3fffffff, and then click OK:
    APM
    PEA
    PIPCAP
    CCIM
    MON
    WIZ
    System
    WNet User Groups
    WNet User
    Repeat this step for each value that you want to change.

  4. Quit Registry Editor.
NOTE: To turn on or turn off verbose logging on a specific computer, you must make the changes on that computer; this is not a site-wide setting.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Systems Management Server 2.0 Service Pack 5.

MORE INFORMATION

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
243385 SMS: Enabling Network Abstraction Layer Logging and Setting Logging Levels
241001 SMS: Troubleshooting Server, Component, and Hierarchy Issues

Properties

Article ID: 327999 - Last Review: October 26, 2013 - Revision: 5.4
APPLIES TO
  • Microsoft Systems Management Server 2.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbqfe kbhotfixserver kbsoftwaredist kbsms200presp5fix kbenv kbprb KB327999

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com