Server and Client Logs

The Adaptiva server logs and client logs are available to monitor the solution and troubleshoot issues. When working with Adaptiva Support, please copy the logs out of their home folder and compress them before sharing with your support agent.

Server Logs

Location: %ADAPTIVASERVER%\logs

• adaptiva.err: Records any errors during the running of the AdaptivaServer service.

• adaptiva.log: Records almost all data regarding AdaptivaServer service.

• AdaptivaNativeUtils.log: AdaptivaServer to windows access logging.

• AdaptivaNativeUtilX.log: AdaptivaClient FIPS cryptography operations using OpenSSL.

• AdaptivaServerNativeUtils.log: Logs from native library such as addition and removal of SMB connections for networked filesystems.

• AdaptivaService.log: AdaptivaService service start/stop logging.

• AdaptiveProtocolTransport.log: AdaptivaServer data transfers using Adaptive Protocol.

• messagingMonitor.log: Logs all RVP advertisements.

• ntlmauth.log: Logs NTLM and Kerberos authentication for SQL Server from native library.

• revision.properties: Contains the timestamp, git commit id, and full version of the code for this install.

• sqlMonitor.log: Call to SQL logging.

• VCDiff.log: Logs generated by the native component responsible for creating diffs between two files. These files typically belong to different versions of application-level content for which differences (diffs) are computed.

• VCDiffDecoder.log: Logs generated by the native component responsible for applying a diff to a previous file version in order to reconstruct the updated content.

Server Component Logs

Location: %ADAPTIVASERVER%\logs\componentlogs

• Akka.log: Logs from the server's REST API.

• BlobServer.log: Logs for internal system used for blob downloads.

• BlobVersionAuditor.log: Used for blob system auditing. Blob system is used when integrated with Microsoft Configuration Manager.

• ByteLevelP2PPublisher.log: Logs publication of content using the byte-range peer-to-peer protocol.

• CdnService: Catch-all log for anything to do with accessing the CDN service. Typically this covers service initialization, obtaining credentials from the operations manager, and upload and download of content.

• ClientUpgrade.log: Client auto upgrade system logs.

• ContentSQLQuery.log: Logs content receipts.

• CrowdStrike.log: Logs operations related to the vulnerability management integration with CrowdStrike.

• DeltaSeries.log: Tracks download and assembly of delta series content, i.e. content for which an earlier version may already exist locally. Typically useful when monitoring feeds, for which it handles content download before consumption. On customer servers, this log also covers distribution of delta series to client systems.

• Feeds.log: Tracks the receipt of feeds from the operations manager, and their subsequent consumption or distribution to client machines. Download of feed content is handled by the delta series system, which logs that part in more detail.

• HTTP.log: Used to monitor the health of the application's HTTP clients and connection managers.

• IntentHistory.log: Logs server-side changes made to Intent Schema objects.

• License.log: Records the status of the licenses enabled on the server.

• MASFileActivity.log: Covers direct content uploads from MAS to the public CDN. Note that this is distinct from feed publication, which also uploads content.

• MemoryManager.log: Current server memory usage and changes in memory usage.

• MetadataCommon.log: Logs CVE mapping updates for metadata objects.

• MetadataOperations.log: Logs patch blocklisting operations.

• MultiTenancy.log: Logs when tenants are created, updated and deleted on multi-tenant systems.

• OperationsManagerRequests.log: Logs requests sent to Operations Manager.

• P2PRing.log: Logs information about P2P ring system which is used for uploading the status messages from clients.

• Patching.log: Miscellaneous patching-related logs.

• PatchingApprovals.log: Logs when patch approvals are created or updated.

• PatchingStatusCollection.log: Logs receipt of patch statuses from clients and persistence to the database.

• Provisioning.log: Logs server activation via Operations Manager.

• PayloadActivation.log: Logs the arrival of new policy payloads from the server pending activation, including their policy ID, payload ID, and scheduled activation time.

• RelayDetailed.log: Detailed logging for Relay connectivity and Security protocols on HTTP. RelayDetailed are the previous HttpTransport, Security, and Relay logs combined into one file. This includes detailed error messages with stack traces as well as verbose logging for tracing requests end to end.

• RelaySimple.log: Provides an overview of handshakes and HTTP messaging from a more conceptual standpoint. Instead of logging through the train of classes and method executions involved in the process, it is intended simply to say the handshake completed successfully. It can be used to confirm that the system is working as intended, or that something broke and the detailed logs may need digging through.

• RestApiFoundry.log: Logs requests and authentication used by the API Foundry tool.

• SensorOfflineCache.log: This system does scheduled collection of data on clients and uploads diffs to the server.

• SqlDataProvider.log: Logs interactions with the system used to author and execute SQL for dashboards and analytics.

• SQLUploader.log: Logs when payloads of data are sent to the server to be inserted into the database in bulk.

• ThreadInfo.log: Output for logging current thread state information when slm.logthreadstates or slm.log_thread_cpu_info is set to true.

• TwilioSendGrid.log: Logs interactions with third-party APIs for communication providers such as Twilio, SendGrid and Microsoft Teams.

• UserDashboardSubscription.log: Logs export of dashboards to Excel.

• Utils.log: Generic utility logs.

• VulnerabilityManagement.log: Logs receipt and processing of vulnerability data from vulnerability management integrations.

• WebUINotifications.log: Notifications delivered and received from the frontend Web UI.

• WindowsPatching.log: Progress and results of scans and patches for Windows Update and Office365.

• WorkflowStatus.log: Execution status, progress and errors related to workflow invocations.

Server Workflow logs

Default Folder: %ADAPTIVASERVER%\logs\workflowlogs

• <workflowname>-<workflowid>-<sequencenumber>.log: All server and business workflows execution logging.

Client Logs

Location: %ADAPTIVACLIENT%\logs

• adaptiva.err: Records any errors during the running of the AdaptivaClient service.

• adaptiva.log: Records almost all data regarding AdaptivaClient service which is not present in component logs.

• AdaptivaClientValidator.log: Adaptiva client setup validator tool logs.

• AdaptivaNativeUtils.log: AdaptivaClient to windows access logging.

• AdaptivaNativeUtilX.log: AdaptivaClient FIPS cryptography operations using OpenSSL.

• AdaptivaRemoteInstallLog.log: (Intune Edition only) Intune p2p content download initiation from IntuneManagementExtension.

• AdaptivaService.log: AdaptivaClient service start/stop logging.

• AdaptivaServiceRestart.log: AdaptivaServiceRestart.exe logging, used mostly by AdaptivaClient Setup during install or upgrades.

• AdaptivaWindowsUpdateHelper.log: Logs for a helper process which is used in Windows Update patching; includes the process ID and start time of the helper process.

• AdaptiveProtocolTransport.log: AdaptivaClient data transfers using Adaptive Protocol.

• messagingMonitor.log: Logs all message counts.

• OneSiteProvider.log: (OneSite Anywhere or ConfigMgr Edition Only) Logs activity of the ConfigMgr Client and the Adaptiva Client ACP and vice-versa for 32-bit OSes.

• OneSiteProvider64.log: (OneSite Anywhere or ConfigMgr Edition Only) Logs activity of the ConfigMgr Client and the Adaptiva Client ACP and vice-versa for 64-bit OSes.

• revision.properties: Contains the timestamp, git commit id, and full version of the code for this install.

• sqlMonitor.log: All SQL row counts.

• VCDiff.log: Logs about generating differentials between different versions of content.

• VCDiffDecoder.log: Logs about applying differentials between different versions of content.

Client Component Logs

Location: %ADAPTIVACLIENT%\logs\componentlogs

• _SDMErrors.log: Errors related to deployment of patches.

• ActionExec.log: Logs activity for action executions.

• BlobSystem.log: Logs for internal system used for blob downloads.

• BRP2PDownload.log: Byte Range Peer-to-peer download for Windows Update and Microsoft 365 updates. Download related information on a client.

• BRP2PDownloadTrace.log: Specific information about where a byte range is downloaded from, it's either from CDN or from a peer.

• BRP2PRvp.log: Information about a client serving as an RVP in the Byte Range Peer-to-peer system.

• BRP2PUpload.log: Byte Range Peer-to-peer upload for Windows Update and Microsoft 365 updates. Upload related information on a client.

• BRP2PUploadTrace.log: Specific information about which peer a specific byte range block is sent to.

• BulkMessaging.log: Logs activity related to extremely fast new P2P messaging system.

• CacheMigrationClient.log: Records activity of the cache migration tool.

• CHSClient.log: Records activity of the Client health modules.

• ClientInfo.log: Client registration with server and Client IP address in use for communication logging.

• ClientSetupChecks.log: Client setup checks logs.

• ClientUpgrade.log: Client auto upgrade system logs.

• Configuration.log: Client system configurations changes logging.

• ContentCache.log: AdaptivaClient cache state logging.

• ContentDeleter.log: Logs activities of Adaptiva Client content deletion.

• ContentDownload.log: Logs all content downloads.

• ContentLockManager.log: Logs activity related to P2P locking done during content downloads.

• ContentPush.log: Content pre-staging/push logging.

• ContentUnpack.log: Content unpacking logging.

• ContentUpload.log: Content uploads from client to client.

• DeltaSeries.log: Logs download and assembly of delta series content, i.e. content for which an earlier version may already exist locally. Typically useful when monitoring feeds, for which it handles content download before consumption.

• DownloadCompleted.log: Logs all the content download completed details.

• EPH.log: (OneSite Health only) Contains information about the execution of OneSite Health policies on the client side. It logs the various health checks performed as part of the policy, along with the results that are sent back to the server.

• Feeds.log: Logs activity related to feeds. This includes initial receipt, dependency checks, consumption, and removal. Note that feed downloads are handled by the delta series system, and covered more extensively in that log.

• FileDeletion.log: Logs all Adaptiva file deletion requests (non-content).

• GPClient.log: (OneSite WakeUp only) Green Planet client logging.

• HTTP.log: Used to monitor the health of the application's HTTP clients and connection managers.

• HttpTransport.log: Client HTTP transport logs. HttpTransport is used when client binds to Adaptiva Server URL.

• InternetPeer.log: Contains details about communication for an internet client. It can be a pure internet or split internet client. This contains details about behaviors and protocols for internet client.

• Inventory.log: AdaptivaClient inventory collection and reporting logging.

• IPC.log: Logs inter-process communication between AdaptivaClient and other applications.

• LargeMsgTransport.log: Logs related to AdaptiveTransport for messages.

• License.log: Records the status of the client license.

• LinuxPatching.log: (OneSite Patch only) Tracks Linux package scanning, policy evaluation, deployment dependencies and patch pausing.

• Locking.log: General concurrent locking logs.

• MemoryCache.log: Logs related to CachedHashMap.

• MemoryManager.log: Current client memory state and changes logging.

• Messaging.log: Messaging ports start and stop logging.

• MKDCHandler.log: Logs the method in case Adaptiva client needs to stop because of some fatal error.

• NatTraversal.log: Logs details about NAT traversal used for internet peer to peer protocol.

• NetworkLocation.log: Contains details about current network location for this client. It can be one of these (ON_PREMISES,ON_PREMISES_SPLIT,INTERNET,FORCED_TUNNEL_VPN,SPLIT_TUNNEL_VPN,UNKNOWN).

• ObjectDeployment.log: Adaptiva object deployment system logs.

• OEMManager.log: (OneSite WorkspaceONE Edition only) Logs related to 3rdParty OEM integrations.

• Office365.log: Logs Office 365 patch installations.

• OfficeLockManager.log: Logs related to Office level locking used in advanced functions. (e.g. in IntelliStage).

• OneSiteDownload.log: ConfigMgr client ACP invocation and downloads logging.

• OneSitePreCache.log: Content pre-caching logging.

• OperationsManagerRequests.log: Logs operations manager requests send from client.

• P2PDiscovery.log: Logs related to P2P discovery.

• P2PDiscoveryCache.log: Logs information about caching of results for P2P system.

• P2PRing.log: Logs information about P2P ring system which is used for sending status messages from client to server.

• P2PStore.log: Logs related to client’s local P2P store.

• PatchContentDownloader.log: Tracks the of non-Windows patch content, the order in which they are downloaded and the space requirement on disk for each update.

• Patching.log: Scan statuses for patches, metrics scans for patches, maintenance window openings.

• PatchingAdmin.log: Logs administrative actions for patching as observed by the client.

• PatchingPolicyClient.log: Logs the arrival of new or updated patching policies from the server, changes in business unit settings, patch prestaging requests, changes in patch desired states.

• PatchNotifier.log: Displaying and cancelling desktop notifications related to patching (such as reboot notifications).

• PayloadActivation: Logs the arrival of new policy payloads from the server pending activation, including their policy ID, payload ID and scheduled activation time.

• PolicyManager.log: Policy operations and processing logging.

• PXE.log: Records PXE service availability and communication.

• RegIPC.log: Logs activity related to IPC using windows registry.

• RelayDetailed.log: Detailed logging for Relay connectivity and Security protocols on HTTP. RelayDetailed are the previous HttpTransport, Security, and Relay logs combined into one file. This includes detailed error messages with stack traces as well as verbose logging for tracing requests end to end.

• RelaySimple.log: Provides an overview of handshakes and HTTP messaging from a more conceptual standpoint. Instead of logging through the train of classes and method executions involved in the process, it is intended simply to say the handshake completed successfully. It can be used to confirm that the system is working as intended, or that something broke and the detailed logs may need digging through.

• RelayTrackingClient.log: Logs messages requested to route through cloud relay servers for internet clients.

• RelayTrackingServer.log: Logs messages received from cloud relay servers for internet clients.

• RemediationExec.log: (OneSite Health only) Logs related to execution of remediation on the client.

• RemoteWorkflowExecution.log: Logging for remote workflow execution using tool foundry.

• RVPOSDSupporter.log: Records RVP content requests for clients executing OSD.

• RVPState.log: Displays RVP state for the local subnet.

• SCCMClient.log: (OneSite Anywhere or ConfigMgr Edition Only) Records interactions with the local ConfigMgr client.

• SCCMDataUpload.log: (OneSite Anywhere or ConfigMgr Edition Only) ConfigMgr client data upload management logging.

• SCCMPolicyPolling.log: (OneSite Anywhere or ConfigMgr Edition Only) ConfigMgr client policy polling management logging.

• Scheduler.log: AdaptivaClient scheduler.

• Security.log: Records the updating of ACLs.

• SensorExec.log: Execution of various sensors designed to query information about the system, such as installed applications.

• SensorOfflineCache.log: This system does scheduled collection of data on clients and uploads diffs to the server.

• SentRecvMsg.log: Logs all messaging between client-server and client-client.

• ServerLocator.log: Logs activity related to server binding, connectivity.

• SmallMsgTransport.log: Logs related to small UDP messages.

• SoftwareDeploymentManager.log: Logs related to patch deployment, including creation, progress, potential issues which may block the deployment of a patch and the success or failure stages of a patch deployment.

• SoftwareInstaller.log: Logs the status of software installation processes, including whether the installer is busy or its exit status.

• SoftwareRelationshipManager.log: Tracks the status of dependencies and relationships between software components being patched.

• SparseFileSystem.log: Data transferred by the Byte Range Peer-to-peer system is stored in sparse files on each participating clients. This file logs information about the reading and writing of these sparse files.

• SQLAccess.log: Logs local client database activity.

• SQLUploader.log: Logs information about uploading data to client SQL.

• Startup.log: Startup and shutdown logging for AdaptivaClient.

• Telemetry.log: This system handled running on demand queries for client data.

• ThreadInfo.log: Output for logging current thread state information when slm.logthreadstates or slm.log_thread_cpu_info is set to true.

• TFTP.log: Records TFTP communications for boot image file delivery during PXE boot.

• UserPortal.log: Logs for the separate AdaptivaUserPortal Service, which performs user-specific actions such as displaying desktop notifications.

• Utils.log: Generic utility logs.

• VirtualSMP.log: Logs virtual state migration point activities.

• WIFI.log: WiFi office transition logging.

• WindowsPatching.log: Progress and results of scans and patches for Windows Update and Office365.

• WOL.log: Logs related to any Wake On LAN activity.

• WorkflowStatus.log: Execution status, progress and errors related to workflow invocations.

• WorkflowSystem.log: Any workflow related logs.

Client MSI Installation Logs

Location: %ADAPTIVACLIENT%\logs\msiLogs

• <productid>_<download identifier>.log: MSI installation log for a given product and download.

Client Workflow Logs

Location: %ADAPTIVACLIENT%\logs\workflowlogs

• <workflowname>-<workflowid>-<sequencenumber>.log: All client workflows execution logging.