SEG: General MEG Queue Service and Troubleshooting

Mobile Email Gateway (MEG) Queue Service uses Microsoft Message Queuing Services (MSMQs) technology to guarantee message delivery, efficient routing, security, and priority-based messaging. MSMQs enable applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. Applications send messages to queues and read messages from queues. To enable Message Queuing Service on a server, go to Server Manager and click on “Add Feature”. Choose Message Queuing and follow the steps to finish the installation. To view the MEG Queues, go to the Server Manager > Features > Message Queuing > Private Queues for Windows Server 2008 R2; Server Manager>Tools > Computer Management > Services and Applications > Message Queuing > Private Queues for Windows Server 2012.


Windows Server 2008 R2




Windows Server 2012


There are two payloads that AirWatch utilizes in a SEG deployment.

  • AWMegPayload – Used to queue up SEG payloads (i.e. device sync time, device access state as reported by the SEG) from the API server before being saved to the database for dashboard real-time updates
  • AWSegCompliance – Used to queue up compliance evaluations (based on device events) before being sent to the SEG server by the MEG Queue Reader Service

Another important component is MEG Queue Reader Service. It is a Windows Service typically resides on Console & Device servers, and reads from the MSMQs to either save SEG payloads to the database or fire off single-device policy updates to the SEG.

Troubleshooting Any information discrepancy between servers can be caused by the Message Queuing Service.  The discrepancy can manifest into issues such as enrolled device blocked from emails, compliance policy not taking effect, email list view not updating. The following are methods to troubleshoot MEG Queue Service.

  1. Check connectivity between MEG Queue Service and target server. The communication is via port 443. Telnet or view in browser to check connectivity on the port.
  2. Check the queue length of awsegcompliance and awsegfastcompliance. If the queue is backed up, check CPU utilization
  3. Check SSL trust between server. Check CAPI2 logs on Windows Server Manager.
  4. Verbose MEG Queue Service log and check the errors.


Sample Log Entries

AW.Meg.Queue.Service.Util.EndpointQueueManager.Process             A message is added to the queue for endpoint 'FastTracked:noEndpointNeeded', for MemConfig Id: '1'.      

2016/01/15 19:21:33.205        SEINT01BLANK      d17d5e1c-ba7b-4654-8d7b-e8f6ed469214            [0000000-0000000]   (7)          Debug                AW.Meg.Queue.Service.Util.EndpointQueueManager._SplitByType     Received 'DeviceStateChangePayload' message.  MemConfig Id: '1', Device Id: '2', StateChangeType: 'Delete'        

2016/01/15 19:21:33.206        SEINT01BLANK      d17d5e1c-ba7b-4654-8d7b-e8f6ed469214            [0000000-0000000]   (7)          Info                 AW.Meg.Queue.Service.DeviceStateChangedHandler.DeviceStateChangedFactory._LoadSecureEmailSettings Mobile Email Settings for MemConfig: '1', Type: '4', Bypass Mode: 'False'    

2016/01/15 19:21:33.207        SEINT01BLANK      d17d5e1c-ba7b-4654-8d7b-e8f6ed469214            [0000000-0000000]   (7)          Debug                AW.Meg.Queue.Service.DeviceStateChangedHandler.DeviceStateChangedFactory.GetHandler        Using GatewayDeviceStateChangedHandler. MemConfig: '1'         

2016/01/15 19:21:33.207        SEINT01BLANK      d17d5e1c-ba7b-4654-8d7b-e8f6ed469214            [0000000-0000000]   (7)          Debug                AW.Meg.Queue.Service.Util.EndpointQueueManager._ReceiveDeviceStateChangePayload               Updating device state. MemConfig Id '1', Device Id: '2'     

2016/01/15 19:21:33.207        SEINT01BLANK      d17d5e1c-ba7b-4654-8d7b-e8f6ed469214            [0000000-0000000]   (7)          Debug                AW.Meg.Queue.Service.DeviceStateChangedHandler.GatewayDeviceStateChangedHandler.UpdateDeviceState             Update device state change for location group 570, which uses native SEG.

2016/01/15 19:21:33.207        SEINT01BLANK      d17d5e1c-ba7b-4654-8d7b-e8f6ed469214            [0000000-0000000]   (7)          Debug                AW.Meg.Queue.Service.Processors.GatewayDeviceStateChangedProcessor.DoProcess   Processing 'Delete' event for LG '570', Device Id: '2', MEM Config Id: '1'       

2016/01/15 19:21:33.321        SEINT01BLANK      d17d5e1c-ba7b-4654-8d7b-e8f6ed469214            [0000000-0000000]   (7)          Debug                AW.Meg.Queue.Service.Processors.GatewayDeviceStateChangedProcessor._RemoveDevicePolicy Removing device policy from SEG.  Device Id: '2', LG: '570', MEMConfigId: '1'.  

2016/01/15 19:21:33.330        SEINT01BLANK      d17d5e1c-ba7b-4654-8d7b-e8f6ed469214            [0000000-0000000]   (7)          Debug                AW.Meg.Queue.Service.Processors.GatewayDeviceStateChangedProcessor._RemoveDevicePolicy Device policy removed successfully.  Device Id: '2', LG: '570', MEMConfigId: '1'.      


Have more questions? Submit a request


Article is closed for comments.