I’ve checked on a few PCs that the file name is correct and the file exists. Setting “_BESClient_ArchiveManager_MaxArchiveSize”=“50000000” on “” for clientĬommand succeeded setting “_BESClient_ArchiveManager_MaxArchiveSize”=“50000000” on “Wed, 18:00:02 +0000” for client (fixlet 23122)Ĭommand succeeded setting “_BESClient_ArchiveManager_OperatingMode”=“2” on “Wed, 18:00:02 +0000” for client (fixlet 23122)Ĭommand succeeded setting “_BESClient_ArchiveManager_FileSet-CST_SW3”=“C:\Support\SWI\swi3_CAN元AA_7676767.gz” on “Wed, 18:00:02 +0000” for client (fixlet 23122)Ĭommand succeeded setting “_BESClient_ArchiveManager_SendAll”=“1” on “Wed, 18:00:02 +0000” for client (fixlet 23122)Ĭommand failed (Unable to archive now failure while building archive: class ArchiveManagerBuildArchiveError) archive now (fixlet 23122)ĪctionLogMessage: (action 23122 ) ending action Checking on a few, I’m seeing that the last successful archive for these computers happened at different points between April and June. The console log shows that the “archive now” command is failing on around 5% of PCs. I have a recurring task that has been running for a year, but I’ve started seeing failures recently with the archiving part of it, which is the last line in the action.
