I had this same issue and setting the CC service to run as a user who had rights to the VSS database path did the trick. By default, the CC service runs under the Local System account. To change this...
1. Right click My Computer.
2. Click Manage.
3. Expand Services and Applications
4. Click on Services.
5. Find CruiseControl .NET Server in the right pane.
6. Right click on it and go to Properties.
7. Go to the Log On tab.
8. Select "This account", and specify a user account that HAS ACCESS to the VSS file path where the database resides, to which CC is trying to connect.
9. Restart the CruisControl .NET Server service.
10. You should be good to go.
Also, be sure that the credentials and VSS database information in your ccnet.config file are accurate.
Main Topics
Browse All Topics





by: HecatonchiresPosted on 2009-03-01 at 14:30:02ID: 23770100
I've recently been bitten by the 'Windows Services cannot access mapped drives' problem. Is your VSS repository access via a mapped drive?
Is the CC Service running as LocalService, or via credentials that allow access to the repository?