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?
Asked
Active
Viewed 2.0k times
119
2 Answers
199
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.
Martijn
- 3,342
- 3
- 16
- 15
-
1I can think of a different solution. :-) – ardave Mar 24 '14 at 20:12
-
3So can I, but that was pointy hairishly rejected – Martijn Mar 25 '14 at 00:04
-
12Thanks 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. – Marcel Gosselin Jun 04 '14 at 15:09
-
1You was right, I just edited my file during review and get this error. Saving helps for me. – RredCat Nov 24 '14 at 12:23
-
Worked for me as well, I had a T-SQL editor window open which, unsaved, caused me to not be able to check in my pending changes. – PeterL Feb 17 '15 at 22:33
-
7File > Save All – Danny Bullis Mar 10 '15 at 23:48
-
In my case I was actually just trying to queue a new build without any checking-in going on. Never would've thought of this, thanks. – makhdumi Sep 23 '15 at 20:22
-
@ardave What different solution was that? – Konrad Viltersten Oct 23 '15 at 10:21
-
1@KonradViltersten not using TFS – Martijn Oct 23 '15 at 10:39
-
@ardave Hehe, that answers my follow-up question on the pointy-hairness of the decision. – Konrad Viltersten Oct 23 '15 at 11:54
-
This happens also when checking in files different from those that were'nt saved. – Shahar Nov 10 '15 at 10:32
-
FYI: Error still happens in VS2015 Update 1. – Steve Feb 08 '16 at 20:17
-
Funny thing is this error still happens in VS 2015 Update 2 with the Git tooling. Anyway, saving all my files before checking in does the job. Thanks! – ajawad987 Apr 12 '16 at 05:50
-
Get this when shelving in VS2017 with TFS 2015 – Andez Sep 25 '17 at 09:47
0
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
Sam
- 1
- 2
-
This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](http://superuser.com/questions/ask). You can also [add a bounty](http://superuser.com/help/privileges/set-bounties) to draw more attention to this question once you have enough [reputation](http://superuser.com/help/whats-reputation). - [From Review](/review/low-quality-posts/503357) – Ramhound Feb 23 '16 at 18:40
-