Kashif Nizam Qureshi

Leave a comment

Project Server 2013 Sending GeneralQueueJobFailed Error Emails

You receive the following email.

Solution: Simply release some memory from server :) Mine was taking 7+ out of 8 GB (Recommended is at least 16 GB)


Subject: Your queue job PreparePSProjectPermissionSynchronization failed. Please contact your administrator for assistance


Your PreparePSProjectPermissionSynchronization job failed. Its current state is FailedNotBlocking. It was 0% complete. It entered the queue at 06/02/2014 09:24:39.


To get more information about the job failure, please go to Project Web App. Select Personal Settings from the left menu. Then select My Queued Jobs.


The errors returned from the queue are as follows:

Error ID: 26000


Detailed error below – send it to the administrator for more detailed troubleshooting.


<?xml version=”1.0″ encoding=”utf-16″?>



<class name=”Queue”>

<error id=”26000″ name=”GeneralQueueJobFailed” uid=”a5295a3b-16ea-e311-93f4-3440b5c8d286″ JobUID=”5e7d692f-16ea-e311-93f4-3440b5c8d286″ ComputerName=”f7e42ffb-822b-4c26-89d7-3887749c7b49″ GroupType=”PreparePSProjectPermissionSynchronization” MessageType=”PreparePSProjectPermissionSynchronizationMessage” MessageId=”1″ Stage=”” CorrelationUID=”62d3969c-70df-e085-c7b4-902232ca1280″ />





You can do the following:

1. Try troubleshooting using the error IDs, error XML.

2. Contact administrator with your jobID (5e7d692f-16ea-e311-93f4-3440b5c8d286) and error XML.


To turn off these notifications, go to PWA Settings, and then click Manage My Alerts and Reminders.


From this page, you can clear the check box for those notifications you no longer want to receive.


Microsoft Project Server

Leave a comment

Project Server 2013 SP1 Error – Derived method ‘RequiresWebPartClientScript’

Installing Project Server 2013 SP1, you welcome yourself to hell! :P

The server went down with the following error.

“Derived method ‘RequiresWebPartClientScript’ in type ‘Microsoft.Office.Project.PWA.WebParts.PWAPart’ from assembly ‘Microsoft.Office.Project.Server.PWA, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ cannot reduce access.”

I was wondering why this PS SP1 is such in small size, where as earlier CUs were over a GB. What I beleive it does not contain anything for SharePoint and that would have caused the issue. So I went for SharePoint 2013 SP1, an another hell! :P well it worked after couple of hours of update :)

Leave a comment

Access Denied: Claims stored in the credentials did not match with the group claim for a group app

This comes when I try to access report after I setup Excel and Secure Store Services. Everything was setup perfectly, as I’ve done it many times but this time nothing seems to be working. I came across a site where it was mentioned that sometimes SSS gets crazy and doesn’t work properly.

The solution that worked for me was to recreate SSS Application, other solution could’ve also worked, that is just to recycle IIS (in my case didn’t require).

Happy Reporting!



Leave a comment

The option for the SharePoint 2013 workflow platform is not available

Register-SPWorkflowService -SPSite “http://vm08/pwa&#8221; -WorkflowHostUri “http://vm08:12291&#8243; -AllowOAuthHttp

Using the above PowerShell command to hook Workflow Manager farm to SharePoint Farm site, throws the following error

“The option for the SharePoint 2013 workflow platform is not available”

In my case, restarting the workflow manager service get me rid of the error!


Get every new post delivered to your Inbox.