Skip to content

Read log messages

Introduction

The CapaInstaller System generates several different types of log files to record the actions taken by its various elements and/or the errors encountered. These are stored in sub-folders located under the following path:
 
<ProgramFiles>\CapaInstaller\Logs\
The logs are always stored on the machine where the relevant application or service that generated them is running. Below you can see the sub-folder and file name of each possible log file and gives a short description of each. These logs can be useful when troubleshooting your CapaInstaller System and applications.

SubfolderFilenameDescription
CistubCapaInstaller CiStub.logDefault location: C:\Program Files\CapaInstaller\Client\logs. This can be altered via the ‘Configure Agent’ menu item in System Administration. The log includes initialization as well as event information.
CapaInstaller CiStub Core.logDefault location: C:\Windows\Temp, but is placed in %temp% according to the context CIStub is running in. The log is geared towards Launch logging for CIStub and stops when CIStub is capable of reporting to its own log file.
CapaInstaller Agent.exe.logDefault location:  C:\Program Files\CapaInstaller\Client\logs. This can be altered via the ‘Configure Agent’ menu item in System Administration. This logfile contains launch information and possibly client installation information. The file is rewritten each time the agent runs.
CisyncCiSync.logDefault location:  C:\Program Files\CapaInstaller\logs\Services. The log includes initialization and synchronization progress/summary log.
Sync_02092009-014321275.logDefault location:  C:\Program Files\CapaInstaller\Logs\Synchronizations. Each Sync_ log in this directory represents a Sync job and contains detailed sync information about service communication and file progress.
CODManCODMan.logActions took the last time the OS Deployment Manager application was run.
Inventory ManagerSQLLog.logDatabase-related errors that have occurred as Inventory Manager ran.
MiscInstallCIStub.logActions are taken during the last several runs of the Agent Deployment tool.
ReplicatorSQLLog.logDatabase-related actions taken by the Replicator during the last several runs.
Ping.logRecent attempts by the Replicator to contact the Container and other machines.
General.logMiscellaneous log messages generated as the Replicator runs. The messages stored here are the same as those shown in the Replicator application window.
Schedule.logSchedule-related log messages generated by the Replicator.
Unit.logEvents related to the Replicator processing units.
Conscom.logEvents related to the Replicator communication with Containers.
Dynamic groups.logEvents related to the Replicator processing dynamic groups.
ReporterSQLlog.logDatabase-related errors that have occurred as the Reporter ran.
ServicesCIDeploy.logDatabase-related errors that have occurred as the Security Manager ran.
CIRepl.logMessages related to the running of the deployment service.
CIStub.logMessages related to the running of the Agent service.
ReplicatorAlways.logLogs errors from the “Reinstall and Wake On LAN Check” replicator task.
Conscom.logLog errors related to Conscom.
Container.logLog errors related to a Management Server.
Group.logLog errors related to Groups.
Inventory.logLog errors related to Inventory Collect.
Outbound.logLog errors related to processing Outbound.
Package.logLog errors related to Packages.
Resources.logLog errors related to building Resources on the Management Server.
Unit.logLog errors related to Units.
WSUS.logLog errors related to WSUS.
PM service (cipms.exe)Services\remoting\remoting.logInformation about events called from CMS-console.
Services\ SyncCategory\SyncCategory.logInformation about synchronizations of Categories between the WSUS server and the CMS database.
Services\ SyncComputers\SyncComputers.logInformation about synchronizations of Computers between the WSUS server and the CMS database.
Services\ SyncUpdates\SyncUpdates.logInformation about synchronizations of Updates between the WSUS server and the CMS database.
Services\cipms.logGeneral log for the PM service.
Services\cipms_SQL.logIf the service failed to communicate with the CMS database.
SetupVariousHere you will find the latest setup log. This log is refreshed every time the setup runs. No history will be kept. You will find MSI logs in the MSI folder.