none
PWA Provisiong failed event ID 6791 RRS feed

  • Question

  • I have Project Server 2013 SP1 installed on Server 2008 R2 SP1.  Keeps failing every time I tried to created a new PWA site on a newly created database content.  Event Viewer keeps saying this:

    Failed to provision site PWA with error: System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.

    Server stack trace:
       at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       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, Boolean fIgnoreMissing, 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)


    Tuesday, April 28, 2015 7:40 PM

All replies

  • Hey Steven,

       Not much really I can say about your error except there is something fairly basic wrong with your installation.  The Project Site feature was unable to make contact with the Project Server Application proxy ... so I would take a look at the topology of you Farm, making sure you have Project Server installed properly and associated into the default proxy group.

    Good luck

       James.


    James Boman BSc. MCP:EAD -

    Thursday, May 7, 2015 7:23 AM