Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Tony, I'm not running any antivirus software nor anything else that would lock the files in the CvsTemp folder. I do, however, have some new information regarding this issue. I ran the SysInternals Filemon program to find out exactly what was going on with the filesystem and discovered that when I do a commit with a user that works, the cvs.exe process does the following: ... READ; F:\cvsroot\repo1\module1\source\Login.cs,v; SUCCESS ... QUERY INFORMATION, F:\cvstemp\cvs-serv1696\Login.cs; NOT FOUND And when I do the same commit on the Login.cs file with a user that does not work, the cvs.exe process does the following: ... QUERY INFORMATION, F:\cvstemp\cvs-serv1234\Login.cs; SUCCESS ... QUERY INFORMATION; F:\cvsroot\repo1\module1\source\,Login.cs,v; NOT FOUND Notice the comma "," before the filename ",Login.cs,v". What's that about? Is this a bug in CVSNT? Tony Hoyle wrote: > Ryan wrote: >> Hello, >> >> We are running CVSNT on Windows 2003 and use SSPI. We have several >> users working with CVSNT just fine, but recently any new user we >> create is unable to commit. This is the error we are getting: >> >> cvs [server aborted]: could not open lock file >> '/cvsroot/web/Project1/source/Login/,Login.cs,': Permission denied >> cvs commit: saving log message in >> C:\Users\testuser4\AppData\Local\Temp\2\cvsCA11. >> tmp >> > > Things like this are almost always due to antivirus running on the and > server locking the temporary files. It's completely unrelated to the > lockserver. > > Tony