locked
Exchange Management log throws 1,000 log 'cmdlet failed, Get-MobileDeviceStatistics' entries RRS feed

  • Question

  • I keep getting this error in my hybrid Exchange setup and it's kind of frustrating. Does anyone know how to stop it?


    Regards,
    Allan Kjær
    blog | cv

    Monday, August 19, 2019 7:03 AM

All replies

  • Hi Allan Kjaer,

    "Exchange Management log", do you mean EMS log?

    Could provide more detail information about this log? Such as, where do you find this log, frequency of log generation, detail log information about one of them.

    I think there exists some thing(such as Task Schedule) in your organization keep running this command, so this log will keep generating. You should find the trigger from this log, then you can stop it.

    Regards,

    Kyle Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, August 20, 2019 2:14 AM
  • Hi Kyle,

    I mean Windows Event Viewer, 'MSExchange Management'.

    Log entries are created every day. Last night it was at 8:43 p.m. (20:43). I have not created any tasks in Task Scheduler that could start this job, so I guess it must be Exchange itself:


    Regards,
    Allan Kjær
    blog | cv

    Tuesday, August 20, 2019 6:17 AM
  • From this event, we can know some one try to run command below, but it failed:

    Get-MobileDeviceStatistics -WarningAction "SilentlyContinue" -Identity "*********/ExchangeActiveSyncDevices/Android5androidc20i8149070"

    A "Get" action will not be logged in admin audit log, so we can know which people run this command on your server.

    You can try to run this command manually, check whether is it could be running successfully. If there exist issue,  try to solve this issue, then this error event will disappear.

    You can also find error message from Event viewer, such as:

    Regards,

    Kyle Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, August 20, 2019 7:53 AM
  • Hi Kyle,

    Thanks. I know that the command will fail, but I'm not interesting in running these 1,000 commands each day as I don't know why it happens. I didn't ask my server to do it.

    Do you know how to stop it from doing it every day?


    Regards,
    Allan Kjær
    blog | cv

    Tuesday, August 20, 2019 8:02 AM
  • Hi Allan Kjaer,

    A "Get" action will not be record in Exchange audit log, so from our side, we cannot find why is this thing occurs. This action will not cause large load on your server, I think you can just bypass it.

    Regards,

    Kyle Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, August 22, 2019 8:08 AM
  • Hi Kyle,

    I don't want to 'bypass it' since it is reporting in my monitoring tool as a failure. So I get 1,000 failures every day.


    Regards,
    Allan Kjær
    blog | cv

    Friday, August 23, 2019 9:26 AM
  • Hi Allan Kjaer,

    We cannot find which people run this command from admin audit log.

    Does the problem occur at a fixed time of day? If so, you should check whether there exist such a task on your server, Exchange will not do such action by default.

    You can also try to reset password for all administrators, in the way, this command will cannot be running due to lacking of permission.

    Regards,

    Kyle Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, August 28, 2019 9:46 AM