"vcproj not found or not valid"

FinalBuilder Bugs
1

[edit]
sorry, wrong section, please move to FinalBuilder bug reports
[/edit]

Hi there,

FinalBuilder copies the projects to build to a new file, containing platform information, replacing $(ProjectDir) with its actual path and so on.
For example, if Test.sln consists of one project Test.vcproj, FinalBuilder copies that project to a file called Test.tmp_Debug_Win32.vcproj for that configuration.

Since we upgraded from 6.3.0.1506 to build 1706 (and later to 1739) we encounter from time to time an error, saying:

TestBuild.fbp6 : Action error “Build VS.Net Solution [ D:\Test\Test.sln ]”: ERROR in VCBUILD(0,0) : project file ‘D:\Test\Test.tmp_Debug_Win32.vcproj’ was not found or not a valid project file.

When browsing to that directory, this file still exists and is valid (loads perfectly in VS2008). So it seems to me, Finalbuilder starts to copy it, tries to access it immediately, but it has not been converted completely yet and FB breaks with an error.

When queuing the same build again, it runs without errors.
The error rate seems to be between 1/10 to 3/10.

Any ideas?
Thanks in advance,
Hans

2

Hi Hans

This may just be windows playing tricks with disk caching etc. Try adding a small delay between copying the file and running the vs.net action. Even just a few ms might be enough.

3

Hi Vincent,

i’m not copying the file, I thought FinalBuilder would do this automatically, just before to executing the project?

Greetings, Hans

4

Hi,

today another error occurred, probably it’s related:

Error Parsing Solution File : Error parsing project file : Not enough storage is available to complete this operation.

There is plenty of free disk space on all partitions (at least 50GB+), so this cannot be the matter.

Greetings

5

Hmmm… sounds like a possible resource leak. It could also be a graphics driver issue (I have seen that before, especially with ATI cards). One thing you should do for long running builds is turn off Live Logging, as it can be a resource hog and is really only designed for debugging use.

6

This is a TFS triggered build, only using FBCMD, no UI…

7

The “ERROR in VCBUILD(0,0)” message is coming from devenv or msbuild (hard to tell since you haven’t given us much to work with). FinalBuilder doesn’t copy the files, that is done by TFS to the TFS working folder.

The “Not enough storage is available to complete this operation.” error message is from the MSXML parser when trying to load a vcproj file. Both of these errors seem to be resource related, most likely memory. If this machine is running SQL Server then it may be that it is hogging the system memory.

8

I did some more googling on the storage error, and it’s usually associated with an out of memory exception. It’s also quite common on TFS servers that have been running for a while, especially on 32 bit systems. Usually a reboot resolves the problem for a while.

HTH

9

Another possible cause is a bug in msxml 4.0, please try updating to msxml 4.0 sp3 :

http://www.microsoft.com/downloads/details.aspx?familyid=7F6C0CB4-7A5E-4790-A7CF-9E139E6819C0&displaylang=en