Log Files

  • Article

Published : June 8, 2005

To understand the management processes, you need to know which sub-processes are part of it and which SMS server and client components participate in it. There are several different log files that provide analysis on the health and functionality of the management point. Table 6 lists the log files and describes their roles.

Table 6   Participating Components Specific to Management Point Setup

Log File Name

Component

Role

MPcontrol.log

Mpcontrol.dll

Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes. IIS issues can occur if the management point is unavailable. Review this log for other IIS communication problems and WINS registration problems.

Mpsetup.log

MPSetup.exe

Records the management point installation wrapper process.  MPSetup.exe is used when you cannot run MP.msi or when management point installation is not completed. Ensure that MP.msi was started.

MPMSI.log

MP.msi

Management point .msi installation log.  Records management point installation errors. You can search this log file for “return value 3” to find errors.

MPfdm.log

Management Point File Dispatch Manager

Moves client files to the corresponding SMS\INBOXES folder.  Review the log when validating problems with file permissions.

For a complete list of all SMS 2003 logs and the processes they monitor, see article 867490 in the Microsoft Knowledge Base at https://go.microsoft.com/fwlink/?LinkId=47289.

The log files listed in Table 7 can be used to identify communication problems between Advanced Clients and the management point or between the management point and the site server.

Table 7   Participating Components Specific to Management Point Operation

Log File Name

Component

Role

MPFDM.log

Management Point File Dispatch Manager

Management point component that moves client files to the corresponding SMS\INBOXES folder.

MPControl.log

Management Point Control Manager

Management point component that registers the management point with WINS. Checks the availability of the management point every 10 minutes. IIS issues can occur if the management point is unavailable. Review this log for other IIS communication issues and WINS registration issues.

MP_Ddr.log

Management Point Discovery Data Manager

Converts XML DDR records received from clients and copies them to the site server. Problems with file corruption or access to the SMS\MP\OUTBOXES\DDR.BOX folder are noted in this log file.

MP_GetAuth.log

MP_GetAuth_ISAPI

Monitors the site management points.  This log file will log IIS access errors specific to management point authorization.

MP_GetPolicy.log

MP_GetPolicy_ISAPI

Retrieves policy information that can help diagnose problems accessing WMI.

MP_Hinv.log

Management Point Hardware Inventory Manager

Converts XML hardware inventory records from clients and copies them to the site server; useful for assessing file corruption or problems accessing the SMS\MP\OUTBOXES\HINV.BOX folder.

MP_Location.log

Management Point Location Manager

Location manager, useful for assessing problems accessing IIS and WMI.

MP_Policy.log

Management Point Policy Manager

Maintains policy communication.  Details problems accessing SQL Server.

MP_Relay.log

Management Point Relay Manager

Copies files that are collected from the client.  File corruption issues are noted in the file.

MP_Retry.log

Management Point Retry Manager

Manages hardware inventory retry process queue; useful for validating corrupt hardware inventory files.

MP_Sinv.log

Management Point Software Inventory Manager

Converts XML hardware inventory records from clients and copies them to the site server; may see file corruption or problems accessing the SMS\MP\OUTBOXES\SINV.BOX folder. Make sure software inventory data is converted from XML to SIC or SID file format.

MP_Status.log

Management Point Status Manager

Converts XML .svf status message files from clients and copies them to the site server; useful for evaluating file corruption or problems accessing the SMS\MP\OUTBOXES\STAT.BOX folder.
On This Page

Debug Logging
Management Point Setup Logging

Debug Logging

When you troubleshoot issues with Advanced Clients or management points, you can turn on debug logging on the computer where the issue occurs. As a result, the actions of Ccmexec.exe are logged. Debug logging works similarly on both Advanced Clients and management points because they use the same Ccmexec framework and process name.

Cc180197.warning(en-us,TechNet.10).gif  WARNING
If you use Registry Editor incorrectly, you might cause serious problems that could require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly.

To turn on the DebugLogging key on the SMS 2003 Advanced Client or management point

  1. Click Start, point to Programs, point to Administrative Tools, and click Services.

  2. Right-click the SMS Agent Host service, and click Stop.

  3. Click Start, click Run, type regedit, and click OK.

  4. In Registry Editor, add the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\DebugLogging

  5. Restart the SMS Agent Host service.

Cc180197.note(en-us,TechNet.10).gif  Note
Enable the DebugLogging key for debugging purposes only. Turn it off when the issue is resolved.

For more information about debug logging, see article 833417 in the Microsoft Knowledge Base at https://go.microsoft.com/fwlink/?LinkId=46661.

Management Point Setup Logging

MPSetup.exe manages the installation process of the management point. The management point setup script is a Windows Installer Script (.MSI) file. Mpsetup.exe does the following:

  • Validates that prerequisites are met.

  • Validates management point status for the site.

MPsetup.exe then starts MP.msi, which writes logging information to MPMSI.log.  MPMSI tracks the entire operation of the installer script. Reviewing the MPMSI.log file can be troublesome because MSI logging is verbose, and using SMS Trace highlights log conditions that are not always errors. The MSI operation lists all dialog entries, and potential error conditions in the MPMSI.log file. When you review a log file, look for RETURN VALUE. If the return value is an error condition, such as return value 3, the line above it should contain a corresponding error code.  Table 8 lists the return values and their descriptions.

Table 8   MP.msi Return Values

Return Value

Description

0

Action not executed

1

Success

2

User cancelled

3

Fatal error

4

Suspended, waiting for reboot