locked
TfsJobAgent - OverflowException in ExtendedStopwatch when working with test environment RRS feed

  • Question

  • Hi

    We currently have a strange error happening on a tfs installation at customer's site. If we interact with a virtual test environent through Lab Management (i.e. shutdown, take snapshot, etc...) there is no task created on SCVMM. We can see in the error log, that the particular job in the TFS Background Job Scheduler fails each 5 seconds.

    The error is the following:

    Exception Message: Arithmetic operation resulted in an overflow. (type OverflowException)

    Exception Stack Trace: at Microsoft.TeamFoundation.Lab.Common.ExtendedStopwatch.NativeMethods.GetMaxCpuFrequency()

    at Microsoft.TeamFoundation.Lab.Common.ExtendedStopwatch..cctor()

    Did anybody encounter the same error? Any clues on how to solve it? We cannot use Lab Management anymore because every operation fails.

    Regards,

    Marc

    Friday, November 9, 2012 9:40 AM

Answers

  • Hi Romit

    Thank you for your answer. We just thought opening an additional social channel could provide addition information if somebody else was facing the same error. Since there has not been any reaction from the community, I'll close the thread and we will work with the support concerning this error.

    Regards,

    Marc

    Friday, November 16, 2012 7:58 AM

All replies

  • Hi Marc, 

    Thanks for your post.

    I’m currently looking into this issue and will give you an update as soon as possible.  


    John Qiao [MSFT]
    MSDN Community Support | Feedback to us

    Monday, November 12, 2012 8:52 AM
  • Hi MarcMuellerCH,

    From a support perspective this is really beyond what we can do here in the forums. I also understand that you are already working with my colleague from CSS on the same issue and he should be able to help you out .

    Thanks,

    Romit Gulati (MSFT)

    Thursday, November 15, 2012 11:21 PM
  • Hi Romit

    Thank you for your answer. We just thought opening an additional social channel could provide addition information if somebody else was facing the same error. Since there has not been any reaction from the community, I'll close the thread and we will work with the support concerning this error.

    Regards,

    Marc

    Friday, November 16, 2012 7:58 AM