2
Activesync logging repeated error
Problem reported by Matthew Titley - 7/25/2016 at 8:35 AM
Submitted
Hi all,
 
I don't expect that I'll get much of a response as this seems more like a ticket issue but I'll give it a go here first. In my SM daily activeSync.log I'm seeing this error with a frequency of every two seconds or greater!
 
07:52:29 [626763109] SYNC KEY MISMATCH: Device=[20160715.135912.3425] Server=[20160715.135924.3426]
07:52:29 System.NullReferenceException: Object reference not set to an instance of an object.
   at MailService.Protocols.ActiveSync.Helpers.SyncBase.#D2j(String #E2j, String #uZi, String #cue, Boolean #ysd)
   at MailService.Protocols.ActiveSync.Helpers.SyncBase.PerformSync(Int32 allowedChanges, Boolean& requiresImmediateResponse, Boolean& saveLastSyncRequest)
   at MailService.Protocols.ActiveSync.Commands.Sync.Execute()
   at MailService.Protocols.ActiveSync.VersionSpecific.VersionHandlerBase.ProcessCommand()
   at MailService.Protocols.ActiveSync.ActiveSyncProcessor.ProcessCommand(EasCommandRequest request)
07:52:31 [626763111] SYNC KEY MISMATCH: Device=[20160715.135912.3425] Server=[20160715.135924.3426]
07:52:31 System.NullReferenceException: Object reference not set to an instance of an object.
   at MailService.Protocols.ActiveSync.Helpers.SyncBase.#D2j(String #E2j, String #uZi, String #cue, Boolean #ysd)
   at MailService.Protocols.ActiveSync.Helpers.SyncBase.PerformSync(Int32 allowedChanges, Boolean& requiresImmediateResponse, Boolean& saveLastSyncRequest)
   at MailService.Protocols.ActiveSync.Commands.Sync.Execute()
   at MailService.Protocols.ActiveSync.VersionSpecific.VersionHandlerBase.ProcessCommand()
   at MailService.Protocols.ActiveSync.ActiveSyncProcessor.ProcessCommand(EasCommandRequest request)
 
I enabled an ActiveSync subscription a few weeks ago but didn't reboot the mail server for any maintenance reasons until last night. After the reboot, I now have a daily 'activesync.log' file in my log folder. This didn't exist prior to the reboot. Anyone have any ideas of what this means or how I troubleshoot? I'm on 14.4.5801. 

2 Replies

Reply to Thread
0
Employee Replied
Employee Post
Hi Matthew.  I believe upgrading will fix this, as this was in the release notes for SmarterMail 14.5.
 
  • Fixed: A scenario in Exchange ActiveSync where a sync key mismatch could cause a null reference exception to occur which prevents a proper response to the client.
0
Matthew Titley Replied
Thanks, I'll get on that at the next maintenance window. Maybe I should just skip and go right to the latest 15.x.

Reply to Thread