Connection to repository fails after VSS import
Moderator: SourceGear
-
- Posts: 4
- Joined: Wed Nov 08, 2006 4:59 pm
Connection to repository fails after VSS import
Hi everyone,
We've recently decided to change our source control from VSS, and thought we'd give Vault a trial. We'd like to of course import our projects as they stand, so the import tool seemed like it would suit. Following all the guidelines like using 6.0c distributables, the import process goes through to completion.
When I attempt to connect to the repository however (which displays as containing a few thousand files, and a few hundred folders as you would expect), every connection attempt fails with "Session is no longer valid. Either the server restarted, or your session timed out. You may need to login again to re-authenticate." This may be explained by some of the other topics I have read through here, except connections to the default repository work just fine.
Any help or guidance on this would be great, and much appreciated.
Oh yeah, tech specs..
Client Information
Vault Client Version: 3.5.1.4786
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT+10:00) Canberra, Melbourne, Sydney
We've recently decided to change our source control from VSS, and thought we'd give Vault a trial. We'd like to of course import our projects as they stand, so the import tool seemed like it would suit. Following all the guidelines like using 6.0c distributables, the import process goes through to completion.
When I attempt to connect to the repository however (which displays as containing a few thousand files, and a few hundred folders as you would expect), every connection attempt fails with "Session is no longer valid. Either the server restarted, or your session timed out. You may need to login again to re-authenticate." This may be explained by some of the other topics I have read through here, except connections to the default repository work just fine.
Any help or guidance on this would be great, and much appreciated.
Oh yeah, tech specs..
Client Information
Vault Client Version: 3.5.1.4786
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT+10:00) Canberra, Melbourne, Sydney
We'd like to see a copy of the Vault server log file -- sgvault.log in %windir%\temp\sgvault. Send a copy of the log to support@sourcegear.com ATTN Linda. Be sure to include a link to this forum post in your email.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 4
- Joined: Wed Nov 08, 2006 4:59 pm
It does look like the Vault server is restarting at short intervals.
What operating system and .NET Framework version is the Vault Server installed on?
If you create another repository and add some folders/files, do you have the same connection issues?
What operating system and .NET Framework version is the Vault Server installed on?
If you create another repository and add some folders/files, do you have the same connection issues?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 4
- Joined: Wed Nov 08, 2006 4:59 pm
Hi Linda,
Here's the details for the Server
.Net Framework Version: 1.1.4322.2300
Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
Also, we have created other repositories with a few thousand files and multiple folders without any issues. We can connect to them just fine. It is only repositories populated from the Import Tool.
Here's the details for the Server
.Net Framework Version: 1.1.4322.2300
Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
Also, we have created other repositories with a few thousand files and multiple folders without any issues. We can connect to them just fine. It is only repositories populated from the Import Tool.
I'd like to see another copy of the Vault log, this time in Debug mode. Enable debug logging in the Vault Admin Tool->Server options->Logging.
Log into and connect to the "good" repository.
Then connect to the VSS import repository. Send me a copy of the log file, and let me know what time in the log and what username to look for.
Log into and connect to the "good" repository.
Then connect to the VSS import repository. Send me a copy of the log file, and let me know what time in the log and what username to look for.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 4
- Joined: Wed Nov 08, 2006 4:59 pm
Hi Linda,
Just making sure you received my last email confirming that I have completed all your suggestions, and whether or not that means you guys are unable to help any further with us getting this installation up and running.
If this is the case we are going to have to move on and start looking at another source control solution.
Just making sure you received my last email confirming that I have completed all your suggestions, and whether or not that means you guys are unable to help any further with us getting this installation up and running.
If this is the case we are going to have to move on and start looking at another source control solution.