Eclipse Connect Error

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

Moderator: SourceGear

Post Reply
Scootin159
Posts: 16
Joined: Wed Apr 12, 2006 6:57 am

Eclipse Connect Error

Post by Scootin159 » Wed Apr 13, 2011 11:20 am

I'm getting the following error when I try to connect to our vault server through Ecilpse:

Code: Select all

"An unknown error occurred during the login process.  Please check the Eclipse error log for exceptions (<workspace>/.metadata/.log)"
When I open the referenced file, I find the following entry:

Code: Select all

!ENTRY org.eclipse.ui 4 0 2011-04-13 13:14:14.963
!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:887)
	at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:426)
	at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
	at org.eclipse.jface.window.Window.open(Window.java:801)
	at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:147)
	at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274)
	at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
	at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
	at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
	at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
	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:1053)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
	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:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	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:620)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
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: The connection to the server failed: server cannot be contacted or uses a protocol that is not supported by this client. Unable to connect to https://<ourvaultserver>/VaultService.  No server was found at the specified URL.  Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.  Web Exception:  ---> System.Exception: Unable to connect to https://<ourvaultserver>/VaultService.  No server was found at the specified URL.  Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.  Web Exception: 
	at clr.System.ExceptionStaticWrapper.ExceptionCtor(Unknown Source)
	at VaultClientNetLib.VaultConnection.Login(Unknown Source)
	at VaultClientOperationsLib.ClientInstance.Login(Unknown Source)
	at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3407)
	at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3537)
	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.ExceptionCtor(Unknown Source)
	at VaultClientNetLib.VaultConnection.Login(Unknown Source)
	at VaultClientOperationsLib.ClientInstance.Login(Unknown Source)
	at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3407)
	at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3537)
	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(Unknown Source)
	at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3418)
	at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3537)
	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.ExceptionCtor(Unknown Source)
	at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3418)
	at VaultClientIntegrationLib.ServerOperations.Login(ServerOperations.cs:3537)
	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
What should be my course of diagnosing this?

Some background info:
- We've been using vault for a long time, and I can use both the standard Vault Client, VS2005 and VS2010 without any issue on this PC.
- I've never used Vault with Eclipse before, so it very well could be that I'm just doing something wrong or that I don't have something configured properly. We've also never used the vault eclipse client anywhere with our server.
- Our server is configured to be https only using a certificate that is accepted by most browsers by default

Version #'s:
Client OS: Windows 7 x64
Eclipse: Helios Service Release 2
Vault Eclipse: 5.1.1.19215
Vault Client: 5.1.0.19172
Vault Server: 5.1.0.19172

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

Re: Eclipse Connect Error

Post by Beth » Wed Apr 13, 2011 12:59 pm

Which URL do you have entered in Eclipse for the Vault update site?

If you are using Vault Standard, then you must use this URL with Eclipse:

Code: Select all

http://download.sourcegear.com/Vault/latest/update
If you are using Vault Professional, then you must use this URL with Eclipse:

Code: Select all

http://download.sourcegear.com/VaultPro/latest/update
Beth Kieler
SourceGear Technical Support

Scootin159
Posts: 16
Joined: Wed Apr 12, 2006 6:57 am

Re: Eclipse Connect Error

Post by Scootin159 » Wed Apr 13, 2011 1:10 pm

We have Vault Standard, and I was using the appropriate URL (http://download.sourcegear.com/Vault/latest/update)

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

Re: Eclipse Connect Error

Post by Beth » Wed Apr 13, 2011 1:21 pm

When you check connectivity with a web browser, can you pull up this page: https://<your vault server>/VaultService?

What version of JAVA do you have on your machine? You need at least JAVA 1.5 for SSL to work.

Have you added the server's certificate to the KeyStore with your trusted certificates?

Here is a KB article on setting up Eclipse with SSL that may help you: http://support.sourcegear.com/viewtopic.php?t=10526
Beth Kieler
SourceGear Technical Support

Scootin159
Posts: 16
Joined: Wed Apr 12, 2006 6:57 am

Re: Eclipse Connect Error

Post by Scootin159 » Wed Apr 13, 2011 1:52 pm

Loading the SSL certificate into the java keystore is exactly what I needed, thank you. I guess just because most browsers accept the key by default, doesn't mean that java does.

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

Re: Eclipse Connect Error

Post by Beth » Wed Apr 13, 2011 3:10 pm

Thanks for the update. I'm happy to hear it's working now.
Beth Kieler
SourceGear Technical Support

Post Reply