Eclipse (Kepler) PlugIn Cant Connect to Vault STD

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

Moderator: SourceGear

Post Reply
integraRob
Posts: 3
Joined: Fri Sep 27, 2013 1:14 pm

Eclipse (Kepler) PlugIn Cant Connect to Vault STD

Post by integraRob » Fri Sep 27, 2013 1:33 pm

Hello,

We have a Vault Standard installation we have been using for years with Windows development, and the windows client works without issue. I am trying to connect to the server via the Eclipse plug-in for Vault Standard using the Team / Share feature. The login/connect to vault server is throwing an exception (see below). Some notes:

Brand new clean Eclipse Kepler J2EE installation (tried 32 and 64 bit)
JDK 1.6 u45
Vault Server is 6.0.1
We are NOT using SSL.

The plugin was downloaded/installed from
http://download.sourcegear.com/Vault/latest/update
via Eclipse' "Help / Install New Software..." option

It said it installed
C:\eclipse\eclipse\plugins\com.cdesg.compare_1.0.0.548
C:\eclipse\eclipse\plugins\com.cdesg.core_1.0.0.548
C:\eclipse\eclipse\plugins\com.cdesg.jni_2.1.0.548
C:\eclipse\eclipse\plugins\com.cdesg.logging_2.1.0.548
C:\eclipse\eclipse\plugins\com.cdesg.resources_1.0.0.548
C:\eclipse\eclipse\plugins\com.cdesg.uihelper_2.1.0.548
C:\eclipse\eclipse\plugins\com.cdesg.util_2.1.0.548
C:\eclipse\eclipse\plugins\com.sourcegear.vault.core_7.0.0.548.jar
C:\eclipse\eclipse\features\com.sourcegear.vault_7.0.0.548
C:\eclipse\eclipse\plugins\com.sourcegear.vault.team_7.0.0.548.jar
C:\eclipse\eclipse\plugins\com.sourcegear.vault.ui_7.0.0.548.jar

The vault connect/login screen says "VaultPRO" all over though I KNOW I installed the plugin using the Vault STD url as advised on your webiste.

Please advise on how this can be fixed.
Thanks

Exception from the .log file:
================================================================


!ENTRY org.eclipse.ui 4 0 2013-09-27 12:20:52.857
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at com.sourcegear.vault.team.wizards.LoginWizardPage.AttemptLogin(LoginWizardPage.java:45)
at com.sourcegear.vault.team.wizards.LoginWizardPage.onPageFinished(LoginWizardPage.java:74)
at com.cdesg.uihelper.wizard.ExtendedWizardPage.getNextPage(ExtendedWizardPage.java:123)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:908)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
at org.eclipse.jface.window.Window.open(Window.java:802)
at org.eclipse.team.internal.ui.wizards.ConfigureProjectWizard.openWizard(ConfigureProjectWizard.java:224)
at org.eclipse.team.internal.ui.wizards.ConfigureProjectWizard.shareProjects(ConfigureProjectWizard.java:124)
at org.eclipse.team.internal.ui.actions.ConfigureProjectAction$1.run(ConfigureProjectAction.java:39)
at org.eclipse.team.internal.ui.actions.TeamAction$3.run(TeamAction.java:266)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.team.internal.ui.actions.TeamAction.run(TeamAction.java:263)
at org.eclipse.team.internal.ui.actions.ConfigureProjectAction.execute(ConfigureProjectAction.java:33)
at org.eclipse.team.internal.ui.actions.TeamAction.run(TeamAction.java:515)
at org.eclipse.team.internal.ui.actions.TeamAction.runWithEvent(TeamAction.java:549)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:241)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
Caused by: java.lang.reflect.InvocationTargetException
at com.cdesg.uihelper.command.RunnableWithProgressCommandAdapter.run(RunnableWithProgressCommandAdapter.java:75)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: System.Exception: You are attempting to connect to a Vault Server with a Fortress Client. Please download a Vault Client from http://sourcegear.com/vault/downloads.html ---> System.Web.Services.Protocols.SoapException: 1026 : FailVaultProClientCantConnectToVault
at system.Web.Services.Protocols.SoapHttpClientProtocol.ReceiveResponse(SoapHttpClientProtocol.cs:351)
at system.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(SoapHttpClientProtocol.cs:379)
at VaultClientNetLib.ClientService.VaultService.ValidateServiceVersions(Unknown Source)
at VaultClientNetLib.VaultConnection.Login(Unknown Source)
at VaultClientOperationsLib.ClientInstance.Login(Unknown Source)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3903)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:4037)
at com.sourcegear.vault.ui.commands.ConnectCommand.doRun(ConnectCommand.java:59)
at com.cdesg.core.command.Command.run(Command.java:80)
at com.cdesg.uihelper.command.RunnableWithProgressCommandAdapter.run(RunnableWithProgressCommandAdapter.java:67)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

at system.Web.Services.Protocols.SoapHttpClientProtocol.ReceiveResponse(SoapHttpClientProtocol.cs:351)
at system.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(SoapHttpClientProtocol.cs:379)
at VaultClientNetLib.ClientService.VaultService.ValidateServiceVersions(Unknown Source)
at VaultClientNetLib.VaultConnection.Login(Unknown Source)
at VaultClientOperationsLib.ClientInstance.Login(Unknown Source)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3903)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:4037)
at com.sourcegear.vault.ui.commands.ConnectCommand.doRun(ConnectCommand.java:59)
at com.cdesg.core.command.Command.run(Command.java:80)
at com.cdesg.uihelper.command.RunnableWithProgressCommandAdapter.run(RunnableWithProgressCommandAdapter.java:67)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--- End of inner exception stack trace ---
at clr.System.ExceptionStaticWrapper.ExceptionCtor(Exception.jvm.cs:45)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3914)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:4037)
at com.sourcegear.vault.ui.commands.ConnectCommand.doRun(ConnectCommand.java:59)
at com.cdesg.core.command.Command.run(Command.java:80)
at com.cdesg.uihelper.command.RunnableWithProgressCommandAdapter.run(RunnableWithProgressCommandAdapter.java:67)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

at clr.System.ExceptionStaticWrapper.access$100(Exception.jvm.cs:61422)
at clr.System.ExceptionStaticWrapper.ExceptionCtor(Exception.jvm.cs:45)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3914)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:4037)
at com.sourcegear.vault.ui.commands.ConnectCommand.doRun(ConnectCommand.java:59)
at com.cdesg.core.command.Command.run(Command.java:80)
at com.cdesg.uihelper.command.RunnableWithProgressCommandAdapter.run(RunnableWithProgressCommandAdapter.java:67)
... 1 more
Caused by: System.Web.Services.Protocols.SoapException: 1026 : FailVaultProClientCantConnectToVault
at system.Web.Services.Protocols.SoapHttpClientProtocol.ReceiveResponse(SoapHttpClientProtocol.cs:351)
at system.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(SoapHttpClientProtocol.cs:379)
at VaultClientNetLib.ClientService.VaultService.ValidateServiceVersions(Unknown Source)
at VaultClientNetLib.VaultConnection.Login(Unknown Source)
at VaultClientOperationsLib.ClientInstance.Login(Unknown Source)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3903)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:4037)
at com.sourcegear.vault.ui.commands.ConnectCommand.doRun(ConnectCommand.java:59)
at com.cdesg.core.command.Command.run(Command.java:80)
at com.cdesg.uihelper.command.RunnableWithProgressCommandAdapter.run(RunnableWithProgressCommandAdapter.java:67)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

at system.Web.Services.Protocols.SoapHttpClientProtocol.ReceiveResponse(SoapHttpClientProtocol.cs:351)
at system.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(SoapHttpClientProtocol.cs:379)
at VaultClientNetLib.ClientService.VaultService.ValidateServiceVersions(Unknown Source)
at VaultClientNetLib.VaultConnection.Login(Unknown Source)
at VaultClientOperationsLib.ClientInstance.Login(Unknown Source)
at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3903)
... 5 more

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Eclipse (Kepler) PlugIn Cant Connect to Vault STD

Post by lbauer » Fri Sep 27, 2013 3:08 pm

It looks like you have the wrong plugin. In anticipation of the Vault 7 release, the URL got updated to the Vault 7 version, but it's too soon. :oops:

You should be able to get the correct plugin at this URL (just paste it into the "install New Software dialog.")

http://download-us.sourcegear.com/Vault ... 598/update

You can also find the manual install .zip here:

http://download-us.sourcegear.com/Vault ... _1_598.zip
Linda Bauer
SourceGear
Technical Support Manager

integraRob
Posts: 3
Joined: Fri Sep 27, 2013 1:14 pm

Re: Eclipse (Kepler) PlugIn Cant Connect to Vault STD

Post by integraRob » Fri Sep 27, 2013 5:30 pm

That fixed it. Thank you!

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Eclipse (Kepler) PlugIn Cant Connect to Vault STD

Post by lbauer » Mon Sep 30, 2013 7:52 am

Thanks for the update. That's good news. : )
Linda Bauer
SourceGear
Technical Support Manager

integraRob
Posts: 3
Joined: Fri Sep 27, 2013 1:14 pm

Re: Eclipse (Kepler) PlugIn Cant Connect to Vault STD

Post by integraRob » Tue Oct 01, 2013 2:36 pm

Today I ran "Update Software" in eclipse, which then installed the Vault Eclipse Plugin 7.0.0.551.

The plugin then broke with

"An error occurred while connectCommand: the server uses a protocol that is not supported by this client."

So what broke?

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

Re: Eclipse (Kepler) PlugIn Cant Connect to Vault STD

Post by Beth » Tue Oct 01, 2013 4:13 pm

Did you upgrade your Vault server to 7.0 as well?

If so, check to make sure you have the Vault Standard server installed and not Professional.
Beth Kieler
SourceGear Technical Support

Post Reply