We use Team Foundation Server as our code repository and Team Foundation Server’s Team Build to do automated nightly builds.  We have configured Team Build for check-ins to trigger a new build.  After check-ins of a large amount of code yesterday for one of our new SQL Server 2008 Database Projects, I arrived at the office today to find a big Build Failed Build Failed icon in my task bar notification area from my friend Team Foundation Build Notification (part of the Microsoft Team Foundation Server 2008 Power Tools).

Looking at the BuildLog.txt I noted several entries one of which is:

C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets(737,5,737,5): error : TF10128: The path C:\Users\TFSBuild\AppData\Local\Temp\Allscripts Extension\Allscripts Extension Master – Daily\Sources\Main\Source\Allscripts Data Warehouse\Source\AEWarehouseDB\Schema Objects\Programmability\Stored Procedures\usp_PopulateFactPaySourceRevenue_ByTrailingYear.proc.sql contains more than the allowed 259 characters. Type or select a shorter path.

After some quick research I found that windows has a paths limitation of 259 characters.  I found a wonderful explanation and workaround by Aaron Hallberg.

I was able to simply rename my Build Definition to a shortened name and all my nightly builds are now back to normal. image