VSS import problems left other problems
Moderator: SourceGear
VSS import problems left other problems
I recently migrated approximately 30 VSS repositories into about 6 Vault repositories. On some imports I got errors while importing labels, some went fine.
Unfortunately it now seems that some of the Vault repositories are failing with FailDBInsert when I try to view Labels or History. I can't be certain, but my guess is that the repositories that are now throwing the error are the same that had label insert failures.
I'd like to *not* have to reimport the entire VSS repositories, as it took we a week to do the first time. Ideally I'd be able to reimport just the labels, but even if the labels that failed to import were simply dropped and I was able to view labels that would be better than the current situation.
The error log shows this on a 'View Labels':
----11/9/2004 9:38:51 AM ctacke--sw2.applieddata.net(192.168.0.50)--SSL Disabled
Violation of PRIMARY KEY constraint 'PK__@resulttree__6FAD9074'. Cannot insert duplicate key in object '#6EB96C3B'.
The statement has been terminated.
----11/9/2004 9:38:51 AM ctacke--sw2.applieddata.net(192.168.0.50)--SSL Disabled
BeginLabelQuery returned: FailDBInsert
I'm using version 2.0.6
Unfortunately it now seems that some of the Vault repositories are failing with FailDBInsert when I try to view Labels or History. I can't be certain, but my guess is that the repositories that are now throwing the error are the same that had label insert failures.
I'd like to *not* have to reimport the entire VSS repositories, as it took we a week to do the first time. Ideally I'd be able to reimport just the labels, but even if the labels that failed to import were simply dropped and I was able to view labels that would be better than the current situation.
The error log shows this on a 'View Labels':
----11/9/2004 9:38:51 AM ctacke--sw2.applieddata.net(192.168.0.50)--SSL Disabled
Violation of PRIMARY KEY constraint 'PK__@resulttree__6FAD9074'. Cannot insert duplicate key in object '#6EB96C3B'.
The statement has been terminated.
----11/9/2004 9:38:51 AM ctacke--sw2.applieddata.net(192.168.0.50)--SSL Disabled
BeginLabelQuery returned: FailDBInsert
I'm using version 2.0.6
I assume that 2.0.6 is for both - I just looked in Help->About to get the version. It's been installed for less than a month if that's any indicator.
The database has not been restored at all. Basically I just did the import and one of my devs tried to view Labels and got the error, which I've confirmed.
If it makes any difference, the import may have been "non standard" in that I merged a lot of separate VSS repositories into only a few Vault repositories. However each VSS repository went into a unique subfolder/tree in the new repository, so there was no overlap, nor was there any sharing on the original.
The database has not been restored at all. Basically I just did the import and one of my devs tried to view Labels and got the error, which I've confirmed.
If it makes any difference, the import may have been "non standard" in that I merged a lot of separate VSS repositories into only a few Vault repositories. However each VSS repository went into a unique subfolder/tree in the new repository, so there was no overlap, nor was there any sharing on the original.
You'll need access to the Vault Admin Tool. Log in, and look at the properties for the Repository in which the label was created.
On the properties page, there will be a check box "Enable Folder Security". Turn this off, and then look at the label from within the GUI client. Does it work with security disabled?
On the properties page, there will be a check box "Enable Folder Security". Turn this off, and then look at the label from within the GUI client. Does it work with security disabled?
Jeff Clausius
SourceGear
SourceGear
Ok, I understand now. In that case then Folder Security is off for the repositories that are showing the error.
I should also elaborate that "Show Labels" doesn't fail for the entire repository, just for some folders.
For example, I had two VSS repositories: PLAT1 and PLAT2
I imported them into a single Vault repository like this
WINCE420
--PLAT1
--PLAT2
I can view labels fine for PLAT1, but PLAT2 gives the error.
Obviously this is simplified - my actual repository has about 10 "PLAT" folders, and a couple of them give the error.
I should also elaborate that "Show Labels" doesn't fail for the entire repository, just for some folders.
For example, I had two VSS repositories: PLAT1 and PLAT2
I imported them into a single Vault repository like this
WINCE420
--PLAT1
--PLAT2
I can view labels fine for PLAT1, but PLAT2 gives the error.
Obviously this is simplified - my actual repository has about 10 "PLAT" folders, and a couple of them give the error.
Chris:
1) If you invoke to recursively "Show Labels" on $/, does that fail? Or is it when you show labels on a sub folder of the tree? If on a sub folder, what is that folders full path?
2) For the history failure, does it fail if you choose to NOT include labels in the history query? Does the history query fail when invoked recursively on $/ or on a sub folder of the tree? If on a sub folder, what is that folders full path?
3) Has the .Net 2.0 Beta framework been installed on the server?
1) If you invoke to recursively "Show Labels" on $/, does that fail? Or is it when you show labels on a sub folder of the tree? If on a sub folder, what is that folders full path?
2) For the history failure, does it fail if you choose to NOT include labels in the history query? Does the history query fail when invoked recursively on $/ or on a sub folder of the tree? If on a sub folder, what is that folders full path?
3) Has the .Net 2.0 Beta framework been installed on the server?
Jeff Clausius
SourceGear
SourceGear