Consistent failures with importing VSS database

[tafountain]

We are currently evaluating SVG and am attempting to import our VSS database but keep running into a variety of errors. Most which appear to be connection related. I have followed the steps as outlined in the "Tips for a successful VSS Import" - checklist as follows:

• VSS db and SVG Import tool on same machine (database also resides on this machine
• Virus scanner off
• VSS 6.0c w/hotfix applied
• Using a backup copy that was 6.0d
• Analyze runs clean
• responseDeadLock set to 24:00:00
• executionTimeOut set to 86400
• SqlCommandTimeout set to 3600
• All deleted files have been purged

However, when I import our entire repository at once it appears to hang. Here is an except of that log file:

Code: Select all

Opening: C:\Program Files\Microsoft Visual Studio\VSS\srcsafe.ini
User: admin
VSS database open: True
Connected to Vault.
Logged out of the Vault Server.
There are 41758 files and projects selected for import.
Refreshing SourceSafe connection...
Opening: C:\Program Files\Microsoft Visual Studio\VSS\srcsafe.ini
User: admin
VSS database open: True
Connected to Vault.

Beginning Export.  5/12/2006 7:33:16 AM
Begin Export....

...rather large log file removed...

Memory used: 95211520.
CONNECTION EXCEPTION: Session is no longer valid.  Either the server restarted, or your session timed out.  You may need to login again to re-authenticate.
**Failed** - Second attempt to process $/<ProjectName>/AdministrativeScripts/AuditTriggerScript.sql - Created 
**Failed** to ProcessTransaction (PassTwo) Object reference not set to an instance of an object..
Trace:    at VSSImport.WizardForm.ExportPassTwo(Hashtable vssUsers)
Unhandled exception during export: Object reference not set to an instance of an object.
Trace:    at VSSImport.WizardForm.PrepareFileForTransaction(Revisions& rev)
   at VSSImport.WizardForm.ExportPassTwo(Hashtable vssUsers)
   at VSSImport.WizardForm.Export()
Logged out of the Vault Server.

Finished Export.  5/12/2006 8:06:37 AM
Item $/<ProjectName1> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName2> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName2> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName2> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName2> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName2> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/<ProjectName2> caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Connected to Vault.
Logged out of the Vault Server.
CONNECTION EXCEPTION: Session is no longer valid.  Either the server restarted, or your session timed out.  You may need to login again to re-authenticate.
VSS Database closed.

With all that in mind, I also get disconnected from both the desktop client and web client periodically. The web client does not display an error, rather it simply returns to the login page. The desktop client returns this error - "Session is no longer valid. Either the server restarted, or your session timed out. You may need to login again to re-authenticate.".

Please advise.

[lbauer]

Check your Vault Server log, sgvault.log in %windir%\temp\sgvault. Are there frequent "System Started" entries?

If so, IIS may be recycling too often. See this KB article for details:

http://support.sourcegear.com/viewtopic.php?t=1014

[tafountain]

There are some of those messages but there does not seem to be any pattern to the frequency. I did make the setting changes described in the link you provided, although, I figured they would not make a difference since Vault had it's own app pool space defined with the options already set as described in the document. I'll attempt another import and see what transpires.

[tafountain]

Linda,

I performed the import over the weekend and it imported successfully this time. However I am at a loss as to why. The KB article you referenced identifies changes to the DefaultAppPool, however the site was already configured to use a new app pool created by the installation named VaultAppPool. The VaultAppPool was already configured from the installation to the values specified in the stated KB article. On a side note, there were still several of the Item $/<ProjectName1> caused the transaction to fail: An item with the same name or object id already exists in the selected folder. messages but they did not cause the import to fail.

Thanks!

[lbauer]

I performed the import over the weekend and it imported successfully this time. However I am at a loss as to why.

Perhaps the stars in the heavens were aligned correctly? Or something about the network environment was better/different the second time? Glad to know it worked this time.