none
Project Server 2013 Error Msg: LastError=GeneralUnhandledException Instructions: Pass this into PSClientError constructor to access all error information RRS feed

  • Question

  • HI All,

    Project Server 2013 Deployed on Win 2008R2 SP1. a Workflow with simple on submit Logic is Created and Published.

    On clicking save in the New project (Workflow attached EPT) page the following error comes up.

    ProjectServerError(s) LastError=GeneralUnhandledException Instructions: Pass this into PSClientError constructor to access all error information

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Web.Services.Protocols.SoapException: ProjectServerError(s) LastError=GeneralUnhandledException Instructions: Pass this into PSClientError constructor to access all error information

    [SoapException: ProjectServerError(s) LastError=GeneralUnhandledException Instructions: Pass this into PSClientError constructor to access all error information]

       Microsoft.Office.Project.PWA.<>c__DisplayClass4.<DoInProcCommands>b__3() +765

       Microsoft.Office.Project.PWA.PWARequestManager.RunInAppTierContext(Action action) +101

       Microsoft.Office.Project.Server.WebServiceProxy.PWARequests.WorkflowGetProjectDrilldownInformationRequest.InProc(PJContext webFrontEndContext, Guid projectUid, String userPropToClear, Boolean bCheckOutProject, Int32 returnLocationId) +235

       Microsoft.Office.Project.Server.WebServiceProxy.PWA.WorkflowGetProjectDrilldownInformation(Guid projectUid, String userPropToClear, Boolean bCheckOutProject, Int32 returnLocationId) +237

       Microsoft.Office.Project.PWA.ProjectDrillDownWebPartPage.OnLoad(EventArgs e) +372

       System.Web.UI.Control.LoadRecursive() +95

       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2936

    Has anyone faced this issue!!

    Saturday, May 16, 2015 2:16 PM

Answers

  • Thank you James for the inputs.

    Looks like the Workflow Service Account doesn't have permissions on the workflow databases. Granting the Permission resolved the issue. 

    Regards
    Daniel.

    • Marked as answer by P Daniel Wednesday, June 3, 2015 5:40 AM
    Monday, May 18, 2015 7:51 AM

All replies

  • Hey there Mr. Daniel,

    This doesn't actually look like a Workflow issue.  The problem appears to be occurring when attempting to navigate to the Project after project creation, the ProjectDrillDown.aspx page attempts to contact the PSI to get some info and fails.   

    I would turn the farm to verbose logging, download a ULS log viewer on the App Server and set the filter to message contains "GetProjectDrilldownInformation" and see what you get.  

    In a multi-server farm this may be a load balancing, or authentication problem.

    Regards,

       James.


    James Boman BSc. MCP:EAD -

    Monday, May 18, 2015 5:14 AM
  • Hi James,

    Thankyou for the reply.

    Below are the ULS Log findings ...

    Exception occured in method 'Workflow.GetProjectDrilldownInformation' Microsoft.Workflow.Client.InternalServerException: Exception thrown from the data layer. For more details, please see the server logs. HTTP headers received from the server - ActivityId: 0156e008-0576-47d4-b25d-f073b2ad6afb. NodeId: ServerName. Scope: /SharePoint/default/58786f58-1a5f-404a-8d69-3a93edac6b37/51418cd7-1fde-4767-9e54-e0702c0f04c9. Client ActivityId : 2c7f079d-f1ec-6092-7234-3f27c206ea7b. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.   

     at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)   

     at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)   

     at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)     -

     -- End of inner exception stack trace ---   

     at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)   

     at Microsoft.Workflow.Client.InstanceManager.Get(String workflowName, String instanceName)   

     at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.GetInstances(String serviceGroupName, Int32 offset, Int32 count, String workflowName, String instanceName, String monitoringParameter, WorkflowInstanceStatus workflowInstanceStatus)   

     at Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider.GetInstance(Guid instanceId)   

     at Microsoft.Office.Project.Server.BusinessLayer.Workflow.GetWorkflow4Instance(Guid instanceUid, WorkflowInstanceService& spwfInstanceProvider)   

     at Microsoft.Office.Project.Server.BusinessLayer.Workflow.GetWorkflowState(Guid projectUid, ProjectDrillDownInfo info)   

     at Microsoft.Office.Project.Server.BusinessLayer.Workflow.GetProjectDrilldownInformation(Guid projectUid, String userPropToClear, Boolean bCheckOutProject, Int32 returnLocationId)   

     at Microsoft.Office.Project.Server.Wcf.Implementation.PWAImpl.<>c__DisplayClass227.<WorkflowGetProjectDrilldownInformation>b__226()   

     at Microsoft.Office.Project.Server.Wcf.Implementation.WcfMethodInvocation.InvokeBusinessObjectMethod(String businessObjectName, String methodName, IEnumerable`1 actions) StackTrace:

     at Microsoft.Office.Project.Server.Native.dll: (sig=6ea170d1-988e-4153-9f1d-0305c0ea0309|2|microsoft.office.project.server.native.pdb, offset=3C1E)

     at Microsoft.Office.Project.Server.Native.dll: (offset=1255D)

    Regards

    Daniel

    Monday, May 18, 2015 7:05 AM
  • Daniel,

        That shows the request that generated the 500 error, and 500 series messages by their design have no capability to report the cause of the problem, so we need to capture the error on the other side of the request - this may be the machine running the Project Application Service or the Web Front End Machine.

    You may need to experiment with the ULS log viewer, but I am confident you can capture the exception that causes the 500 message you have posted.  Keep an eye out for ULS entries marked "Critical" at the time of the request.

    Sorry I couldn't be more specific.

    Cheers,

       James.


    James Boman BSc. MCP:EAD -

    Monday, May 18, 2015 7:40 AM
  • Thank you James for the inputs.

    Looks like the Workflow Service Account doesn't have permissions on the workflow databases. Granting the Permission resolved the issue. 

    Regards
    Daniel.

    • Marked as answer by P Daniel Wednesday, June 3, 2015 5:40 AM
    Monday, May 18, 2015 7:51 AM
  • Please check mode(automatic or Manual) while creating assignment it will work if you mode of select should be automatic.
    Thursday, November 17, 2016 10:41 AM