none
Errors 6966 and 6971 when provisioning Project 2013 web app instance RRS feed

  • Question

  • I am trying to install Project Server 2013 on a brand new installation of SharePoint 2013.  When starting the provisioning of the project web app instance the following two errors are thrown and provisioning fails. Any idea what am I missing here? Which server is unavailable???

    Error 6966:

    Provisioning 'PWA': Post provisioning setup failed. Exception 'System.ServiceModel.ServerTooBusyException: The HTTP service located at http://abc-test03:32843/e5c5985bf3dd4a2d942be8f003c64f51/PSI/psiserviceapp.svc is unavailable.  This could be because the service is too busy or because no endpoint was found listening at the specified address. Please ensure that the address is correct and try accessing the service again later. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
       at System.Net.HttpWebRequest.GetResponse()
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       --- End of inner exception stack trace ---
    
    Server stack trace: 
       at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(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.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.Administration.IPsiServiceApplication.GetServiceApplicationName()
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplicationProxy.<>c__DisplayClass4.<GetServiceApplicationName>b__3(IPsiServiceApplication channel)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplicationProxy.ExecuteOnChannel(String operationName, CodeBlock codeBlock)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplicationProxy.GetServiceApplicationName()
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.GetServiceApplicationAndProxyByWebApplication(SPWebApplication webApp, PsiServiceApplication& serviceApplication, PsiServiceApplicationProxy& serviceAppProxy)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.GetServiceAppByWebApp(SPWebApplication webapp)
       at Microsoft.Office.Project.Server.Administration.ProvisionFeatureEventHandler.FeatureActivated(SPFeatureReceiverProperties properties)
       at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
       at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, SPFeatureActivateFlags activateFlags, Boolean fForce)
       at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly)
       at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, Int32 compatibilityLevel, String featureName, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
       at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
       at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureProvisioningFeature(SPSite site)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)'.

    Error 6971:

    Failed to provision site PWA with error: System.ServiceModel.ServerTooBusyException: The HTTP service located at http://abc-test03:32843/e5c5985bf3dd4a2d942be8f003c64f51/PSI/psiserviceapp.svc is unavailable.  This could be because the service is too busy or because no endpoint was found listening at the specified address. Please ensure that the address is correct and try accessing the service again later. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
       at System.Net.HttpWebRequest.GetResponse()
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       --- End of inner exception stack trace ---
    
    Server stack trace: 
       at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(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.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.Administration.IPsiServiceApplication.GetServiceApplicationName()
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplicationProxy.<>c__DisplayClass4.<GetServiceApplicationName>b__3(IPsiServiceApplication channel)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplicationProxy.ExecuteOnChannel(String operationName, CodeBlock codeBlock)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplicationProxy.GetServiceApplicationName()
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.GetServiceApplicationAndProxyByWebApplication(SPWebApplication webApp, PsiServiceApplication& serviceApplication, PsiServiceApplicationProxy& serviceAppProxy)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.GetServiceAppByWebApp(SPWebApplication webapp)
       at Microsoft.Office.Project.Server.Administration.ProvisionFeatureEventHandler.FeatureActivated(SPFeatureReceiverProperties properties)
       at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
       at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, SPFeatureActivateFlags activateFlags, Boolean fForce)
       at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly)
       at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, Int32 compatibilityLevel, String featureName, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
       at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
       at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureProvisioningFeature(SPSite site)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)



    Saturday, May 4, 2013 11:21 PM

All replies

  • Is you farm spec'd as per the minimum requirements stated by MS? Can you share details about your environment?

    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    Sunday, May 5, 2013 1:52 AM
    Moderator
  • Is you farm spec'd as per the minimum requirements stated by MS? Can you share details about your environment?

    This is my test environment. Both SharePoint and SQL 2012 on separate virtual machines. I turned off my other test machines so I have plenty of resources available (10GB of RAM each). I tried this many times both with fully configured SP server and with minimum configuration. The Project database is created on a SQL server so it can connect to it. Maybe it is a permission issue but not sure where - the installation seems to be very straight forward. (installed with the admin account I used for the SP installation and dedicated account for project app pool). Let me know if you need more details.
    Sunday, May 5, 2013 2:01 AM
  • I don't know what instruction set you are following, but most people do not find this installation process "to be very straight forward." That gives me pause for concern. I suggest that you consider getting a copy of my Kindle Single, Project Server 2013 Intall and Wire-up http://amzn.to/164yW3O

    There are a myriad of preparation steps you need to take before you begin this installation and a raft of work to get it wired-up to SharePoint service applications. the instructions on TechNet are a light, especially if this is the first you are installing it.


    Gary Chefetz, MCITP, MCP, MVP msProjectExperts
    Project and Project ServerFAQs
    Project Server Help BLOG

    Friday, July 26, 2013 11:25 AM
    Moderator