lpatnaik
Programmer
- Jul 11, 2002
- 53
- 0
- 0
Hi,
We have the VSS installed in the dev server, where our web resides. Since there was a space crunch, we decided to attach a hard disk and move the vss from the C drive to the new E drive. There were no specific instructions by microsoft on moving VSS from one drive to another on the SAME computer. So we perfomed the following:
1. We copied the contents of the old vss to another place, as a backup.
2. Installed the VSS on the E drive.
3. Renamed the data folder for the new vss.
3. Copied the data, users, user.txt, temp folders to the new vss location.
4. Shared the vss folder.
This worked fine. We could open the VSS client on desktops and connect, check in and checkout files from the new vss. But the PROBLEM was that the existing web projects in VI did not connect to the new vss. When we checked the vss path in VI, the VI referred to the new vss path, and the files were said to be under source control. But the check outs and checkins did not reflect in the VSS client. I dont know, where these check outs were actually happening.
We tried several combinations, but in vain.
PLease, this is very very urgent and we have been fighting on this since days. Kindly provide a feasible solution. Most probably, if you have actually carried out sucha movement and reintegration, it will be very helpful.
Thanks.
We have the VSS installed in the dev server, where our web resides. Since there was a space crunch, we decided to attach a hard disk and move the vss from the C drive to the new E drive. There were no specific instructions by microsoft on moving VSS from one drive to another on the SAME computer. So we perfomed the following:
1. We copied the contents of the old vss to another place, as a backup.
2. Installed the VSS on the E drive.
3. Renamed the data folder for the new vss.
3. Copied the data, users, user.txt, temp folders to the new vss location.
4. Shared the vss folder.
This worked fine. We could open the VSS client on desktops and connect, check in and checkout files from the new vss. But the PROBLEM was that the existing web projects in VI did not connect to the new vss. When we checked the vss path in VI, the VI referred to the new vss path, and the files were said to be under source control. But the check outs and checkins did not reflect in the VSS client. I dont know, where these check outs were actually happening.
We tried several combinations, but in vain.
PLease, this is very very urgent and we have been fighting on this since days. Kindly provide a feasible solution. Most probably, if you have actually carried out sucha movement and reintegration, it will be very helpful.
Thanks.
