none
Issue opening PWA: EndpointNotFoundException: Could not connect to PSI/Authentication.svc. RRS feed

  • Question

  • Hi,

     

    In one of the environments at a client site users get an error screen when they try to open the PWA. The error message is: An unexpected error has occured. In the ULS logs I see this error:

     System.ServiceModel.EndpointNotFoundException:
    Could not connect to http://server:port/00656193b6e142ca87eed4cfd38ae45e/PSI/Authentication.svc.
    TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ip:port. 
    ---> System.Net.WebException: Unable to connect to the remote server
    ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ip:port    
    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, Int32 timeout, 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.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()    
    at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)    
    at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)    
    at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)    
    at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)    
    at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)    
    at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)    
    at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)    
    at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)   
    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 Microsoft.Office.Project.Server.Interfaces.IAuthentication.GetUserByName(String username)    
    at Microsoft.Office.Project.Server.AuthenticationHelper.AuthenticateUserByName(String userName, Guid siteId)

     

    We are running Project Server 2010 in a multi server farm: an application server, a web frontend server and a shared sql server. We have not installed SP1 or the June CU yet. This error does not occur everytime, but every now and then. I have not been able to find any pattern in the occurrences yet. I found threads that said this could be caused by a service application proxy that is not associated to the web application. In our case this is all setup correctly.

    All help will be appreciated.

    Regards,

    Quint

    Friday, July 8, 2011 8:10 AM

Answers

  • It turns out that it was caused by connectivity issues between the web and app server. These were caused by the virtual machines that had been moved to another host.

    Regards,

    Quint

    Monday, July 11, 2011 8:30 PM

All replies

  • Hi Quint,

    As this occurs randomly it might be difficult to diagnose. The things I would look at first are:

    • Network - do the client machines lose connectivity to the App Server? Does the App Server lose connectivity to the SQL Server? A simple test would be to run a constant ping test to a text file and review the text files as soon as a user experiences the issue
    • Are the servers overloaded at the time the issue occurs?

    Does this happen at different times of the day or is it always first thing in the morning? If it is first thing in the morning it might be a timeout due to the pages being cached in IIS (unless you run any warm up scripts?)

    Thanks

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com
    Friday, July 8, 2011 12:06 PM
    Moderator
  • It turns out that it was caused by connectivity issues between the web and app server. These were caused by the virtual machines that had been moved to another host.

    Regards,

    Quint

    Monday, July 11, 2011 8:30 PM