Vault import - is it still working?

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 8:44 am

We began an import yesterday for one of our VSS branches.

After nearly 24 hours, the import tool is working on the labels.

The top line reads "Pinning files..." and it mentions which label it's working on.

Other than checking task manager, is there any way to determine if the import is still working? The last log file entry was 3 hours ago,

----8/30/2005 4:35:41 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Logout
----8/30/2005 4:35:45 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Login
----8/30/2005 4:35:46 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled (5df6dd0a-59a5-47b1-addd-63766dff8076) BeginTxVSSImport returned: FailCheckInCommentRequired
----8/30/2005 4:35:46 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled (5df6dd0a-59a5-47b1-addd-63766dff8076) CheckIn: $/AdManager/Manteo/vibe/scripts/mandatory.sql returned: FailCheckInCommentRequired
----8/30/2005 4:35:46 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Logout
----8/30/2005 4:35:48 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Login
----8/30/2005 4:53:59 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Logout
----8/30/2005 4:54:01 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Login
----8/30/2005 5:14:14 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Logout
----8/30/2005 5:14:18 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Login
----8/30/2005 5:33:47 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Logout
----8/30/2005 5:33:50 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Login
----8/30/2005 5:55:24 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Logout
----8/30/2005 5:55:26 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Login
----8/30/2005 6:14:58 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Logout
----8/30/2005 6:15:00 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Login
----8/30/2005 7:30:36 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled PromoteLabelItems returned: FailInvalidObjVerID
----8/30/2005 7:30:59 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled PromoteLabelItems returned: FailInvalidObjVerID
----8/30/2005 7:31:07 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled PromoteLabelItems returned: FailInvalidObjVerID
----8/30/2005 7:31:16 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled PromoteLabelItems returned: FailInvalidObjVerID
----8/30/2005 7:32:08 AM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled Logout

Any suggestions?

lbauer · Post by **lbauer** » Tue Aug 30, 2005 9:47 am

As long as there's CPU or disk drive activity from the Import Tool, it's probably still working. Labels take a long time to import since the label needs to be "reconstructed."

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 9:59 am

I checked TaskManager, and the vssimport.exe is at "00".
How would I check disk activity for that process?

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 10:47 am

I've noticed that the Vault client also fails to connect, similarly "hanging".

I think the import is stalled completely at this point.

This is extremely frustrating. This will mark the 6th time in as many days I've attempted to import from VSS.

Each time, something always goes awry - and I have no feedback from the tool, until after a day or so passes, that anything is wrong.

There has to be a better way to do this...

lbauer · Post by **lbauer** » Tue Aug 30, 2005 10:59 am

Send me a copy of your sgvault.log file and the import log from the VSS import tool directory so we can see what's going on. Sometimes labels need to be imported separately.

Email to linda at SourceGear.com

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 11:42 am

How would I go about importing the labels seperately?

lbauer · Post by **lbauer** » Tue Aug 30, 2005 1:24 pm

OK, here's what the logs say about your import:

There were lots of errors like this:

----8/29/2005 6:26:48 PM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled (1ade3f7b-604b-450b-9384-628e0282f4c2) AddFolder: $/AdManager/Manteo/accse returned: FailObjAlreadyExists

It looks like you may have tried to reimport without deleting folders/files from the previous import attempts.

Also, the import log shows failed transactions:

Transaction failed
**Failed** - Error trying to commit. Exception of type System.Exception was thrown.

These are most likely related to these errors in the sgvault.log file:

----8/29/2005 10:37:47 PM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled (955d1ed5-2d71-4c53-93f5-2c96c48e9d42) BeginTxVSSImport returned: FailCheckInCommentRequired

It looks like your Vault server is configured to require checkin comments. Checkins (commits) by the import tool are failing because there is no comment. Be sure this is off before your next import. The setting is in the Vault Admin Tool->Repository Options.

In your email you also mentioned running out of disk space due to cache filescreated by the import tool. If you plan to reimport, you can safely delete these files. Once you've completed a successful import, you can delete them as well.

You might be able to change the location for these cache files if you login as Admin using a Vault Client that's on the same machine as the Import Tool. The option is in the Vault 3.1.x client under Tools->Options->Local Files->Cache/Backup locations. Since the Import Tool runs under the Admin account, changing this setting may change the cache location for the import as well.

If you delete items from previous import attempts, clear some disk space, and disable the requirement for checkin comments, your import should proceed more smoothly.

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 1:27 pm

Linda,

Thank you for your suggestions... I will try them now.

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 1:40 pm

It was mentioned that labels might have to be imported separately - how is this done?

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 1:46 pm

During the delete of the old repository, I got this message:

VaultServiceAPILib.VaultSoapException: 1104 : FailDBReader
at VaultService.VaultAdminService.DeleteRepository(Int32 nRepID)

lbauer · Post by **lbauer** » Tue Aug 30, 2005 1:56 pm

Are you using SQL Server SP 4?

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 2:04 pm

Possibly - where should I look to verify that?

If I am, what should I do? I'll check the requirement for Vault and re-read the section about SQL Server in the meantime.

lbauer · Post by **lbauer** » Tue Aug 30, 2005 2:07 pm

It was mentioned that labels might have to be imported separately - how is this done?

In earlier versions of Vault if there was a problem importing labels, we'd have users import without labels and then provide a special build of the Import Tool which would import the labels.

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 2:09 pm

I used the Help->Tech Support option:

SQL Version: Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

lbauer · Post by **lbauer** » Tue Aug 30, 2005 2:20 pm

Looks like you have the RTM version:

http://support.microsoft.com/default.as ... -us;321185

I don't know that we've tested Vault with that. There's a known issue with SQL Server 2000 SP 4 and deleting a repository. But this may be something else.

Ok, send me another copy of the sgvault.log file.