Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
An unexpected error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello there

    I am running Project Server 2010+...

    I created new group in PWA. After I get An unexpected error when launch PWA.

    INFO:

    System.Web.Services.Protocols.SoapException: ProjectServerError(s) LastError=GeneralSecurityAccessDenied Instructions: Pass this into PSClientError constructore to access all error information

    Stack Trace:

    [SoapException: ProjectServerError(s) LastError=GeneralSecurityAccessDenied Instructions: Pass this into PSClientError constructore to access all error information]
       Microsoft.Office.Project.Server.WebServiceProxy.PWA.SecurityCheckUserPagePermission(Guid pageUid) +377
       Microsoft.Office.Project.PWA.PJBaseWebPartPage.CheckPagePermission() +94
       Microsoft.Office.Project.PWA.PJBaseWebPartPage.OnPreInit(EventArgs e) +302
       System.Web.UI.Page.PerformPreInit() +42
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1256

     Can anybody help me with this matter.

    Wednesday, February 9, 2011 12:42 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    First try dumping the cache in your browser. If that doesn't help, please explain what exact steps you took prior to and during the error.
    Gary Chefetz, MCITP, MCP, MVP msProjectExperts
    Project and Project ServerFAQs
    Project Server Help BLOG
    Wednesday, February 9, 2011 1:47 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    We had the same error and stack trace at a customer.

    In our case it was because of a delegate session. The removal of the delegate session and dumping the cache in the browser worked for us.

    - Dennis | Netherlands | Blog | Twitter

    • Proposed as answer by Apps User Tuesday, November 28, 2017 1:12 PM
    Friday, July 13, 2012 2:20 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Actually had a very similar situation.  It turned out the person that I was working in Behave OF for did not have any security roles, such as TEAM MEMBER.  Once I added this role, they had access to PWA.

    Cheers!

    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Thursday, May 15, 2014 3:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We had the same error and stack trace at a customer.

    In our case it was because of a delegate session. The removal of the delegate session and dumping the cache in the browser worked for us.

    - Dennis

    This solved the problem in my case too, Maybe Wharton's solution is correct and better, but I only saw it afterwards, so you may want to check it

    BR,



    • Edited by Apps User Wednesday, November 29, 2017 7:46 AM
    Tuesday, November 28, 2017 1:13 PM