SourceGear Support

Hi Tonya,

I've gone through all of the suggestions in the referenced topic. All of this looks good.

I did just find something interesting. I can upload the file into a new folder in the same repository without any problem. Does that give us anything new to try?

We have one large file that will not check in to our Vault Standard Server. The server and client is version 10.2.0.1222. The message on the client is: Upload for item filename failed too many times, aborting transaction. Please verify your network settings using the Options dialog under the Tools m...

The log has been sent.

Good morning, We are trying to rollback an object and keep receiving the following messages: [3/1/2021 11:10:35 AM] An error occurred while trying to end a transaction. [3/1/2021 11:10:35 AM] An exception was encountered during the transaction. Exception: 1 : Failure at System.Web.Services.Protocols...

TLS 1.0 was deprecated when Vault 10 was released. You've released patches for the GUI and command-line clients, why not the MSSCCI client?

TLS 1.0 has been deprecated for more than a year by most companies. This is a showstopper for us, and may require us to move to different SCC software, which I really don't want to do. I'd hate to lose all of our history just because our SCC provider doesn't keep up with the prevailing security requ...

As I stated in my original post: I've installed both the "Vault GUI Client update for TLS 1.1/1.2" and the "Vault Command Line Client update for TLS 1.1/1.2", but neither of those update VaultIDE.dll. Is there a workaround for this? The GUI Client connects just fine, but the MSSC...

Good afternoon, We recently upgraded to Vault Standard 10 and are using Ivercy to connect to the Vault Server from Access 365 using the MSSCCI-API. Unfortunately we are unsuccessful in this and it appears to be because the VaultIDE.dll does not support a connection using TLS 1.2. Our internal securi...