SourceGear Support

That did it (client cache). Thanks for the help!

Jeramie

I have kind of an odd problem in fortress 1.1.2. The pattern is summarized below. Actual names of things are changed for simplicity. I've assigned RCA rights to a folder in source control ("$/Folder1") to a group "Group1" and then assigned two users "User1" and "Us...

Thanks, Linda.

I've emailed the log as you've requested. Yes, we're on Fortress 1.1.1.

Regards,
Jeramie

We recently (within the last week) upgraded from Vault 3.x / Dragnet 1.x to Fortress. All was well until this morning when developers began receiving the following error message when attempting to check out a file from the Fortress Client: "A database error has occured (FailDBInsert)". Dev...

Windows Server 2003 (Standard). I'll try deleting the user's profile and see if that fixes it. I'll post back with the result. Thanks for the prompt response.

Regards,
Jeramie

Thanks for the reply, Beth. I did read that article, but since this doesn't appear to be an issue with the server, felt that it wasn't relevant to the client problem I'm seeing. Again, I can connect to the Vault server from any other machine using the same Vault account + same Vault client version w...

I'm currently hitting an issue with the 3.5.1.x Vault client running on Windows Server 2003. When I try to connect to any Vault 3.5.1.x server instance using the client, I get the following error: CryptoAPI cryptographic service provider (CSP) for this implementation could not be acquired. I've trie...

I've looked in the docs + can't seem to figure out how to resolve an issue in Dragnet (e.g. to get it so that it doesn't show up in unresolved...). If I've missed a post on this, please point me in the right direction. Is there a certain status that needs to be assigned the issue? I usually open an ...

On the original machine that I was running Vault Admin on, I deleted the cache and tried again with the same results. I went ahead and installed the client on a new machine that had never had Vault Admin on it and achieved the same result (e.g. issue still exists). As an additional data point, I tri...

I'll give it a try and get back to you. Thanks for being so responsive on this...

The restart happens because we run IIS Crash/Hang Agent on the IIS server that the Vault web service is running on. The restart occurs because when trying to add the assignment to the user or group, the admin app hangs past the trigger point for a "Hang" in the IIS Crash Hang Agent (curren...

I tried the suggestions in that thread and I have the same outcome as that individual. Also - I had the same perflib error that he mentioned showing up. I corrected the error by granting read access to the reg key noted in the dotnet247 article. That error no longer appears but the behavior of not b...

This morning I uninstalled/reinstalled the Vault admin tool and got the same behavior. I also was able to add default rights to a user for the entire repository, but was still unable to add an assignment to either a user or a group. Still effectively no-ops with no exception being thrown to the clie...

We're running Vault 3.1.1.3506. Other Vault operations seem to be working fine, but if I try to add an assignment to either a group or a specific user, I get one of two outcomes: 1) It appears to add (e.g. closes dialog), but the assignment doesn't show up in the list of assignments for the user or ...

Now that's turn around - thanks!

Jeramie