Orphaned repository after 3.5.2 -> 4.1.1 upgrade
Moderator: SourceGear
Orphaned repository after 3.5.2 -> 4.1.1 upgrade
We upgraded from Vault 3.5.2 to 4.1.1 recently, and we've discovered that one of our users has access to a repository that doesn't show up in the admin client.
Nobody else has access to that repository either.
We tried upgrading to 4.1.2 but that didn't help.
We'd like to delete the repository and verify that there are no other "orphaned" repositories.
How do we do that?
Thanks.
Nobody else has access to that repository either.
We tried upgrading to 4.1.2 but that didn't help.
We'd like to delete the repository and verify that there are no other "orphaned" repositories.
How do we do that?
Thanks.
Are they logging into the correct Vault Server?
Can they actually log into that repository?
If not, the first thing I would do is delete the user's client-side cache.
http://support.sourcegear.com/viewtopic.php?t=6
Can they actually log into that repository?
If not, the first thing I would do is delete the user's client-side cache.
http://support.sourcegear.com/viewtopic.php?t=6
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Thank you for the quick reply.
He can log into the repository.
I took a peek into the sgvault database and opened dbo.tblrepositories. The repository is there, along with the correct file count. It just doesn't show up in the admin client.
On the upside, it's the only repository that's missing from the admin client.
He can log into the repository.
I took a peek into the sgvault database and opened dbo.tblrepositories. The repository is there, along with the correct file count. It just doesn't show up in the admin client.
On the upside, it's the only repository that's missing from the admin client.
Can the admin user see the repository when logging in with a GUI client?
Have you tried restarting IIS? That would flush out the server cache.
If none of this helps, please send me a copy of the The Vault server log is sgvault.log and is in %windir%\temp\sgvault on the server machine.
Send it zipped up to support at sourcegear.com, Attn: Linda.
Have you tried restarting IIS? That would flush out the server cache.
If none of this helps, please send me a copy of the The Vault server log is sgvault.log and is in %windir%\temp\sgvault on the server machine.
Send it zipped up to support at sourcegear.com, Attn: Linda.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager