Vault Standard Handoff from VSS

[clarkec21]

Hi
I am getting an issue when handing off a folder from VSS to SGV:
Handoff
Summary
The following errors were encountered during the handoff:
Object reference not set to an instance of an object.

SGV Standard V6.1.0
VSS V6.0

The issue is with two out of the many files in the VSS folder. Taking the files out of the VSS, handoff works fine. Put them back, does not work. Delete the files and add a new version of the file at V1 same issue.

Any ideas what could be wrong here.
We do have a huge very old VSS system and there are many folders with this issue.
**Brief update, managed to get files to handoff by deleting, renaming locally to lowercase and copying into a source VSS folder, then them copying to the folder I need them in within VSS and finally handing off...complex - How do I identify all these files I could have issue with?

[lbauer]

Do these problem files have anything in common -- type, size, content?

Maybe we can get a better idea of what's happening by looking at the the Vault Server log.

The Vault server log is called sgvault.log and is in %windir%\temp\sgvault on the server machine. Send it to support at sourcegear.com, ATTN: Linda.

Please include a link to this forum post.

Also -- any errors captured in the Windows Event viewer that correspond to the Object Reference error?

[clarkec21]

Hi Linda, its seems by simply changing to lowercase file type (not sure why our developer used uppercase) and it works.

Here is the output from the log file.

----01/02/2013 15:56:44 admin--10636-dv.nhbc.ad(10.137.121.32)--SSL Disabled System.NullReferenceException: Object reference not set to an instance of an object.
at VaultServiceBase.ThreadCommand.GetResult()
at VaultServiceBase.ThreadCommand.RunOnThread(MultiUseWorkerThread worker)
at VaultServiceAPILib.VSSOperations.CreateShareChanges(String vssPath, String vaultPath, Int32 importRunID, ArrayList& requests)
at VaultServiceAPILib.VaultServiceAPI.RunCannedImport(Int32 externalID, Int32 repid, Int32 userid, String srcsafeImportRoot, String vaultDestinationPath, VSSImportProgressMessage message, VSSImportErrorMessage error)
at VaultService.Admin.Handoff.ThreadCallBack(Object state)
at VaultServiceBase.WorkerThread.ThreadMain() at VaultServiceBase.ThreadCommand.GetResult()
at VaultServiceBase.ThreadCommand.RunOnThread(MultiUseWorkerThread worker)
at VaultServiceAPILib.VSSOperations.CreateShareChanges(String vssPath, String vaultPath, Int32 importRunID, ArrayList& requests)
at VaultServiceAPILib.VaultServiceAPI.RunCannedImport(Int32 externalID, Int32 repid, Int32 userid, String srcsafeImportRoot, String vaultDestinationPath, VSSImportProgressMessage message, VSSImportErrorMessage error)
at VaultService.Admin.Handoff.ThreadCallBack(Object state)
at VaultServiceBase.WorkerThread.ThreadMain()
----01/02/2013 15:56:46 admin--10636-dv.nhbc.ad(10.137.121.32)--SSL Disabled Handoff Error: Object reference not set to an instance of an object.

Where/how can I see the windows event viewer?

[lbauer]

The Windows Event Viewer would be on the Vault Server machine in Control Panel->System and Security->Administrative Tools->Event Viewer. I'd suggest looking in the Application logs.

[lbauer]

Vault Server uses the SourceSafe Automation Component to communicate with the SourceSafe database. Sometimes different versions of the ssapi.dll behave differently.

What version of the SourceSafe Automation Component is Vault Server using?

This will help you find the version:

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

[clarkec21]

Hi Linda

The ssapi.dll file version is 6.0.81.69. Cannot seem to see anything of significance in the logs, nothing related to VSS or SGV.

[lbauer]

That version of the ssapi.dll is not the best to use.

We'd recommend that you use either VSS 2005 sp1 or VSS 6.0c.

VSS 6.0.c version 96.40 was a special fix of the ssapi.dll from Microsoft. It's available at http://download.sourcegear.com/files/vss_60c_hotfix.zip. You can use the contents of the .zip file to replace the contents of the win32 directory of your existing SourceSafe directory

[clarkec21]

Linda,
I applied the 6c fix, that had no effect - I am still having to find those uppercase file types to stop this error.

On another folder I am getting the following
Lots of these errors for different files:
Exception creating add request for $/fusion/Implementation/Software Components/Java/projects/OnlineServicesProgramme/weblogic_project/Extranet/.settings/.jsdtscope: Object reference not set to an instance of an object.Finally this one:
NO_SUCH_FILE_OR_PROJECT

Do you know if this is related or something else?

[lbauer]

There were issues with older versions of VSS changing the case on files added from the file system. I also seem to recall another customer who had trouble moving to Vault because of case issues in VSS and the automation component not being able to handle them.

In some Internet searches, this particular case issue was fixed in VSS 6.0d, build 31112, which was included in Visual Studio 6, SP 6.

Another version of the automation component might help, if you have later versions of VSS. Or you may have to change the cases on your files.

The NO_SUCH_FILE_OR_PROJECT is usually seen when there's VSS database corruption.

Did you run Analyze on the VSS database before doing the handoff?

http://msdn.microsoft.com/en-us/library ... s.80).aspx

We recommend the -f and -c parameters.

Also, sometimes an Archive and Restore operation to a new database can help clear up VSS database corruption.

[clarkec21]

More progress : )
The folders called '.settings' had to be renamed to stop the error in my last post, however I still get NO_SUCH_FILE_OR_PROJECT.

I looked into VSS 6.0d and despite saying success I seem to still have 6.0c....??

Yes I analysed VSS using the following:
analyze -C -D -F -V4 "E:\Program Files\Microsoft Visual Studio\VSS\data"

I have emailed you the log file ( support at sourcegear.com). Took around 10 hours and looks to have found some pretty serious issues!