Import Tool Exceptions

cs · Post by cs » Tue Oct 25, 2005 2:04 am

You may be familiar with my failed import in the 'Obliterate Issues' topic.

As instructed I deleted the Vault database and attempted another import with the last few labels (7).

The prescan worked fine.

All the labels I selected to import failed with exceptions as shown at the bottom of the import report shown below:

.....
**Failed** to Get version 4 of $/Source/MyProject/Plugins/0012/codebase.dat to upload.
**Failed** to Get version 5 of $/Source/MyProject/Plugins/0012/codebase.dat to upload.
**Failed** to Get version 6 of $/Source/MyProject/Plugins/0012/codebase.dat to upload.
**Failed** to Get version 7 of $/Source/MyProject/Plugins/0012/codebase.dat to upload.
**Failed** to Get version 8 of $/Source/MyProject/Plugins/0012/codebase.dat to upload.
Label Import: The label $/Source/MyProject (V2.36) could not be imported because an exception occured.
Label Import: The label $/Source/MyProject (V2.35) could not be imported because an exception occured.
Label Import: The label $/Source/MyProject (V2.33) could not be imported because an exception occured.
Label Import: The label $/Source/MyProject (V2.38) could not be imported because an exception occured.
Label Import: The label $/Source/MyProject (2.40) could not be imported because an exception occured.
Label Import: The label $/Source/MyProject (2.37) could not be imported because an exception occured.
Label Import: The label $/Source/MyProject (V2.39) could not be imported because an exception occured.
Label Import: The label $/Source/MyProject (V2.34) could not be imported because an exception occured.
12:04:32.7197974

The labels appear when click on 'Show Labels' in Vault client.

1) Do I need to re-import the project?

2) Why were there exceptions?

Post by **jeremy_sg** » Tue Oct 25, 2005 10:44 am

What does your import log file look like? This will probably have more information about the exceptions.

cs · Post by cs » Wed Oct 26, 2005 1:27 am

The file is 10Mb. Searched for 'exception'. Results below.

Had hundreds of:

**Failed** to get the VSSItem for version nn of: '$/Source/myproject/myfiles/blabla/myfile.ext'
System.Runtime.InteropServices.COMException
Error reading from file

The number nn above can be any number.

Several of these:

Exception during label import $/Source/Myproject (V2.36) : System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at VaultServiceAPILib.VaultServiceAPI.PromoteLabelItems(Int32 nUserID, Int32 nRepID, String strItemPath, Int64 nLabelID, String strLabelName, VaultLabelPromotionItem[] vlpi, DateTime importLabelDate, Boolean bIsImport, DateTime& dtLastChange, Int32& nIdxFailed, String& strRootPathConflict)
at VaultService.VaultService.ImportPromoteLabelItems(Int32 nRepID, String strItemPath, Int64 nLabelID, String strLabelName, VaultLabelPromotionItem[] vlpi, DateTime labelDate, DateTime& dtLastChange, Int32& nIdxFailed)
--- End of inner exception stack trace ---
Trace: at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.ClientService.VaultService.ImportPromoteLabelItems(Int32 nRepID, String strItemPath, Int64 nLabelID, String strLabelName, VaultLabelPromotionItem[] vlpi, DateTime labelDate, DateTime& dtLastChange, Int32& nIdxFailed)
at VaultClientNetLib.VaultConnection.ImportPromoteLabelItems(Int32 nRepID, String strItemPath, Int64 nLabelID, String strLabelName, DateTime labelDate, DateTime& dtLastChange, VaultLabelPromotionItem[] vlpi, Int32& nIdxFailed)
at VSSImport.WizardForm.DoLabel(Hashtable labelItems, String strVSSLabelRoot, String labelString, Int32 nUserID, VaultLabelInfo& vaultLabelInfo)
at VSSImport.WizardForm.ExportPassThree(Hashtable vssUsers)

Post by **jeremy_sg** » Wed Oct 26, 2005 12:40 pm

Unfortunately, there's not much help on that VSS error message.

http://msdn.microsoft.com/library/defau ... e_read.asp

I would recommend retrying the import.

cs · Post by cs » Thu Oct 27, 2005 1:49 am

That's a great help.

We've spent enough time and money trying to import our source code using your poor tools, thanks.

Here's another exception your Import Wizard raises:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ObjectDisposedException: Cannot access a disposed object named "FormCheckComments".
Object name: "FormCheckComments".
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Form.CreateHandle()
at System.Windows.Forms.Control.get_Handle()
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at VSSImport.WizardForm.wizard1_NextButtonClick(Object sender, WizardPageCancelEventArgs e)
at ActiproSoftware.Wizard.Wizard.?(WizardPageCancelEventArgs )
at ActiproSoftware.Wizard.Wizard.?(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2300
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
VSSImport
Assembly Version: 3.1.2.3511
Win32 Version: 3.1.2.3511
CodeBase: file:///C:/Program%20Files/SourceGear/SourceSafe%20Import%20Tool/VSSImport.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2300
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2300
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
VaultClientOperationsLib
Assembly Version: 3.1.2.3511
Win32 Version: 3.1.2.3511
CodeBase: file:///C:/Program%20Files/SourceGear/SourceSafe%20Import%20Tool/VaultClientOperationsLib.DLL
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2300
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
ActiproSoftware.Wizard
Assembly Version: 1.4.60.0
Win32 Version: 1.4.60.0
CodeBase: file:///C:/Program%20Files/SourceGear/SourceSafe%20Import%20Tool/ActiproSoftware.Wizard.DLL
----------------------------------------
VaultLib
Assembly Version: 3.1.2.3511
Win32 Version: 3.1.2.3511
CodeBase: file:///C:/Program%20Files/SourceGear/SourceSafe%20Import%20Tool/VaultLib.DLL
----------------------------------------
VaultClientNetLib
Assembly Version: 3.1.2.3511
Win32 Version: 3.1.2.3511
CodeBase: file:///C:/Program%20Files/SourceGear/SourceSafe%20Import%20Tool/VaultClientNetLib.DLL
----------------------------------------
System.Web.Services
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2300
CodeBase: file:///c:/windows/assembly/gac/system.web.services/1.0.5000.0__b03f5f7f11d50a3a/system.web.services.dll
----------------------------------------
Interop.SourceSafeTypeLib
Assembly Version: 5.1.0.0
Win32 Version: 5.1.0.0
CodeBase: file:///C:/Program%20Files/SourceGear/SourceSafe%20Import%20Tool/Interop.SourceSafeTypeLib.DLL
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2300
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
zinawtq4
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2300
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Web
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2300
CodeBase: file:///c:/windows/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
----------------------------------------
2o1wjeqq
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2300
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Management
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2300
CodeBase: file:///c:/windows/assembly/gac/system.management/1.0.5000.0__b03f5f7f11d50a3a/system.management.dll
----------------------------------------
CustomMarshalers
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/custommarshalers/1.0.5000.0__b03f5f7f11d50a3a/custommarshalers.dll
----------------------------------------
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------
VCDiff
Assembly Version: 3.1.2.3511
Win32 Version: 3.1.2.3511
CodeBase: file:///C:/Program%20Files/SourceGear/SourceSafe%20Import%20Tool/VCDiff.DLL
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.

Post by **jeremy_sg** » Thu Oct 27, 2005 7:42 am

cs,

Email me using the button below this post, and I'll try to figure out why the import tool is failing you.

ian_sg · Post by **ian_sg** » Thu Oct 27, 2005 2:22 pm

cs,

It's unfortunate that your first experience with Vault involved probably the two most difficult things Vault does:

1) Import from SourceSafe
2) Obliterate, particularly the atypical data that comes from the SourceSafe import.

Getting past this phase can be difficult for folks with lots of data in SourceSafe, but done carefully it is very much worth the effort.