none
PJContext is not valid. PJContext is null. RRS feed

  • Question

  • Dear All,

    When we tried browse to pwa, we got welcomed by this message "Sorry this site hasn't been shared to you". Checking ULS we found this message "PJContext is not valid. PJContext is null". This PWA site had been working perfectly until this error occurred. We access the site with domain account and all our user has admin rights on the PWA. This is part of ULS log we discovered:

    01/19/2016 15:35:55.14 w3wp.exe (0x3240) 0x2C8C Project Server Security aeauy Medium PJContext is not valid. PJContext is null. 38b3569d-a41a-2062-b5ed-f60140efa40c
    01/19/2016 15:35:55.14 w3wp.exe (0x3240) 0x2C8C SharePoint Foundation General ftd0 Medium Access Denied. Exception: Attempted to perform an unauthorized operation., StackTrace:   at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(Exception ex)     at Microsoft.Office.Project.PWA.PJBaseWebPartPage.OnPreInit(EventArgs e)     at System.Web.UI.Page.PerformPreInit()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()     at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)     at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)     at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)     at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)     at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  . 38b3569d-a41a-2062-b5ed-f60140efa40c


    Ariwibawa

    Tuesday, 19 January 2016 8:51 AM

All replies

  • Hi,

    Is this issue is resolved ?

    We are also facing the same issue today.

    Thanks & Best Regards,

    Venkat

    Monday, 6 January 2020 2:22 PM
  • if I remembered correctly this was due to untrusted PWA server with AD server, it was because different time between AD server and pwa server was greater than 7 minutes (I'm not sure about how much different in minutes was allowed). Resync time was the remedy.

    Ariwibawa

    Tuesday, 7 January 2020 3:45 AM