VSS Import crashes on No Users

[wkrzystek]

Good evening. I'm trying to build a demo of the VSS import utility for a conference presentation on Vault and I've setup a basic VSS 6.0c database with a couple of folders and one user other than the admin. There is only one file in the database with 3 revisions. This is a clean install of VSS 6.0c and a brand new database created just for demo purposes. In the pre-scan, the message "the data to be imported contains -1 files and 5 projects. It is estimated that when the import begins, it will take 00:00:00 for completion" is shown and when the user mapping is shown, there are no VSS users listed:

usermapping.png (15.88 KiB) Viewed 3623 times

This then produced the following error:

errordialog.png (27.84 KiB) Viewed 3623 times

I'm using Vault 4.1.4. The VSS database is on the same demo machine as my Vault server installation. I've tried every combination, removed and reinstalled VSS a few times, deleted databases and created new databases, folder security enabled and not. I'm somewhat lost on what to do next.

This seems to be the same error as http://support.sourcegear.com/viewtopic ... ers#p15559 but their issues seemed to be related to VSS 5.0. Mine is a 6.0c clean install.

Any help you can provide would be greatly appreciated. I'd hate to have to skip the demo on how to convert from VSS to Vault. Does Vault 5.0 still offer a convert option from VSS or does it just use the new handoff solution?

[lbauer]

Is there a VSS Explorer client 6.0.c installed on the VSS Import Tool machine? The VSS Import Tool uses the automation component provided by the client installation.

Check to see if you have this registry entry in HKEY_CLASSES_ROOT\CLSID:

783CD4E4-9D54-11CF-B8EE-00608CC9A71F

This is the ClassID for the automation component, called ssapi.dll.

[wkrzystek]

Yes, I have that clsid installed. Here is the contents of the registry at that location:

Code: Select all

[HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}]
@="Microsoft Visual SourceSafe Automation"

[HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32]
@="C:\\Program Files\\Microsoft Visual Studio\\VSS\\win32\\SSAPI.DLL"
"ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\NotInsertable]

[HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\ProgID]
@="SourceSafe.0"

[HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\VersionIndependentProgID]
@="SourceSafe"

The ssapi.dll is dated Thursday, May 23, 2002, 10:43:38 AM and was part of the VSS 6.0c hotfix. Just an FYI - I had tried this before and after I discovered the hotfix requirement and I received the same results each time.

[lbauer]

Do you have the right version of the VSS Import Tool -- the one for 4.1.4?

It would be helpful to see the log files. There should be an import log in the import tool directory.

We'd like to see a copy of the Vault Server log that covers the import failure, It's called sgvault.log and is in %windir%\temp\sgvault on the server machine.

Also, any errors in the Windows Event viewer on the Import Tool machine?

Send the logs zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[wkrzystek]

Linda,

I've sent the log files over via email. Nothing in the windows event viewer that jumped out at me. I had to try it again this morning with the server logging set to debug. Let me know anything else you need. Thanks.

Walt

[lbauer]

The user sent his VSS database and we were able to import it with no problems. There may be something specific to the automation component or something on his machine. He's decided to use the VSS Handoff in 5.0 instead, and that worked fine.