Free Threads? Please help - getting an error

timskau · Post by **timskau** » Fri Oct 13, 2006 1:19 am

Hello,
We're new to using sourcegear. A great tool, but now we have a small problem that I can't find a solution for.

When some of us try to check in a file, they get this message:

"There were not enough free treads in the ThreadPool object to complete the operation", and the file is not checked in. Maybe a setting in IIS ?

Do you have any ideas?

We're using Vault 3.5 and Visual Studio 2003 (with SP1). The server runs Win2003 with IIS 6.0

Regards
Tim

lbauer · Post by **lbauer** » Fri Oct 13, 2006 9:22 am

Before we can answer this, we need to see a copy of the Vault server log to see what is reported on the server side.

Send a copy of the sgvault.log file (in %windir%\temp\sgvault) to support@sourcegear.com. Let us know the time in the log that corresponds to the error message.

Include a link to this forum post in your email.

uberbloke · Post by **uberbloke** » Mon Jan 08, 2007 5:07 am

Was there any resolution to this issue...

We are experiencing exactly the same problem with VS2003, only running against the vault server on a W2K box with IIS5

I have looked in the log and cant see anything that **I** think would be useful... but can post it up if required

Please note we are currently evaluating Vault as a replacment sourcecontrol system and this is a show stopper for us

lbauer · Post by **lbauer** » Mon Jan 08, 2007 9:05 am

We've had 2 or 3 users report this. We're not sure what caused the problem, though in most cases it went away.

One user unbound his project from source control and then rebound it. He had to do this a couple of times.

If this doesn't help, we can investigate further.

uberbloke · Post by **uberbloke** » Mon Jan 08, 2007 9:18 am

As this was working Friday and then not this morning we, flippantly, put this down to Vault suffering from MMS (Monday Morning Syndrom)

From your response it would seem that this is actually the correct answer!

Unbounding and rebounding coupled with reducing the number of files in the VS project (not the Vault repository) seemed to help

We'll be keeping an eye on this during the evaluation period