All the client and site server components in Microsoft
Systems Management Server (SMS) 2003 record process information in individual
log files. You can use the information in the client and site server log files
to help you troubleshoot issues that may occur in your SMS 2003
hierarchy.
By default, client and server component logging is turned on
in SMS 2003. However, the log files differ according to the type of client that
is installed. For example, the following rules apply:
- The SMS 2003 Legacy Client logs record the same information
as the SMS 2.0 client. The Legacy Client log files are located in the
%Windir%\MS\SMS\Logs folder on the client computer.
- The SMS 2003 Advanced Client uses different log files than
the Legacy Client to record information. The Advanced Client logs are located
in one of the following locations:
- On computers that serve as management points, the
Advanced Client logs are located in the SMS_CCM\Logs folder.
- On all other computers, the Advanced Client log files
are located in the %Windir%\System32\CCM\Logs folder.
Legacy Client log files
The following table describes the Legacy Client log files and
lists possible issues that apply.
Collapse this tableExpand this table
| Log file name | Description | Used to help
troubleshoot |
| APASetup.log | Installation of the Advertised Programs
Agent (APA). | Installation of software distribution components. |
| Ccim32.log | Client Configuration Installation Manager
(CCIM). Logs routine verification of client components. | Client
installation and upgrade problems. |
| CliCore.log | Client core components. | Client
installation and upgrade problems. |
| CLISVC.log | Activity of the SMS Client
service. | SMS Client service problems. |
| CQMGR32.log | File copy activity to the client access
point (CAP). | Inventory data or status data that is not received by the
site. |
| Hinv32.log | Hardware inventory
process. | Hardware inventory problems. |
| Inhinv32.log | Installation of hardware
inventory. | Scenarios where hardware inventory is turned on, but it is
not installed on the client. |
| Insinv32.log | Installation of software
inventory. | Scenarios where software inventory is turned on, but it is
not installed on the client. |
| Launch32.log | Records whether users are logged on to
the computer. | Scenarios where SMSMON32 does not start, or there are
problems with software distribution. |
| ODPSys32.log | Records the Offer Data Provider (ODP)
polling process for advertisements that are based on the computer
name. | Scenarios where the client computer does not receive
advertisements. |
| ODPUsr32.log | Records the Offer Data Provider (ODP)
polling process for advertisements that are based on the user
name. | Scenarios where the user does not receive advertisements. |
| ODPWnt32.log | Records the Offer Data Provider (ODP)
polling process for advertisements that are based on the user group
name. | Scenarios where a user group does not receive
advertisements. |
| RemCtrl.log | Installation of the remote control
component. | Scenarios where remote control is turned on, but it is not
installed on the client. |
| Sinv32.log | Software inventory
process. | Scenarios where software inventory does not run. |
| SMSAPM32.log | Logs the processing of advertised
programs by the Available Programs Manager (APM). | Scenarios where
advertisements fail or do not run. |
| Smscli.log | Logs the start of the Systems Management
tool in Control Panel. | Scenarios where the Systems Management tool does
not start or does not work correctly. |
| SMSCLREG.log | Logs registry access when the client is
installed. | Client installation issues. |
| SMSMon32.log | Advertised Programs Monitor
log. | Advertisement issues. |
| SWDist.log | Records the installation of the software
distribution components. | Scenarios where software distribution is
turned on, but it is not installed. |
| WNLOGON.log | Logs the client installation process when
the logon script is used. | Client installation issues. |
| WNMANUAL.log | Logs the manual client installation
process. | Client installation issues. |
| WNREMOTE.log | Logs the remote “push” installation of
the client software. | Client installation issues. |
Advanced Client log files
The following table describes the Advanced Client log files and
lists possible issues that apply.
Collapse this tableExpand this table
| Log file name | Description | Used to help
troubleshoot |
| CAS | Content Access service. Maintains the local
package cache. | Downloaded package issues and "cache out of space"
errors. Make sure package content access is completed. |
| CcmExec.log | Records activities of the client and the
SMS Agent Host service. | Scenarios where the client is corrupted or not
functioning. For example, this log applies to a scenario where the client
cannot communicate with a management point. Make sure that there are no errors,
such as WinHTTP errors, listed. |
| CertificateMaintenance.log | Maintains certificates for
Active Directory directory service and management points. | Scenarios
where the client cannot communicate with a management point or with Active
Directory. |
| ClientIDManagerStartup.log | Creates and maintains the
client GUID. | Scenarios where the client changes its GUID after a
hardware change or after Windows activation. |
| ClientLocation.log | Site assignment
tasks. | Scenarios where the client is not assigned to a site. Make sure
that the client has determined its assigned site. |
| ContentTransferManager.log | Schedules the Background
Intelligent Transfer Service (BITS) or the server message block (SMB) to
download or to access SMS packages. | Package version issues or packages
that are not available. |
| DataTransferService.log | Records all BITS
communication for policy or package access. | Download problems from a
management point or a distribution point. |
| Execmgr.log | Records advertisements that
run. | Package errors or packages that are unavailable. Make sure that
the program command line has run successfully and that status is
generated. |
| FileBITS.log | Records all SMB package access
tasks. | Problems that occur when you run a package from the distribution
point when BITS is not turned on. |
| Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs)
| Windows Management Instrumentation (WMI) provider for software
inventory and file collection. | File system access or the WMI
provider. |
| InventoryAgent.log | This component creates discovery
data records (DDRs) and hardware and software inventory
records. | Inventory issues or problems where the client cannot access
the management point. Make sure that inventory or discovery has finished and
that the report is copied to the management point. |
| LocationServices.log | Finds management points and
distribution points. | Name resolution or scenarios where the client
cannot find the management point or distribution point in Active Directory or
in WINS. Make sure that the client has identified its default management point
in WMI. Additionally, make sure that the resident management point or the proxy
management point is identified. |
| Mifprovider.log | The WMI provider for .MIF
files. | Scenarios where MIFs are marked "invalid". |
| Mtrmgr.log | Monitors all software metering
processes. | Scenarios where metering cannot monitor a program or add to
WMI. Make sure that the software metering rules were downloaded, and that the
programs are matched by the rules. |
| PolicyAgent.log | Requests policies by using the Data
Transfer service. | Policy request problems. Make sure that policies were
downloaded from the management point. |
| PolicyAgentProvider.log | Records policy
changes. | Policy request problems or WMI errors. |
| PolicyEvaluator.log | Records new policy
settings. | Policy override issues. Make sure that the downloaded
policies are applied to the local computer. |
| Scheduler.log | Records schedule tasks for all client
operations. | WMI access errors or scenarios where tasks do not
start. |
| Smscliui.log | Records usage of the Systems Management
tool in Control Panel. | The Systems Management tool in Control
Panel. |
| StatusAgent.log | Logs status messages that are created
by the client components. | Scenarios where the client cannot send status
to the management point. |
| SWMTRReportGen.log | Generates a usage data report that
is collected by the metering agent. (This data is logged in
Mtrmgr.log.) | Scenarios where the client cannot send a software metering
report to the management point. Make sure that the client can generate a usage
report and send it to the management point. |
| Remctrl.log | Logs when the remote control component
(WUSER32) starts. | Scenarios where you try to control the client
remotely. |
You may see repeated log entries in the SMS 2003
Advanced Client log when the client reports inventory. The log entries indicate
any problems that occur when the inventory is reported. For example, you may
see the following log entry:
Inventory: Successfully sent
report. Destination:mp:MP_SinvEndpoint, ID:
{AAEE97B0-271B-42F5-A946-B996592A2539}, Timeout: 10080 minutes
In this
example, the destination is defined as a
MP_
xxxxEndpoint, where
xxxx is the SINV component in this example.
Site server log files
The SMS 2003 site server log files are located in the SMS\LOGS
folder. Because SMS 2003 relies heavily on Microsoft Internet Information
Services (IIS), you can review the IIS log file for additional errors that
relate to client access to the IIS server. The IIS log file is located in the
%Windir%\System32\logfiles\W3SVC1 folder on the IIS server. The following table
describes the site server log files and lists possible issues that
apply.
Collapse this tableExpand this table
| Log file name | Description | Used to help
troubleshoot |
| Adminui.log | Records the local SMS Administrator
Console tasks when you connect to SMS sites. | Connectivity errors to
site servers or to site databases. |
| Ccm.log | Client Configuration Manager
tasks. | Scenarios where the site cannot connect to computers because of
permissions or name resolution. Make sure that the site server can connect to
the Admin$ share on the client computer. |
| Cidm.log | Records changes to the client settings by
the Client Install Data Manager (CIDM). | Scenarios where the site is not
updating CLIDATA.SRC files. Make sure that the correct files are copied to the
SMS\Inboxes\Clicomp.src folder. |
| Colleval.log | Logs when collections are created,
changed, and deleted by the Collection Evaluator. | Problems with
collections. Make sure that collections are created and updated
successfully. |
| Compsumm.log | Records Component Status Summarizer
tasks. | Scenarios that occur when the status system does not update
component tallies. |
| Cscnfsvc.log | Records Courier Sender confirmation
service tasks. | Courier Sender errors. |
| Dataldr.log | Processes Management Information Format
(MIF) files and hardware inventory in the SMS database. | Communications
errors in the SMS database or "bad" hardware inventory files. Make sure that
the delta MIF file was processed to the SMS site database. |
| Ddm.log | Saves DDR information to the SMS database by
the Discovery Data Manager. | Communicating errors with Microsoft SQL
Server or "bad" discovery records. |
| Despool.log | Records incoming site-to-site
communication transfers. | Corrupted files or when the Despooler
component cannot decompress packages. |
| Distmgr.log | Records package creation, compression,
delta replication, and information updates. | Package source version
issues or package update issues. |
| Hman.log | Records site configuration changes and
publishes site information in Active Directory. | Site control serial
number or delta serial number issues, or scenarios where the site cannot
publish site information to Active Directory. Make sure that *.CT2 files are
processed and that child sites attach correctly. Make sure that the site code
and roaming boundaries are published to the Active Directory. |
| Inboxast.log | Records files that are moved from the
CAP to the corresponding SMS\INBOXES folder. | Problems with site server
permissions or scenarios where the registry is corrupted. |
| Inboxmgr.log | Records CAP file
maintenance. | Problems with permissions or scenarios where the registry
is corrupted. |
| Invproc.log | Records the processing of delta MIF files
for the SMS Dataloader component from client inventory files. | Problems
with file corruption. Make sure that .nhm files are processed to .mif
files. |
| Mpcontrol.log | Records the registration of the
management point with WINS. Records the availability of the management point
every ten minutes. | Possible IIS issues if the management point is
unavailable. Review this log for other IIS communication issues and WINS
registration issues. |
| Mpfdm.log | Management point component that moves
client files to the corresponding SMS\INBOXES folder. | Problems with
file permissions. |
| MPMSI.log | Management point .msi installation
log. | Management point installation errors. Search for “return value 3”
errors. |
| MPSetup.log | Records the management point installation
wrapper process. | Scenarios where you cannot run Mp.msi or management
point installation is not completed. Make sure that Mp.msi was started. |
| Ntsvrdis.log | SMS server discovery. | Problems
with SMS site systems discovery. |
| Offermgr.log | Records advertisement
updates. | File corruption or scenarios where notification and
advertisement changes do not occur. |
| Offersum.log | Records summarization of advertisement
status messages. | Status message miscounts or scenarios where
summarization files are not created. |
| Policypv.log | Records updates to the Advanced Client
policies to reflect changes to client settings or
advertisements. | Scenarios where policy updates do not occur after you
make changes to advertisements or to client settings. |
| Replmgr.log | Records the replication of files between
the site server components and the Scheduler component. | A backlog of
files in the INBOXES\Schedulr.box\tosend folder or file permission issues. Make
sure that outgoing requests are changed to minijobs for the Scheduler component
and that incoming files are moved to the correct component. |
| Rsetup.log | Reporting point setup
log. | Installation errors. |
| Sched.log | Records site-to-site job and package
replication. | A backlog of files that are caused by sender errors or by
package corruption. |
| Sender.log | Records files that are sent to other child
and parent sites. | Permissions problems for the
INBOXES\DESPOOLR.BOX\RECEIVE sending site folder or an incorrect site address.
Make sure that the site can connect to the SMS_Site share on the destination
site and that data was transferred. |
| Sinvproc.log | Records client software inventory data
processing to the SMS site database in SQL Server. | Problems with
corrupted files or access to SQL Server. |
| Sitecomp.log | Records maintenance of the installed
site components. | Upgrade issues, registry or file system permission
issues, or scenarios where the site cannot publish site information to Active
Directory. |
| Sitectrl.log | Records site setting changes to the
Sitectrl.ct0 file. | Site control file or database corruption. Make sure
that the Sitectrl.ct0 file is updated. |
| Sitestat.log | Records the monitoring process of all
site systems. | Scenarios where the site cannot access remote site
systems to generate status information for available drive space or available
database space. |
| Smsdbmon.log | Records database
changes. | Possible corruption of the registry triggers or a scenario
where the site cannot access SQL Server. |
| Smsexec.log | Records processing of all site server
component threads. | Problems with possible site corruption or a
scenario where the component services do not start. |
| Smsprov.log | Records WMI provider access to the SMS
database. | Possible WMI corruption or permissions issues with the WMI
provider. This file also logs the WMI and SQL queries that are used to access
the SMS database. |
| SMSReportingInstall.log | Records the Reporting Point
installation. This component starts the installation tasks and processes
configuration changes. | Reporting Point installation. |
| Srvacct.log | Records the maintenance of accounts when
the site uses standard security. | Scenarios where accounts are removed
or changed. |
| Statmgr.log | This component writes all status messages
to the database. | Scenarios where status messages do not appear, or they
appear corrupted. |
| Swmproc.log | This component processes metering files
and maintains settings. | Scenarios where software metering information
does not appear or appears corrupted. |
If management points are installed in the site hierarchy,
management point log files are stored in the SMS_CCM\LOGS folder on the
management point computer. The following table describes the management point
log files and lists possible issues that apply.
Collapse this tableExpand this table
| Log file name | Description | Used to help
troubleshoot |
| MP_Ddr.log | Records the conversion of XML.ddr records
from clients and copies them to the site server. | File corruption or
access to the SMS\MP\OUTBOXES\DDR.BOX folder. |
| MP_GetAuth.log | Records the status of the site
management points. | IIS access errors. |
| MP_GetPolicy.log | Records policy
information. | WMI access problems. |
| MP_Hinv.log | This component converts XML hardware
inventory records from clients and copies the files to the site
server. | File corruption or access to the SMS\MP\OUTBOXES\HINV.BOX
folder. Make sure hardware inventory data is converted from XML to NHM file
format. |
| MP_Location.log | Records location manager
tasks. | IIS and WMI access problems. |
| MP_Policy.log | Records policy
communication. | SQL Server access problems. |
| MP_Relay.log | This component copies files that are
collected from the client. | File corruption issues. |
| MP_Retry.log | Records the hardware inventory retry
processes. | Corrupted hardware inventory files. |
| MP_Sinv.log | This component converts XML hardware
inventory records from clients and then copies them to the site
server. | File corruption or access to the SMS\MP\OUTBOXES\SINV.BOX
folder. Make sure that software inventory data is converted from XML to SIC or
SID file format. |
| MP_Status.log | This component converts XML.svf status
message files from clients and copies them to the site server. | File
corruption or access to the SMS\MP\OUTBOXES\STAT.BOX folder. Make sure that the
status message data is converted from XML to SVF file format. |
To turn off logging
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows
You can manually turn on or turn off logging of
the SMS components on the SMS 2003 site server. To turn on logging for the site
components, follow these steps:
- Click Start, click Run,
type regedit, and then click
OK.
- Locate the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing
subkey. - Double-click the Enabled value.
- Type 1 in the Value
data text box, and then click OK. To turn off
logging, use 0 as the Value data. If
you want turn off component logging, skip steps 6 and 7.
- Click Start, point to
Administrative Tools, and then click
Services.
- Stop and then restart the SMS_EXECUTIVE and
SMS_SITE_COMPONENT_MANAGER services.
The SMS Trace utility
You can use the SMS Trace utility (Trace32.exe) to view the SMS
log files in real time. When you use the SMS Trace utility, the log view
automatically updates to show new entries. The SMS 2003 SMS Trace utility is
included in SMS 2003 Toolkit 1. For more information about SMS 2003 Toolkit 1,
visit the following Microsoft Web site:
The SMS 2003 version of the SMS Trace utility includes specific
improvements to help you identify error messages and read log files that are
generated by IIS.
The SMS 2003 SMS Trace utility has the following
feature enhancements:
- You can view IIS, Unicode, and MSI logs.
- You can select errors.
- You can search error codes.
- You can use a new information pane to see additional data
that is contained in the log entry.
Article ID: 867490 - Last Review: November 27, 2007 - Revision: 2.6
APPLIES TO
- Microsoft Systems Management Server 2003
| kbtshoot kbmisctools kbinfo KB867490 |
Back to the top
