I am surprised this has not been mentioned. TBC, apparently since January 1st, has a problem. When you import static data, the start and stop times have an "invalid leap second" statement instead of the times. The data processes okay, because the processor uses the GPS week and seconds of the week (which is what is contained in the dat file). It also processes rinex data OK, using the dates/times in the file. It appears to be only a problem when it tries to convert GPS time to UTC, for example when it displays the start/stop times. But the baseline processing report has that message anywhere a start/stop time is displayed.
When I started TBC right now, there is news about a fix, I didn't notice that before. I guess I was expecting an update to TBC itself, the fix is to download a new GPS Configuration utility. And it worked.
I downloaded and applied the config utility, then tested a January 4 baseline. It worked as advertised. (I probably should have tested the baseline before updating just to very John's results, but it's too late now...)
Had to update using the config utility the other day.
http://www.trimble.com/Infrastructure/trimbleconfiguration_ts.aspx