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.
Hi All, Recently my place of work upgraded our network from a Novell server to a windows 2003 server. This caused our previously working cvsnt server to stop allowing write access. (Previous to this the server had been running for about 3 years). All my attempts to fix this problem have been for naught. Basically I have a permissions issue and I have not been able to resolve it. The cvsnt is running on windows XP sp2. The version of CVSNT is 2.5.03 Build 2382 (we had the same problem with a previous build of CVSNT, so I upgraded to the most recent I could find ). Read access to the server is working fine, we have viewCVS setup and that is also working fine. We are using sspi protocol, the CVS repo and temp directories have full permissions enabled for a group called Engineering and for myself and other test users (who are in the engineering group). (I can access the files via the network, see the expected permissions and change read/write mode). However, write access does not work. Any attempt to commit a file does not work and the error cvs [server aborted]: "commit" requires write access to the repository Is displayed. Currently I have no writer file (although I have attempted adding one which made no difference). My configuration is as follows: I am running a local lock server. Run as user: client user Default Domain: OMNITRONICS Temp Directory: c:\cvstemp Repository: c:\cvsrepo Defaults for the lock server Compatibility options : No flags ticked Clients allowed to connect; Any CVS/CVSNT All default plug ins installed The SSPI had default settings Advanced settings that are on Lockserver listens locally only Allow clients to trace server I would greatly appreciate and tips or suggestions on What should I try next? Regards Paul