API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jan 10th, 2019
374
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 259.33 KB | None | 0 0
raw download clone embed print report
  1. 2019-01-10 09:06:25 I #4948 UdatrUI START
  2. 2019-01-10 09:06:25 I #4948 UdatrUI No previous instance found
  3. 2019-01-10 09:06:25 I #4948 UdatrUI >>>> Operation Result : The operation completed successfully.
  4.  
  5. 2019-01-10 09:06:25 I #4948 UdatrUI (0)
  6. 2019-01-10 09:06:25 I #4948 msgbus starting msgbus i/o thread...
  7. 2019-01-10 09:06:25 I #4948 msgbus Ok, started msgbus i/o thread, waiting for thread to complete initialization...
  8. 2019-01-10 09:06:25 I #2864 loop_worker Created name pipe
  9. 2019-01-10 09:06:25 I #2864 loop_worker Opened named pipe
  10. 2019-01-10 09:06:25 I #2864 loop_worker Loop worker started
  11. 2019-01-10 09:06:25 I #2864 msgbus Configuring auth info from db = <C:\ProgramData\McAfee\Agent\\db\msgbus.db>
  12. 2019-01-10 09:06:25 I #2864 msgbus Added file watcher on broker config file <C:\ProgramData\McAfee\Agent\msgbus\config.ini>
  13. 2019-01-10 09:06:25 I #4948 msgbus i/o thread initialization complete, bus now running
  14. 2019-01-10 09:06:25 I #4948 msgbus Subscriber <00E2B330> created
  15. 2019-01-10 09:06:25 I #4948 msgbus Subscriber <(null)> set option: <0x10004>, return value: <0>
  16. 2019-01-10 09:06:25 I #4948 msgbus Subscriber <(null)> set option: <0x10002>, return value: <0>
  17. 2019-01-10 09:06:25 I #4948 msgbus Submitting loop worker request to subscribe topic filter <ma.*>
  18. 2019-01-10 09:06:25 I #4948 loop_worker scheduled an async work request, now has 1 pending work requests
  19. 2019-01-10 09:06:25 I #2864 msgbus Subscribing topic filter <ma.*>
  20. 2019-01-10 09:06:25 I #2864 msgbus Subscriber <ma.*> Registration
  21. 2019-01-10 09:06:25 I #4948 ma_client ma client is started.
  22. 2019-01-10 09:06:25 I #4948 ma_client Adding ma.client.policy.EPOAGENT3000 to client manager.
  23. 2019-01-10 09:06:25 I #2864 msgbus Message created for Registration of <ma.*> subscriber
  24. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> creation successful, reachability: <0>, timeout: <5000>, priority: <0>, thread model: <0>
  25. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> option <0x10002> set, return value is <0>
  26. 2019-01-10 09:06:25 I #2864 msgbus <ma.msgbus.pubsub_service.service> service is not available in router
  27. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> option <0x10004> set, return value is <0>
  28. 2019-01-10 09:06:25 I #2864 msgbus Service <ma.msgbus.pubsub_service.service> not found in local search and reachability is <1>
  29. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy>, sync send call
  30. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> option <0x10004> set, return value is <0>
  31. 2019-01-10 09:06:25 I #2864 msgbus <ma.msgbus.pubsub_service.service> service lookup start, ep lookup <00E2D5F8>
  32. 2019-01-10 09:06:25 I #4948 msgbus Messagebus Request object Created
  33. 2019-01-10 09:06:25 I #4948 loop_worker scheduled an async work request, now has 1 pending work requests
  34. 2019-01-10 09:06:25 I #2864 msgbus Resolving broker services connection, broker pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  35. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> succeessfully submitted request to loop worker
  36. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy>, submitted loop worker request for sync send
  37. 2019-01-10 09:06:25 I #2864 msgbus searching named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> in connection manager
  38. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy>, waiting for loop worker sync request acknowledgement...
  39. 2019-01-10 09:06:25 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> not found in connection manager
  40. 2019-01-10 09:06:25 I #2864 msgbus connecting to named pipe....
  41. 2019-01-10 09:06:25 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> is added into connection manager
  42. 2019-01-10 09:06:25 I #2864 msgbus set consumer in named pipe connection
  43. 2019-01-10 09:06:25 I #2864 msgbus named pipe connect succeeded
  44. 2019-01-10 09:06:25 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <00E2D5F8>
  45. 2019-01-10 09:06:25 I #2864 msgbus uv timer data(00E2D2E0)
  46. 2019-01-10 09:06:25 I #2864 msgbus
  47. 2019-01-10 09:06:25 I #2864 loop_worker loop worker successfully processed a message, still 0 more to go...
  48. 2019-01-10 09:06:25 I #2864 msgbus Adding received message into queue
  49. 2019-01-10 09:06:25 I #2864 msgbus Local broker lookup cb received status <0>
  50. 2019-01-10 09:06:25 I #2864 msgbus Local broker lookup cb execution on service/subscriber <ma.*> registration
  51. 2019-01-10 09:06:25 I #2864 msgbus Name pipe connection callback with status <0>
  52. 2019-01-10 09:06:25 I #2864 msgbus Received secure credentials for peer pipe handle=<600>, pid=<5880>.
  53. 2019-01-10 09:06:25 I #2864 msgbus Opening msgbus DB in read only mode
  54. 2019-01-10 09:06:25 I #2864 crypto Using C:\ProgramData\McAfee\Agent\\keystore as keystore path
  55. 2019-01-10 09:06:25 I #2864 crypto Using C:\ProgramData\McAfee\Agent\\certstore as certstore path
  56. 2019-01-10 09:06:25 I #2864 crypto Using C:\ProgramData\McAfee\Agent\\crlstore as crlstore path
  57. 2019-01-10 09:06:25 I #2864 crypto Using C:\Program Files\McAfee\Agent\x86\ as crypto lib path
  58. 2019-01-10 09:06:25 I #2864 crypto RSA version : 4.0.1.0
  59. 2019-01-10 09:06:25 I #2864 crypto RSA crypto role : User Role
  60. 2019-01-10 09:06:25 I #2864 crypto RSA crypto mode : FIPS Mode
  61. 2019-01-10 09:06:25 I #2864 crypto RSA rand algo : HMAC Random
  62. 2019-01-10 09:06:25 I #2864 crypto RSA self test : passed
  63. 2019-01-10 09:06:25 I #2864 crypto Successfully initialized crypto library
  64. 2019-01-10 09:06:25 I #2864 msgbus created crypto object successfully
  65. 2019-01-10 09:06:25 I #2864 msgbus Successfully get trust level of pid <5880> , truest level : <1>
  66. 2019-01-10 09:06:25 I #2864 msgbus Allowing <5880> onto msgbus
  67. 2019-01-10 09:06:25 I #2864 msgbus Get the peer SID from the local trust store
  68. 2019-01-10 09:06:25 I #2864 msgbus Opening msgbus DB in read only mode
  69. 2019-01-10 09:06:25 I #2864 msgbus Successfully get sid of pid <5880> from trust store, sid : <S-1-5-18>
  70. 2019-01-10 09:06:25 I #2864 msgbus peer sid is <S-1-5-18>
  71. 2019-01-10 09:06:25 I #2864 msgbus setting the the sid object retrieved from the database
  72. 2019-01-10 09:06:25 I #2864 msgbus uv timer data(00E2DC60)
  73. 2019-01-10 09:06:25 I #2864 msgbus
  74. 2019-01-10 09:06:25 I #2864 msgbus named pipe authentication started.
  75. 2019-01-10 09:06:25 I #2864 msgbus uv timer data(00E2D6E0)
  76. 2019-01-10 09:06:25 I #2864 msgbus
  77. 2019-01-10 09:06:25 I #2864 msgbus <ma.service.policy> service is not available in router
  78. 2019-01-10 09:06:25 I #2864 msgbus Service <ma.service.policy> not found in local search and reachability is <1>
  79. 2019-01-10 09:06:25 I #2864 msgbus <ma.service.policy> service lookup start, ep lookup <02E6CCE0>
  80. 2019-01-10 09:06:25 I #2864 msgbus resolve request message created source name <ma.ep.lookup.internal.0000086C.1> for service <ma.service.policy>
  81. 2019-01-10 09:06:25 I #2864 msgbus Searching broker consumer and sending the service <ma.service.policy> resolve request to name service
  82. 2019-01-10 09:06:25 I #2864 msgbus Calling lookup callback in async way with status <516> from ep lookup <02E6CCE0>
  83. 2019-01-10 09:06:25 I #2864 msgbus uv timer data(02E7E9A8)
  84. 2019-01-10 09:06:25 I #2864 msgbus
  85. 2019-01-10 09:06:25 I #2864 msgbus <ma.msgbus.name_service.service> service is not available in router
  86. 2019-01-10 09:06:25 I #2864 msgbus Service <ma.msgbus.name_service.service> not found in local search and reachability is <1>
  87. 2019-01-10 09:06:25 I #2864 msgbus <ma.msgbus.name_service.service> service lookup start, ep lookup <02E71890>
  88. 2019-01-10 09:06:25 I #2864 msgbus Resolving broker services connection, broker pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  89. 2019-01-10 09:06:25 I #2864 msgbus searching named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> in connection manager
  90. 2019-01-10 09:06:25 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> found in connection manager
  91. 2019-01-10 09:06:25 I #2864 msgbus named pipe connection is already available in named pipe connection manager
  92. 2019-01-10 09:06:25 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E71890>
  93. 2019-01-10 09:06:25 I #2864 msgbus uv timer data(02E7E948)
  94. 2019-01-10 09:06:25 I #2864 msgbus
  95. 2019-01-10 09:06:25 I #2864 msgbus local broker look up succeeded for service <ma.service.policy> and started timer with timeout <20000> for request <00E2D6E0>
  96. 2019-01-10 09:06:25 I #2864 msgbus Added request object <00E2D6E0> into request manager
  97. 2019-01-10 09:06:25 I #2864 msgbus Endpoint <ma.service.policy> request successfully initiated
  98. 2019-01-10 09:06:25 I #2864 loop_worker loop worker successfully processed a message, still 0 more to go...
  99. 2019-01-10 09:06:25 I #2864 msgbus on_server_authenticate_cb callback called with status <0>.
  100. 2019-01-10 09:06:25 I #2864 msgbus on_server_authenticate_cb secure pid <5880>.
  101. 2019-01-10 09:06:25 I #2864 msgbus Sending pid <2156>
  102. 2019-01-10 09:06:25 I #2864 msgbus Sending data on connected name pipe
  103. 2019-01-10 09:06:25 I #2864 msgbus named pipe connection authenticated
  104. 2019-01-10 09:06:25 I #2864 msgbus Status from connect callback <0>
  105. 2019-01-10 09:06:25 I #2864 msgbus Connection Established
  106. 2019-01-10 09:06:25 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> start receiving...
  107. 2019-01-10 09:06:25 I #2864 msgbus Sending pending messages..
  108. 2019-01-10 09:06:25 I #2864 msgbus Message bus request <00E2D6E0> lookup cb is invoked with status <516> from ep lookup <02E6CCE0>
  109. 2019-01-10 09:06:25 I #2864 msgbus Received broker consumer, sending service <ma.service.policy> pipe name request msg
  110. 2019-01-10 09:06:25 I #2864 msgbus Adding received message into queue
  111. 2019-01-10 09:06:25 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  112. 2019-01-10 09:06:25 I #2864 msgbus Received 5 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  113. 2019-01-10 09:06:25 I #2864 msgbus received peer process pid <5880> via message
  114. 2019-01-10 09:06:25 I #2864 msgbus Sending data on connected name pipe
  115. 2019-01-10 09:06:25 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  116. 2019-01-10 09:06:25 I #2864 msgbus Sending data on connected name pipe
  117. 2019-01-10 09:06:25 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  118. 2019-01-10 09:06:25 I #2864 msgbus Received 245 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  119. 2019-01-10 09:06:25 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  120. 2019-01-10 09:06:25 I #2864 msgbus Received response from broker with status <0>
  121. 2019-01-10 09:06:25 I #2864 msgbus Received response type <prop.value.register_subscriber_request> from broker
  122. 2019-01-10 09:06:25 I #2864 msgbus Not expecting any content in reply from broker for register and unregister requests
  123. 2019-01-10 09:06:25 I #2864 msgbus Received 366 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  124. 2019-01-10 09:06:25 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  125. 2019-01-10 09:06:25 I #2864 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
  126. 2019-01-10 09:06:25 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  127. 2019-01-10 09:06:25 I #2864 msgbus Received 460 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  128. 2019-01-10 09:06:25 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  129. 2019-01-10 09:06:25 I #2864 msgbus Recevied response from broker with status <0>
  130. 2019-01-10 09:06:25 I #528 msgbus Subscriber now invoking handler...
  131. 2019-01-10 09:06:25 I #2864 msgbus Recevied response type <prop.value.discover_service_request> from broker
  132. 2019-01-10 09:06:25 I #2864 msgbus Recevied info from broker, service name: <ma.service.policy>
  133. 2019-01-10 09:06:25 I #2864 msgbus pipe name: <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  134. 2019-01-10 09:06:25 I #2864 msgbus pid : <5880>
  135. 2019-01-10 09:06:25 I #2864 msgbus ep lookup <02E71890> stop, connection status recevied <No> ref count <3>
  136. 2019-01-10 09:06:25 I #2864 msgbus searching named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> in connection manager
  137. 2019-01-10 09:06:25 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> found in connection manager
  138. 2019-01-10 09:06:25 I #2864 msgbus named pipe connection is already available in named pipe connection manager
  139. 2019-01-10 09:06:25 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E6CCE0>
  140. 2019-01-10 09:06:25 I #2864 msgbus uv timer data(02E7E908)
  141. 2019-01-10 09:06:25 I #2864 msgbus
  142. 2019-01-10 09:06:25 I #2864 msgbus Message bus request <00E2D6E0> lookup cb is invoked with status <0> from ep lookup <02E6CCE0>
  143. 2019-01-10 09:06:25 I #2864 msgbus Sending message to router - correlation id <1> ephemeral name buffer <ma.internal.request.0000086C.1>
  144. 2019-01-10 09:06:25 I #2864 msgbus Adding received message into queue
  145. 2019-01-10 09:06:25 I #2864 msgbus Sending data on connected name pipe
  146. 2019-01-10 09:06:25 I #2864 msgbus After Worker callback is Invoked in Subscriber
  147. 2019-01-10 09:06:25 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  148. 2019-01-10 09:06:25 I #2864 msgbus Received 7588 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  149. 2019-01-10 09:06:25 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  150. 2019-01-10 09:06:25 I #2864 msgbus Recevied expected response to message bus request
  151. 2019-01-10 09:06:25 I #2864 msgbus message bus request Released
  152. 2019-01-10 09:06:25 I #2864 msgbus Invoking user callback in I/O thread
  153. 2019-01-10 09:06:25 I #2864 msgbus Endpoint <ma.service.policy>, sync send callback invoked
  154. 2019-01-10 09:06:25 I #2864 msgbus ep lookup <02E6CCE0> stop, connection status recevied <No> ref count <3>
  155. 2019-01-10 09:06:25 I #4948 msgbus message bus request Released
  156. 2019-01-10 09:06:25 I #2864 msgbus Request Object Closes
  157. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> release
  158. 2019-01-10 09:06:25 I #2864 msgbus message bus request Released
  159. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Enforcing UI policies
  160. 2019-01-10 09:06:25 I #2864 msgbus Messagebus Request object Destroys
  161. 2019-01-10 09:06:25 I #2864 msgbus Endpoint <ma.service.policy> release
  162. 2019-01-10 09:06:25 I #2864 msgbus Endpoint <ma.service.policy> destroys
  163. 2019-01-10 09:06:25 I #4948 UpdaterUIModule AgentMode = 1
  164. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Show Agent UI: 1
  165. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Allow Security Update: 1
  166. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Language from policy : 0000
  167. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> creation successful, reachability: <0>, timeout: <5000>, priority: <0>, thread model: <0>
  168. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> option <0x10002> set, return value is <0>
  169. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> option <0x10004> set, return value is <0>
  170. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy>, sync send call
  171. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> option <0x10004> set, return value is <0>
  172. 2019-01-10 09:06:25 I #4948 msgbus Messagebus Request object Created
  173. 2019-01-10 09:06:25 I #4948 loop_worker scheduled an async work request, now has 1 pending work requests
  174. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> succeessfully submitted request to loop worker
  175. 2019-01-10 09:06:25 I #2864 msgbus uv timer data(00E2D6E0)
  176. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy>, submitted loop worker request for sync send
  177. 2019-01-10 09:06:25 I #2864 msgbus
  178. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy>, waiting for loop worker sync request acknowledgement...
  179. 2019-01-10 09:06:25 I #2864 msgbus <ma.service.policy> service found in router
  180. 2019-01-10 09:06:25 I #2864 msgbus Service <ma.service.policy> found in local search and status of ep lookup is <2>
  181. 2019-01-10 09:06:25 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E6CCE0>
  182. 2019-01-10 09:06:25 I #2864 msgbus uv timer data(02E5BE60)
  183. 2019-01-10 09:06:25 I #2864 msgbus
  184. 2019-01-10 09:06:25 I #2864 msgbus local broker look up succeeded for service <ma.service.policy> and started timer with timeout <20000> for request <00E2D6E0>
  185. 2019-01-10 09:06:25 I #2864 msgbus Added request object <00E2D6E0> into request manager
  186. 2019-01-10 09:06:25 I #2864 msgbus Endpoint <ma.service.policy> request successfully initiated
  187. 2019-01-10 09:06:25 I #2864 loop_worker loop worker successfully processed a message, still 0 more to go...
  188. 2019-01-10 09:06:25 I #2864 msgbus Message bus request <00E2D6E0> lookup cb is invoked with status <0> from ep lookup <02E6CCE0>
  189. 2019-01-10 09:06:25 I #2864 msgbus Sending message to router - correlation id <2> ephemeral name buffer <ma.internal.request.0000086C.2>
  190. 2019-01-10 09:06:25 I #2864 msgbus Adding received message into queue
  191. 2019-01-10 09:06:25 I #2864 msgbus Sending data on connected name pipe
  192. 2019-01-10 09:06:25 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  193. 2019-01-10 09:06:25 I #2864 msgbus Received 7588 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  194. 2019-01-10 09:06:25 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  195. 2019-01-10 09:06:25 I #2864 msgbus Recevied expected response to message bus request
  196. 2019-01-10 09:06:25 I #2864 msgbus message bus request Released
  197. 2019-01-10 09:06:25 I #2864 msgbus Invoking user callback in I/O thread
  198. 2019-01-10 09:06:25 I #2864 msgbus Endpoint <ma.service.policy>, sync send callback invoked
  199. 2019-01-10 09:06:25 I #2864 msgbus ep lookup <02E6CCE0> stop, connection status recevied <No> ref count <3>
  200. 2019-01-10 09:06:25 I #2864 msgbus Request Object Closes
  201. 2019-01-10 09:06:25 I #4948 msgbus message bus request Released
  202. 2019-01-10 09:06:25 I #2864 msgbus message bus request Released
  203. 2019-01-10 09:06:25 I #4948 msgbus Endpoint <ma.service.policy> release
  204. 2019-01-10 09:06:25 I #2864 msgbus Messagebus Request object Destroys
  205. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Enforcing UI policies
  206. 2019-01-10 09:06:25 I #4948 UpdaterUIModule AgentMode = 1
  207. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Show Agent UI: 1
  208. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Allow Security Update: 1
  209. 2019-01-10 09:06:25 I #2864 msgbus Endpoint <ma.service.policy> release
  210. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Language from policy : 0000
  211. 2019-01-10 09:06:25 I #2864 msgbus Endpoint <ma.service.policy> destroys
  212. 2019-01-10 09:06:25 I #4948 Main Allow McTray to be launched in RDP : False
  213. 2019-01-10 09:06:25 I #4948 Cmalib The environment variable SESSIONNAME = RDP-Tcp#4
  214. 2019-01-10 09:06:25 I #4948 Main Updater UI launch conditionTrue
  215. 2019-01-10 09:06:25 I #4948 Cmalib The environment variable SESSIONNAME = RDP-Tcp#4
  216. 2019-01-10 09:06:25 I #4948 Cmalib The environment variable SESSIONNAME = RDP-Tcp#4
  217. 2019-01-10 09:06:25 I #4948 UpdaterUIModule AgentMode = 1
  218. 2019-01-10 09:06:25 I #4948 UpdaterUIModule AgentMode = 1
  219. 2019-01-10 09:06:25 I #4948 UpdaterUI Allow Update Security option State = 1
  220. 2019-01-10 09:06:25 I #4948 UpdaterUI McTray seems to be already launched before updater ui. Determining whether to block shutdown
  221. 2019-01-10 09:06:25 I #4948 UpdaterUI Deployment Status 0
  222. 2019-01-10 09:06:25 I #4948 msgbus Subscriber <02E6F238> created
  223. 2019-01-10 09:06:25 I #4948 msgbus Subscriber <(null)> set option: <0x10002>, return value: <0>
  224. 2019-01-10 09:06:25 I #4948 msgbus Subscriber <(null)> set option: <0x10004>, return value: <0>
  225. 2019-01-10 09:06:25 I #4948 msgbus Submitting loop worker request to subscribe topic filter <ma.logger.msg.pub.topic>
  226. 2019-01-10 09:06:25 I #4948 loop_worker scheduled an async work request, now has 1 pending work requests
  227. 2019-01-10 09:06:25 I #2864 msgbus Subscribing topic filter <ma.logger.msg.pub.topic>
  228. 2019-01-10 09:06:25 I #2864 msgbus Subscriber <ma.logger.msg.pub.topic> Registration
  229. 2019-01-10 09:06:25 I #2864 msgbus Message created for Registration of <ma.logger.msg.pub.topic> subscriber
  230. 2019-01-10 09:06:25 I #2864 msgbus <ma.msgbus.pubsub_service.service> service found in router
  231. 2019-01-10 09:06:25 I #2864 msgbus Service <ma.msgbus.pubsub_service.service> found in local search and status of ep lookup is <2>
  232. 2019-01-10 09:06:25 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <00E2D5F8>
  233. 2019-01-10 09:06:25 I #2864 msgbus uv timer data(02EA5580)
  234. 2019-01-10 09:06:25 I #2864 msgbus
  235. 2019-01-10 09:06:25 I #2864 loop_worker loop worker successfully processed a message, still 0 more to go...
  236. 2019-01-10 09:06:25 I #2864 msgbus Adding received message into queue
  237. 2019-01-10 09:06:25 I #2864 msgbus Sending data on connected name pipe
  238. 2019-01-10 09:06:25 I #2864 msgbus Local broker lookup cb received status <0>
  239. 2019-01-10 09:06:25 I #2864 msgbus Local broker lookup cb execution on service/subscriber <ma.logger.msg.pub.topic> registration
  240. 2019-01-10 09:06:25 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  241. 2019-01-10 09:06:25 I #2864 msgbus Received 245 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  242. 2019-01-10 09:06:25 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  243. 2019-01-10 09:06:25 I #2864 msgbus Received response from broker with status <0>
  244. 2019-01-10 09:06:25 I #2864 msgbus Received response type <prop.value.register_subscriber_request> from broker
  245. 2019-01-10 09:06:25 I #2864 msgbus Not expecting any content in reply from broker for register and unregister requests
  246. 2019-01-10 09:06:25 I #2864 msgbus Received 385 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  247. 2019-01-10 09:06:25 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  248. 2019-01-10 09:06:25 I #2864 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
  249. 2019-01-10 09:06:25 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  250. 2019-01-10 09:06:25 I #3000 msgbus Subscriber now invoking handler...
  251. 2019-01-10 09:06:25 I #2864 msgbus After Worker callback is Invoked in Subscriber
  252. 2019-01-10 09:06:25 I #4948 msgbus msgbus server <ma.service.updater.uiprovider.EPOAGENT3000.2.0> succesfully created
  253. 2019-01-10 09:06:25 I #4948 msgbus Server <ma.service.updater.uiprovider.EPOAGENT3000.2.0>: <0x10004> option set, return value is <0>
  254. 2019-01-10 09:06:25 I #4948 msgbus Server <ma.service.updater.uiprovider.EPOAGENT3000.2.0>: <0x10002> option set, return value is <0>
  255. 2019-01-10 09:06:25 I #4948 msgbus Submitting async loop work item to register the server <ma.service.updater.uiprovider.EPOAGENT3000.2.0>
  256. 2019-01-10 09:06:25 I #2864 msgbus Registering server <ma.service.updater.uiprovider.EPOAGENT3000.2.0>
  257. 2019-01-10 09:06:25 I #2864 msgbus Service <ma.service.updater.uiprovider.EPOAGENT3000.2.0> Registration
  258. 2019-01-10 09:06:25 I #4948 loop_worker scheduled an async work request, now has 1 pending work requests
  259. 2019-01-10 09:06:25 I #4948 ma_client Adding ma.service.updater.uiprovider.EPOAGENT3000.2.0 to client manager.
  260. 2019-01-10 09:06:25 I #4948 UdatrUI McTray installed Location : C:\Program Files\McAfee\Agent\x86\McTray.exe
  261. 2019-01-10 09:06:25 I #2864 msgbus Name pipe server started for pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492>
  262. 2019-01-10 09:06:25 I #2864 msgbus named pipe server started from local broker
  263. 2019-01-10 09:06:25 I #2864 msgbus Message created for Registration of <ma.service.updater.uiprovider.EPOAGENT3000.2.0> service
  264. 2019-01-10 09:06:25 I #2864 msgbus <ma.msgbus.name_service.service> service found in router
  265. 2019-01-10 09:06:25 I #2864 msgbus Service <ma.msgbus.name_service.service> found in local search and status of ep lookup is <2>
  266. 2019-01-10 09:06:25 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E71890>
  267. 2019-01-10 09:06:25 I #2864 msgbus uv timer data(02EA54A0)
  268. 2019-01-10 09:06:25 I #2864 msgbus
  269. 2019-01-10 09:06:25 I #2864 loop_worker loop worker successfully processed a message, still 0 more to go...
  270. 2019-01-10 09:06:25 I #2864 msgbus Adding received message into queue
  271. 2019-01-10 09:06:25 I #2864 msgbus Sending data on connected name pipe
  272. 2019-01-10 09:06:25 I #2864 msgbus Local broker lookup cb received status <0>
  273. 2019-01-10 09:06:25 I #2864 msgbus Local broker lookup cb execution on service/subscriber <ma.service.updater.uiprovider.EPOAGENT3000.2.0> registration
  274. 2019-01-10 09:06:25 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  275. 2019-01-10 09:06:25 I #4948 UdatrUI Launching process suceeded
  276. 2019-01-10 09:06:25 I #4948 UdatrUI HWND = NOT NULL
  277. 2019-01-10 09:06:25 I #4948 UpdaterUIModule AgentMode = 1
  278. 2019-01-10 09:06:25 I #4948 UpdaterUI Allow Update Security option State = 0
  279. 2019-01-10 09:06:25 I #4948 UdatrUI McTray Started
  280. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Enforcing UI policies
  281. 2019-01-10 09:06:25 I #4948 UpdaterUIModule AgentMode = 1
  282. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Show Agent UI: 1
  283. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Allow Security Update: 1
  284. 2019-01-10 09:06:25 I #4948 UpdaterUIModule Language from policy : 0000
  285. 2019-01-10 09:06:25 I #4948 UpdaterUI Allow Update Security option State = 1
  286. 2019-01-10 09:06:25 I #3240 UpdaterUIModule AgentMode = 1
  287. 2019-01-10 09:06:25 I #3240 UpdaterUIModule Agent Service Started
  288. 2019-01-10 09:06:25 I #3240 Logging StartReadingMessages (\\.\mailslot\{76889C92-A0C0-46e3-A4E1-1D6A5439B8DD}0000086c, 0x7f57, 4)
  289. 2019-01-10 09:06:25 I #3240 Logging - using empty 0
  290. 2019-01-10 09:06:25 I #2864 msgbus Received 238 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  291. 2019-01-10 09:06:25 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  292. 2019-01-10 09:06:25 I #2864 msgbus Received response from broker with status <0>
  293. 2019-01-10 09:06:25 I #2864 msgbus Received response type <prop.value.register_service_request> from broker
  294. 2019-01-10 09:06:25 I #2864 msgbus Not expecting any content in reply from broker for register and unregister requests
  295. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater> creation successful, reachability: <0>, timeout: <5000>, priority: <0>, thread model: <0>
  296. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater> option <0x10004> set, return value is <0>
  297. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater> option <0x10002> set, return value is <0>
  298. 2019-01-10 09:06:36 I #5616 schedulerclient scheduler adding task_id({08452aae-14b7-11e9-0a03-b8fa921cfca7}) task_name(empty) task_type(ma.updater.task.type.update)
  299. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.scheduler> creation successful, reachability: <0>, timeout: <5000>, priority: <0>, thread model: <0>
  300. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.scheduler> option <0x10004> set, return value is <0>
  301. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.scheduler> option <0x10002> set, return value is <0>
  302. 2019-01-10 09:06:36 I #5616 schedulerclient scheduler add task id({08452aae-14b7-11e9-0a03-b8fa921cfca7}) request sent to scheduler service
  303. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.scheduler>, sync send call
  304. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.scheduler> option <0x10004> set, return value is <0>
  305. 2019-01-10 09:06:36 I #5616 msgbus Messagebus Request object Created
  306. 2019-01-10 09:06:36 I #5616 loop_worker scheduled an async work request, now has 1 pending work requests
  307. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.scheduler> succeessfully submitted request to loop worker
  308. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.scheduler>, submitted loop worker request for sync send
  309. 2019-01-10 09:06:36 I #2864 msgbus uv timer data(00E2D6E0)
  310. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.scheduler>, waiting for loop worker sync request acknowledgement...
  311. 2019-01-10 09:06:36 I #2864 msgbus
  312. 2019-01-10 09:06:36 I #2864 msgbus <ma.service.scheduler> service is not available in router
  313. 2019-01-10 09:06:36 I #2864 msgbus Service <ma.service.scheduler> not found in local search and reachability is <1>
  314. 2019-01-10 09:06:36 I #2864 msgbus <ma.service.scheduler> service lookup start, ep lookup <02E778B0>
  315. 2019-01-10 09:06:36 I #2864 msgbus resolve request message created source name <ma.ep.lookup.internal.0000086C.2> for service <ma.service.scheduler>
  316. 2019-01-10 09:06:36 I #2864 msgbus Searching broker consumer and sending the service <ma.service.scheduler> resolve request to name service
  317. 2019-01-10 09:06:36 I #2864 msgbus Calling lookup callback in async way with status <516> from ep lookup <02E778B0>
  318. 2019-01-10 09:06:36 I #2864 msgbus uv timer data(02E7E808)
  319. 2019-01-10 09:06:36 I #2864 msgbus
  320. 2019-01-10 09:06:36 I #2864 msgbus <ma.msgbus.name_service.service> service found in router
  321. 2019-01-10 09:06:36 I #2864 msgbus Service <ma.msgbus.name_service.service> found in local search and status of ep lookup is <2>
  322. 2019-01-10 09:06:36 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E71890>
  323. 2019-01-10 09:06:36 I #2864 msgbus uv timer data(02E7E908)
  324. 2019-01-10 09:06:36 I #2864 msgbus
  325. 2019-01-10 09:06:36 I #2864 msgbus local broker look up succeeded for service <ma.service.scheduler> and started timer with timeout <20000> for request <00E2D6E0>
  326. 2019-01-10 09:06:36 I #2864 msgbus Added request object <00E2D6E0> into request manager
  327. 2019-01-10 09:06:36 I #2864 msgbus Endpoint <ma.service.scheduler> request successfully initiated
  328. 2019-01-10 09:06:36 I #2864 loop_worker loop worker successfully processed a message, still 0 more to go...
  329. 2019-01-10 09:06:36 I #2864 msgbus Message bus request <00E2D6E0> lookup cb is invoked with status <516> from ep lookup <02E778B0>
  330. 2019-01-10 09:06:36 I #2864 msgbus Received broker consumer, sending service <ma.service.scheduler> pipe name request msg
  331. 2019-01-10 09:06:36 I #2864 msgbus Adding received message into queue
  332. 2019-01-10 09:06:36 I #2864 msgbus Sending data on connected name pipe
  333. 2019-01-10 09:06:36 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  334. 2019-01-10 09:06:36 I #2864 msgbus Received 463 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  335. 2019-01-10 09:06:36 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  336. 2019-01-10 09:06:36 I #2864 msgbus Recevied response from broker with status <0>
  337. 2019-01-10 09:06:36 I #2864 msgbus Recevied response type <prop.value.discover_service_request> from broker
  338. 2019-01-10 09:06:36 I #2864 msgbus Recevied info from broker, service name: <ma.service.scheduler>
  339. 2019-01-10 09:06:36 I #2864 msgbus pipe name: <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  340. 2019-01-10 09:06:36 I #2864 msgbus pid : <5880>
  341. 2019-01-10 09:06:36 I #2864 msgbus ep lookup <02E71890> stop, connection status recevied <No> ref count <4>
  342. 2019-01-10 09:06:36 I #2864 msgbus searching named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> in connection manager
  343. 2019-01-10 09:06:36 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> found in connection manager
  344. 2019-01-10 09:06:36 I #2864 msgbus named pipe connection is already available in named pipe connection manager
  345. 2019-01-10 09:06:36 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E778B0>
  346. 2019-01-10 09:06:36 I #2864 msgbus uv timer data(02E7E848)
  347. 2019-01-10 09:06:36 I #2864 msgbus
  348. 2019-01-10 09:06:36 I #2864 msgbus Message bus request <00E2D6E0> lookup cb is invoked with status <0> from ep lookup <02E778B0>
  349. 2019-01-10 09:06:36 I #2864 msgbus Sending message to router - correlation id <3> ephemeral name buffer <ma.internal.request.0000086C.3>
  350. 2019-01-10 09:06:36 I #2864 msgbus Adding received message into queue
  351. 2019-01-10 09:06:36 I #2864 msgbus Sending data on connected name pipe
  352. 2019-01-10 09:06:36 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  353. 2019-01-10 09:06:36 I #2864 msgbus Received 253 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  354. 2019-01-10 09:06:36 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  355. 2019-01-10 09:06:36 I #2864 msgbus Recevied expected response to message bus request
  356. 2019-01-10 09:06:36 I #2864 msgbus message bus request Released
  357. 2019-01-10 09:06:36 I #2864 msgbus Invoking user callback in I/O thread
  358. 2019-01-10 09:06:36 I #2864 msgbus Endpoint <ma.service.scheduler>, sync send callback invoked
  359. 2019-01-10 09:06:36 I #2864 msgbus ep lookup <02E778B0> stop, connection status recevied <No> ref count <3>
  360. 2019-01-10 09:06:36 I #2864 msgbus Request Object Closes
  361. 2019-01-10 09:06:36 I #5616 msgbus message bus request Released
  362. 2019-01-10 09:06:36 I #2864 msgbus message bus request Released
  363. 2019-01-10 09:06:36 I #5616 schedulerclient scheduler add task id({08452aae-14b7-11e9-0a03-b8fa921cfca7}) reply status(TASK_REPLY_STATUS_SUCCESS)
  364. 2019-01-10 09:06:36 I #2864 msgbus Messagebus Request object Destroys
  365. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.scheduler> release
  366. 2019-01-10 09:06:36 I #2864 msgbus Endpoint <ma.service.scheduler> release
  367. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater>, sync send call
  368. 2019-01-10 09:06:36 I #2864 msgbus Endpoint <ma.service.scheduler> destroys
  369. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater> option <0x10004> set, return value is <0>
  370. 2019-01-10 09:06:36 I #5616 msgbus Messagebus Request object Created
  371. 2019-01-10 09:06:36 I #5616 loop_worker scheduled an async work request, now has 1 pending work requests
  372. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater> succeessfully submitted request to loop worker
  373. 2019-01-10 09:06:36 I #2864 msgbus uv timer data(00E2D6E0)
  374. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater>, submitted loop worker request for sync send
  375. 2019-01-10 09:06:36 I #2864 msgbus
  376. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater>, waiting for loop worker sync request acknowledgement...
  377. 2019-01-10 09:06:36 I #2864 msgbus <ma.service.updater> service is not available in router
  378. 2019-01-10 09:06:36 I #2864 msgbus Service <ma.service.updater> not found in local search and reachability is <1>
  379. 2019-01-10 09:06:36 I #2864 msgbus <ma.service.updater> service lookup start, ep lookup <02E69EE0>
  380. 2019-01-10 09:06:36 I #2864 msgbus resolve request message created source name <ma.ep.lookup.internal.0000086C.3> for service <ma.service.updater>
  381. 2019-01-10 09:06:36 I #2864 msgbus Searching broker consumer and sending the service <ma.service.updater> resolve request to name service
  382. 2019-01-10 09:06:36 I #2864 msgbus Calling lookup callback in async way with status <516> from ep lookup <02E69EE0>
  383. 2019-01-10 09:06:36 I #2864 msgbus uv timer data(02E7E828)
  384. 2019-01-10 09:06:36 I #2864 msgbus
  385. 2019-01-10 09:06:36 I #2864 msgbus <ma.msgbus.name_service.service> service found in router
  386. 2019-01-10 09:06:36 I #2864 msgbus Service <ma.msgbus.name_service.service> found in local search and status of ep lookup is <2>
  387. 2019-01-10 09:06:36 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E71890>
  388. 2019-01-10 09:06:36 I #2864 msgbus uv timer data(02E7EBA8)
  389. 2019-01-10 09:06:36 I #2864 msgbus
  390. 2019-01-10 09:06:36 I #2864 msgbus local broker look up succeeded for service <ma.service.updater> and started timer with timeout <20000> for request <00E2D6E0>
  391. 2019-01-10 09:06:36 I #2864 msgbus Added request object <00E2D6E0> into request manager
  392. 2019-01-10 09:06:36 I #2864 msgbus Endpoint <ma.service.updater> request successfully initiated
  393. 2019-01-10 09:06:36 I #2864 loop_worker loop worker successfully processed a message, still 0 more to go...
  394. 2019-01-10 09:06:36 I #2864 msgbus Message bus request <00E2D6E0> lookup cb is invoked with status <516> from ep lookup <02E69EE0>
  395. 2019-01-10 09:06:36 I #2864 msgbus Received broker consumer, sending service <ma.service.updater> pipe name request msg
  396. 2019-01-10 09:06:36 I #2864 msgbus Adding received message into queue
  397. 2019-01-10 09:06:36 I #2864 msgbus Sending data on connected name pipe
  398. 2019-01-10 09:06:36 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  399. 2019-01-10 09:06:36 I #2864 msgbus Received 461 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  400. 2019-01-10 09:06:36 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  401. 2019-01-10 09:06:36 I #2864 msgbus Recevied response from broker with status <0>
  402. 2019-01-10 09:06:36 I #2864 msgbus Recevied response type <prop.value.discover_service_request> from broker
  403. 2019-01-10 09:06:36 I #2864 msgbus Recevied info from broker, service name: <ma.service.updater>
  404. 2019-01-10 09:06:36 I #2864 msgbus pipe name: <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  405. 2019-01-10 09:06:36 I #2864 msgbus pid : <5880>
  406. 2019-01-10 09:06:36 I #2864 msgbus ep lookup <02E71890> stop, connection status recevied <No> ref count <4>
  407. 2019-01-10 09:06:36 I #2864 msgbus searching named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> in connection manager
  408. 2019-01-10 09:06:36 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> found in connection manager
  409. 2019-01-10 09:06:36 I #2864 msgbus named pipe connection is already available in named pipe connection manager
  410. 2019-01-10 09:06:36 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E69EE0>
  411. 2019-01-10 09:06:36 I #2864 msgbus uv timer data(02E7E888)
  412. 2019-01-10 09:06:36 I #2864 msgbus
  413. 2019-01-10 09:06:36 I #2864 msgbus Message bus request <00E2D6E0> lookup cb is invoked with status <0> from ep lookup <02E69EE0>
  414. 2019-01-10 09:06:36 I #2864 msgbus Sending message to router - correlation id <4> ephemeral name buffer <ma.internal.request.0000086C.4>
  415. 2019-01-10 09:06:36 I #2864 msgbus Adding received message into queue
  416. 2019-01-10 09:06:36 I #2864 msgbus Sending data on connected name pipe
  417. 2019-01-10 09:06:36 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  418. 2019-01-10 09:06:36 I #2864 msgbus Received 152 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  419. 2019-01-10 09:06:36 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  420. 2019-01-10 09:06:36 I #2864 msgbus Recevied expected response to message bus request
  421. 2019-01-10 09:06:36 I #2864 msgbus message bus request Released
  422. 2019-01-10 09:06:36 I #2864 msgbus Invoking user callback in I/O thread
  423. 2019-01-10 09:06:36 I #2864 msgbus Endpoint <ma.service.updater>, sync send callback invoked
  424. 2019-01-10 09:06:36 I #2864 msgbus ep lookup <02E69EE0> stop, connection status recevied <No> ref count <3>
  425. 2019-01-10 09:06:36 I #2864 msgbus Request Object Closes
  426. 2019-01-10 09:06:36 I #2864 msgbus message bus request Released
  427. 2019-01-10 09:06:36 I #5616 msgbus message bus request Released
  428. 2019-01-10 09:06:36 I #5616 msgbus Messagebus Request object Destroys
  429. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater> release
  430. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater> release
  431. 2019-01-10 09:06:36 I #5616 msgbus Endpoint <ma.service.updater> destroys
  432. 2019-01-10 09:06:36 I #5616 AgentClient Initiated run update now request.
  433. 2019-01-10 09:06:36 I #2864 msgbus Received 366 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  434. 2019-01-10 09:06:36 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  435. 2019-01-10 09:06:36 I #2864 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
  436. 2019-01-10 09:06:36 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  437. 2019-01-10 09:06:36 I #3000 msgbus Subscriber now invoking handler...
  438. 2019-01-10 09:06:36 I #2864 msgbus After Worker callback is Invoked in Subscriber
  439. 2019-01-10 09:06:36 I #2864 msgbus New connection on pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492> with status <0>, provider: 00E2B220
  440. 2019-01-10 09:06:36 I #2864 msgbus Received secure credentials for peer pipe handle=<852>, pid=<4592>.
  441. 2019-01-10 09:06:36 I #2864 msgbus Opening msgbus DB in read only mode
  442. 2019-01-10 09:06:36 I #2864 msgbus Successfully get trust level of pid <4592> , truest level : <1>
  443. 2019-01-10 09:06:36 I #2864 msgbus Allowing <4592> onto msgbus
  444. 2019-01-10 09:06:36 I #2864 msgbus Get the peer SID from the local trust store
  445. 2019-01-10 09:06:36 I #2864 msgbus Opening msgbus DB in read only mode
  446. 2019-01-10 09:06:36 I #2864 msgbus Successfully get sid of pid <4592> from trust store, sid : <S-1-5-18>
  447. 2019-01-10 09:06:36 I #2864 msgbus peer sid is <S-1-5-18>
  448. 2019-01-10 09:06:36 I #2864 msgbus setting the the sid object retrieved from the database
  449. 2019-01-10 09:06:36 I #2864 msgbus uv timer data(02E77998)
  450. 2019-01-10 09:06:36 I #2864 msgbus
  451. 2019-01-10 09:06:36 I #2864 msgbus named pipe authentication started.
  452. 2019-01-10 09:06:36 I #2864 msgbus on_client_authenticate_cb callback called with status <0>.
  453. 2019-01-10 09:06:36 I #2864 msgbus on_client_authenticate_cb secure pid <4592>.
  454. 2019-01-10 09:06:36 I #2864 msgbus named pipe connection peer is mcafee trusted, hence accepted.
  455. 2019-01-10 09:06:36 I #2864 msgbus accept callback invoked pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492> with status <0>
  456. 2019-01-10 09:06:36 I #2864 msgbus Calling user callback on this new connection on pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492>
  457. 2019-01-10 09:06:36 I #2864 msgbus Adding new accepted connection object with pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900>
  458. 2019-01-10 09:06:36 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900> is added into connection manager
  459. 2019-01-10 09:06:36 I #2864 msgbus set consumer in named pipe connection
  460. 2019-01-10 09:06:36 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900> start receiving...
  461. 2019-01-10 09:06:36 I #2864 msgbus ma_named_pipe_connection_release, ref count <3>
  462. 2019-01-10 09:06:36 I #2864 msgbus Received 5 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900>
  463. 2019-01-10 09:06:36 I #2864 msgbus received peer process pid <4592> via message
  464. 2019-01-10 09:06:36 I #2864 msgbus Sending pid <2156>
  465. 2019-01-10 09:06:36 I #2864 msgbus Sending data on connected name pipe
  466. 2019-01-10 09:06:36 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900> with status <0>
  467. 2019-01-10 09:06:36 I #2864 msgbus Received 389 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900>
  468. 2019-01-10 09:06:36 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  469. 2019-01-10 09:06:36 I #2864 msgbus Checking the authentication level of requesting peer ...
  470. 2019-01-10 09:06:36 I #2864 msgbus received the request message from process <4592> for server <ma.service.updater.uiprovider.EPOAGENT3000.2.0>.
  471. 2019-01-10 09:06:36 I #2864 msgbus Server <ma.service.updater.uiprovider.EPOAGENT3000.2.0> received a request message...
  472. 2019-01-10 09:06:36 I #2864 msgbus scheduling server callback to be run from thread pool...
  473. 2019-01-10 09:06:36 I #3000 UiProviderAdaptor >>>>ShowUpdateDialog Progress Dialog, Title= Update in Progress, Message= Please wait for update to finish...
  474. 2019-01-10 09:06:36 I #3000 UiProviderAdaptor On Progress Callback EventType=ProgressStart ProgressStep=1 MaxProgress = 100 Progress Message =
  475. 2019-01-10 09:06:38 I #2864 msgbus Received 343 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  476. 2019-01-10 09:06:38 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  477. 2019-01-10 09:06:38 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  478. 2019-01-10 09:06:38 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  479. 2019-01-10 09:06:38 I #3000 msgbus Subscriber now invoking handler...
  480. 2019-01-10 09:06:38 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=1, MaxProgress = 0, Progress Message = Checking update packages from repository ePO_UK-VM-AV1.
  481. 2019-01-10 09:06:38 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=1 MaxProgress = 0 Progress Message = Checking update packages from repository ePO_UK-VM-AV1.
  482. 2019-01-10 09:06:38 I #2864 msgbus After Worker callback is Invoked in Subscriber
  483. 2019-01-10 09:06:38 I #2864 msgbus Received 309 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  484. 2019-01-10 09:06:38 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  485. 2019-01-10 09:06:38 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  486. 2019-01-10 09:06:38 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  487. 2019-01-10 09:06:38 I #3000 msgbus Subscriber now invoking handler...
  488. 2019-01-10 09:06:38 I #3000 UiProviderAdaptor On Progress Callback EventType=ProgressStart , ProgressStep=15, MaxProgress = 1, Progress Message = Initializing update...
  489. 2019-01-10 09:06:38 I #3000 UiProviderAdaptor On Progress Callback EventType=ProgressStart ProgressStep=15 MaxProgress = 1 Progress Message = Initializing update...
  490. 2019-01-10 09:06:38 I #2864 msgbus After Worker callback is Invoked in Subscriber
  491. 2019-01-10 09:06:38 I #2864 msgbus Received 307 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  492. 2019-01-10 09:06:38 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  493. 2019-01-10 09:06:38 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  494. 2019-01-10 09:06:38 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  495. 2019-01-10 09:06:38 I #3000 msgbus Subscriber now invoking handler...
  496. 2019-01-10 09:06:38 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=3, MaxProgress = 0, Progress Message = Verifying catalog.z.
  497. 2019-01-10 09:06:38 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=3 MaxProgress = 0 Progress Message = Verifying catalog.z.
  498. 2019-01-10 09:06:38 I #2864 msgbus After Worker callback is Invoked in Subscriber
  499. 2019-01-10 09:06:38 I #2864 msgbus Received 308 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  500. 2019-01-10 09:06:38 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  501. 2019-01-10 09:06:38 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  502. 2019-01-10 09:06:38 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  503. 2019-01-10 09:06:38 I #3000 msgbus Subscriber now invoking handler...
  504. 2019-01-10 09:06:38 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=4, MaxProgress = 0, Progress Message = Extracting catalog.z.
  505. 2019-01-10 09:06:38 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=4 MaxProgress = 0 Progress Message = Extracting catalog.z.
  506. 2019-01-10 09:06:38 I #2864 msgbus After Worker callback is Invoked in Subscriber
  507. 2019-01-10 09:06:38 I #2864 msgbus Received 334 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  508. 2019-01-10 09:06:38 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  509. 2019-01-10 09:06:38 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  510. 2019-01-10 09:06:38 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  511. 2019-01-10 09:06:38 I #3000 msgbus Subscriber now invoking handler...
  512. 2019-01-10 09:06:38 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=5, MaxProgress = 0, Progress Message = Loading update configuration from: catalog.xml
  513. 2019-01-10 09:06:38 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=5 MaxProgress = 0 Progress Message = Loading update configuration from: catalog.xml
  514. 2019-01-10 09:06:38 I #2864 msgbus After Worker callback is Invoked in Subscriber
  515. 2019-01-10 09:06:39 I #2864 msgbus Received 603 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  516. 2019-01-10 09:06:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  517. 2019-01-10 09:06:39 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  518. 2019-01-10 09:06:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  519. 2019-01-10 09:06:39 I #3000 msgbus Subscriber now invoking handler...
  520. 2019-01-10 09:06:39 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=2, MaxProgress = 0, Progress Message = These updates will be applied if they are in the repository: Engine, DAT, EPOAGENT3000META, VIRUSCAN8800, BOCVSE__1000, TELECONT1000_EPO, TELECONT1000, VSCANMAC9500, MAR_CONTENT_1000, EPOAGENT5000META, EXTRADAT1000, SUPPCLNT1000, SIAREVOK1000, ENDP_GS_1050, LV2SNENG1000, MSCANENG1000, ENDPCNT_1000, AMCORDAT2000.
  521. 2019-01-10 09:06:39 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=2 MaxProgress = 0 Progress Message = These updates will be applied if they are in the repository: Engine, DAT, EPOAGENT3000META, VIRUSCAN8800, BOCVSE__1000, TELECONT1000_EPO, TELECONT1000, VSCANMAC9500, MAR_CONTENT_1000, EPOAGENT5000META, EXTRADAT1000, SUPPCLNT1000, SIAREVOK1000, ENDP_GS_1050, LV2SNENG1000, MSCANENG1000, ENDPCNT_1000, AMCORDAT2000.
  522. 2019-01-10 09:06:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  523. 2019-01-10 09:06:39 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  524. 2019-01-10 09:06:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  525. 2019-01-10 09:06:39 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  526. 2019-01-10 09:06:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  527. 2019-01-10 09:06:39 I #3000 msgbus Subscriber now invoking handler...
  528. 2019-01-10 09:06:39 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading PkgCatalog.z.
  529. 2019-01-10 09:06:39 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading PkgCatalog.z.
  530. 2019-01-10 09:06:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  531. 2019-01-10 09:06:40 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  532. 2019-01-10 09:06:40 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  533. 2019-01-10 09:06:40 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  534. 2019-01-10 09:06:40 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  535. 2019-01-10 09:06:40 I #3000 msgbus Subscriber now invoking handler...
  536. 2019-01-10 09:06:40 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=9, MaxProgress = 0, Progress Message = Verifying PkgCatalog.z.
  537. 2019-01-10 09:06:40 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=9 MaxProgress = 0 Progress Message = Verifying PkgCatalog.z.
  538. 2019-01-10 09:06:40 I #2864 msgbus After Worker callback is Invoked in Subscriber
  539. 2019-01-10 09:06:40 I #2864 msgbus Received 311 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  540. 2019-01-10 09:06:40 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  541. 2019-01-10 09:06:40 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  542. 2019-01-10 09:06:40 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  543. 2019-01-10 09:06:40 I #3000 msgbus Subscriber now invoking handler...
  544. 2019-01-10 09:06:40 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=10, MaxProgress = 0, Progress Message = Extracting PkgCatalog.z.
  545. 2019-01-10 09:06:40 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=10 MaxProgress = 0 Progress Message = Extracting PkgCatalog.z.
  546. 2019-01-10 09:06:40 I #2864 msgbus After Worker callback is Invoked in Subscriber
  547. 2019-01-10 09:06:40 I #2864 msgbus Received 337 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  548. 2019-01-10 09:06:40 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  549. 2019-01-10 09:06:40 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  550. 2019-01-10 09:06:40 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  551. 2019-01-10 09:06:40 I #3000 msgbus Subscriber now invoking handler...
  552. 2019-01-10 09:06:40 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Loading update configuration from: PkgCatalog.xml
  553. 2019-01-10 09:06:40 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Loading update configuration from: PkgCatalog.xml
  554. 2019-01-10 09:06:40 I #2864 msgbus After Worker callback is Invoked in Subscriber
  555. 2019-01-10 09:06:41 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  556. 2019-01-10 09:06:41 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  557. 2019-01-10 09:06:41 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  558. 2019-01-10 09:06:41 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  559. 2019-01-10 09:06:41 I #3000 msgbus Subscriber now invoking handler...
  560. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Verifying V2engdet.mcs.
  561. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Verifying V2engdet.mcs.
  562. 2019-01-10 09:06:41 I #2864 msgbus After Worker callback is Invoked in Subscriber
  563. 2019-01-10 09:06:41 I #2864 msgbus Received 325 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  564. 2019-01-10 09:06:41 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  565. 2019-01-10 09:06:41 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  566. 2019-01-10 09:06:41 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  567. 2019-01-10 09:06:41 I #3000 msgbus Subscriber now invoking handler...
  568. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Product(s) running the latest Engine.
  569. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Product(s) running the latest Engine.
  570. 2019-01-10 09:06:41 I #2864 msgbus After Worker callback is Invoked in Subscriber
  571. 2019-01-10 09:06:41 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  572. 2019-01-10 09:06:41 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  573. 2019-01-10 09:06:41 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  574. 2019-01-10 09:06:41 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  575. 2019-01-10 09:06:41 I #3000 msgbus Subscriber now invoking handler...
  576. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading PkgCatalog.z.
  577. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading PkgCatalog.z.
  578. 2019-01-10 09:06:41 I #2864 msgbus After Worker callback is Invoked in Subscriber
  579. 2019-01-10 09:06:41 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  580. 2019-01-10 09:06:41 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  581. 2019-01-10 09:06:41 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  582. 2019-01-10 09:06:41 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  583. 2019-01-10 09:06:41 I #3000 msgbus Subscriber now invoking handler...
  584. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=9, MaxProgress = 0, Progress Message = Verifying PkgCatalog.z.
  585. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=9 MaxProgress = 0 Progress Message = Verifying PkgCatalog.z.
  586. 2019-01-10 09:06:41 I #2864 msgbus After Worker callback is Invoked in Subscriber
  587. 2019-01-10 09:06:41 I #2864 msgbus Received 311 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  588. 2019-01-10 09:06:41 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  589. 2019-01-10 09:06:41 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  590. 2019-01-10 09:06:41 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  591. 2019-01-10 09:06:41 I #3000 msgbus Subscriber now invoking handler...
  592. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=10, MaxProgress = 0, Progress Message = Extracting PkgCatalog.z.
  593. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=10 MaxProgress = 0 Progress Message = Extracting PkgCatalog.z.
  594. 2019-01-10 09:06:41 I #2864 msgbus After Worker callback is Invoked in Subscriber
  595. 2019-01-10 09:06:41 I #2864 msgbus Received 337 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  596. 2019-01-10 09:06:41 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  597. 2019-01-10 09:06:41 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  598. 2019-01-10 09:06:41 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  599. 2019-01-10 09:06:41 I #3000 msgbus Subscriber now invoking handler...
  600. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Loading update configuration from: PkgCatalog.xml
  601. 2019-01-10 09:06:41 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Loading update configuration from: PkgCatalog.xml
  602. 2019-01-10 09:06:41 I #2864 msgbus After Worker callback is Invoked in Subscriber
  603. 2019-01-10 09:06:42 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  604. 2019-01-10 09:06:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  605. 2019-01-10 09:06:42 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  606. 2019-01-10 09:06:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  607. 2019-01-10 09:06:42 I #3000 msgbus Subscriber now invoking handler...
  608. 2019-01-10 09:06:42 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Verifying V2datdet.mcs.
  609. 2019-01-10 09:06:42 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Verifying V2datdet.mcs.
  610. 2019-01-10 09:06:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  611. 2019-01-10 09:06:43 I #2864 msgbus Received 329 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  612. 2019-01-10 09:06:43 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  613. 2019-01-10 09:06:43 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  614. 2019-01-10 09:06:43 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  615. 2019-01-10 09:06:43 I #3000 msgbus Subscriber now invoking handler...
  616. 2019-01-10 09:06:43 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=0, MaxProgress = 0, Progress Message = Unable to find any qualifying product(s).
  617. 2019-01-10 09:06:43 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=0 MaxProgress = 0 Progress Message = Unable to find any qualifying product(s).
  618. 2019-01-10 09:06:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  619. 2019-01-10 09:06:43 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  620. 2019-01-10 09:06:43 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  621. 2019-01-10 09:06:43 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  622. 2019-01-10 09:06:43 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  623. 2019-01-10 09:06:43 I #3000 msgbus Subscriber now invoking handler...
  624. 2019-01-10 09:06:43 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying AgtMetaDet.McS.
  625. 2019-01-10 09:06:43 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying AgtMetaDet.McS.
  626. 2019-01-10 09:06:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  627. 2019-01-10 09:06:43 I #2864 msgbus Received 340 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  628. 2019-01-10 09:06:43 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  629. 2019-01-10 09:06:43 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  630. 2019-01-10 09:06:43 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  631. 2019-01-10 09:06:43 I #3000 msgbus Subscriber now invoking handler...
  632. 2019-01-10 09:06:43 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Searching available updates for McAfee Agent Plugin.
  633. 2019-01-10 09:06:43 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Searching available updates for McAfee Agent Plugin.
  634. 2019-01-10 09:06:43 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  635. 2019-01-10 09:06:43 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  636. 2019-01-10 09:06:43 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  637. 2019-01-10 09:06:43 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  638. 2019-01-10 09:06:43 I #528 msgbus Subscriber now invoking handler...
  639. 2019-01-10 09:06:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  640. 2019-01-10 09:06:43 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading PkgCatalog.z.
  641. 2019-01-10 09:06:43 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading PkgCatalog.z.
  642. 2019-01-10 09:06:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  643. 2019-01-10 09:06:44 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  644. 2019-01-10 09:06:44 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  645. 2019-01-10 09:06:44 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  646. 2019-01-10 09:06:44 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  647. 2019-01-10 09:06:44 I #528 msgbus Subscriber now invoking handler...
  648. 2019-01-10 09:06:44 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=9, MaxProgress = 0, Progress Message = Verifying PkgCatalog.z.
  649. 2019-01-10 09:06:44 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=9 MaxProgress = 0 Progress Message = Verifying PkgCatalog.z.
  650. 2019-01-10 09:06:44 I #2864 msgbus After Worker callback is Invoked in Subscriber
  651. 2019-01-10 09:06:44 I #2864 msgbus Received 311 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  652. 2019-01-10 09:06:44 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  653. 2019-01-10 09:06:44 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  654. 2019-01-10 09:06:44 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  655. 2019-01-10 09:06:44 I #528 msgbus Subscriber now invoking handler...
  656. 2019-01-10 09:06:44 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=10, MaxProgress = 0, Progress Message = Extracting PkgCatalog.z.
  657. 2019-01-10 09:06:44 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=10 MaxProgress = 0 Progress Message = Extracting PkgCatalog.z.
  658. 2019-01-10 09:06:44 I #2864 msgbus Received 337 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  659. 2019-01-10 09:06:44 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  660. 2019-01-10 09:06:44 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  661. 2019-01-10 09:06:44 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  662. 2019-01-10 09:06:44 I #3000 msgbus Subscriber now invoking handler...
  663. 2019-01-10 09:06:44 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Loading update configuration from: PkgCatalog.xml
  664. 2019-01-10 09:06:44 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Loading update configuration from: PkgCatalog.xml
  665. 2019-01-10 09:06:44 I #2864 msgbus After Worker callback is Invoked in Subscriber
  666. 2019-01-10 09:06:44 I #2864 msgbus After Worker callback is Invoked in Subscriber
  667. 2019-01-10 09:06:45 I #2864 msgbus Received 325 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  668. 2019-01-10 09:06:45 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  669. 2019-01-10 09:06:45 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  670. 2019-01-10 09:06:45 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  671. 2019-01-10 09:06:45 I #3000 msgbus Subscriber now invoking handler...
  672. 2019-01-10 09:06:45 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Product(s) running the latest Plugin.
  673. 2019-01-10 09:06:45 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Product(s) running the latest Plugin.
  674. 2019-01-10 09:06:45 I #2864 msgbus After Worker callback is Invoked in Subscriber
  675. 2019-01-10 09:06:45 I #2864 msgbus Received 311 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  676. 2019-01-10 09:06:45 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  677. 2019-01-10 09:06:45 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  678. 2019-01-10 09:06:45 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  679. 2019-01-10 09:06:45 I #3000 msgbus Subscriber now invoking handler...
  680. 2019-01-10 09:06:45 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying VSE880Det.McS.
  681. 2019-01-10 09:06:45 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying VSE880Det.McS.
  682. 2019-01-10 09:06:45 I #2864 msgbus After Worker callback is Invoked in Subscriber
  683. 2019-01-10 09:06:45 I #2864 msgbus Received 314 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  684. 2019-01-10 09:06:45 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  685. 2019-01-10 09:06:45 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  686. 2019-01-10 09:06:45 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  687. 2019-01-10 09:06:45 I #3000 msgbus Subscriber now invoking handler...
  688. 2019-01-10 09:06:45 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying TelemetryDet.mcs.
  689. 2019-01-10 09:06:45 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying TelemetryDet.mcs.
  690. 2019-01-10 09:06:45 I #2864 msgbus After Worker callback is Invoked in Subscriber
  691. 2019-01-10 09:06:45 I #2864 msgbus Received 325 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  692. 2019-01-10 09:06:45 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  693. 2019-01-10 09:06:45 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  694. 2019-01-10 09:06:45 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  695. 2019-01-10 09:06:45 I #3000 msgbus Subscriber now invoking handler...
  696. 2019-01-10 09:06:45 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=0, MaxProgress = 0, Progress Message = Unable to find the specified section.
  697. 2019-01-10 09:06:45 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=0 MaxProgress = 0 Progress Message = Unable to find the specified section.
  698. 2019-01-10 09:06:45 I #2864 msgbus Received 313 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  699. 2019-01-10 09:06:45 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  700. 2019-01-10 09:06:45 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  701. 2019-01-10 09:06:45 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  702. 2019-01-10 09:06:45 I #528 msgbus Subscriber now invoking handler...
  703. 2019-01-10 09:06:45 I #2864 msgbus After Worker callback is Invoked in Subscriber
  704. 2019-01-10 09:06:45 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying TeleContent.mcs.
  705. 2019-01-10 09:06:45 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying TeleContent.mcs.
  706. 2019-01-10 09:06:45 I #2864 msgbus After Worker callback is Invoked in Subscriber
  707. 2019-01-10 09:06:45 I #2864 msgbus Received 321 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  708. 2019-01-10 09:06:45 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  709. 2019-01-10 09:06:45 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  710. 2019-01-10 09:06:45 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  711. 2019-01-10 09:06:45 I #528 msgbus Subscriber now invoking handler...
  712. 2019-01-10 09:06:45 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying MsgBusCertsUpdater.McS.
  713. 2019-01-10 09:06:45 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying MsgBusCertsUpdater.McS.
  714. 2019-01-10 09:06:45 I #2864 msgbus After Worker callback is Invoked in Subscriber
  715. 2019-01-10 09:06:45 I #2864 msgbus Received 351 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  716. 2019-01-10 09:06:45 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  717. 2019-01-10 09:06:45 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  718. 2019-01-10 09:06:45 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  719. 2019-01-10 09:06:45 I #528 msgbus Subscriber now invoking handler...
  720. 2019-01-10 09:06:45 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Searching available updates for McAfee Agent Message Bus Certs.
  721. 2019-01-10 09:06:45 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Searching available updates for McAfee Agent Message Bus Certs.
  722. 2019-01-10 09:06:45 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  723. 2019-01-10 09:06:45 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  724. 2019-01-10 09:06:45 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  725. 2019-01-10 09:06:45 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  726. 2019-01-10 09:06:45 I #3000 msgbus Subscriber now invoking handler...
  727. 2019-01-10 09:06:45 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading PkgCatalog.z.
  728. 2019-01-10 09:06:45 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading PkgCatalog.z.
  729. 2019-01-10 09:06:45 I #2864 msgbus After Worker callback is Invoked in Subscriber
  730. 2019-01-10 09:06:45 I #2864 msgbus After Worker callback is Invoked in Subscriber
  731. 2019-01-10 09:06:46 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  732. 2019-01-10 09:06:46 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  733. 2019-01-10 09:06:46 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  734. 2019-01-10 09:06:46 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  735. 2019-01-10 09:06:46 I #3000 msgbus Subscriber now invoking handler...
  736. 2019-01-10 09:06:46 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=9, MaxProgress = 0, Progress Message = Verifying PkgCatalog.z.
  737. 2019-01-10 09:06:46 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=9 MaxProgress = 0 Progress Message = Verifying PkgCatalog.z.
  738. 2019-01-10 09:06:46 I #2864 msgbus After Worker callback is Invoked in Subscriber
  739. 2019-01-10 09:06:46 I #2864 msgbus Received 311 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  740. 2019-01-10 09:06:46 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  741. 2019-01-10 09:06:46 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  742. 2019-01-10 09:06:46 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  743. 2019-01-10 09:06:46 I #3000 msgbus Subscriber now invoking handler...
  744. 2019-01-10 09:06:46 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=10, MaxProgress = 0, Progress Message = Extracting PkgCatalog.z.
  745. 2019-01-10 09:06:46 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=10 MaxProgress = 0 Progress Message = Extracting PkgCatalog.z.
  746. 2019-01-10 09:06:46 I #2864 msgbus Received 337 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  747. 2019-01-10 09:06:46 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  748. 2019-01-10 09:06:46 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  749. 2019-01-10 09:06:46 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  750. 2019-01-10 09:06:46 I #528 msgbus Subscriber now invoking handler...
  751. 2019-01-10 09:06:46 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Loading update configuration from: PkgCatalog.xml
  752. 2019-01-10 09:06:46 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Loading update configuration from: PkgCatalog.xml
  753. 2019-01-10 09:06:46 I #2864 msgbus After Worker callback is Invoked in Subscriber
  754. 2019-01-10 09:06:46 I #2864 msgbus After Worker callback is Invoked in Subscriber
  755. 2019-01-10 09:06:47 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  756. 2019-01-10 09:06:47 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  757. 2019-01-10 09:06:47 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  758. 2019-01-10 09:06:47 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  759. 2019-01-10 09:06:47 I #528 msgbus Subscriber now invoking handler...
  760. 2019-01-10 09:06:47 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying extradat.mcs.
  761. 2019-01-10 09:06:47 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying extradat.mcs.
  762. 2019-01-10 09:06:47 I #2864 msgbus After Worker callback is Invoked in Subscriber
  763. 2019-01-10 09:06:47 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  764. 2019-01-10 09:06:47 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  765. 2019-01-10 09:06:47 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  766. 2019-01-10 09:06:47 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  767. 2019-01-10 09:06:47 I #528 msgbus Subscriber now invoking handler...
  768. 2019-01-10 09:06:47 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading extradat.mcs.
  769. 2019-01-10 09:06:47 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading extradat.mcs.
  770. 2019-01-10 09:06:47 I #2864 msgbus After Worker callback is Invoked in Subscriber
  771. 2019-01-10 09:06:47 I #2864 msgbus Received 327 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  772. 2019-01-10 09:06:48 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  773. 2019-01-10 09:06:48 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  774. 2019-01-10 09:06:48 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  775. 2019-01-10 09:06:48 I #528 msgbus Subscriber now invoking handler...
  776. 2019-01-10 09:06:48 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Product(s) running the latest ExtraDAT.
  777. 2019-01-10 09:06:48 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Product(s) running the latest ExtraDAT.
  778. 2019-01-10 09:06:48 I #2864 msgbus After Worker callback is Invoked in Subscriber
  779. 2019-01-10 09:06:48 I #2864 msgbus Received 315 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  780. 2019-01-10 09:06:48 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  781. 2019-01-10 09:06:48 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  782. 2019-01-10 09:06:48 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  783. 2019-01-10 09:06:48 I #528 msgbus Subscriber now invoking handler...
  784. 2019-01-10 09:06:48 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying SuppClientDet.McS.
  785. 2019-01-10 09:06:48 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying SuppClientDet.McS.
  786. 2019-01-10 09:06:48 I #2864 msgbus After Worker callback is Invoked in Subscriber
  787. 2019-01-10 09:06:48 I #2864 msgbus Received 317 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  788. 2019-01-10 09:06:48 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  789. 2019-01-10 09:06:48 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  790. 2019-01-10 09:06:48 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  791. 2019-01-10 09:06:48 I #528 msgbus Subscriber now invoking handler...
  792. 2019-01-10 09:06:48 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading SuppClientDet.McS.
  793. 2019-01-10 09:06:48 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading SuppClientDet.McS.
  794. 2019-01-10 09:06:48 I #2864 msgbus After Worker callback is Invoked in Subscriber
  795. 2019-01-10 09:06:48 I #2864 msgbus Received 311 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  796. 2019-01-10 09:06:48 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  797. 2019-01-10 09:06:48 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  798. 2019-01-10 09:06:48 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  799. 2019-01-10 09:06:48 I #528 msgbus Subscriber now invoking handler...
  800. 2019-01-10 09:06:48 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying CommonDet.mcs.
  801. 2019-01-10 09:06:48 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying CommonDet.mcs.
  802. 2019-01-10 09:06:48 I #2864 msgbus After Worker callback is Invoked in Subscriber
  803. 2019-01-10 09:06:48 I #2864 msgbus Received 313 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  804. 2019-01-10 09:06:48 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  805. 2019-01-10 09:06:48 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  806. 2019-01-10 09:06:48 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  807. 2019-01-10 09:06:48 I #528 msgbus Subscriber now invoking handler...
  808. 2019-01-10 09:06:48 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading CommonDet.mcs.
  809. 2019-01-10 09:06:48 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading CommonDet.mcs.
  810. 2019-01-10 09:06:48 I #2864 msgbus After Worker callback is Invoked in Subscriber
  811. 2019-01-10 09:06:49 I #2864 msgbus Received 354 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  812. 2019-01-10 09:06:49 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  813. 2019-01-10 09:06:49 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  814. 2019-01-10 09:06:49 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  815. 2019-01-10 09:06:49 I #528 msgbus Subscriber now invoking handler...
  816. 2019-01-10 09:06:49 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Searching available updates for Endpoint Security Platform 10.5.0.
  817. 2019-01-10 09:06:49 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Searching available updates for Endpoint Security Platform 10.5.0.
  818. 2019-01-10 09:06:49 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  819. 2019-01-10 09:06:49 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  820. 2019-01-10 09:06:49 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  821. 2019-01-10 09:06:49 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  822. 2019-01-10 09:06:49 I #3000 msgbus Subscriber now invoking handler...
  823. 2019-01-10 09:06:49 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading PkgCatalog.z.
  824. 2019-01-10 09:06:49 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading PkgCatalog.z.
  825. 2019-01-10 09:06:49 I #2864 msgbus After Worker callback is Invoked in Subscriber
  826. 2019-01-10 09:06:49 I #2864 msgbus After Worker callback is Invoked in Subscriber
  827. 2019-01-10 09:06:49 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  828. 2019-01-10 09:06:49 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  829. 2019-01-10 09:06:49 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  830. 2019-01-10 09:06:49 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  831. 2019-01-10 09:06:49 I #3000 msgbus Subscriber now invoking handler...
  832. 2019-01-10 09:06:49 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=9, MaxProgress = 0, Progress Message = Verifying PkgCatalog.z.
  833. 2019-01-10 09:06:49 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=9 MaxProgress = 0 Progress Message = Verifying PkgCatalog.z.
  834. 2019-01-10 09:06:49 I #2864 msgbus After Worker callback is Invoked in Subscriber
  835. 2019-01-10 09:06:49 I #2864 msgbus Received 311 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  836. 2019-01-10 09:06:49 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  837. 2019-01-10 09:06:49 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  838. 2019-01-10 09:06:49 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  839. 2019-01-10 09:06:49 I #3000 msgbus Subscriber now invoking handler...
  840. 2019-01-10 09:06:49 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=10, MaxProgress = 0, Progress Message = Extracting PkgCatalog.z.
  841. 2019-01-10 09:06:49 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=10 MaxProgress = 0 Progress Message = Extracting PkgCatalog.z.
  842. 2019-01-10 09:06:49 I #2864 msgbus After Worker callback is Invoked in Subscriber
  843. 2019-01-10 09:06:49 I #2864 msgbus Received 337 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  844. 2019-01-10 09:06:49 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  845. 2019-01-10 09:06:49 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  846. 2019-01-10 09:06:49 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  847. 2019-01-10 09:06:49 I #3000 msgbus Subscriber now invoking handler...
  848. 2019-01-10 09:06:49 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Loading update configuration from: PkgCatalog.xml
  849. 2019-01-10 09:06:49 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Loading update configuration from: PkgCatalog.xml
  850. 2019-01-10 09:06:49 I #2864 msgbus After Worker callback is Invoked in Subscriber
  851. 2019-01-10 09:06:50 I #2864 msgbus Received 309 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  852. 2019-01-10 09:06:50 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  853. 2019-01-10 09:06:50 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  854. 2019-01-10 09:06:50 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  855. 2019-01-10 09:06:50 I #3000 msgbus Subscriber now invoking handler...
  856. 2019-01-10 09:06:50 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Verifying setupCC.exe.
  857. 2019-01-10 09:06:50 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Verifying setupCC.exe.
  858. 2019-01-10 09:06:50 I #2864 msgbus After Worker callback is Invoked in Subscriber
  859. 2019-01-10 09:06:50 I #2864 msgbus Received 311 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  860. 2019-01-10 09:06:50 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  861. 2019-01-10 09:06:50 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  862. 2019-01-10 09:06:50 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  863. 2019-01-10 09:06:50 I #3000 msgbus Subscriber now invoking handler...
  864. 2019-01-10 09:06:50 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=12, MaxProgress = 0, Progress Message = Downloading setupCC.exe.
  865. 2019-01-10 09:06:50 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=12 MaxProgress = 0 Progress Message = Downloading setupCC.exe.
  866. 2019-01-10 09:06:50 I #2864 msgbus After Worker callback is Invoked in Subscriber
  867. 2019-01-10 09:06:51 I #2864 msgbus Received 323 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  868. 2019-01-10 09:06:51 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  869. 2019-01-10 09:06:51 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  870. 2019-01-10 09:06:51 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  871. 2019-01-10 09:06:51 I #3000 msgbus Subscriber now invoking handler...
  872. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Verifying McAfee_Common_HF_x64.msp.
  873. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Verifying McAfee_Common_HF_x64.msp.
  874. 2019-01-10 09:06:51 I #2864 msgbus After Worker callback is Invoked in Subscriber
  875. 2019-01-10 09:06:51 I #2864 msgbus Received 325 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  876. 2019-01-10 09:06:51 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  877. 2019-01-10 09:06:51 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  878. 2019-01-10 09:06:51 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  879. 2019-01-10 09:06:51 I #3000 msgbus Subscriber now invoking handler...
  880. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=12, MaxProgress = 0, Progress Message = Downloading McAfee_Common_HF_x64.msp.
  881. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=12 MaxProgress = 0 Progress Message = Downloading McAfee_Common_HF_x64.msp.
  882. 2019-01-10 09:06:51 I #2864 msgbus After Worker callback is Invoked in Subscriber
  883. 2019-01-10 09:06:51 I #2864 msgbus Received 316 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  884. 2019-01-10 09:06:51 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  885. 2019-01-10 09:06:51 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  886. 2019-01-10 09:06:51 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  887. 2019-01-10 09:06:51 I #3000 msgbus Subscriber now invoking handler...
  888. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Verifying MfeSysPrep_x64.zip.
  889. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Verifying MfeSysPrep_x64.zip.
  890. 2019-01-10 09:06:51 I #2864 msgbus After Worker callback is Invoked in Subscriber
  891. 2019-01-10 09:06:51 I #2864 msgbus Received 318 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  892. 2019-01-10 09:06:51 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  893. 2019-01-10 09:06:51 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  894. 2019-01-10 09:06:51 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  895. 2019-01-10 09:06:51 I #3000 msgbus Subscriber now invoking handler...
  896. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=12, MaxProgress = 0, Progress Message = Downloading MfeSysPrep_x64.zip.
  897. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=12 MaxProgress = 0 Progress Message = Downloading MfeSysPrep_x64.zip.
  898. 2019-01-10 09:06:51 I #2864 msgbus After Worker callback is Invoked in Subscriber
  899. 2019-01-10 09:06:51 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  900. 2019-01-10 09:06:51 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  901. 2019-01-10 09:06:51 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  902. 2019-01-10 09:06:51 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  903. 2019-01-10 09:06:51 I #3000 msgbus Subscriber now invoking handler...
  904. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Verifying vscore_all.cab.
  905. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Verifying vscore_all.cab.
  906. 2019-01-10 09:06:51 I #2864 msgbus After Worker callback is Invoked in Subscriber
  907. 2019-01-10 09:06:51 I #2864 msgbus Received 314 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  908. 2019-01-10 09:06:51 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  909. 2019-01-10 09:06:51 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  910. 2019-01-10 09:06:51 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  911. 2019-01-10 09:06:51 I #3000 msgbus Subscriber now invoking handler...
  912. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=12, MaxProgress = 0, Progress Message = Downloading vscore_all.cab.
  913. 2019-01-10 09:06:51 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=12 MaxProgress = 0 Progress Message = Downloading vscore_all.cab.
  914. 2019-01-10 09:06:51 I #2864 msgbus After Worker callback is Invoked in Subscriber
  915. 2019-01-10 09:06:55 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  916. 2019-01-10 09:06:55 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  917. 2019-01-10 09:06:55 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  918. 2019-01-10 09:06:55 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  919. 2019-01-10 09:06:55 I #3000 msgbus Subscriber now invoking handler...
  920. 2019-01-10 09:06:55 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Verifying mfehidin64.exe.
  921. 2019-01-10 09:06:55 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Verifying mfehidin64.exe.
  922. 2019-01-10 09:06:55 I #2864 msgbus After Worker callback is Invoked in Subscriber
  923. 2019-01-10 09:06:55 I #2864 msgbus Received 314 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  924. 2019-01-10 09:06:55 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  925. 2019-01-10 09:06:55 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  926. 2019-01-10 09:06:55 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  927. 2019-01-10 09:06:55 I #3000 msgbus Subscriber now invoking handler...
  928. 2019-01-10 09:06:55 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=12, MaxProgress = 0, Progress Message = Downloading mfehidin64.exe.
  929. 2019-01-10 09:06:55 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=12 MaxProgress = 0 Progress Message = Downloading mfehidin64.exe.
  930. 2019-01-10 09:06:55 I #2864 msgbus After Worker callback is Invoked in Subscriber
  931. 2019-01-10 09:06:55 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  932. 2019-01-10 09:06:55 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  933. 2019-01-10 09:06:55 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  934. 2019-01-10 09:06:55 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  935. 2019-01-10 09:06:55 I #3000 msgbus Subscriber now invoking handler...
  936. 2019-01-10 09:06:55 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=11, MaxProgress = 0, Progress Message = Starting HotFix update.
  937. 2019-01-10 09:06:55 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=11 MaxProgress = 0 Progress Message = Starting HotFix update.
  938. 2019-01-10 09:06:55 I #2864 msgbus After Worker callback is Invoked in Subscriber
  939. 2019-01-10 09:07:05 I #2864 msgbus Received 331 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  940. 2019-01-10 09:07:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  941. 2019-01-10 09:07:05 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  942. 2019-01-10 09:07:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  943. 2019-01-10 09:07:05 I #3000 msgbus Subscriber now invoking handler...
  944. 2019-01-10 09:07:05 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=12, MaxProgress = 0, Progress Message = Update succeeded to version HotFix 1238207.
  945. 2019-01-10 09:07:05 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=12 MaxProgress = 0 Progress Message = Update succeeded to version HotFix 1238207.
  946. 2019-01-10 09:07:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  947. 2019-01-10 09:07:05 I #2864 msgbus Received 322 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  948. 2019-01-10 09:07:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  949. 2019-01-10 09:07:05 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  950. 2019-01-10 09:07:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  951. 2019-01-10 09:07:05 I #3000 msgbus Subscriber now invoking handler...
  952. 2019-01-10 09:07:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  953. 2019-01-10 09:07:05 I #2864 msgbus Received 842 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  954. 2019-01-10 09:07:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  955. 2019-01-10 09:07:05 I #2864 msgbus Received topic <ma.topic.pubsub.custom_events>, matched <ma.*>
  956. 2019-01-10 09:07:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  957. 2019-01-10 09:07:05 I #3000 msgbus Subscriber now invoking handler...
  958. 2019-01-10 09:07:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  959. 2019-01-10 09:07:05 I #2864 msgbus Received 317 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  960. 2019-01-10 09:07:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  961. 2019-01-10 09:07:05 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  962. 2019-01-10 09:07:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  963. 2019-01-10 09:07:05 I #3000 msgbus Subscriber now invoking handler...
  964. 2019-01-10 09:07:05 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying EndPoint_Detect.mcs.
  965. 2019-01-10 09:07:05 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying EndPoint_Detect.mcs.
  966. 2019-01-10 09:07:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  967. 2019-01-10 09:07:05 I #2864 msgbus Received 320 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  968. 2019-01-10 09:07:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  969. 2019-01-10 09:07:05 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  970. 2019-01-10 09:07:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  971. 2019-01-10 09:07:05 I #3000 msgbus Subscriber now invoking handler...
  972. 2019-01-10 09:07:05 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading EndPoint_Detect.mcs.
  973. 2019-01-10 09:07:05 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading EndPoint_Detect.mcs.
  974. 2019-01-10 09:07:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  975. 2019-01-10 09:07:06 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  976. 2019-01-10 09:07:06 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  977. 2019-01-10 09:07:06 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  978. 2019-01-10 09:07:06 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  979. 2019-01-10 09:07:06 I #3000 msgbus Subscriber now invoking handler...
  980. 2019-01-10 09:07:06 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading PkgCatalog.z.
  981. 2019-01-10 09:07:06 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading PkgCatalog.z.
  982. 2019-01-10 09:07:06 I #2864 msgbus After Worker callback is Invoked in Subscriber
  983. 2019-01-10 09:07:06 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  984. 2019-01-10 09:07:06 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  985. 2019-01-10 09:07:06 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  986. 2019-01-10 09:07:06 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  987. 2019-01-10 09:07:06 I #3000 msgbus Subscriber now invoking handler...
  988. 2019-01-10 09:07:06 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=9, MaxProgress = 0, Progress Message = Verifying PkgCatalog.z.
  989. 2019-01-10 09:07:06 I #3000 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=9 MaxProgress = 0 Progress Message = Verifying PkgCatalog.z.
  990. 2019-01-10 09:07:06 I #2864 msgbus Received 311 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  991. 2019-01-10 09:07:06 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  992. 2019-01-10 09:07:06 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  993. 2019-01-10 09:07:06 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  994. 2019-01-10 09:07:06 I #528 msgbus Subscriber now invoking handler...
  995. 2019-01-10 09:07:06 I #2864 msgbus After Worker callback is Invoked in Subscriber
  996. 2019-01-10 09:07:06 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=10, MaxProgress = 0, Progress Message = Extracting PkgCatalog.z.
  997. 2019-01-10 09:07:06 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=10 MaxProgress = 0 Progress Message = Extracting PkgCatalog.z.
  998. 2019-01-10 09:07:06 I #2864 msgbus After Worker callback is Invoked in Subscriber
  999. 2019-01-10 09:07:07 I #2864 msgbus Received 308 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1000. 2019-01-10 09:07:07 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1001. 2019-01-10 09:07:07 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1002. 2019-01-10 09:07:07 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1003. 2019-01-10 09:07:07 I #528 msgbus Subscriber now invoking handler...
  1004. 2019-01-10 09:07:07 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying amcore.mcs.
  1005. 2019-01-10 09:07:07 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying amcore.mcs.
  1006. 2019-01-10 09:07:07 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1007. 2019-01-10 09:07:07 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1008. 2019-01-10 09:07:07 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1009. 2019-01-10 09:07:07 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1010. 2019-01-10 09:07:07 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1011. 2019-01-10 09:07:07 I #528 msgbus Subscriber now invoking handler...
  1012. 2019-01-10 09:07:07 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Downloading amcore.mcs.
  1013. 2019-01-10 09:07:07 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Downloading amcore.mcs.
  1014. 2019-01-10 09:07:07 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1015. 2019-01-10 09:07:08 I #2864 msgbus Received 302 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1016. 2019-01-10 09:07:08 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1017. 2019-01-10 09:07:08 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1018. 2019-01-10 09:07:08 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1019. 2019-01-10 09:07:08 I #528 msgbus Subscriber now invoking handler...
  1020. 2019-01-10 09:07:08 I #528 UiProviderAdaptor On Progress Callback EventType=ProgressFinished, ProgressStep=0, MaxProgress = 0, Progress Message = Update Finished
  1021. 2019-01-10 09:07:08 I #528 UiProviderAdaptor On Progress Callback EventType=ProgressFinished ProgressStep=0 MaxProgress = 0 Progress Message = Update Finished
  1022. 2019-01-10 09:07:08 I #2864 msgbus Received 361 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1023. 2019-01-10 09:07:08 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1024. 2019-01-10 09:07:08 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1025. 2019-01-10 09:07:08 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1026. 2019-01-10 09:07:08 I #3000 msgbus Subscriber now invoking handler...
  1027. 2019-01-10 09:07:08 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1028. 2019-01-10 09:07:08 I #3000 UiProviderAdaptor On Progress Callback EventType=ProgressFinished ProgressStep=0 MaxProgress = 0 Progress Message =
  1029. 2019-01-10 09:07:08 I #3000 UiProviderAdaptor <<<<<EndUpdateDialog Title=Update FinishedEnd Message: Please check the update log for more details. CountDownMessage : Auto close in CountDownValue : 10
  1030. 2019-01-10 09:07:08 I #3000 UiProviderAdaptor
  1031. 2019-01-10 09:07:08 I #2864 msgbus Received 321 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1032. 2019-01-10 09:07:08 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1033. 2019-01-10 09:07:08 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1034. 2019-01-10 09:07:08 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1035. 2019-01-10 09:07:08 I #528 msgbus Subscriber now invoking handler...
  1036. 2019-01-10 09:07:13 I #2864 msgbus Received 368 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1037. 2019-01-10 09:07:13 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1038. 2019-01-10 09:07:13 I #2864 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
  1039. 2019-01-10 09:07:13 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1040. 2019-01-10 09:07:13 I #5684 msgbus Subscriber now invoking handler...
  1041. 2019-01-10 09:07:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1042. 2019-01-10 09:07:13 I #2864 msgbus got <EOF> on pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900>
  1043. 2019-01-10 09:07:13 I #2864 msgbus peer end connection of <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900> was terminated
  1044. 2019-01-10 09:07:13 I #2864 msgbus topic <ma.msgbus.peer_end_termination> reachability <0>
  1045. 2019-01-10 09:07:13 I #2864 loop_worker scheduled an async work request, now has 1 pending work requests
  1046. 2019-01-10 09:07:13 I #2864 msgbus searching named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900> in connection manager
  1047. 2019-01-10 09:07:13 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900> found in connection manager
  1048. 2019-01-10 09:07:13 I #2864 msgbus Removed named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900> from connection manager
  1049. 2019-01-10 09:07:13 I #2864 msgbus ma_named_pipe_connection_release, ref count <2>
  1050. 2019-01-10 09:07:13 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900> connection closed...
  1051. 2019-01-10 09:07:13 I #2864 msgbus ma_named_pipe_connection_release, ref count <2>
  1052. 2019-01-10 09:07:13 I #2864 msgbus <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_2156.00E2B0C8_3223752492_02E5E900> pipe closed completely
  1053. 2019-01-10 09:07:13 I #2864 msgbus ma_named_pipe_connection_release, ref count <1>
  1054. 2019-01-10 09:07:13 I #2864 msgbus Received topic <ma.msgbus.peer_end_termination>, matched <ma.*>
  1055. 2019-01-10 09:07:13 I #2864 msgbus Setting the auth info...
  1056. 2019-01-10 09:07:13 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1057. 2019-01-10 09:07:13 I #2864 msgbus Clean up publisher data
  1058. 2019-01-10 09:07:13 I #2864 loop_worker loop worker successfully processed a message, still 0 more to go...
  1059. 2019-01-10 09:07:13 I #5684 msgbus Subscriber now invoking handler...
  1060. 2019-01-10 09:07:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1061. 2019-01-10 09:07:13 I #2864 msgbus Received 186 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1062. 2019-01-10 09:07:13 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1063. 2019-01-10 09:07:13 I #2864 msgbus Received topic <ma.io.service.update.registry>, matched <ma.*>
  1064. 2019-01-10 09:07:13 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1065. 2019-01-10 09:07:13 I #5684 msgbus Subscriber now invoking handler...
  1066. 2019-01-10 09:07:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1067. 2019-01-10 09:07:18 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1068. 2019-01-10 09:07:18 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1069. 2019-01-10 09:08:01 I #4948 UdaterUI sending collect props command.
  1070. 2019-01-10 09:08:01 I #4948 msgbus Endpoint <ma.service.property> creation successful, reachability: <0>, timeout: <5000>, priority: <0>, thread model: <0>
  1071. 2019-01-10 09:08:01 I #4948 msgbus Endpoint <ma.service.property> option <0x10002> set, return value is <0>
  1072. 2019-01-10 09:08:01 I #4948 msgbus Endpoint <ma.service.property> option <0x10004> set, return value is <0>
  1073. 2019-01-10 09:08:01 I #4948 msgbus Endpoint <ma.service.property>, async send call...
  1074. 2019-01-10 09:08:01 I #4948 msgbus Messagebus Request object Created
  1075. 2019-01-10 09:08:01 I #4948 loop_worker scheduled an async work request, now has 1 pending work requests
  1076. 2019-01-10 09:08:01 I #4948 msgbus Endpoint <ma.service.property> succeessfully submitted request to loop worker
  1077. 2019-01-10 09:08:01 I #4948 UdaterUI Properties collect and send command initiated by monitor.
  1078. 2019-01-10 09:08:01 I #2864 msgbus uv timer data(00E2D6E0)
  1079. 2019-01-10 09:08:01 I #2864 msgbus
  1080. 2019-01-10 09:08:01 I #2864 msgbus <ma.service.property> service is not available in router
  1081. 2019-01-10 09:08:01 I #2864 msgbus Service <ma.service.property> not found in local search and reachability is <1>
  1082. 2019-01-10 09:08:01 I #2864 msgbus <ma.service.property> service lookup start, ep lookup <02E69FC8>
  1083. 2019-01-10 09:08:01 I #2864 msgbus resolve request message created source name <ma.ep.lookup.internal.0000086C.4> for service <ma.service.property>
  1084. 2019-01-10 09:08:01 I #2864 msgbus Searching broker consumer and sending the service <ma.service.property> resolve request to name service
  1085. 2019-01-10 09:08:01 I #2864 msgbus Calling lookup callback in async way with status <516> from ep lookup <02E69FC8>
  1086. 2019-01-10 09:08:01 I #2864 msgbus uv timer data(02E7E908)
  1087. 2019-01-10 09:08:01 I #2864 msgbus
  1088. 2019-01-10 09:08:01 I #2864 msgbus <ma.msgbus.name_service.service> service found in router
  1089. 2019-01-10 09:08:01 I #2864 msgbus Service <ma.msgbus.name_service.service> found in local search and status of ep lookup is <2>
  1090. 2019-01-10 09:08:01 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E71890>
  1091. 2019-01-10 09:08:01 I #2864 msgbus uv timer data(02E7E928)
  1092. 2019-01-10 09:08:01 I #2864 msgbus
  1093. 2019-01-10 09:08:01 I #2864 msgbus local broker look up succeeded for service <ma.service.property> and started timer with timeout <20000> for request <00E2D6E0>
  1094. 2019-01-10 09:08:01 I #2864 msgbus Added request object <00E2D6E0> into request manager
  1095. 2019-01-10 09:08:01 I #2864 msgbus Endpoint <ma.service.property> request successfully initiated
  1096. 2019-01-10 09:08:01 I #2864 loop_worker loop worker successfully processed a message, still 0 more to go...
  1097. 2019-01-10 09:08:01 I #2864 msgbus Message bus request <00E2D6E0> lookup cb is invoked with status <516> from ep lookup <02E69FC8>
  1098. 2019-01-10 09:08:01 I #2864 msgbus Received broker consumer, sending service <ma.service.property> pipe name request msg
  1099. 2019-01-10 09:08:01 I #2864 msgbus Adding received message into queue
  1100. 2019-01-10 09:08:01 I #2864 msgbus Sending data on connected name pipe
  1101. 2019-01-10 09:08:01 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  1102. 2019-01-10 09:08:01 I #2864 msgbus Received 462 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1103. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1104. 2019-01-10 09:08:01 I #2864 msgbus Recevied response from broker with status <0>
  1105. 2019-01-10 09:08:01 I #2864 msgbus Recevied response type <prop.value.discover_service_request> from broker
  1106. 2019-01-10 09:08:01 I #2864 msgbus Recevied info from broker, service name: <ma.service.property>
  1107. 2019-01-10 09:08:01 I #2864 msgbus pipe name: <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1108. 2019-01-10 09:08:01 I #2864 msgbus pid : <5880>
  1109. 2019-01-10 09:08:01 I #2864 msgbus ep lookup <02E71890> stop, connection status recevied <No> ref count <4>
  1110. 2019-01-10 09:08:01 I #2864 msgbus searching named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> in connection manager
  1111. 2019-01-10 09:08:01 I #2864 msgbus named pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> found in connection manager
  1112. 2019-01-10 09:08:01 I #2864 msgbus named pipe connection is already available in named pipe connection manager
  1113. 2019-01-10 09:08:01 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E69FC8>
  1114. 2019-01-10 09:08:01 I #2864 msgbus uv timer data(02E7EB08)
  1115. 2019-01-10 09:08:01 I #2864 msgbus
  1116. 2019-01-10 09:08:01 I #2864 msgbus Message bus request <00E2D6E0> lookup cb is invoked with status <0> from ep lookup <02E69FC8>
  1117. 2019-01-10 09:08:01 I #2864 msgbus Sending message to router - correlation id <5> ephemeral name buffer <ma.internal.request.0000086C.5>
  1118. 2019-01-10 09:08:01 I #2864 msgbus Adding received message into queue
  1119. 2019-01-10 09:08:01 I #2864 msgbus Sending data on connected name pipe
  1120. 2019-01-10 09:08:01 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  1121. 2019-01-10 09:08:01 I #2864 msgbus Received 153 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1122. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1123. 2019-01-10 09:08:01 I #2864 msgbus Recevied expected response to message bus request
  1124. 2019-01-10 09:08:01 I #2864 msgbus message bus request Released
  1125. 2019-01-10 09:08:01 I #2864 msgbus Invoking user callback in different thread
  1126. 2019-01-10 09:08:01 I #2864 msgbus ep lookup <02E69FC8> stop, connection status recevied <No> ref count <3>
  1127. 2019-01-10 09:08:01 I #2864 msgbus Request Object Closes
  1128. 2019-01-10 09:08:01 I #2864 msgbus message bus request Released
  1129. 2019-01-10 09:08:01 I #2864 msgbus Received 268 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1130. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1131. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1132. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1133. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1134. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1135. 2019-01-10 09:08:01 I #528 msgbus Worker callback is Invoked in msgbus request
  1136. 2019-01-10 09:08:01 I #528 msgbus Endpoint <ma.service.property> release
  1137. 2019-01-10 09:08:01 I #528 msgbus message bus request Released
  1138. 2019-01-10 09:08:01 I #2864 msgbus message bus request Released
  1139. 2019-01-10 09:08:01 I #2864 msgbus Messagebus Request object Destroys
  1140. 2019-01-10 09:08:01 I #2864 msgbus Endpoint <ma.service.property> release
  1141. 2019-01-10 09:08:01 I #2864 msgbus Endpoint <ma.service.property> destroys
  1142. 2019-01-10 09:08:01 I #528 msgbus Subscriber now invoking handler...
  1143. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1144. 2019-01-10 09:08:01 I #528 msgbus Subscriber now invoking handler...
  1145. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1146. 2019-01-10 09:08:01 I #2864 msgbus Received 298 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1147. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1148. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.property.collect>, matched <ma.*>
  1149. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1150. 2019-01-10 09:08:01 I #528 msgbus Subscriber now invoking handler...
  1151. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1152. 2019-01-10 09:08:01 I #2864 msgbus Received 186 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1153. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1154. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.io.service.update.registry>, matched <ma.*>
  1155. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1156. 2019-01-10 09:08:01 I #528 msgbus Subscriber now invoking handler...
  1157. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1158. 2019-01-10 09:08:01 I #2864 msgbus Received 276 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1159. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1160. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1161. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1162. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1163. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1164. 2019-01-10 09:08:01 I #528 msgbus Subscriber now invoking handler...
  1165. 2019-01-10 09:08:01 I #528 msgbus Subscriber now invoking handler...
  1166. 2019-01-10 09:08:01 I #2864 msgbus Received 300 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1167. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1168. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1169. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1170. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1171. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1172. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1173. 2019-01-10 09:08:01 I #3000 msgbus Subscriber now invoking handler...
  1174. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1175. 2019-01-10 09:08:01 I #3000 msgbus Subscriber now invoking handler...
  1176. 2019-01-10 09:08:01 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1177. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1178. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1179. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1180. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1181. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1182. 2019-01-10 09:08:01 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1183. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1184. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1185. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1186. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1187. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1188. 2019-01-10 09:08:01 I #5684 msgbus Subscriber now invoking handler...
  1189. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1190. 2019-01-10 09:08:01 I #5684 msgbus Subscriber now invoking handler...
  1191. 2019-01-10 09:08:01 I #6072 msgbus Subscriber now invoking handler...
  1192. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1193. 2019-01-10 09:08:01 I #2724 msgbus Subscriber now invoking handler...
  1194. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1195. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1196. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1197. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1198. 2019-01-10 09:08:01 I #2864 msgbus Received 291 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1199. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1200. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1201. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1202. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1203. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1204. 2019-01-10 09:08:01 I #2724 msgbus Subscriber now invoking handler...
  1205. 2019-01-10 09:08:01 I #2724 msgbus Subscriber now invoking handler...
  1206. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1207. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1208. 2019-01-10 09:08:01 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1209. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1210. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1211. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1212. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1213. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1214. 2019-01-10 09:08:01 I #2864 msgbus Received 816 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1215. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1216. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  1217. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1218. 2019-01-10 09:08:01 I #2724 msgbus Subscriber now invoking handler...
  1219. 2019-01-10 09:08:01 I #2724 msgbus Subscriber now invoking handler...
  1220. 2019-01-10 09:08:01 I #5684 msgbus Subscriber now invoking handler...
  1221. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1222. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1223. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1224. 2019-01-10 09:08:01 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1225. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1226. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1227. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1228. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1229. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1230. 2019-01-10 09:08:01 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1231. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1232. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1233. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1234. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1235. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1236. 2019-01-10 09:08:01 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1237. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1238. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1239. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1240. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1241. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1242. 2019-01-10 09:08:01 I #2724 msgbus Subscriber now invoking handler...
  1243. 2019-01-10 09:08:01 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1244. 2019-01-10 09:08:01 I #2724 msgbus Subscriber now invoking handler...
  1245. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1246. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1247. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1248. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1249. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1250. 2019-01-10 09:08:01 I #5684 msgbus Subscriber now invoking handler...
  1251. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1252. 2019-01-10 09:08:01 I #3000 msgbus Subscriber now invoking handler...
  1253. 2019-01-10 09:08:01 I #528 msgbus Subscriber now invoking handler...
  1254. 2019-01-10 09:08:01 I #5684 msgbus Subscriber now invoking handler...
  1255. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1256. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1257. 2019-01-10 09:08:01 I #856 msgbus Subscriber now invoking handler...
  1258. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1259. 2019-01-10 09:08:01 I #6072 msgbus Subscriber now invoking handler...
  1260. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1261. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1262. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1263. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1264. 2019-01-10 09:08:01 I #2864 msgbus Received 291 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1265. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1266. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1267. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1268. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1269. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1270. 2019-01-10 09:08:01 I #6072 msgbus Subscriber now invoking handler...
  1271. 2019-01-10 09:08:01 I #5684 msgbus Subscriber now invoking handler...
  1272. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1273. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1274. 2019-01-10 09:08:01 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1275. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1276. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1277. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1278. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1279. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1280. 2019-01-10 09:08:01 I #2864 msgbus Received 261 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1281. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1282. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1283. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1284. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1285. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1286. 2019-01-10 09:08:01 I #2864 msgbus Received 289 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1287. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1288. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1289. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1290. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1291. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1292. 2019-01-10 09:08:01 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1293. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1294. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1295. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1296. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1297. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1298. 2019-01-10 09:08:01 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1299. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1300. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1301. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1302. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1303. 2019-01-10 09:08:01 I #5684 msgbus Subscriber now invoking handler...
  1304. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1305. 2019-01-10 09:08:01 I #5684 msgbus Subscriber now invoking handler...
  1306. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1307. 2019-01-10 09:08:01 I #6072 msgbus Subscriber now invoking handler...
  1308. 2019-01-10 09:08:01 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1309. 2019-01-10 09:08:01 I #6072 msgbus Subscriber now invoking handler...
  1310. 2019-01-10 09:08:01 I #3000 msgbus Subscriber now invoking handler...
  1311. 2019-01-10 09:08:01 I #2724 msgbus Subscriber now invoking handler...
  1312. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1313. 2019-01-10 09:08:01 I #6072 msgbus Subscriber now invoking handler...
  1314. 2019-01-10 09:08:01 I #856 msgbus Subscriber now invoking handler...
  1315. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1316. 2019-01-10 09:08:01 I #528 msgbus Subscriber now invoking handler...
  1317. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1318. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1319. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1320. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1321. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1322. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1323. 2019-01-10 09:08:01 I #2864 msgbus Received 820 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1324. 2019-01-10 09:08:01 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1325. 2019-01-10 09:08:01 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  1326. 2019-01-10 09:08:01 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1327. 2019-01-10 09:08:01 I #3688 msgbus Subscriber now invoking handler...
  1328. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1329. 2019-01-10 09:08:01 I #3688 msgbus Subscriber now invoking handler...
  1330. 2019-01-10 09:08:01 I #2308 msgbus Subscriber now invoking handler...
  1331. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1332. 2019-01-10 09:08:01 I #856 msgbus Subscriber now invoking handler...
  1333. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1334. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1335. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1336. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1337. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1338. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1339. 2019-01-10 09:08:01 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1340. 2019-01-10 09:08:02 I #2864 msgbus Received 288 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1341. 2019-01-10 09:08:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1342. 2019-01-10 09:08:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1343. 2019-01-10 09:08:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1344. 2019-01-10 09:08:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1345. 2019-01-10 09:08:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1346. 2019-01-10 09:08:02 I #3688 msgbus Subscriber now invoking handler...
  1347. 2019-01-10 09:08:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1348. 2019-01-10 09:08:02 I #528 msgbus Subscriber now invoking handler...
  1349. 2019-01-10 09:08:02 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1350. 2019-01-10 09:08:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1351. 2019-01-10 09:08:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1352. 2019-01-10 09:08:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1353. 2019-01-10 09:08:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1354. 2019-01-10 09:08:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1355. 2019-01-10 09:08:02 I #3688 msgbus Subscriber now invoking handler...
  1356. 2019-01-10 09:08:02 I #3688 msgbus Subscriber now invoking handler...
  1357. 2019-01-10 09:08:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1358. 2019-01-10 09:08:02 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1359. 2019-01-10 09:08:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1360. 2019-01-10 09:08:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1361. 2019-01-10 09:08:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1362. 2019-01-10 09:08:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1363. 2019-01-10 09:08:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1364. 2019-01-10 09:08:02 I #2864 msgbus Received 818 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1365. 2019-01-10 09:08:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1366. 2019-01-10 09:08:02 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  1367. 2019-01-10 09:08:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1368. 2019-01-10 09:08:02 I #2724 msgbus Subscriber now invoking handler...
  1369. 2019-01-10 09:08:02 I #6072 msgbus Subscriber now invoking handler...
  1370. 2019-01-10 09:08:02 I #3000 msgbus Subscriber now invoking handler...
  1371. 2019-01-10 09:08:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1372. 2019-01-10 09:08:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1373. 2019-01-10 09:08:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1374. 2019-01-10 09:08:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1375. 2019-01-10 09:08:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1376. 2019-01-10 09:09:02 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1377. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1378. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1379. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1380. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1381. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1382. 2019-01-10 09:09:02 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1383. 2019-01-10 09:09:02 I #2724 msgbus Subscriber now invoking handler...
  1384. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1385. 2019-01-10 09:09:02 I #2724 msgbus Subscriber now invoking handler...
  1386. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1387. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1388. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1389. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1390. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1391. 2019-01-10 09:09:02 I #3688 msgbus Subscriber now invoking handler...
  1392. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1393. 2019-01-10 09:09:02 I #528 msgbus Subscriber now invoking handler...
  1394. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1395. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1396. 2019-01-10 09:09:02 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1397. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1398. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1399. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1400. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1401. 2019-01-10 09:09:02 I #528 msgbus Subscriber now invoking handler...
  1402. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1403. 2019-01-10 09:09:02 I #528 msgbus Subscriber now invoking handler...
  1404. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1405. 2019-01-10 09:09:02 I #2864 msgbus Received 818 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1406. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1407. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  1408. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1409. 2019-01-10 09:09:02 I #2724 msgbus Subscriber now invoking handler...
  1410. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1411. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1412. 2019-01-10 09:09:02 I #2864 msgbus Received 3225 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1413. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1414. 2019-01-10 09:09:02 I #2864 msgbus Received 328 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1415. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1416. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1417. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1418. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1419. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1420. 2019-01-10 09:09:02 I #528 msgbus Subscriber now invoking handler...
  1421. 2019-01-10 09:09:02 I #2864 msgbus Received 305 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1422. 2019-01-10 09:09:02 I #528 msgbus Subscriber now invoking handler...
  1423. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1424. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1425. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1426. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1427. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1428. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1429. 2019-01-10 09:09:02 I #2724 msgbus Subscriber now invoking handler...
  1430. 2019-01-10 09:09:02 I #2724 msgbus Subscriber now invoking handler...
  1431. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1432. 2019-01-10 09:09:02 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1433. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1434. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1435. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1436. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1437. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1438. 2019-01-10 09:09:02 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1439. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1440. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1441. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1442. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1443. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1444. 2019-01-10 09:09:02 I #3688 msgbus Subscriber now invoking handler...
  1445. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1446. 2019-01-10 09:09:02 I #3688 msgbus Subscriber now invoking handler...
  1447. 2019-01-10 09:09:02 I #3000 msgbus Subscriber now invoking handler...
  1448. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1449. 2019-01-10 09:09:02 I #3000 msgbus Subscriber now invoking handler...
  1450. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1451. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1452. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1453. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1454. 2019-01-10 09:09:02 I #2864 msgbus Received 302 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1455. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1456. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1457. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1458. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1459. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1460. 2019-01-10 09:09:02 I #3000 msgbus Subscriber now invoking handler...
  1461. 2019-01-10 09:09:02 I #3000 msgbus Subscriber now invoking handler...
  1462. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1463. 2019-01-10 09:09:02 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1464. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1465. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1466. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1467. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1468. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1469. 2019-01-10 09:09:02 I #2864 msgbus Received 817 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1470. 2019-01-10 09:09:02 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1471. 2019-01-10 09:09:02 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  1472. 2019-01-10 09:09:02 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1473. 2019-01-10 09:09:02 I #3688 msgbus Subscriber now invoking handler...
  1474. 2019-01-10 09:09:02 I #3688 msgbus Subscriber now invoking handler...
  1475. 2019-01-10 09:09:02 I #2724 msgbus Subscriber now invoking handler...
  1476. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1477. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1478. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1479. 2019-01-10 09:09:02 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1480. 2019-01-10 09:09:05 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1481. 2019-01-10 09:09:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1482. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1483. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1484. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1485. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1486. 2019-01-10 09:09:05 I #2864 msgbus Received 306 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1487. 2019-01-10 09:09:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1488. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1489. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1490. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1491. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1492. 2019-01-10 09:09:05 I #2864 msgbus Received 2004 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1493. 2019-01-10 09:09:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1494. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.task.execute>, matched <ma.*>
  1495. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1496. 2019-01-10 09:09:05 I #3688 msgbus Subscriber now invoking handler...
  1497. 2019-01-10 09:09:05 I #3688 msgbus Subscriber now invoking handler...
  1498. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1499. 2019-01-10 09:09:05 I #3000 msgbus Subscriber now invoking handler...
  1500. 2019-01-10 09:09:05 I #528 msgbus Subscriber now invoking handler...
  1501. 2019-01-10 09:09:05 I #2724 msgbus Subscriber now invoking handler...
  1502. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1503. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1504. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1505. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1506. 2019-01-10 09:09:05 I #2864 msgbus Received 305 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1507. 2019-01-10 09:09:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1508. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1509. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1510. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1511. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1512. 2019-01-10 09:09:05 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1513. 2019-01-10 09:09:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1514. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1515. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1516. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1517. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1518. 2019-01-10 09:09:05 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1519. 2019-01-10 09:09:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1520. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1521. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1522. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1523. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1524. 2019-01-10 09:09:05 I #2724 msgbus Subscriber now invoking handler...
  1525. 2019-01-10 09:09:05 I #2724 msgbus Subscriber now invoking handler...
  1526. 2019-01-10 09:09:05 I #3688 msgbus Subscriber now invoking handler...
  1527. 2019-01-10 09:09:05 I #2724 msgbus Subscriber now invoking handler...
  1528. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1529. 2019-01-10 09:09:05 I #528 msgbus Subscriber now invoking handler...
  1530. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1531. 2019-01-10 09:09:05 I #528 msgbus Subscriber now invoking handler...
  1532. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1533. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1534. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1535. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1536. 2019-01-10 09:09:05 I #2864 msgbus Received 302 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1537. 2019-01-10 09:09:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1538. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1539. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1540. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1541. 2019-01-10 09:09:05 I #528 msgbus Subscriber now invoking handler...
  1542. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1543. 2019-01-10 09:09:05 I #528 msgbus Subscriber now invoking handler...
  1544. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1545. 2019-01-10 09:09:05 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1546. 2019-01-10 09:09:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1547. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1548. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1549. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1550. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1551. 2019-01-10 09:09:05 I #2724 msgbus Subscriber now invoking handler...
  1552. 2019-01-10 09:09:05 I #2724 msgbus Subscriber now invoking handler...
  1553. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1554. 2019-01-10 09:09:05 I #2864 msgbus Received 366 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1555. 2019-01-10 09:09:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1556. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
  1557. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1558. 2019-01-10 09:09:05 I #3688 msgbus Subscriber now invoking handler...
  1559. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1560. 2019-01-10 09:09:05 I #2864 msgbus Received 817 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1561. 2019-01-10 09:09:05 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1562. 2019-01-10 09:09:05 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  1563. 2019-01-10 09:09:05 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1564. 2019-01-10 09:09:05 I #3688 msgbus Subscriber now invoking handler...
  1565. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1566. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1567. 2019-01-10 09:09:05 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1568. 2019-01-10 09:09:06 I #2864 msgbus Received 357 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1569. 2019-01-10 09:09:06 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1570. 2019-01-10 09:09:06 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1571. 2019-01-10 09:09:06 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1572. 2019-01-10 09:09:06 I #2724 msgbus Subscriber now invoking handler...
  1573. 2019-01-10 09:09:06 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=1, MaxProgress = 0, Progress Message = Checking update packages from repository ePO_UK-VM-AV1.
  1574. 2019-01-10 09:09:06 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=1 MaxProgress = 0 Progress Message = Checking update packages from repository ePO_UK-VM-AV1.
  1575. 2019-01-10 09:09:06 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1576. 2019-01-10 09:09:06 I #2864 msgbus Received 323 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1577. 2019-01-10 09:09:06 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1578. 2019-01-10 09:09:06 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1579. 2019-01-10 09:09:06 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1580. 2019-01-10 09:09:06 I #2724 msgbus Subscriber now invoking handler...
  1581. 2019-01-10 09:09:06 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressStart , ProgressStep=20, MaxProgress = 1, Progress Message = Initializing update...
  1582. 2019-01-10 09:09:06 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressStart ProgressStep=20 MaxProgress = 1 Progress Message = Initializing update...
  1583. 2019-01-10 09:09:06 I #2864 msgbus Received 321 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1584. 2019-01-10 09:09:06 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1585. 2019-01-10 09:09:06 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1586. 2019-01-10 09:09:06 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1587. 2019-01-10 09:09:06 I #528 msgbus Subscriber now invoking handler...
  1588. 2019-01-10 09:09:06 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=3, MaxProgress = 0, Progress Message = Verifying catalog.z.
  1589. 2019-01-10 09:09:06 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=3 MaxProgress = 0 Progress Message = Verifying catalog.z.
  1590. 2019-01-10 09:09:06 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1591. 2019-01-10 09:09:06 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1592. 2019-01-10 09:09:06 I #2864 msgbus Received 322 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1593. 2019-01-10 09:09:06 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1594. 2019-01-10 09:09:06 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1595. 2019-01-10 09:09:06 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1596. 2019-01-10 09:09:06 I #528 msgbus Subscriber now invoking handler...
  1597. 2019-01-10 09:09:06 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=4, MaxProgress = 0, Progress Message = Extracting catalog.z.
  1598. 2019-01-10 09:09:06 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=4 MaxProgress = 0 Progress Message = Extracting catalog.z.
  1599. 2019-01-10 09:09:06 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1600. 2019-01-10 09:09:06 I #2864 msgbus Received 348 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1601. 2019-01-10 09:09:06 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1602. 2019-01-10 09:09:06 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1603. 2019-01-10 09:09:06 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1604. 2019-01-10 09:09:06 I #528 msgbus Subscriber now invoking handler...
  1605. 2019-01-10 09:09:06 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=5, MaxProgress = 0, Progress Message = Loading update configuration from: catalog.xml
  1606. 2019-01-10 09:09:06 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=5 MaxProgress = 0 Progress Message = Loading update configuration from: catalog.xml
  1607. 2019-01-10 09:09:06 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1608. 2019-01-10 09:09:07 I #2864 msgbus Received 334 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1609. 2019-01-10 09:09:07 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1610. 2019-01-10 09:09:07 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1611. 2019-01-10 09:09:07 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1612. 2019-01-10 09:09:07 I #528 msgbus Subscriber now invoking handler...
  1613. 2019-01-10 09:09:07 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=5, MaxProgress = 0, Progress Message = Checking for software conflicts.
  1614. 2019-01-10 09:09:07 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=5 MaxProgress = 0 Progress Message = Checking for software conflicts.
  1615. 2019-01-10 09:09:07 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1616. 2019-01-10 09:09:07 I #2864 msgbus Received 356 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1617. 2019-01-10 09:09:07 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1618. 2019-01-10 09:09:07 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1619. 2019-01-10 09:09:07 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1620. 2019-01-10 09:09:07 I #528 msgbus Subscriber now invoking handler...
  1621. 2019-01-10 09:09:07 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=6, MaxProgress = 0, Progress Message = Product Conflict: EPOAGENT3000 will not be installed.
  1622. 2019-01-10 09:09:07 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=6 MaxProgress = 0 Progress Message = Product Conflict: EPOAGENT3000 will not be installed.
  1623. 2019-01-10 09:09:07 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1624. 2019-01-10 09:09:07 I #2864 msgbus Received 356 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1625. 2019-01-10 09:09:07 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1626. 2019-01-10 09:09:07 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1627. 2019-01-10 09:09:07 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1628. 2019-01-10 09:09:07 I #2864 msgbus Received 325 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1629. 2019-01-10 09:09:07 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1630. 2019-01-10 09:09:07 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1631. 2019-01-10 09:09:07 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1632. 2019-01-10 09:09:07 I #528 msgbus Subscriber now invoking handler...
  1633. 2019-01-10 09:09:07 I #528 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=6, MaxProgress = 0, Progress Message = Product Conflict: ENDP_AM_1050 will not be installed.
  1634. 2019-01-10 09:09:07 I #528 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=6 MaxProgress = 0 Progress Message = Product Conflict: ENDP_AM_1050 will not be installed.
  1635. 2019-01-10 09:09:07 I #2724 msgbus Subscriber now invoking handler...
  1636. 2019-01-10 09:09:07 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying CommonDet.mcs.
  1637. 2019-01-10 09:09:07 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1638. 2019-01-10 09:09:07 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying CommonDet.mcs.
  1639. 2019-01-10 09:09:07 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1640. 2019-01-10 09:09:08 I #2864 msgbus Received 325 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1641. 2019-01-10 09:09:08 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1642. 2019-01-10 09:09:08 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1643. 2019-01-10 09:09:08 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1644. 2019-01-10 09:09:08 I #2724 msgbus Subscriber now invoking handler...
  1645. 2019-01-10 09:09:08 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying CommonDet.mcs.
  1646. 2019-01-10 09:09:08 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying CommonDet.mcs.
  1647. 2019-01-10 09:09:08 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1648. 2019-01-10 09:09:08 I #2864 msgbus Received 316 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1649. 2019-01-10 09:09:08 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1650. 2019-01-10 09:09:08 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1651. 2019-01-10 09:09:08 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1652. 2019-01-10 09:09:08 I #2724 msgbus Subscriber now invoking handler...
  1653. 2019-01-10 09:09:08 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressFinished, ProgressStep=0, MaxProgress = 0, Progress Message = Update Finished
  1654. 2019-01-10 09:09:08 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressFinished ProgressStep=0 MaxProgress = 0 Progress Message = Update Finished
  1655. 2019-01-10 09:09:08 I #2864 msgbus Received 335 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1656. 2019-01-10 09:09:08 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1657. 2019-01-10 09:09:08 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1658. 2019-01-10 09:09:08 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1659. 2019-01-10 09:09:08 I #528 msgbus Subscriber now invoking handler...
  1660. 2019-01-10 09:09:08 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1661. 2019-01-10 09:09:08 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1662. 2019-01-10 09:09:13 I #2864 msgbus Received 368 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1663. 2019-01-10 09:09:13 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1664. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
  1665. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1666. 2019-01-10 09:09:13 I #528 msgbus Subscriber now invoking handler...
  1667. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1668. 2019-01-10 09:09:13 I #2864 msgbus Received 305 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1669. 2019-01-10 09:09:13 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1670. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1671. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1672. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1673. 2019-01-10 09:09:13 I #528 msgbus Subscriber now invoking handler...
  1674. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1675. 2019-01-10 09:09:13 I #528 msgbus Subscriber now invoking handler...
  1676. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1677. 2019-01-10 09:09:13 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1678. 2019-01-10 09:09:13 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1679. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1680. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1681. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1682. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1683. 2019-01-10 09:09:13 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1684. 2019-01-10 09:09:13 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1685. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1686. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1687. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1688. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1689. 2019-01-10 09:09:13 I #2724 msgbus Subscriber now invoking handler...
  1690. 2019-01-10 09:09:13 I #2724 msgbus Subscriber now invoking handler...
  1691. 2019-01-10 09:09:13 I #3688 msgbus Subscriber now invoking handler...
  1692. 2019-01-10 09:09:13 I #3688 msgbus Subscriber now invoking handler...
  1693. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1694. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1695. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1696. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1697. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1698. 2019-01-10 09:09:13 I #2864 msgbus Received 302 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1699. 2019-01-10 09:09:13 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1700. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1701. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1702. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1703. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1704. 2019-01-10 09:09:13 I #3688 msgbus Subscriber now invoking handler...
  1705. 2019-01-10 09:09:13 I #3688 msgbus Subscriber now invoking handler...
  1706. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1707. 2019-01-10 09:09:13 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1708. 2019-01-10 09:09:13 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1709. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1710. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1711. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1712. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1713. 2019-01-10 09:09:13 I #2724 msgbus Subscriber now invoking handler...
  1714. 2019-01-10 09:09:13 I #2724 msgbus Subscriber now invoking handler...
  1715. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1716. 2019-01-10 09:09:13 I #2864 msgbus Received 817 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1717. 2019-01-10 09:09:13 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1718. 2019-01-10 09:09:13 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  1719. 2019-01-10 09:09:13 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1720. 2019-01-10 09:09:13 I #528 msgbus Subscriber now invoking handler...
  1721. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1722. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1723. 2019-01-10 09:09:13 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1724. 2019-01-10 09:09:14 I #2864 msgbus Received 305 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1725. 2019-01-10 09:09:14 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1726. 2019-01-10 09:09:14 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1727. 2019-01-10 09:09:14 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1728. 2019-01-10 09:09:14 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1729. 2019-01-10 09:09:14 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1730. 2019-01-10 09:09:14 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1731. 2019-01-10 09:09:14 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1732. 2019-01-10 09:09:14 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1733. 2019-01-10 09:09:14 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1734. 2019-01-10 09:09:14 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1735. 2019-01-10 09:09:14 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1736. 2019-01-10 09:09:14 I #2724 msgbus Subscriber now invoking handler...
  1737. 2019-01-10 09:09:14 I #2724 msgbus Subscriber now invoking handler...
  1738. 2019-01-10 09:09:14 I #3688 msgbus Subscriber now invoking handler...
  1739. 2019-01-10 09:09:14 I #3688 msgbus Subscriber now invoking handler...
  1740. 2019-01-10 09:09:14 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1741. 2019-01-10 09:09:14 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1742. 2019-01-10 09:09:14 I #2864 msgbus Received 2003 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1743. 2019-01-10 09:09:14 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1744. 2019-01-10 09:09:14 I #2864 msgbus Received topic <ma.task.remove>, matched <ma.*>
  1745. 2019-01-10 09:09:14 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1746. 2019-01-10 09:09:14 I #2864 msgbus Received 300 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1747. 2019-01-10 09:09:14 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1748. 2019-01-10 09:09:14 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1749. 2019-01-10 09:09:14 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1750. 2019-01-10 09:09:14 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1751. 2019-01-10 09:09:14 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1752. 2019-01-10 09:09:14 I #3000 msgbus Subscriber now invoking handler...
  1753. 2019-01-10 09:09:14 I #3000 msgbus Subscriber now invoking handler...
  1754. 2019-01-10 09:09:14 I #528 msgbus Subscriber now invoking handler...
  1755. 2019-01-10 09:09:14 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1756. 2019-01-10 09:09:14 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1757. 2019-01-10 09:09:14 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1758. 2019-01-10 09:09:14 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1759. 2019-01-10 09:09:14 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1760. 2019-01-10 09:15:31 I #2864 msgbus Received 1177 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1761. 2019-01-10 09:15:31 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1762. 2019-01-10 09:15:31 I #2864 msgbus Received topic <ma.task.execute>, matched <ma.*>
  1763. 2019-01-10 09:15:31 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1764. 2019-01-10 09:15:31 I #3000 msgbus Subscriber now invoking handler...
  1765. 2019-01-10 09:15:31 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1766. 2019-01-10 09:15:32 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1767. 2019-01-10 09:15:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1768. 2019-01-10 09:15:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1769. 2019-01-10 09:15:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1770. 2019-01-10 09:15:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1771. 2019-01-10 09:15:32 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1772. 2019-01-10 09:15:32 I #3000 msgbus Subscriber now invoking handler...
  1773. 2019-01-10 09:15:32 I #3000 msgbus Subscriber now invoking handler...
  1774. 2019-01-10 09:15:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1775. 2019-01-10 09:15:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1776. 2019-01-10 09:22:38 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1777. 2019-01-10 09:22:38 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1778. 2019-01-10 09:22:38 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1779. 2019-01-10 09:22:38 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1780. 2019-01-10 09:22:38 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1781. 2019-01-10 09:22:38 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1782. 2019-01-10 09:22:38 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1783. 2019-01-10 09:22:38 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1784. 2019-01-10 09:22:38 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1785. 2019-01-10 09:22:38 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1786. 2019-01-10 09:22:38 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1787. 2019-01-10 09:22:38 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1788. 2019-01-10 09:22:38 I #3000 msgbus Subscriber now invoking handler...
  1789. 2019-01-10 09:22:38 I #3000 msgbus Subscriber now invoking handler...
  1790. 2019-01-10 09:22:38 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1791. 2019-01-10 09:22:38 I #3688 msgbus Subscriber now invoking handler...
  1792. 2019-01-10 09:22:38 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1793. 2019-01-10 09:22:38 I #3688 msgbus Subscriber now invoking handler...
  1794. 2019-01-10 09:22:38 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1795. 2019-01-10 09:22:38 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1796. 2019-01-10 09:22:39 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1797. 2019-01-10 09:22:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1798. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1799. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1800. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1801. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1802. 2019-01-10 09:22:39 I #2864 msgbus Received 818 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1803. 2019-01-10 09:22:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1804. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  1805. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1806. 2019-01-10 09:22:39 I #3000 msgbus Subscriber now invoking handler...
  1807. 2019-01-10 09:22:39 I #3688 msgbus Subscriber now invoking handler...
  1808. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1809. 2019-01-10 09:22:39 I #3688 msgbus Subscriber now invoking handler...
  1810. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1811. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1812. 2019-01-10 09:22:39 I #2864 msgbus Received 3225 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1813. 2019-01-10 09:22:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1814. 2019-01-10 09:22:39 I #2864 msgbus Received 328 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1815. 2019-01-10 09:22:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1816. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1817. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1818. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1819. 2019-01-10 09:22:39 I #3000 msgbus Subscriber now invoking handler...
  1820. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1821. 2019-01-10 09:22:39 I #3000 msgbus Subscriber now invoking handler...
  1822. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1823. 2019-01-10 09:22:39 I #2864 msgbus Received 305 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1824. 2019-01-10 09:22:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1825. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1826. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1827. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1828. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1829. 2019-01-10 09:22:39 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1830. 2019-01-10 09:22:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1831. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1832. 2019-01-10 09:22:39 I #2724 msgbus Subscriber now invoking handler...
  1833. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1834. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1835. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1836. 2019-01-10 09:22:39 I #6072 msgbus Subscriber now invoking handler...
  1837. 2019-01-10 09:22:39 I #6072 msgbus Subscriber now invoking handler...
  1838. 2019-01-10 09:22:39 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1839. 2019-01-10 09:22:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1840. 2019-01-10 09:22:39 I #3688 msgbus Subscriber now invoking handler...
  1841. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1842. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1843. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1844. 2019-01-10 09:22:39 I #528 msgbus Subscriber now invoking handler...
  1845. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1846. 2019-01-10 09:22:39 I #528 msgbus Subscriber now invoking handler...
  1847. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1848. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1849. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1850. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1851. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1852. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1853. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1854. 2019-01-10 09:22:39 I #2864 msgbus Received 302 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1855. 2019-01-10 09:22:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1856. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1857. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1858. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1859. 2019-01-10 09:22:39 I #528 msgbus Subscriber now invoking handler...
  1860. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1861. 2019-01-10 09:22:39 I #528 msgbus Subscriber now invoking handler...
  1862. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1863. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1864. 2019-01-10 09:22:39 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1865. 2019-01-10 09:22:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1866. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1867. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1868. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1869. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1870. 2019-01-10 09:22:39 I #2864 msgbus Received 817 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1871. 2019-01-10 09:22:39 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1872. 2019-01-10 09:22:39 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  1873. 2019-01-10 09:22:39 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1874. 2019-01-10 09:22:39 I #528 msgbus Subscriber now invoking handler...
  1875. 2019-01-10 09:22:39 I #528 msgbus Subscriber now invoking handler...
  1876. 2019-01-10 09:22:39 I #3688 msgbus Subscriber now invoking handler...
  1877. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1878. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1879. 2019-01-10 09:22:39 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1880. 2019-01-10 09:22:42 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1881. 2019-01-10 09:22:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1882. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1883. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1884. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1885. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1886. 2019-01-10 09:22:42 I #2864 msgbus Received 306 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1887. 2019-01-10 09:22:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1888. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1889. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1890. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1891. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1892. 2019-01-10 09:22:42 I #2864 msgbus Received 2004 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1893. 2019-01-10 09:22:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1894. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.task.execute>, matched <ma.*>
  1895. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1896. 2019-01-10 09:22:42 I #3688 msgbus Subscriber now invoking handler...
  1897. 2019-01-10 09:22:42 I #3688 msgbus Subscriber now invoking handler...
  1898. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1899. 2019-01-10 09:22:42 I #528 msgbus Subscriber now invoking handler...
  1900. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1901. 2019-01-10 09:22:42 I #528 msgbus Subscriber now invoking handler...
  1902. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1903. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1904. 2019-01-10 09:22:42 I #6072 msgbus Subscriber now invoking handler...
  1905. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1906. 2019-01-10 09:22:42 I #2864 msgbus Received 305 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1907. 2019-01-10 09:22:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1908. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1909. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1910. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1911. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1912. 2019-01-10 09:22:42 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1913. 2019-01-10 09:22:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1914. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1915. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1916. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1917. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1918. 2019-01-10 09:22:42 I #6072 msgbus Subscriber now invoking handler...
  1919. 2019-01-10 09:22:42 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1920. 2019-01-10 09:22:42 I #6072 msgbus Subscriber now invoking handler...
  1921. 2019-01-10 09:22:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1922. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1923. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1924. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1925. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1926. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1927. 2019-01-10 09:22:42 I #6072 msgbus Subscriber now invoking handler...
  1928. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1929. 2019-01-10 09:22:42 I #6072 msgbus Subscriber now invoking handler...
  1930. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1931. 2019-01-10 09:22:42 I #6072 msgbus Subscriber now invoking handler...
  1932. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1933. 2019-01-10 09:22:42 I #6072 msgbus Subscriber now invoking handler...
  1934. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1935. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1936. 2019-01-10 09:22:42 I #2864 msgbus Received 302 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1937. 2019-01-10 09:22:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1938. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1939. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1940. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1941. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1942. 2019-01-10 09:22:42 I #2724 msgbus Subscriber now invoking handler...
  1943. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1944. 2019-01-10 09:22:42 I #2724 msgbus Subscriber now invoking handler...
  1945. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1946. 2019-01-10 09:22:42 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1947. 2019-01-10 09:22:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1948. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  1949. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1950. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  1951. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  1952. 2019-01-10 09:22:42 I #2864 msgbus Received 817 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1953. 2019-01-10 09:22:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1954. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  1955. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1956. 2019-01-10 09:22:42 I #2864 msgbus Received 366 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1957. 2019-01-10 09:22:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1958. 2019-01-10 09:22:42 I #2864 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
  1959. 2019-01-10 09:22:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1960. 2019-01-10 09:22:42 I #2724 msgbus Subscriber now invoking handler...
  1961. 2019-01-10 09:22:42 I #2724 msgbus Subscriber now invoking handler...
  1962. 2019-01-10 09:22:42 I #6072 msgbus Subscriber now invoking handler...
  1963. 2019-01-10 09:22:42 I #6072 msgbus Subscriber now invoking handler...
  1964. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1965. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1966. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1967. 2019-01-10 09:22:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1968. 2019-01-10 09:22:45 I #2864 msgbus Received 357 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1969. 2019-01-10 09:22:45 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1970. 2019-01-10 09:22:45 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1971. 2019-01-10 09:22:45 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1972. 2019-01-10 09:22:45 I #2724 msgbus Subscriber now invoking handler...
  1973. 2019-01-10 09:22:45 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=1, MaxProgress = 0, Progress Message = Checking update packages from repository ePO_UK-VM-AV1.
  1974. 2019-01-10 09:22:45 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=1 MaxProgress = 0 Progress Message = Checking update packages from repository ePO_UK-VM-AV1.
  1975. 2019-01-10 09:22:45 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1976. 2019-01-10 09:22:46 I #2864 msgbus Received 323 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1977. 2019-01-10 09:22:46 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1978. 2019-01-10 09:22:46 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1979. 2019-01-10 09:22:46 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1980. 2019-01-10 09:22:46 I #2724 msgbus Subscriber now invoking handler...
  1981. 2019-01-10 09:22:46 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressStart , ProgressStep=20, MaxProgress = 1, Progress Message = Initializing update...
  1982. 2019-01-10 09:22:46 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressStart ProgressStep=20 MaxProgress = 1 Progress Message = Initializing update...
  1983. 2019-01-10 09:22:46 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1984. 2019-01-10 09:22:46 I #2864 msgbus Received 321 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1985. 2019-01-10 09:22:46 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1986. 2019-01-10 09:22:46 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1987. 2019-01-10 09:22:46 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1988. 2019-01-10 09:22:46 I #2724 msgbus Subscriber now invoking handler...
  1989. 2019-01-10 09:22:46 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=3, MaxProgress = 0, Progress Message = Verifying catalog.z.
  1990. 2019-01-10 09:22:46 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=3 MaxProgress = 0 Progress Message = Verifying catalog.z.
  1991. 2019-01-10 09:22:46 I #2864 msgbus After Worker callback is Invoked in Subscriber
  1992. 2019-01-10 09:22:46 I #2864 msgbus Received 322 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  1993. 2019-01-10 09:22:46 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  1994. 2019-01-10 09:22:46 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  1995. 2019-01-10 09:22:46 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  1996. 2019-01-10 09:22:46 I #2724 msgbus Subscriber now invoking handler...
  1997. 2019-01-10 09:22:46 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=4, MaxProgress = 0, Progress Message = Extracting catalog.z.
  1998. 2019-01-10 09:22:46 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=4 MaxProgress = 0 Progress Message = Extracting catalog.z.
  1999. 2019-01-10 09:22:46 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2000. 2019-01-10 09:22:46 I #2864 msgbus Received 348 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2001. 2019-01-10 09:22:46 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2002. 2019-01-10 09:22:46 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2003. 2019-01-10 09:22:46 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2004. 2019-01-10 09:22:46 I #2724 msgbus Subscriber now invoking handler...
  2005. 2019-01-10 09:22:46 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=5, MaxProgress = 0, Progress Message = Loading update configuration from: catalog.xml
  2006. 2019-01-10 09:22:46 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=5 MaxProgress = 0 Progress Message = Loading update configuration from: catalog.xml
  2007. 2019-01-10 09:22:46 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2008. 2019-01-10 09:22:47 I #2864 msgbus Received 334 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2009. 2019-01-10 09:22:47 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2010. 2019-01-10 09:22:47 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2011. 2019-01-10 09:22:47 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2012. 2019-01-10 09:22:47 I #2724 msgbus Subscriber now invoking handler...
  2013. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=5, MaxProgress = 0, Progress Message = Checking for software conflicts.
  2014. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=5 MaxProgress = 0 Progress Message = Checking for software conflicts.
  2015. 2019-01-10 09:22:47 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2016. 2019-01-10 09:22:47 I #2864 msgbus Received 356 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2017. 2019-01-10 09:22:47 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2018. 2019-01-10 09:22:47 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2019. 2019-01-10 09:22:47 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2020. 2019-01-10 09:22:47 I #2724 msgbus Subscriber now invoking handler...
  2021. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=6, MaxProgress = 0, Progress Message = Product Conflict: EPOAGENT3000 will not be installed.
  2022. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=6 MaxProgress = 0 Progress Message = Product Conflict: EPOAGENT3000 will not be installed.
  2023. 2019-01-10 09:22:47 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2024. 2019-01-10 09:22:47 I #2864 msgbus Received 356 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2025. 2019-01-10 09:22:47 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2026. 2019-01-10 09:22:47 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2027. 2019-01-10 09:22:47 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2028. 2019-01-10 09:22:47 I #2724 msgbus Subscriber now invoking handler...
  2029. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=6, MaxProgress = 0, Progress Message = Product Conflict: ENDP_AM_1050 will not be installed.
  2030. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=6 MaxProgress = 0 Progress Message = Product Conflict: ENDP_AM_1050 will not be installed.
  2031. 2019-01-10 09:22:47 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2032. 2019-01-10 09:22:47 I #2864 msgbus Received 325 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2033. 2019-01-10 09:22:47 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2034. 2019-01-10 09:22:47 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2035. 2019-01-10 09:22:47 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2036. 2019-01-10 09:22:47 I #2724 msgbus Subscriber now invoking handler...
  2037. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying CommonDet.mcs.
  2038. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying CommonDet.mcs.
  2039. 2019-01-10 09:22:47 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2040. 2019-01-10 09:22:47 I #4948 UpdaterUI Received shutdown notification
  2041. 2019-01-10 09:22:47 I #4948 UpdaterUI Successfully blocked shutdown
  2042. 2019-01-10 09:22:47 I #2864 msgbus Received 325 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2043. 2019-01-10 09:22:47 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2044. 2019-01-10 09:22:47 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2045. 2019-01-10 09:22:47 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2046. 2019-01-10 09:22:47 I #2724 msgbus Subscriber now invoking handler...
  2047. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying CommonDet.mcs.
  2048. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying CommonDet.mcs.
  2049. 2019-01-10 09:22:47 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2050. 2019-01-10 09:22:47 I #2864 msgbus Received 316 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2051. 2019-01-10 09:22:47 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2052. 2019-01-10 09:22:47 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2053. 2019-01-10 09:22:47 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2054. 2019-01-10 09:22:47 I #2724 msgbus Subscriber now invoking handler...
  2055. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressFinished, ProgressStep=0, MaxProgress = 0, Progress Message = Update Finished
  2056. 2019-01-10 09:22:47 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressFinished ProgressStep=0 MaxProgress = 0 Progress Message = Update Finished
  2057. 2019-01-10 09:22:47 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2058. 2019-01-10 09:22:47 I #2864 msgbus Received 335 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2059. 2019-01-10 09:22:47 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2060. 2019-01-10 09:22:47 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2061. 2019-01-10 09:22:47 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2062. 2019-01-10 09:22:47 I #2724 msgbus Subscriber now invoking handler...
  2063. 2019-01-10 09:22:47 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2064. 2019-01-10 09:22:52 I #4948 UpdaterUI Received shutdown notification
  2065. 2019-01-10 09:22:52 I #4948 UpdaterUI unblocked shutdown
  2066. 2019-01-10 09:22:52 I #2864 msgbus Received 368 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2067. 2019-01-10 09:22:52 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2068. 2019-01-10 09:22:52 I #2864 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
  2069. 2019-01-10 09:22:52 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2070. 2019-01-10 09:22:52 I #2724 msgbus Subscriber now invoking handler...
  2071. 2019-01-10 09:22:52 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2072. 2019-01-10 09:22:53 I #2864 msgbus Received 305 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2073. 2019-01-10 09:22:53 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2074. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2075. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2076. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2077. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2078. 2019-01-10 09:22:53 I #2724 msgbus Subscriber now invoking handler...
  2079. 2019-01-10 09:22:53 I #2724 msgbus Subscriber now invoking handler...
  2080. 2019-01-10 09:22:53 I #2864 msgbus Received 283 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2081. 2019-01-10 09:22:53 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2082. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2083. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2084. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2085. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2086. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2087. 2019-01-10 09:22:53 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2088. 2019-01-10 09:22:53 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2089. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2090. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2091. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2092. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2093. 2019-01-10 09:22:53 I #528 msgbus Subscriber now invoking handler...
  2094. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2095. 2019-01-10 09:22:53 I #528 msgbus Subscriber now invoking handler...
  2096. 2019-01-10 09:22:53 I #3688 msgbus Subscriber now invoking handler...
  2097. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2098. 2019-01-10 09:22:53 I #6072 msgbus Subscriber now invoking handler...
  2099. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2100. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2101. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2102. 2019-01-10 09:22:53 I #2864 msgbus Received 302 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2103. 2019-01-10 09:22:53 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2104. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2105. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2106. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2107. 2019-01-10 09:22:53 I #528 msgbus Subscriber now invoking handler...
  2108. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2109. 2019-01-10 09:22:53 I #528 msgbus Subscriber now invoking handler...
  2110. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2111. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2112. 2019-01-10 09:22:53 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2113. 2019-01-10 09:22:53 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2114. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2115. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2116. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2117. 2019-01-10 09:22:53 I #528 msgbus Subscriber now invoking handler...
  2118. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2119. 2019-01-10 09:22:53 I #528 msgbus Subscriber now invoking handler...
  2120. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2121. 2019-01-10 09:22:53 I #2864 msgbus Received 817 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2122. 2019-01-10 09:22:53 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2123. 2019-01-10 09:22:53 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  2124. 2019-01-10 09:22:53 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2125. 2019-01-10 09:22:53 I #6072 msgbus Subscriber now invoking handler...
  2126. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2127. 2019-01-10 09:22:53 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2128. 2019-01-10 09:22:54 I #2864 msgbus Received 305 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2129. 2019-01-10 09:22:54 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2130. 2019-01-10 09:22:54 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2131. 2019-01-10 09:22:54 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2132. 2019-01-10 09:22:54 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2133. 2019-01-10 09:22:54 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2134. 2019-01-10 09:22:54 I #2864 msgbus Received 312 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2135. 2019-01-10 09:22:54 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2136. 2019-01-10 09:22:54 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2137. 2019-01-10 09:22:54 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2138. 2019-01-10 09:22:54 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2139. 2019-01-10 09:22:54 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2140. 2019-01-10 09:22:54 I #2864 msgbus Received 2003 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2141. 2019-01-10 09:22:54 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2142. 2019-01-10 09:22:54 I #2864 msgbus Received topic <ma.task.remove>, matched <ma.*>
  2143. 2019-01-10 09:22:54 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2144. 2019-01-10 09:22:54 I #2864 msgbus Received 300 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2145. 2019-01-10 09:22:54 I #528 msgbus Subscriber now invoking handler...
  2146. 2019-01-10 09:22:54 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2147. 2019-01-10 09:22:54 I #528 msgbus Subscriber now invoking handler...
  2148. 2019-01-10 09:22:54 I #6072 msgbus Subscriber now invoking handler...
  2149. 2019-01-10 09:22:54 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2150. 2019-01-10 09:22:54 I #2724 msgbus Subscriber now invoking handler...
  2151. 2019-01-10 09:22:54 I #3688 msgbus Subscriber now invoking handler...
  2152. 2019-01-10 09:22:54 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2153. 2019-01-10 09:22:54 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2154. 2019-01-10 09:22:54 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2155. 2019-01-10 09:22:54 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2156. 2019-01-10 09:22:54 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2157. 2019-01-10 09:22:54 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2158. 2019-01-10 09:22:54 I #3688 msgbus Subscriber now invoking handler...
  2159. 2019-01-10 09:22:54 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2160. 2019-01-10 09:22:54 I #3688 msgbus Subscriber now invoking handler...
  2161. 2019-01-10 09:22:54 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2162. 2019-01-10 09:22:54 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2163. 2019-01-10 09:22:54 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2164. 2019-01-10 09:32:34 I #2864 msgbus Received 316 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2165. 2019-01-10 09:32:34 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2166. 2019-01-10 09:32:34 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2167. 2019-01-10 09:32:34 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2168. 2019-01-10 09:32:34 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2169. 2019-01-10 09:32:34 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2170. 2019-01-10 09:32:34 I #2864 msgbus Received 310 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2171. 2019-01-10 09:32:34 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2172. 2019-01-10 09:32:34 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2173. 2019-01-10 09:32:34 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2174. 2019-01-10 09:32:34 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2175. 2019-01-10 09:32:34 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2176. 2019-01-10 09:32:34 I #2864 msgbus Received 1586 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2177. 2019-01-10 09:32:34 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2178. 2019-01-10 09:32:34 I #2864 msgbus Received topic <ma.task.execute>, matched <ma.*>
  2179. 2019-01-10 09:32:34 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2180. 2019-01-10 09:32:34 I #3688 msgbus Subscriber now invoking handler...
  2181. 2019-01-10 09:32:34 I #3688 msgbus Subscriber now invoking handler...
  2182. 2019-01-10 09:32:34 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2183. 2019-01-10 09:32:34 I #2724 msgbus Subscriber now invoking handler...
  2184. 2019-01-10 09:32:34 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2185. 2019-01-10 09:32:34 I #2724 msgbus Subscriber now invoking handler...
  2186. 2019-01-10 09:32:34 I #528 msgbus Subscriber now invoking handler...
  2187. 2019-01-10 09:32:34 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2188. 2019-01-10 09:32:34 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2189. 2019-01-10 09:32:34 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2190. 2019-01-10 09:32:34 I #2864 msgbus Received 366 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2191. 2019-01-10 09:32:34 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2192. 2019-01-10 09:32:34 I #2864 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
  2193. 2019-01-10 09:32:34 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2194. 2019-01-10 09:32:34 I #2724 msgbus Subscriber now invoking handler...
  2195. 2019-01-10 09:32:34 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2196. 2019-01-10 09:32:35 I #2864 msgbus Received 306 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2197. 2019-01-10 09:32:35 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2198. 2019-01-10 09:32:35 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2199. 2019-01-10 09:32:35 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2200. 2019-01-10 09:32:35 I #2724 msgbus Subscriber now invoking handler...
  2201. 2019-01-10 09:32:35 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=1, MaxProgress = 0, Progress Message = Checking update packages from repository ePO_UK-VM-AV1.
  2202. 2019-01-10 09:32:35 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=1 MaxProgress = 0 Progress Message = Checking update packages from repository ePO_UK-VM-AV1.
  2203. 2019-01-10 09:32:35 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2204. 2019-01-10 09:32:35 I #2864 msgbus Received 272 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2205. 2019-01-10 09:32:35 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2206. 2019-01-10 09:32:35 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2207. 2019-01-10 09:32:35 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2208. 2019-01-10 09:32:35 I #2724 msgbus Subscriber now invoking handler...
  2209. 2019-01-10 09:32:35 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressStart , ProgressStep=15, MaxProgress = 1, Progress Message = Initializing update...
  2210. 2019-01-10 09:32:35 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressStart ProgressStep=15 MaxProgress = 1 Progress Message = Initializing update...
  2211. 2019-01-10 09:32:35 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2212. 2019-01-10 09:32:35 I #2864 msgbus Received 270 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2213. 2019-01-10 09:32:35 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2214. 2019-01-10 09:32:35 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2215. 2019-01-10 09:32:35 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2216. 2019-01-10 09:32:35 I #2724 msgbus Subscriber now invoking handler...
  2217. 2019-01-10 09:32:35 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=3, MaxProgress = 0, Progress Message = Verifying catalog.z.
  2218. 2019-01-10 09:32:35 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=3 MaxProgress = 0 Progress Message = Verifying catalog.z.
  2219. 2019-01-10 09:32:35 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2220. 2019-01-10 09:32:36 I #2864 msgbus Received 271 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2221. 2019-01-10 09:32:36 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2222. 2019-01-10 09:32:36 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2223. 2019-01-10 09:32:36 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2224. 2019-01-10 09:32:36 I #2724 msgbus Subscriber now invoking handler...
  2225. 2019-01-10 09:32:36 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=4, MaxProgress = 0, Progress Message = Extracting catalog.z.
  2226. 2019-01-10 09:32:36 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=4 MaxProgress = 0 Progress Message = Extracting catalog.z.
  2227. 2019-01-10 09:32:36 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2228. 2019-01-10 09:32:36 I #2864 msgbus Received 297 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2229. 2019-01-10 09:32:36 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2230. 2019-01-10 09:32:36 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2231. 2019-01-10 09:32:36 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2232. 2019-01-10 09:32:36 I #2724 msgbus Subscriber now invoking handler...
  2233. 2019-01-10 09:32:36 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=5, MaxProgress = 0, Progress Message = Loading update configuration from: catalog.xml
  2234. 2019-01-10 09:32:36 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=5 MaxProgress = 0 Progress Message = Loading update configuration from: catalog.xml
  2235. 2019-01-10 09:32:36 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2236. 2019-01-10 09:32:37 I #2864 msgbus Received 326 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2237. 2019-01-10 09:32:37 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2238. 2019-01-10 09:32:37 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2239. 2019-01-10 09:32:37 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2240. 2019-01-10 09:32:37 I #2724 msgbus Subscriber now invoking handler...
  2241. 2019-01-10 09:32:37 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=2, MaxProgress = 0, Progress Message = These updates will be applied if they are in the repository: EXTRADAT1000.
  2242. 2019-01-10 09:32:37 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=2 MaxProgress = 0 Progress Message = These updates will be applied if they are in the repository: EXTRADAT1000.
  2243. 2019-01-10 09:32:37 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2244. 2019-01-10 09:32:37 I #2864 msgbus Received 273 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2245. 2019-01-10 09:32:37 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2246. 2019-01-10 09:32:37 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2247. 2019-01-10 09:32:37 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2248. 2019-01-10 09:32:37 I #2724 msgbus Subscriber now invoking handler...
  2249. 2019-01-10 09:32:37 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=7, MaxProgress = 0, Progress Message = Verifying extradat.mcs.
  2250. 2019-01-10 09:32:37 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=7 MaxProgress = 0 Progress Message = Verifying extradat.mcs.
  2251. 2019-01-10 09:32:37 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2252. 2019-01-10 09:32:37 I #2864 msgbus Received 290 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2253. 2019-01-10 09:32:37 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2254. 2019-01-10 09:32:37 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2255. 2019-01-10 09:32:37 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2256. 2019-01-10 09:32:37 I #2724 msgbus Subscriber now invoking handler...
  2257. 2019-01-10 09:32:37 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress, ProgressStep=8, MaxProgress = 0, Progress Message = Product(s) running the latest ExtraDAT.
  2258. 2019-01-10 09:32:37 I #2724 UiProviderAdaptor On Progress Callback EventType=Progress ProgressStep=8 MaxProgress = 0 Progress Message = Product(s) running the latest ExtraDAT.
  2259. 2019-01-10 09:32:37 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2260. 2019-01-10 09:32:37 I #2864 msgbus Received 265 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2261. 2019-01-10 09:32:37 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2262. 2019-01-10 09:32:37 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2263. 2019-01-10 09:32:37 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2264. 2019-01-10 09:32:37 I #2724 msgbus Subscriber now invoking handler...
  2265. 2019-01-10 09:32:37 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressFinished, ProgressStep=0, MaxProgress = 0, Progress Message = Update Finished
  2266. 2019-01-10 09:32:37 I #2724 UiProviderAdaptor On Progress Callback EventType=ProgressFinished ProgressStep=0 MaxProgress = 0 Progress Message = Update Finished
  2267. 2019-01-10 09:32:37 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2268. 2019-01-10 09:32:37 I #2864 msgbus Received 284 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2269. 2019-01-10 09:32:37 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2270. 2019-01-10 09:32:37 I #2864 msgbus Received topic <ma.mue_event.publish>, matched <ma.*>
  2271. 2019-01-10 09:32:37 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2272. 2019-01-10 09:32:37 I #2724 msgbus Subscriber now invoking handler...
  2273. 2019-01-10 09:32:37 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2274. 2019-01-10 09:32:42 I #2864 msgbus Received 368 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2275. 2019-01-10 09:32:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2276. 2019-01-10 09:32:42 I #2864 msgbus Received topic <ma.msgbus.subscriber_change_notification>, matched <ma.*>
  2277. 2019-01-10 09:32:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2278. 2019-01-10 09:32:42 I #2724 msgbus Subscriber now invoking handler...
  2279. 2019-01-10 09:32:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2280. 2019-01-10 09:32:42 I #2864 msgbus Received 186 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2281. 2019-01-10 09:32:42 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2282. 2019-01-10 09:32:42 I #2864 msgbus Received topic <ma.io.service.update.registry>, matched <ma.*>
  2283. 2019-01-10 09:32:42 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2284. 2019-01-10 09:32:42 I #2724 msgbus Subscriber now invoking handler...
  2285. 2019-01-10 09:32:42 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2286. 2019-01-10 09:32:43 I #2864 msgbus Received 309 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2287. 2019-01-10 09:32:43 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2288. 2019-01-10 09:32:43 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2289. 2019-01-10 09:32:43 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2290. 2019-01-10 09:32:43 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2291. 2019-01-10 09:32:43 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2292. 2019-01-10 09:32:43 I #2864 msgbus Received 316 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2293. 2019-01-10 09:32:43 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2294. 2019-01-10 09:32:43 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2295. 2019-01-10 09:32:43 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2296. 2019-01-10 09:32:43 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2297. 2019-01-10 09:32:43 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2298. 2019-01-10 09:32:43 I #2864 msgbus Received 1585 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2299. 2019-01-10 09:32:43 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2300. 2019-01-10 09:32:43 I #2864 msgbus Received topic <ma.task.remove>, matched <ma.*>
  2301. 2019-01-10 09:32:43 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2302. 2019-01-10 09:32:43 I #2864 msgbus Received 304 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2303. 2019-01-10 09:32:43 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2304. 2019-01-10 09:32:43 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2305. 2019-01-10 09:32:43 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2306. 2019-01-10 09:32:43 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2307. 2019-01-10 09:32:43 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2308. 2019-01-10 09:32:43 I #3688 msgbus Subscriber now invoking handler...
  2309. 2019-01-10 09:32:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2310. 2019-01-10 09:32:43 I #3688 msgbus Subscriber now invoking handler...
  2311. 2019-01-10 09:32:43 I #2724 msgbus Subscriber now invoking handler...
  2312. 2019-01-10 09:32:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2313. 2019-01-10 09:32:43 I #2724 msgbus Subscriber now invoking handler...
  2314. 2019-01-10 09:32:43 I #528 msgbus Subscriber now invoking handler...
  2315. 2019-01-10 09:32:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2316. 2019-01-10 09:32:43 I #528 msgbus Subscriber now invoking handler...
  2317. 2019-01-10 09:32:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2318. 2019-01-10 09:32:43 I #528 msgbus Subscriber now invoking handler...
  2319. 2019-01-10 09:32:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2320. 2019-01-10 09:32:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2321. 2019-01-10 09:32:43 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2322. 2019-01-10 09:35:33 I #2864 msgbus Received 1177 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2323. 2019-01-10 09:35:33 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2324. 2019-01-10 09:35:33 I #2864 msgbus Received topic <ma.task.execute>, matched <ma.*>
  2325. 2019-01-10 09:35:33 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2326. 2019-01-10 09:35:33 I #528 msgbus Subscriber now invoking handler...
  2327. 2019-01-10 09:35:33 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2328. 2019-01-10 09:35:33 I #2864 msgbus Received 282 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2329. 2019-01-10 09:35:33 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2330. 2019-01-10 09:35:33 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2331. 2019-01-10 09:35:33 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2332. 2019-01-10 09:35:33 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2333. 2019-01-10 09:35:33 I #528 msgbus Subscriber now invoking handler...
  2334. 2019-01-10 09:35:33 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2335. 2019-01-10 09:35:33 I #528 msgbus Subscriber now invoking handler...
  2336. 2019-01-10 09:35:33 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2337. 2019-01-10 09:35:33 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2338. 2019-01-10 09:40:32 I #2864 msgbus Received 1159 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2339. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2340. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.task.execute>, matched <ma.*>
  2341. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2342. 2019-01-10 09:40:32 I #528 msgbus Subscriber now invoking handler...
  2343. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2344. 2019-01-10 09:40:32 I #2864 msgbus Received 287 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2345. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2346. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2347. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2348. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2349. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2350. 2019-01-10 09:40:32 I #2864 msgbus Received 263 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2351. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2352. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2353. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2354. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2355. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2356. 2019-01-10 09:40:32 I #528 msgbus Subscriber now invoking handler...
  2357. 2019-01-10 09:40:32 I #528 msgbus Subscriber now invoking handler...
  2358. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2359. 2019-01-10 09:40:32 I #528 msgbus Subscriber now invoking handler...
  2360. 2019-01-10 09:40:32 I #528 msgbus Subscriber now invoking handler...
  2361. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2362. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2363. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2364. 2019-01-10 09:40:32 I #2864 msgbus Received 334 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2365. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2366. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.policy.notification>, matched <ma.*>
  2367. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2368. 2019-01-10 09:40:32 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2369. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2370. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2371. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2372. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2373. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2374. 2019-01-10 09:40:32 I #2864 msgbus Received 281 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2375. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2376. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2377. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2378. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2379. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2380. 2019-01-10 09:40:32 I #2864 msgbus Received 279 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2381. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2382. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.*>
  2383. 2019-01-10 09:40:32 I #528 msgbus Subscriber now invoking handler...
  2384. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2385. 2019-01-10 09:40:32 I #528 msgbus Endpoint <ma.service.policy> creation successful, reachability: <0>, timeout: <5000>, priority: <0>, thread model: <0>
  2386. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.logger.msg.pub.topic>, matched <ma.logger.msg.pub.topic>
  2387. 2019-01-10 09:40:32 I #528 msgbus Endpoint <ma.service.policy> option <0x10002> set, return value is <0>
  2388. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.logger.msg.pub.topic> callback to run from thread pool...
  2389. 2019-01-10 09:40:32 I #2864 msgbus Received 247 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2390. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2391. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.topic.pubsub.event_filter>, matched <ma.*>
  2392. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2393. 2019-01-10 09:40:32 I #2864 msgbus Received 235 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2394. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2395. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.subscribers.updaterui.WM_DESTROY>, matched <ma.*>
  2396. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2397. 2019-01-10 09:40:32 I #2864 msgbus Received 818 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2398. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2399. 2019-01-10 09:40:32 I #2864 msgbus Received topic <ma.info.events.publish>, matched <ma.*>
  2400. 2019-01-10 09:40:32 I #2864 msgbus Scheduling subscriber <ma.*> callback to run from thread pool...
  2401. 2019-01-10 09:40:32 I #528 msgbus Endpoint <ma.service.policy> option <0x10004> set, return value is <0>
  2402. 2019-01-10 09:40:32 I #528 msgbus Endpoint <ma.service.policy>, sync send call
  2403. 2019-01-10 09:40:32 I #528 msgbus Endpoint <ma.service.policy> option <0x10004> set, return value is <0>
  2404. 2019-01-10 09:40:32 I #528 msgbus Messagebus Request object Created
  2405. 2019-01-10 09:40:32 I #2864 msgbus uv timer data(00E2D6E0)
  2406. 2019-01-10 09:40:32 I #2864 msgbus
  2407. 2019-01-10 09:40:32 I #2864 msgbus <ma.service.policy> service found in router
  2408. 2019-01-10 09:40:32 I #2864 msgbus Service <ma.service.policy> found in local search and status of ep lookup is <2>
  2409. 2019-01-10 09:40:32 I #2864 msgbus Calling lookup callback in async way with status <0> from ep lookup <02E6CCE0>
  2410. 2019-01-10 09:40:32 I #2864 msgbus uv timer data(02E7EF68)
  2411. 2019-01-10 09:40:32 I #2864 msgbus
  2412. 2019-01-10 09:40:32 I #2864 msgbus local broker look up succeeded for service <ma.service.policy> and started timer with timeout <20000> for request <00E2D6E0>
  2413. 2019-01-10 09:40:32 I #2864 msgbus Added request object <00E2D6E0> into request manager
  2414. 2019-01-10 09:40:32 I #2864 msgbus Endpoint <ma.service.policy> request successfully initiated
  2415. 2019-01-10 09:40:32 I #2864 loop_worker loop worker successfully processed a message, still 0 more to go...
  2416. 2019-01-10 09:40:32 I #2864 msgbus Message bus request <00E2D6E0> lookup cb is invoked with status <0> from ep lookup <02E6CCE0>
  2417. 2019-01-10 09:40:32 I #2864 msgbus Sending message to router - correlation id <6> ephemeral name buffer <ma.internal.request.0000086C.6>
  2418. 2019-01-10 09:40:32 I #2864 msgbus Adding received message into queue
  2419. 2019-01-10 09:40:32 I #2864 msgbus Sending data on connected name pipe
  2420. 2019-01-10 09:40:32 I #2864 msgbus Write callback is invoked in named pipe connection of pipe name <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548> with status <0>
  2421. 2019-01-10 09:40:32 I #528 loop_worker scheduled an async work request, now has 1 pending work requests
  2422. 2019-01-10 09:40:32 I #528 msgbus Endpoint <ma.service.policy> succeessfully submitted request to loop worker
  2423. 2019-01-10 09:40:32 I #528 msgbus Endpoint <ma.service.policy>, submitted loop worker request for sync send
  2424. 2019-01-10 09:40:32 I #528 msgbus Endpoint <ma.service.policy>, waiting for loop worker sync request acknowledgement...
  2425. 2019-01-10 09:40:32 I #3688 msgbus Subscriber now invoking handler...
  2426. 2019-01-10 09:40:32 I #2724 msgbus Subscriber now invoking handler...
  2427. 2019-01-10 09:40:32 I #6072 msgbus Subscriber now invoking handler...
  2428. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2429. 2019-01-10 09:40:32 I #2724 msgbus Subscriber now invoking handler...
  2430. 2019-01-10 09:40:32 I #4672 msgbus Subscriber now invoking handler...
  2431. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2432. 2019-01-10 09:40:32 I #3688 msgbus Subscriber now invoking handler...
  2433. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2434. 2019-01-10 09:40:32 I #3688 msgbus Subscriber now invoking handler...
  2435. 2019-01-10 09:40:32 I #3688 msgbus Subscriber now invoking handler...
  2436. 2019-01-10 09:40:32 I #2620 msgbus Subscriber now invoking handler...
  2437. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2438. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2439. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2440. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2441. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2442. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
  2443. 2019-01-10 09:40:32 I #2864 msgbus Received 7588 bytes from pipe <\\.\pipe\ma_5bd9fa52-9d71-e8fd-20b0-306ab91d3db1_5880.00000000012D4720_1828927548>
  2444. 2019-01-10 09:40:32 I #2864 msgbus Set the destination pid to zero to stop the sending this message to other named pipe connections
  2445. 2019-01-10 09:40:32 I #2864 msgbus Recevied expected response to message bus request
  2446. 2019-01-10 09:40:32 I #2864 msgbus message bus request Released
  2447. 2019-01-10 09:40:32 I #2864 msgbus Invoking user callback in I/O thread
  2448. 2019-01-10 09:40:32 I #2864 msgbus Endpoint <ma.service.policy>, sync send callback invoked
  2449. 2019-01-10 09:40:32 I #2864 msgbus ep lookup <02E6CCE0> stop, connection status recevied <No> ref count <3>
  2450. 2019-01-10 09:40:32 I #2864 msgbus Request Object Closes
  2451. 2019-01-10 09:40:32 I #528 msgbus message bus request Released
  2452. 2019-01-10 09:40:32 I #2864 msgbus message bus request Released
  2453. 2019-01-10 09:40:32 I #528 msgbus Endpoint <ma.service.policy> release
  2454. 2019-01-10 09:40:32 I #2864 msgbus Messagebus Request object Destroys
  2455. 2019-01-10 09:40:32 I #2864 msgbus Endpoint <ma.service.policy> release
  2456. 2019-01-10 09:40:32 I #2864 msgbus Endpoint <ma.service.policy> destroys
  2457. 2019-01-10 09:40:32 I #528 UpdaterUIModule Enforcing UI policies
  2458. 2019-01-10 09:40:32 I #528 UpdaterUIModule AgentMode = 1
  2459. 2019-01-10 09:40:32 I #528 UpdaterUIModule Show Agent UI: 1
  2460. 2019-01-10 09:40:32 I #528 UpdaterUIModule Allow Security Update: 1
  2461. 2019-01-10 09:40:32 I #528 UpdaterUIModule Language from policy : 0000
  2462. 2019-01-10 09:40:32 I #528 UpdaterUI Allow Update Security option State = 1
  2463. 2019-01-10 09:40:32 I #2864 msgbus After Worker callback is Invoked in Subscriber
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!