none
How to track down an unexpected error? RRS feed

  • Question

  • Hello,

    I am able to successfully provision a PWA site but when I visit it get:

    "An unexpected error has occurred.

     

    Troubleshoot issues with Microsoft SharePoint Foundation.

    Correlation ID: 4afe84ab-4862-4635-b0fa-ae3ad93ff2b7

    Date and Time: 7/20/2010 4:14:52 PM"


    I don't see anything in the Application Logs that correspond to this. How can I troubleshoot it?

     

    Thanks,

    Chris.

    Tuesday, July 20, 2010 11:24 PM

Answers

  • Thanks to MS support (and a 4 hour phone call) this issue has been resolved. It had to do with the default Project services that was being applied to the PWA site. A simple answer in the end but it took forever to get there.
    • Marked as answer by cparker4486 Wednesday, July 21, 2010 8:46 PM
    Wednesday, July 21, 2010 8:46 PM

All replies

  • When SharePoint or Project Server throws an error it will log to the Unified Logging Service (ULS) logs. The location of the ULS logs can be configured by the SharePoint administrator in Central Admin, but in most cases they will reside in  C:\Program Files\Common Files\Microsoft Shared\web server extensions\14\LOGS.

    The correlation id in the error message allows easy correlation between the error condition and the log messages that caused it. I would recommend using a tool such as ULSViewer to view and trawl the logs for the relevant error and either search to see if anyone has had a similar problem, or post another message to the forums with the relevant ULS lines.

    More info on the ULSViewer can be seen at http://blogs.msdn.com/b/chrisfie/archive/2009/10/30/sharepoint-and-project-server-uls-viewer-tool-released.aspx

    Hope this helps,

     


    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Wednesday, July 21, 2010 2:00 AM
    Moderator
  • Hi Alexander,

    That is a very cool tool. I did find out about ULS yesterday after my post but could not make heads or tails of the errors but here they are:

     

    (1)

    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 3.0 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.Interfaces.IAuthentication.GetUserByName(String username)   
     at Microsoft.Office.Project.Server.AuthenticationHelper.AuthenticateUserByName(String userName, Guid siteId)

    (2)

    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 3.0 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.Interfaces.IAuthentication.GetUserByName(String username)   
     at Microsoft.Office.Project.Server.AuthenticationHelper.AuthenticateUserByName(String userName, Guid siteId)   
     at Microsoft.Office.Project.PWA.PJContext.AuthenticateUserForPWA(Boolean needToValidateUser, String username, Guid siteId)

    (3)

    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 3.0 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.Interfaces.IAuthentication.GetUserByName(String username)   
     at Microsoft.Office.Project.Server.AuthenticationHelper.AuthenticateUserByName(String userName, Guid siteId)   
     at Microsoft.Office.Project.PWA.PJContext.AuthenticateUserForPWA(Boolean needToValidateUser, String username, Guid siteId)   
     at Microsoft.Office.Project.PWA.PJContext.AuthenticateUserForPWA(Boolean newCookie)   
     at Microsoft.Office.Project.PWA.PJContext.GetContext(Boolean isWebServiceCall, Boolean newCookie, Guid siteId, Nullable`1 zone, Boolean useCache)   
     at Microsoft.Office.Project.PWA.PJContext.GetContext(Boolean isWebServiceCall, Boolean newCookie, Guid siteId, Nullable`1 zone)   
     at Microsoft.Office.Project.PWA.PJBaseWebPartPage..ctor()   
     at ASP.DEFAULT_ASPX__1514027361..ctor() in c:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\00354d9e\d48754ec\App_Web_default.aspx_-1514027361.kvj-x3nk.0.cs:line 0   
     at __ASP.FastObjectFactory_app_web_default_aspx__1514027361_kvj_x3nk.Create_ASP_DEFAULT_ASPX__1514027361() in c:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\00354d9e\d48754ec\App_Web_default.aspx_-1514027361.kvj-x3nk.1.cs:line 0   
     at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert)   
     at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)   
     at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()   
     at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    Wednesday, July 21, 2010 4:11 PM
  • Thanks to MS support (and a 4 hour phone call) this issue has been resolved. It had to do with the default Project services that was being applied to the PWA site. A simple answer in the end but it took forever to get there.
    • Marked as answer by cparker4486 Wednesday, July 21, 2010 8:46 PM
    Wednesday, July 21, 2010 8:46 PM
  • Sorry to revive this post, but I'm having this exact problem with the Demo VPC for project 2010, what did they do exactly to fix it?

    Thanks!

    Wednesday, November 17, 2010 11:10 AM
  • Hi, i am also having the same problem, can you please let us know what they did to fix it?

    Thanks!

    Thursday, November 18, 2010 12:28 AM