WAN login Vault Pro 2014 issue, not with 2012 client

[spascual]

Hi Sirs,

While I'm trying to connect vault via wan, I obtain next error on log file...

If I try to connect with 2012 Client, it runs well...

Any idea welcome, regards,

04/12/2013 8:28:51 *******************************************************************
Error: Soap Exception ( mesg-id = 635217425317060352 )
Exception: WebServiceError [8005] (http://spascual.dyndns.org/)
Stacktrace:    en Connectivity.Server.Proxies.ServiceAccessor`3.Execute(String remoteServer, Action`1 action)
   en Connectivity.Filestore.AuthenticationService.CreateSession(AuthCredentials creds, String dataServer, String knowledgeVault, Boolean isLicensed, Byte[] p)
   en SyncInvokeSignIn(Object , Object[] , Object[] )
   en System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   en System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   en System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   en System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   en System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

Exception(Inner): Error al recibir la respuesta HTTP a http://spascual.dyndns.org/AutodeskDM/Services/_impl/SiteService.svc. Puede deberse a que el enlace del extremo de servicio no usa el protocolo HTTP. También puede deberse a que el servidor anula un contexto de solicitud HTTP (posiblemente por el cierre del servicio). Consulte los registros del servidor para obtener más información.
Stacktrace(Inner):
Server stack trace:
   en System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
   en System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   en System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   en System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   en System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   en System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   en System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   en System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   en Connectivity.Server.Proxies.SiteService.SiteService.SignInSite2(SignInSite2Request request)
   en Connectivity.Server.Proxies.SiteAuthenticator.SignIntoSite(String remoteServer, String vaultname)
   en Connectivity.Server.Proxies.ServerTokenCache.Get(Lazy`1 authenticator, String remoteServer, IResourceStore vault, SecurityHeader expiredToken)
   en Connectivity.Server.Proxies.ServiceAccessor`3._service(String remoteServer, Boolean reSignin)
   en Connectivity.Server.Proxies.ServiceAccessor`3.tryexecute(String remoteServer, Action`1 action, Int32 attemptCount)
   en Connectivity.Server.Proxies.ServiceAccessor`3.Execute(String remoteServer, Action`1 action)

Exception(Inner): Se ha terminado la conexión: Error inesperado de recepción.
Stacktrace(Inner):    en System.Net.HttpWebRequest.GetResponse()
   en System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

Exception(Inner): No se puede escribir datos de en la conexión de transporte: Se ha forzado la interrupción de una conexión existente por el host remoto.
Stacktrace(Inner):    en System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   en System.Net.HttpWebRequest.MakeMemoryStream(Stream stream)

Exception(Inner): Se ha forzado la interrupción de una conexión existente por el host remoto
Stacktrace(Inner):    en System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

[johannes.bauer]

hi
you have set a proxy server in the internet explorer settings?

[spascual]

Hi Johannes,

Thanks for your interest.

I have not proxy server. I have ports open into router.

Desktop client 2012 conects perfectly with server 2014, but desktop client 2014 is unable to conect with the same server.

WebClient conects well.

Regards,

[johannes.bauer]

Hi,
the error message (although it is in spansish) says something about proxy server. please check from the client you want to access over wan the internet explorer settings for proxy.
thanks

[Anonymous]

Hei Johannes

I am Lluis and I work face to face with Tomas

The Webclient have not a problem

can check yourself by going directly to
With a 2012 VP customer you can not problems
And with a customer VP2014 you can not connect
We've checked it on multiple clients (XP, W7, W view) with the same result

Data to connect are:
User Name: AUTODESK
Password: AUTODESK
Server: onduexadms.dyndns.org

Vault: Vault
Internal IP:172.168.0.110

[johannes.bauer]

Hi,
can reproduce.
Is there anything in the logs of IIS?
Haven't seen this before.

[spascual]

Hei Johannes,

This is not a clear installation of ADMS. Before 2014 version, was 2012 version installed.

Could be issue origin??

Regards,

[johannes.bauer]

Hi,

uninstall reinstall vault could be a possibility.

have you change something?

I get now a different error message from my 2014 client, when trying to connect.

It tells me, that our versions differ (I got subscription release installed on my client)

is it working now?

if yes, please share the solution.

Thanks

[lluisg]

Hi Johanes I am Lluis.

Today is a holiday in Spain, we tested another server with ADMS 2014 and the problem is the same.
I'm doing tests and the error is still the same, do not understand how I now present to you another error. I think the problem is in the 2014 VP client, specifically the authentication (the file "Connectivity.VaultPro.exe.config" is correct).
Today I tested the connection with the client and VP 2013 also works correctly.
We suggest that you can test or changes we can make

[herrerh]

Sicne you are most likely using port forwarding, is IIS configured to accept the FQDN that you are using for people to connect to?

-Hywell

[lluisg]

IIS is not configurate for conections FQDN. But I do not understand your question. VP Client 2012, 2013 works without problems, but VP 2014.

[spascual]

Hi herreh

Here you can find the iss log file.

Thanks,

Repeat: Vault Desktop Client 2012 conecting vault server 2014 is running well

[herrerh]

Can you add the AVFS log file and vlog, and the exact error the Vault 2014 client is getting?

[lluisg]

Hei Hywell

In a 1 Message you have this error. I attach a today log file, it as the following sequence:

1. Conexion VP2014 LAN- Ok
2. Conexion Cliente Web - WAN-Ok
3. Conexion VP2014 WAN- ERROR
4. Conexion VP2012 WAN- Ok

[herrerh]

Try the following so that the Vault does not try to go back out to the Inernet and back in for some calls.

On the Vault server:

Navigate to C:\Windows\System32\Drivers\Etc

Open hosts with notepad.

Create a new entry for 

http://onduexadms.dyndns.org/
point to the local IP Address of the server 

Do an IISRESET and then test.

-Hywell

[lluisg]

Hywell

iisreset

I hope...

LLuis

[herrerh · Accepted solution]

Sorry, remove the http:// from the hostname.

[lluisg]

Hywell

How it is fine all

Thans you very much

Lluis

[spascual]

Great, thank you very much