Adding a Solution to Vault error -

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

Moderator: SourceGear

Post Reply
Tom

Adding a Solution to Vault error -

Post by Tom » Fri May 13, 2005 8:09 am

While trying to save the Solution file back to Vault, I got this error.

Required fiedl/property VaultService.VaultAuthValue of SOAP header VaultAuth was not set by the client prior to making the call.

Can you assist?

Also is this error logged on the server or the client or both?

Thanks

Tom

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Fri May 13, 2005 11:24 am

Are you using VS 2002 or .Net Framework 1.0? If so, see http://support.sourcegear.com/viewtopic.php?t=2685

btd
Posts: 324
Joined: Fri May 13, 2005 1:50 pm

btd

Post by btd » Fri May 13, 2005 1:53 pm

Dan:

I'm getting message back from Vault saying the topic does not exist in your database! Cab you send me the context?

Thanks


Tom

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Fri May 13, 2005 2:31 pm

Sorry - this was in a different area of the support site than I thought it was. Try this: http://kb.sourcegear.com/VaultHelp/sear ... 8395563c9f

Or, try clicking on the link for more info in the dialog Vault displays when the error happens.

Tom

Adding a Solution to Vault error

Post by Tom » Mon May 16, 2005 5:43 am

Dan:

The second link didn't work either! Is the site down or something?

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Mon May 16, 2005 8:05 am

Sorry about that - I give up on trying to provide a link :) Here is the text of the article (it comes from our error message section, where you can click on an error from within Vault, and it will take you to the website for more info, which is why it takes special handling).

-------------------------------

Full error is: Server did not find required VaultAuth SOAP header in the message.

This error occurs with Vault 3.0 when the .NET Framework 1.0 is being used by the ASPNET process. Vault 3.0 requires .NET Framework 1.1.
You may have the .NET Framework 1.1 installed, but it is not being used.

The error also occurs when trying to use VS.NET 2002 with Vault 3.0. VS.NET 2002 is not supported, as it needs the .NET Framework 1.0.

For information about switching the version of .NET Framework, see this post:

http://support.sourcegear.com/viewtopic.php?t=866

Tom

Post by Tom » Tue May 17, 2005 5:47 am

Thanks Dan. I got it.

Appreciate your willingness to help out. That's what it was. One of my developers was trying to open Visual Studio .nET 2002 with Vault as its SCC provider.

But are there any plans to integrate Vault with VS 2002? I wonder what the limitaiton is and why Vault can't integrate with VS 2002!

Tom

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Tue May 17, 2005 7:08 am

The problem is that Vault 2.0 and above require the 1.1 framework, and VS 2002 only supports the 1.0 framework. We had a patch for Vault 2.0 that allowed it to work with VS 2002, but did not make Vault 3.0 compatible, so there is no available patch for it.

Post Reply