continuing problems with server/NIC disconnects
Moderator: SourceGear
continuing problems with server/NIC disconnects
We continue to have problems with our VSS/SoS server disconnecting from the network when our users perform a GET.
Our server is:
Compaq DL-320
Windows 2000 w/ SP4 and all updates.
SourceOffsite 3.5.3
VSS 6.0(not d)
We also had this problem with the following environment:
Compaq DL-320
Windows 2003 w/ all updates.
SourceOffsite 3.5.3
VSS 6.0(not d)
The only fix for this issue is to manually goto the machine and disable/re-enable the network card.
Other steps taken to troubleshoot.
1. Built a separate machine for SoS/VSS that then had a drive mapped to the box with the code tree on it. This did NOT cause the network connectivity to drop, however it did cause SoS to cease to function. Stopping and restarting the SoS service did not resolve the problem. Only by rebooting the SoS/VSS server was functionality restored.
2. Since initial machine was running Windows2003, we have since re-built the box on a completely separate server and it now runs 2000 (see platform descriptions above). This has eliminated Windows 2003, and that particular DL-320, out of the equation.
3. We have made sure we have the most up-to-date version of the MSVM on the machine per your recommendations.
4. The SourceGear log.txt file shows no indication of error or problem.
Question:
Should the 'Syncronize access to Sourcesafe automation component' box be checked?
It should also be noted that none of our standard VSS users report any problems with these machines, only SoS users. We are completely at a loss here, and have many developers and managers who are frustrated with our configuration and environment. Any help SourceGear can provide would be greatly appreciated.
Our server is:
Compaq DL-320
Windows 2000 w/ SP4 and all updates.
SourceOffsite 3.5.3
VSS 6.0(not d)
We also had this problem with the following environment:
Compaq DL-320
Windows 2003 w/ all updates.
SourceOffsite 3.5.3
VSS 6.0(not d)
The only fix for this issue is to manually goto the machine and disable/re-enable the network card.
Other steps taken to troubleshoot.
1. Built a separate machine for SoS/VSS that then had a drive mapped to the box with the code tree on it. This did NOT cause the network connectivity to drop, however it did cause SoS to cease to function. Stopping and restarting the SoS service did not resolve the problem. Only by rebooting the SoS/VSS server was functionality restored.
2. Since initial machine was running Windows2003, we have since re-built the box on a completely separate server and it now runs 2000 (see platform descriptions above). This has eliminated Windows 2003, and that particular DL-320, out of the equation.
3. We have made sure we have the most up-to-date version of the MSVM on the machine per your recommendations.
4. The SourceGear log.txt file shows no indication of error or problem.
Question:
Should the 'Syncronize access to Sourcesafe automation component' box be checked?
It should also be noted that none of our standard VSS users report any problems with these machines, only SoS users. We are completely at a loss here, and have many developers and managers who are frustrated with our configuration and environment. Any help SourceGear can provide would be greatly appreciated.
oops..forgot to login ...
forgot to login to the forum before posting the issue...
Re: oops..forgot to login ...
Does this server have more than one NIC in it?blackbaud wrote:forgot to login to the forum before posting the issue...
Go Illini!
yes, and no...
these new DL-320s have dual NICs, but the HP utilities allow you to 'cluster' them in a failover manner. In other words, the two NICs are currently acting as one interface, which in Win2k shows up as 'Network Connection 3'. We have tried configuring just one NIC and disabling the other, all with the same results. These machines have never been configured with separate networks on either interface to do any kind of routing.
these new DL-320s have dual NICs, but the HP utilities allow you to 'cluster' them in a failover manner. In other words, the two NICs are currently acting as one interface, which in Win2k shows up as 'Network Connection 3'. We have tried configuring just one NIC and disabling the other, all with the same results. These machines have never been configured with separate networks on either interface to do any kind of routing.
I don't know if your case is the same, but most multi-NIC users reported that their problems went away when they removed one NIC (not possible on the DL-320, right?).
Have you tried the latest preview of SOS 4? The server is written in C# and SourceGear doesn't think the multi-NIC card problem exists any longer.
Have you tried the latest preview of SOS 4? The server is written in C# and SourceGear doesn't think the multi-NIC card problem exists any longer.
Go Illini!
Same Problem
We are having the same problem. Is there any fix to this? We are using HP servers.
See this KB article for details on this issue:
http://support.sourcegear.com/viewtopic.php?p=1153
This problem will be fixed in SOS 4.0, which is not written in Java.
http://support.sourcegear.com/viewtopic.php?p=1153
This problem will be fixed in SOS 4.0, which is not written in Java.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
See this KB article for details on this issue:
http://support.sourcegear.com/viewtopic.php?p=1153
This problem will be fixed in SOS 4.0, which is not written in Java.
http://support.sourcegear.com/viewtopic.php?p=1153
This problem will be fixed in SOS 4.0, which is not written in Java.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager