Can't login - vault pro server with vault standard client?
Posted: Tue Apr 24, 2012 5:10 pm
I'm just trying to connect to vault so I can play with adding a work item but can't get past the login part. The details are below!
ClientAPI 5.1.2.19281 - downloaded it today
VaultService "about" page says I'm on 5.1.2.19283 and that's what our installed clients say, too.
The actual sourcegear clients connect fine.
My code using one of the connection methods found around the boards - seems like the usual:
My unusual exception:
Edit:
This post has a similar problem but the resolution seemed to point to the same API examples that connect in the way I am...
http://support.sourcegear.com/viewtopic ... 48&t=18723
Can you not use the Client API to do this? Do you need to connect to the web service directly?
ClientAPI 5.1.2.19281 - downloaded it today
VaultService "about" page says I'm on 5.1.2.19283 and that's what our installed clients say, too.
The actual sourcegear clients connect fine.
My code using one of the connection methods found around the boards - seems like the usual:
Code: Select all
A function:
string url = "http://intranet source gear site name:port number/VaultService";
string username = "windows/vault user name";
string password = "my password";
string repository = "my repository";
string workingFolder = @"my working folder";
// set the login options and login/connect to a repository.
Vault.Login(url, username, password, repository, workingFolder);
The Login function:
ServerOperations.client.LoginOptions.URL = serverUrl;
ServerOperations.client.LoginOptions.User = userName;
ServerOperations.client.LoginOptions.Password = password;
ServerOperations.client.LoginOptions.Repository = repository;
ServerOperations.Login();
My unusual exception:
System.Exception: You are attempting to connect to a Vault Professional Server with a Vault Standard Client. Please download the correct client from http://sourcegear.com/vaultpro/downloads.html --->
System.Web.Services.Protocols.SoapException: 1025 : FailVaultClientCantConnectToVaultPro at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.ClientService.VaultService.ValidateServiceVersions(Int32[] clientSupportedVersions)
at VaultClientNetLib.VaultConnection.Login(String strURLBase, String strUserLogin, String strPassword)
at VaultClientOperationsLib.ClientInstance.Login(String urlbase, String username, String password)
at VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)
--- End of inner exception stack trace ---
at VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)
at VaultClientIntegrationLib.ServerOperations.Login()
at Vault.Login(String serverUrl, String userName, String password, String repository, String workingFolder) in ...\Vault.cs:line 165
at CustomVaultInterface.MainScreen.btnAddWorkItem_Click(Object sender, EventArgs e) in ...\MainScreen.cs:line 31
Edit:
This post has a similar problem but the resolution seemed to point to the same API examples that connect in the way I am...
http://support.sourcegear.com/viewtopic ... 48&t=18723
Can you not use the Client API to do this? Do you need to connect to the web service directly?
Thank you. I'm not the one who set up Vault for our team. However, I'm curious, would she have gotten information about this?