Skip to main content

ProjectCheckinNotifyWorkflowMessage - Project Server

While developing a new program in Project Server CSOM today I got a strange error message in the queue:

 GeneralQueueJobFailed (26000) - WorkflowCheckinNotify.ProjectCheckinNotifyWorkflowMessage.   
 Details: id='26000' name='GeneralQueueJobFailed' uid='c71ab4e8-161e-e411-94b6-00155d006e04'   
 JobUID='c41ab4e8-161e-e411-94b6-00155d006e04'   
 ComputerName='20cd9b2e-c115-41ab-b138-70be4280f816'   
 GroupType='WorkflowCheckinNotify'   
 MessageType='ProjectCheckinNotifyWorkflowMessage' MessageId='1' Stage=''   
 CorrelationUID='4620ac9c-98d6-207f-0f81-68c3227e07e2'.   
 For more details, check the ULS logs on machine 20cd9b2e-c115-41ab-b138-70be4280f816 for entries with JobUID c41ab4e8-161e-e411-94b6-00155d006e04.   

The program was trying to insert a new task in a project. Inserting the task manually through the PWA also causes the error. There is no workflow on my EPT which makes the error message much more confusing.
The ULS logs didn't provide any other information.

Reason

The reason for the error is strait forward. I had not configured outgoing e-mail settings and when Project Server tried to send an email on workflow check-in it causes the error.

Solution

Disable notifications under Manage My Alerts in the PWA
or
Configure outgoing e-mail settings in SharePoint-Central Administration.


Comments

Popular posts from this blog

Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.

Received this error today when trying to create a SharePoint solution against a newly created site.


My first problem was the site was configured to use a port which was already used by another web site. Therefore the site could not start at all.

In my case both Default Web Site and SharePoint - 2000 was both using port 2000. Changing the port of Default Web Site and I was able to start the site.

However now I still received the same error message. When browsing the site I realized I did not have access to the site.

Giving access to my user and I was able to deploy the solution.

To sum up this post:
 - Check the site can start
 - Check the site can be browsed
 - Check your user have access to the site

SharePoint 2013 : Cannot connect to the targeted site.

On my Contoso environment I was trying to create a sandboxed solution. I have already configured my app domain and app management services. But when I tried to validate the site I got the following error message.
Error

Cannot connect to the targeted site. This error can occur if the specified site is not hosted on the local system. SharePoint solutions work only with locally-installed versions of SharePoint Foundation or SharePoint Server. Remote development is supported only for apps for SharePoint 2013.
If you search around the internet you will find many people suggesting to change your host file from 127.0.0.1 to the actual IP.

Solution However the solution, at least on a Contoso environment, is to type in the actual IP address in the host file.
(the IP 192.168.150.1 is the special IP for Contoso, I have 2 network adapters)
And do not forget to clear/flush the DNS cache. Now the solution can be created and validates.


PowerShell results size unlimited/truncated - $FormatEnumerationLimit/Width

Ever experienced the problem where you run a Powershell command and you cannot see the whole result because the result is truncated.

Problem: If you for example run the Test-SPsite command you might see something like the following:


Site : SPSite Url=http://atlas/pwa Results : { SPSiteHealthResult Status=Passed RuleName="Conflicting Content Types" RuleId=befe203b-a8c0-48c2-b5f0-27c10f9e1622, SPSiteHealthResult Status=FailedWarning RuleName="Customized Files" RuleId=cd839b0d-9707-4950-8fac-f306cb920f6c, SPSiteHealthResult Status=Passed RuleName="Missing Galleries" RuleId=ee967197-ccbe-4c00-88e4-e6fab81145e1, SPSiteHealthResult Status=Passed RuleName="Missing Parent Content Types" RuleId=a9a6769f-7289-4b9f-ae7f-5db4b997d284, SPSiteHealthResult Status=FailedError RuleName="Missing Site Templates" RuleId=5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd, …