Jump to content


Photo

Protocol Driver error or Workstation connection refused

Started by Rajendran Vedachalam , 19 April 2017 - 10:56 AM
2 replies to this topic

Rajendran Vedachalam Members

Rajendran Vedachalam
  • 29 posts

Posted 19 April 2017 - 10:56 AM

We have Xendesktop 7.6 version ( no FP installed). client Windows 7 32bit Desktop. 

 

we have two different set of issue. 

1. Users unable to reconnect disconnected session back from different endpoints. ( we have free seating) so user can connect VDI desktop from any wyse terminal.

2. every Morning 40+ user unable to login even to register machine until we reboot again. 

 

Mainly Japan User impacted. 

 

some time user getting protocol driver error or DPerrorId: workstation connection refused.( attached screenshot in japanese )

 

When i check few desktop and see there are multiple error related to Citrix. when i run Citrix health check assistance tool is say all fine. 

 

I have check DNS/ SPN / DHCP / Network port all looks fine. But still some reason VDA desktop through below event and stop users to connect VDA desktop.

 

 

Below error event log collected from single VDA machine for last one month,

__________________________________________________________________

02/04/2017 - EVENT ID 1014
 
The Citrix Desktop Service lost contact with the Citrix Desktop Delivery Controller Service on server 'DDC servername'. 
The service will now attempt to register again. 
 
Error details: 
Exception 'The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.' of type 'System.TimeoutException'
 

**************************************************************************************************************************

06/04/2017 -EVENt ID 1048
The Citrix Desktop Service is re-registering with the DDC: 'COM スタック通信障害 (DDC: DDC servername)'
 
 
**************************************************************************************************************************
 
16/04/2017 -EVENt ID 1014 
The Citrix Desktop Service lost contact with the Citrix Desktop Delivery Controller Service on server 'DDC servername'. 
The service will now attempt to register again. 
 
Error details: 
Exception 'There was no endpoint listening at http://DDC servername/Citrix/CdsController/IRegistrar that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.' of type 'System.ServiceModel.EndpointNotFoundException'
 
 
**************************************************************************************************************************
16/04/2017 - EVENT ID 1002
The Citrix Desktop Service cannot connect to the delivery controller 'http://DDC servername:80/Citrix/CdsController/IRegistrar' (IP Address '') 
 
Check that the system clock is in sync between this machine and the delivery controller. If this does not resolve the problem, please refer to Citrix Knowledge Base article CTX117248 for further information. 
 
Error Details: 
Exception 'Error occurred when attempting to connect to endpoint at address http://CDDC servername:80/Citrix/CdsController/IRegistrar, binding WsHttpBindingIRegistrarEndpoint and contract Citrix.Cds.Protocol.Controller.IRegistrar: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://DDC servername/Citrix/CdsController/IRegistrar that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: 対象のコンピューターによって拒否されたため、接続できませんでした。 DDC servername:80
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   --- End of inner exception stack trace ---
 
Server stack trace: 
   at System.ServiceModel.Security.IssuanceTokenProviderBase`1.DoNegotiation(TimeSpan timeout)
   at System.ServiceModel.Security.SspiNegotiationTokenProvider.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Security.CommunicationObjectSecurityTokenProvider.Open(TimeSpan timeout)
   at System.ServiceModel.Security.SymmetricSecurityProtocol.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.SecurityChannelFactory`1.ClientSecurityChannel`1.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperation(SecuritySessionOperation operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout)
   at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.GetTokenCore(TimeSpan timeout)
   at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)
   at System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open()
 
Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.ICommunicationObject.Open()
   at Citrix.Cds.BrokerAgent.ControllerConnectionFactory.AttemptConnection[T](EndpointReference endpoint, Boolean throwOnError, Boolean allowNtlmAuthentication, String connectUsingIpThisIpAddress, Boolean cacheFactory)' of type 'Citrix.Cds.BrokerAgent.ConnectionFailedException'..
 
 
**************************************************************************************************************************
17/04/2017 -EVENT ID 1015
The Citrix Desktop Service's connection to the Citrix Desktop Delivery Controller Service was terminated. The Citrix Desktop Delivery Controller Service is running on server 'cscmljx55tky01.japan.corp.manulife.com'. 
 
Check that there is no active firewall blocking the controller communicating with this machine. 
 
Please refer to Citrix Knowledge Base article CTX117248 for further information. 
 
Error details: 
Keep-alive request was rejected.
 
 
**************************************************************************************************************************
 
19/04/2017 - EVENT ID 1048
The Citrix Desktop Service is re-registering with the DDC: 'COM stack communication failure
 

 

**************************************************************************************************************************

*************************************************************************************************************************

Attached Thumbnails

  • citrix health assistance.jpg
  • protocol drive error.jpg
  • VDI error (002).jpg


Carl Stalhood CTP Member

Carl Stalhood
  • 11,621 posts

Posted 19 April 2017 - 11:54 AM

Same problem in VDA 7.6.3000 or in VDA 7.13? You can upgrade the VDA without upgrading the Controllers.

Rajendran Vedachalam Members

Rajendran Vedachalam
  • 29 posts

Posted 20 April 2017 - 04:44 AM

our current VDA version is 7.6.0.5026. I will try to install VDA 7.13 and see issue resolve