The server uses a protocol that is not supported by this cli

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

Moderator: SourceGear

Post Reply
bootsauce
Posts: 3
Joined: Tue Nov 25, 2014 9:58 am

The server uses a protocol that is not supported by this cli

Post by bootsauce » Tue Nov 25, 2014 10:25 am

We receive an error message every time we open a project from the project list. However if we open a project by "Open from Vault" if opens successfully. We are using version 7.2.1 (265) of the client and version 7.2.1.265 of the server. We are using Visual Studio 2010 - version 10.0.40219.1 SP1. I enabled diagnostic logging through Visual Studio and this is what we get:

...
11/25/2014 9:44:24 AM <vsip ide>: [<No Name>:1] In VaultVsipClient.QuerySaveSolutionProps()
11/25/2014 9:44:24 AM <vsip ide>: [<No Name>:1] QuerySaveSolutionProps: QSP_HasNoDirtyProps
11/25/2014 9:44:24 AM <busy>: [<No Name>:1] Setting GUI to busy from Init
11/25/2014 9:44:24 AM <connection>: [<No Name>:1] InitService started.
11/25/2014 9:44:25 AM <connection>: [<No Name>:1] InitService finished.
11/25/2014 9:44:25 AM <eol>: [<No Name>:1] Native EOL is \r\n, which Vault thinks is CRLF
11/25/2014 9:44:25 AM <busy>: [<No Name>:1] Setting GUI to unbusy from Init.
11/25/2014 9:44:25 AM <eventengine>: [<No Name>:1] Event fired: VaultClientOperationsLib.ConnectionStateChangedEvent
11/25/2014 9:44:25 AM <connection>: [<No Name>:1] Login started.
11/25/2014 9:44:25 AM <eventengine>: [<No Name>:1] Event fired: VaultClientOperationsLib.ConnectionStateChangedEvent
11/25/2014 9:44:25 AM <connection>: [<No Name>:1] Logout started.
11/25/2014 9:44:25 AM <connection>: [<No Name>:1] Logout finished.
11/25/2014 9:44:25 AM <generic>: [<No Name>:1] SetActiveRepositoryID(id:-1)
11/25/2014 9:44:25 AM <eventengine>: [<No Name>:1] Event fired: VaultClientOperationsLib.ChangeSetItemsChangedEvent
11/25/2014 9:44:25 AM <eventengine>: [<No Name>:1] Event fired: VaultClientOperationsLib.ActiveRepositoryChangedEvent
11/25/2014 9:44:25 AM <eventengine>: [<No Name>:1] Event fired: VaultClientOperationsLib.TreeStructureChangedEvent
11/25/2014 9:44:25 AM <eventengine>: [<No Name>:1] Event fired: VaultClientOperationsLib.ConnectionStateChangedEvent
11/25/2014 9:44:25 AM <generic>: [<No Name>:1] Attempting to login. [System.Web.Services.Protocols.SoapException: 1021 : FailServiceVersionNotSupported
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 SourceGearLLC.VaultVsipClient.Vault.LogIn(String serverURL, Int32 repID, String repGuidString, String userName, String password, IntPtr mainWindowHandle) in E:\Builds\Vault7.2.1.x_Nightly\vault\src\VaultVsipClient\VaultWrapper.cs:line 457
at SourceGearLLC.VaultVsipClient.Vault.GuiLoginForRepository(Repository repository, Boolean cancelMeansOffline, IntPtr mainWindowHandle) in E:\Builds\Vault7.2.1.x_Nightly\vault\src\VaultVsipClient\VaultWrapper.cs:line 2001] 1021 : FailServiceVersionNotSupported
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 SourceGearLLC.VaultVsipClient.Vault.LogIn(String serverURL, Int32 repID, String repGuidString, String userName, String password, IntPtr mainWindowHandle) in E:\Builds\Vault7.2.1.x_Nightly\vault\src\VaultVsipClient\VaultWrapper.cs:line 457
at SourceGearLLC.VaultVsipClient.Vault.GuiLoginForRepository(Repository repository, Boolean cancelMeansOffline, IntPtr mainWindowHandle) in E:\Builds\Vault7.2.1.x_Nightly\vault\src\VaultVsipClient\VaultWrapper.cs:line 2001

Stack Trace:
at SourceGearLLC.VaultVsipClient.Vault.GuiLoginForRepository(Repository repository, Boolean cancelMeansOffline, IntPtr mainWindowHandle)
at SourceGearLLC.VaultVsipClient.VaultCommandOnline.DoPerform()
at SourceGearLLC.VaultVsipClient.VaultCommand.Perform()
at SourceGearLLC.VaultVsipClient.VaultVsipClient.Exec_icmdOnline(Object sender, EventArgs e)
at System.ComponentModel.Design.MenuCommand.Invoke()
at System.ComponentModel.Design.MenuCommand.Invoke(Object arg)
at Microsoft.VisualStudio.Shell.OleMenuCommandService.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& guidGroup, UInt32 nCmdId, UInt32 nCmdExcept, IntPtr pIn, IntPtr vOut)
at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& guidGroup, UInt32 nCmdId, UInt32 nCmdExcept, IntPtr pIn, IntPtr vOut)
at Microsoft.VisualStudio.Shell.Interop.IVsUIDataSource.Invoke(String verb, Object pvaIn, Object& pvaOut)
at Microsoft.Internal.VisualStudio.PlatformUI.DataSource.Invoke(String verb, Object pvaIn, Object& pvaOut)
at Microsoft.VisualStudio.PlatformUI.VsCommand.Execute(Object parameter)
at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
at System.Windows.Controls.MenuItem.InvokeClickAfterRender(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

11/25/2014 9:44:25 AM <generic>: [<No Name>:1] [System.Exception: The server uses a protocol that is not supported by this client.] The server uses a protocol that is not supported by this client.


Stack Trace:
at VaultClientPresentationLib.GUIClientInstance.ShowCommandException(Exception e, IWin32Window dialogOwner)
at SourceGearLLC.VaultVsipClient.Vault.GuiLoginForRepository(Repository repository, Boolean cancelMeansOffline, IntPtr mainWindowHandle)
at SourceGearLLC.VaultVsipClient.VaultCommandOnline.DoPerform()
at SourceGearLLC.VaultVsipClient.VaultCommand.Perform()
at SourceGearLLC.VaultVsipClient.VaultVsipClient.Exec_icmdOnline(Object sender, EventArgs e)
at System.ComponentModel.Design.MenuCommand.Invoke()
at System.ComponentModel.Design.MenuCommand.Invoke(Object arg)
at Microsoft.VisualStudio.Shell.OleMenuCommandService.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& guidGroup, UInt32 nCmdId, UInt32 nCmdExcept, IntPtr pIn, IntPtr vOut)
at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& guidGroup, UInt32 nCmdId, UInt32 nCmdExcept, IntPtr pIn, IntPtr vOut)
at Microsoft.VisualStudio.Shell.Interop.IVsUIDataSource.Invoke(String verb, Object pvaIn, Object& pvaOut)
at Microsoft.Internal.VisualStudio.PlatformUI.DataSource.Invoke(String verb, Object pvaIn, Object& pvaOut)
at Microsoft.VisualStudio.PlatformUI.VsCommand.Execute(Object parameter)
at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
at System.Windows.Controls.MenuItem.InvokeClickAfterRender(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

11/25/2014 9:44:26 AM <vsip ide>: [<No Name>:1] In VaultVsipClient.QuerySaveSolutionProps()
11/25/2014 9:44:26 AM <vsip ide>: [<No Name>:1] QuerySaveSolutionProps: QSP_HasNoDirtyProps
11/25/2014 9:44:26 AM <vsip ide>: [<No Name>:1] In VaultVsipClient.QuerySaveSolutionProps()
11/25/2014 9:44:26 AM <vsip ide>: [<No Name>:1] QuerySaveSolutionProps: QSP_HasNoDirtyProps
11/25/2014 9:44:27 AM <vsip ide>: [<No Name>:1] In VaultVsipClient.QuerySaveSolutionProps()
...


Why are we getting this "FailServiceVersionNotSupported" when we are running the same client and server versions?

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: The server uses a protocol that is not supported by this

Post by Beth » Tue Nov 25, 2014 3:57 pm

The error that says it's an unsupported protocol is almost always the wrong client version. Did you by any chance install the Vault Pro client when you have Vault Standard or vice versa?
Beth Kieler
SourceGear Technical Support

bootsauce
Posts: 3
Joined: Tue Nov 25, 2014 9:58 am

Re: The server uses a protocol that is not supported by this

Post by bootsauce » Wed Nov 26, 2014 9:00 am

Thanks for the reply Beth. I have verified that both server and client are Vault Standard version 7.2.1 (265). The server is the 64bit version running on Windows 2012 R2 Server against a 2012 SQL Server.

On Monday we upgraded from Vault 5.1 to Vault 6.1 then to Vault 7.2 but the web server is a clean install of Vault 7.2. The upgrade went fine. The only issue we have is opening a project through the Visual Studio 2010 IDE doesn't connect to Vault (project opens but there are no source control icons beside the files) and when we "Go Online" we get the "The server uses a protocol that is not supported by this client." message.

Is there anything else I can check?

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: The server uses a protocol that is not supported by this

Post by Beth » Wed Nov 26, 2014 9:14 am

Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

I haven't seen this type of behavior after having the correct client version installed, so a closer look might help.
Beth Kieler
SourceGear Technical Support

bootsauce
Posts: 3
Joined: Tue Nov 25, 2014 9:58 am

Re: The server uses a protocol that is not supported by this

Post by bootsauce » Thu Nov 27, 2014 12:02 pm

Email sent.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: The server uses a protocol that is not supported by this

Post by Beth » Mon Dec 01, 2014 1:52 pm

Quick update for other readers. Root problem was an unbound solution file. The Vault Enhanced Client works best when the solution files are bound. The Vault Classic Client doesn't require solution files to be bound.

HS: 232060
Beth Kieler
SourceGear Technical Support

Post Reply