Hey Scarab. This might be a conversion of the statistics files taking place. Have you checked back since then to see if they sorted themselves out? The archival issues sounds like it may be locked files - do you see any file access in that directory outside of SM/IIS?

Kyle,

The \Archives\Current did eventually get indexed, compressed, and moved to \Archive\Indexed. Apparently the timer for that function is exactly 12:00 AM, so if it is missed one day it completes the next time that function fires.

The SysAdmin reports issue is still persisting. The \Smartermail\Service\Settings\Stats\2021.12.stat4 hasn't updated since before the migration (it still has a Date Modified of 12/9/2021 12:19 PM and was migrated on 12/10/2021 at 11:59 PM). Whereas the \Smartermail\Domains\%domain.tld%\Stats\%username%\2021.12.stat4 have been updating, which would explain why Domain & User Reports are still running fine. I have verified permissions, made sure that it isn't locked or in use. I compared the file with the one from Build 7887 that worked and a diff shows the files are identical. If I remove the file the SysAdmin reports still won't load but then give a different error:

angular-v-100.0.7957.24844.8d98f5c6726e000.js:15638 TypeError: Cannot read properties of undefined (reading 'updateValue')
    at site-v-100.0.7957.24844.8d98f5c6726e000.js:57
    at Array.forEach (<anonymous>)
    at site-v-100.0.7957.24844.8d98f5c6726e000.js:57
    at Scope.$digest (angular-v-100.0.7957.24844.8d98f5c6726e000.js:19183)
    at Scope.$apply (angular-v-100.0.7957.24844.8d98f5c6726e000.js:19571)
    at angular-v-100.0.7957.24844.8d98f5c6726e000.js:21672
    at TaskTracker.completeTask (angular-v-100.0.7957.24844.8d98f5c6726e000.js:21302)
    at angular-v-100.0.7957.24844.8d98f5c6726e000.js:6882

So, from what I can surmise it appears that the problem is the 2021.12.stat4 file. It would appear that the \SmarterMail\Service\Settings\Stats updates for the previous day but unlike other triggers if the Service Stats miss their update timer they are not updated the next time that timer fires. (And if that is the case Reports will probably automagically start working on January 2nd, 2022.)

Is there any way to force an update of the 2021.12.stat4 file?

Just to let you know that Build 8025 resolved the issue with our corrupted stat4 file and Admin Reports are now able to load without an error just sans the data for how long the file was corrupted. It properly shows data before and after the corruption.

That is great news, glad to hear it!