Error popup on import

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
OrovilleTim
Posts: 16
Joined: Tue Apr 18, 2006 2:32 pm
Location: Lake Oroville, CA

Error popup on import

Post by OrovilleTim » Wed Apr 19, 2006 9:08 am

I'm doing some test importing as part of an evaluation. Here's the scoop:

Server where the import is occurring has the database copied from the production server. It has the 6.0c w/ hotfix.
The Vault server is on a remote server.

We have what I thought was a large SourceSafe database. It's like 1.7GB on disk, but for an archive, it's only 176MB.

Anyway, I've tried to do imports of the entire database into one repository, or just the main project in the database into its own repository.
The pre-scan eventually completes, but in the import process the following error dialog pops up:

Window title = "SourceGear Vault - SourceSafe Import", error text = "Error opening SourceSafe database. Object reference not set to an instance of an object."

If you click it, it continues, but later in the import it just sits there with idle CPU and has to be cancelled.

I thought first maybe there was something with the database and did and analyze with no errors found and tried it again with similar results. This morning I started again but started doing little sections of the database into their own repositories and they seem to be working fine so far.

Any insight? Sorry if this is covered in here somewhere, but when I tried searching for this error here, it contains so many terms that hit. I tried quoting the string still didn't get me a literal search, just a bunch of hits on individual words.

Thanks,
Tim

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Apr 19, 2006 10:45 am

Is there any useful information in the import.log file in the Import Tool directory that coincides with the original failure?
Linda Bauer
SourceGear
Technical Support Manager

OrovilleTim
Posts: 16
Joined: Tue Apr 18, 2006 2:32 pm
Location: Lake Oroville, CA

Post by OrovilleTim » Wed Apr 19, 2006 11:18 am

the earliest errors seen are as follows:


Code: Select all

Created 	($/Companions/PDA Line/PDA100Palm/frmLoading.frx) at 5/1/2002 3:36:56 PM(Links: $/Companions/PDA Line/PDA100PPC/frmLoading.frx	$/Companions/PDA Line/PT01PPC/frmLoading.frx	$/Companions/PDA Line/PT01Palm/frmLoading.frx	)
Change set type: AddFile
Adding to transaction: $/Companions/PDA Line/PDA100Palm/frmLoading.frx - C:\DOCUME~1\ADMINI~1.QSS\LOCALS~1\Temp\tmpFDF9.tmp
An error occurred while trying to end a transaction.
An exception was encountered during the transaction.  Exception: Exception of type System.Exception was thrown.   at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)
Transaction failed
Transaction failed
**Failed** - Error trying to commit. Exception of type System.Exception was thrown.
Trace:   at VSSImport.WizardForm.ProcessTransaction(String strProgressText, DateTime dtg, Int32 userID)
4/19/2006 8:51:40 AM - Unable to commit for 5/1/2002 3:36:56 PM - $/Companions/PDA Line/PDA100Palm/frmLoading.frx - Created .
Refreshing SourceSafe connection...
Opening: C:\SourceSafe\srcsafe.ini
User: admin
VSS database open: True
It then gets a bunch of these and later more errors show up like this:

Code: Select all

nable to Get $/Companions/QC01/QC01.BAS to disk.
**Failed** to Get version 9 of $/Companions/QC01/QC01.BAS to upload.
VSS Database closed.
Checked in $/Companions/QC01	($/Companions/QC01/QC01.BAS) at 11/15/2002 2:17:40 PM
**Failed**. File not found in tree: $/Companions/QC01/QC01.BAS 	Converting action to a ChangeSetItem_AddFile message.
Change set type: AddFile
**Failed** to get the VSSItem for version 10 of: '$/Companions/QC01/QC01.BAS'
System.NullReferenceException
Object reference not set to an instance of an object.
I can send you a log file via email if you like.

Thanks,
Tim

OrovilleTim
Posts: 16
Joined: Tue Apr 18, 2006 2:32 pm
Location: Lake Oroville, CA

Post by OrovilleTim » Wed Apr 19, 2006 11:58 am

I am trying something else too... I've deleted everything from the copy of the database on the second machine, am reimporting from an archive, and then will give it a go again in case there was something the analyze didn't catch.

Tim

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Apr 19, 2006 12:11 pm

If this reimport has problems, I'd like to see both the import log and the Vault server log for the time of the import. It's sgvault.log in the %windir%\temp\sgvault directory on the server machine.
Linda Bauer
SourceGear
Technical Support Manager

OrovilleTim
Posts: 16
Joined: Tue Apr 18, 2006 2:32 pm
Location: Lake Oroville, CA

Post by OrovilleTim » Wed Apr 19, 2006 12:15 pm

lbauer wrote:If this reimport has problems, I'd like to see both the import log and the Vault server log for the time of the import. It's sgvault.log in the %windir%\temp\sgvault directory on the server machine.
Ok, this may take a while, but either way I'll report back.

OrovilleTim
Posts: 16
Joined: Tue Apr 18, 2006 2:32 pm
Location: Lake Oroville, CA

Post by OrovilleTim » Thu Apr 20, 2006 2:42 pm

Received that popup again, so I cancelled it, collected the requested logs, and emailed them to the support address.

Thanks,
Tim

Post Reply