Project Server 2010 - endpoint error for ProjectServer.svc when using AAM RRS feed

  • Question

  • On Project Server 2010 when accessing PSI API via a public url other than the default (setup via Alternate Access Mapping), PWA throws an 'there was no endpoint listening' SOAP exception

    There is a need to access the pwa with the name newdemo so setup Alternate Access Mappings

    • Tried "Adding Internal Urls" - this redirects http://newdemo/pwa to http://vmtest/pwa
    • so tried adding a public url, added http://newdemo as a public url for a different zone other than default (default is http://vmtest)
    • This works BUT the code that uses PSI API fails with the exception

    Error: There was no endpoint listening
     at http://newdemo/PWA/_vti_bin/PSI/ProjectServer.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.   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.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 Ptc.Ppm.PSIUtility.SvcProject.Project.ReadProjectList()   
     at Ptc.Ppm.PSIUtility.SvcProject.ProjectClient.ReadProjectList()   
     at Ptc.Ppm.PSIUtility.ProjectUtils.CheckProjectExists(String strMSProjectName)   
     at Ptc.Ppm.Core.Controls.CustomControl.CreatePortfolio.<>c__DisplayClass2.<fnCreatePortfolioSite>b__0()   
     at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()   
     at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)   
     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)   
     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)   

    Seems like calls to the PSI services are accepted only with the machine name and are not accessible via the AAM public url.

    Any suggestions on what could be wrong and/or how to fix this is greatly appreciated.


    Thursday, December 2, 2010 6:35 PM

All replies

  • Trying doing this:

    create a DNS alias for your new URL name pointing to the IP address of the Project Server.

    You should be able to set up the SharePoint Web Application to use host headers and then setup the default alternate access mapping to use the host header URL.  The PSI should be available on the Host Header URL but not the host name URL.


    Project Server 2010 Archive Tool.


    Ray McCoppin
    Friday, December 3, 2010 4:31 PM
  • Thanks Ray. I am not sure what you mean by 'create a DNS alias'. I know a little bit of about A-records and CNAME records, are you referring to a CNAME record or something like that to be setup for the new machine name?

    But this is all on the local intranet so where would I set this? Would I be able to do this as a mapping to the IP address like putting an entry in the hosts file with the new name?

    Sorry for all the questions. As you can see I am ignorant in this area if you could give some more details or refer me to some documentation that would great.



    Monday, December 13, 2010 6:39 PM
  • Karthik, did you find a solution to your problem? If not, perhaps the problem is the Loopback Check?  Since Server 2003 SP1 (I believe), which includes Server 2008 and 2008 R2, you may need to disable the Loopback Check if you attempt to call a server by anything but it's server name.

    Information is here: on Disabling the Loopback Check.  It's a registry edit, so proceed with caution.  But it's usually why Alternate Access Mappings don't work 'on-server.'


    Dave Dunn
    Thursday, February 17, 2011 6:45 AM
  • Dave,

    I havent found a solution. I thought I would get an email if someone responds to this post but for whatever reason I didnt and missed your post until today. I will try this and let you know.




    Monday, April 18, 2011 4:39 AM