SCOM Synthetic Transactions – strange values


  • Hi All,

    We have Lync 2013 and SCOM 2012R2 with Lync MP & synthetic transaction node.

    Synthetic transaction node working fine, I can successfully run any Test-CS* cmdlets on the transaction node.

    Inside SCOM i can see the synthetic transaction results, but the result is very strange, it is about millions of seconds :)

    Operations Manager log File, on the synthetic transaction node, do not have any errors 

    I think, that something is wrong, our Lync working fine )

    Can someone help me to fix this issue? 

    SCOM Result: 

    Synthetic transaction node result:

    MCITP:EA,EMA; MCSE, MCSA:Messaging

    mercredi 26 février 2014 10:47

Toutes les réponses

  • Hi,

    Did you feel latency when using Lync?

    From the second screenshot you provided we can also see the Latency is a little high.

    Please check the network configuration in your Lync environment.

    Please update to the latest version for Lync server and then test again.

    Best Regards,

    Eason Huang

    Eason Huang
    TechNet Community Support

    vendredi 28 février 2014 08:22
  • Hi,

    Lync seems to run smooth without delays.

    I will perform additional tests.

    But i wonder - why scom result is so high?

    30000000 seconds it's something unreal )

    MCITP:EA,EMA; MCSE, MCSA:Messaging

    mardi 4 mars 2014 08:11
  • Hi,

    The unit of Y-axis in the SCOM chart may not express in seconds. If Lync use smoothly without issue you can ignore it temporarily.

    Best Regards,

    Eason Huang

    Eason Huang
    TechNet Community Support

    jeudi 6 mars 2014 05:37
  • Have you fixed this already? We have the exact same problem. Values are unreal high.
    mardi 21 octobre 2014 09:13
  • Good Day!

    Same problem... Thresholds in Transaction Performance collection Rules are 30 secs, hence the Lync Pool State is always "Warning" comparing ~10E+7 values... Lync Watcher Operations Manager Log entries (Event ID 335/334) show 'right' values (0-6 secs)...

    Dear colleagues from Microsoft, is it problem/issue/bug?

    P.S. Rule "Address Book Service Synthetic Transaction collection Rule" collects 0.00 values, values in Lync Watcher Operations Manager Log Events ID 335 are OK, in Events ID 334 are 0.00.

    P.P.S. "Value in SCOM" = "real Value in transaction" * 10E7, except "Address Book Service Synthetic Transaction collection Rule" (in my case all values are 0.00)

    jeudi 11 décembre 2014 06:13
  • Hi!

    Same issue at our enviroment! (Lync 2013, SCOM 2012R2)

    e.g. "Counter Name: "LS IM Performance Latency (sec)" = Value: 16565566"

    Counter Name: "LS Registration Performance Latency (sec)" = Value: 26872539

    Any news about this Problem?


    • Modifié Simon Rüesch mercredi 9 septembre 2015 09:37
    • Proposé comme réponse Simon Rüesch mercredi 9 septembre 2015 12:07
    • Non proposé comme réponse Simon Rüesch mercredi 9 septembre 2015 12:07
    mercredi 9 septembre 2015 09:21
  • It was a problem from the region settings, change to Engl. US, the values are displayed ok.

    Thanks JonRunheim

    mercredi 9 septembre 2015 12:09
  • Hi

    Was it on the SCOM server or the watcher node, you change region? I'm having the Issue with Skype for Business mgm pack.

    vendredi 13 novembre 2015 09:20
  • Hi.

    I am facing the same issue here.

    Did you get a response on where the change of regional settings did the trick ?

    mercredi 18 mai 2016 11:35
  • We have same problem with Skype For Business Management Pack

    Change region settings to Engl. US ?? where ? in which computer ??

    mercredi 8 juin 2016 09:50
  • Hi everyone,

    does anyone have an update for this?

    I am facing exactely the same issue.



    vendredi 3 novembre 2017 08:27
  • Hi all,

    What you can also do is to run KHI and check if the same values appear. You can download the key health indicators from:



    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

    vendredi 3 novembre 2017 09:54
  • Hi,

    Found the final solution for this issue.

    The actual Regional settings that you have to change for the watcher nodes is the System Locale.

    Changing the System Locale to English (United States) and rebooting has fixed the issue.


    mercredi 6 juin 2018 13:51