Server unavailable for transaction end

Ken · Post by **Ken** » Thu Mar 18, 2004 10:23 am

I have had this problem in the past but it is reoccuring with different information. This time the server log file says:

SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM.

and then:

FailDBInsert

anytime I try to add a file. I have been working this morning with checkout and checkin in the VS IDE without a problem but when I try to add a new file through the GUI Client, I get the "Server unavailable for transaction end" and the server logs have the above messages in them.

Please help, I have been getting complaints from other developers of the same problem.

Ken · Post by **Ken** » Thu Mar 18, 2004 10:29 am

I am running Version 2.0.0.2120 of Vault. Also, I just tried adding files through the IDE and I was able to do it. I am running the .NET 1.0 compiled version of the IDE Client for Visual Studio 2002.

Post by **jeremy_sg** » Thu Mar 18, 2004 10:43 am

Can you look at the timestamp on the file and the current time/date on your computer? It could be that Vault is reading a bogus date from the file's properties and VS.Net is not. Does this happen if you create a brand new file and try to add it to Vault?

Ken · Post by **Ken** » Thu Mar 18, 2004 10:54 am

That is really wierd. The date on the file is Monday, January 01, 1601, 12:00:00 AM. I modifed the file and saved it and I was able to add the files. Now I just need to figure out how such a bogus created/modifed date was in the file in the first place

SourceGear Support

Server unavailable for transaction end

Server unavailable for transaction end

Version Info