Help with Error Logs
Question asked by kevind - 5/11/2023 at 3:29 PM
Hello, looking for help on these error logs. In Build 8451 - 2/20/23, I go to Troubleshooting -> View Logs -> Type = Error.  The same thing shows up every day (admin@domain.x is an actual account on server).

Is it a hacker, bad account, etc.? There are about 25 more lines that I didn't copy.  Then the whole thing repeats again every 30 minutes or so. Thanks in Advance!

[2023.05.01] 00:21:29.445 [admin@domain.x] Password encrypted is null: admin@domain.x--not writing file
[2023.05.01] 00:21:29.492 [admin@domain.x]    at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
[2023.05.01]    at System.Environment.get_StackTrace()
[2023.05.01]    at MailService.Repositories.UserRepository.UserSettingsSaveFile(UserSettingsFile file)
[2023.05.01]    at MailService.Repositories.UserRepository.ApplyUserSettingsFileChanges(Func`2 changesToMakeShouldSave)
[2023.05.01]    at MailService.Protocols.EWS.OperationHelper.OldFileCleanUpForUsers(User user, Int32& userCount, Boolean& changed)
[2023.05.01]    at MailService.Protocols.EWS.OperationHelper.OldFileCleanUpForDomainsAndUsers(Int32& domainCount, Int32& userCount, Boolean& changed)
[2023.05.01]    at MailService.Protocols.EWS.OperationHelper.<EwsOldFileCleanUp>d__43.MoveNext()
[2023.05.01]    at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
[2023.05.01]    at MailService.Protocols.EWS.OperationHelper.EwsOldFileCleanUp()
[2023.05.01]    at MailService.Core.MailServer.<>c.<<DayChanged>b__163_0>d.MoveNext()

2 Replies

Reply to Thread
Matt Petty Replied
Employee Post
We've got safety checks that we do right before saving the file to ensure we aren't saving bad data. In this case we were about to save the user with a blank password, which would cause the user to break. This error is that safety check kicking in and it reports where in the code the issue likely came from. I would make a new ticket and send this stacktrace and maybe a copy of the config file. 
The good news is that the user should not be broken as we DIDNT save the file to disk, but the bad news it appears there is a bug attempting to clearing data on a user. 
Matt Petty
Software Developer
SmarterTools Inc.
(877) 357-6278
kevind Replied
Yes, this account had no password. So we entered one to see if that eliminates the errors.

Thanks and have a nice weekend!

Reply to Thread