When attempting to check in code through TFS in visual studio 2012 or 2013 sometimes results in displaying an error message "Value was either too large or too small for a UINT32" error message. What is causing this, and how can I fix this?

2 Answers 2


This seems to be a bug in the dialog. This seems to consistently happen when you try to check in code that hasn't been saved, confusing the feature to a sufficient degree to throw up its hands in the air with this error.

The solution is simple: save your files before committing them.

  • 1
    I can think of a different solution. :-)
    – ardave
    Mar 24, 2014 at 20:12
  • 3
    So can I, but that was pointy hairishly rejected
    – Martijn
    Mar 25, 2014 at 0:04
  • 12
    Thanks for that one, it appears the same occurs for an unsaved file that is not even part of the solution... I just had to close it and everything went fine. Jun 4, 2014 at 15:09
  • 1
    You was right, I just edited my file during review and get this error. Saving helps for me.
    – RredCat
    Nov 24, 2014 at 12:23
  • 7
    File > Save All Mar 10, 2015 at 23:48

Another possible Scenario: this happens after reverting to older file versions from TFS and then changing a file and trying to checkin.

Solution : update to latest version before checkin

  • This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. - From Review
    – Ramhound
    Feb 23, 2016 at 18:40
  • updated the solution , to be clearer
    – Sam
    Feb 24, 2016 at 10:21

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .