Forum Discussion

LandofOz's avatar
LandofOz
Level 3
8 years ago

EMA returns no data

Good morning, all. I’m hitting an error when running EMA against Exchange2013SP1. A colleague has reproduced the “no data” symptom (though not the error text) when running the same version of EMA against an Exchange 2016 setup. Environment: Exchange 2013 SP1 with EMA 3.2.4.12195 (current) I began with a fresh database. Added both mailbox servers Selected All, then scanned to get the mailbox counts. Selected All again, then Analyze Selected The screenshot below shows the completion. (well, if I could paste the screenshot it would. See attachment instead) Clicking the Overall Statistics button produces the error text (attached) Then clicking OK from that error dialog, I see the empty results page (attached)
  • Working with our channel manager we simlutaneously discovered that if the "Connect using SSL" box is UNchecked, it produces the symptoms of no-data with no other warnings.

    When we checked the SSL box, the analyzer connected properly and did what analyzers do.

     

  • That's a boatload of error text but all it's really doing is summing up six stats from a SQL table. You can run it manually by copying everything from "SELECT" through "exchangeserverID=2" into a new query in SQL Management Studio. (I hope you have a copy-paste-friendly version of the error in some log somewhere.)

    The problem is that one of these six sums is returning NULL, while the EMA expects it to have a value and doesn't account for the possibility that it might be NULL. When the EMA assumes the result will contain a numeric value and it does not, this conversion error occurs.

    This needs to be fixed by the author of the EMA by testing that each SQL result is not equal to DBNull before assigning it to a variable of type Long. See example here.

    While you wait for that to happen, you could probably circumvent the problem by making sure that none of the SUM functions results in NULL. That is, if the column returning NULL is AttachmentCount, send a message with an attachment to at least one mailbox.

     

    --Chris

    • LandofOz's avatar
      LandofOz
      Level 3

      Thanks Chris - I'm getting some guidance that it's indicative of permission problem with the proxy user but so far I'm not seeing an error to confirm that.  The EMA manual page 5 says

      "If permissions are not set up correctly, the user will be notified and EMA will terminate"

      but that isn't what I am seeing happen.

      I'm verifying with customer that the emaproxy account isn't locked/expired/something like that, but puzzled that if that were the case, why EMA wouldn't complain about it directly.  I'll post here when I know more.

       

      • LandofOz's avatar
        LandofOz
        Level 3

        Working with our channel manager we simlutaneously discovered that if the "Connect using SSL" box is UNchecked, it produces the symptoms of no-data with no other warnings.

        When we checked the SSL box, the analyzer connected properly and did what analyzers do.