none
Error workflow has been created successfully, but failed to publish and will not be listed in the Project Center RRS feed

  • Question

  • hello,

    when i try creating projects in Project center am posted on with this error.

    Your new XXXX workflow has been created successfully, but failed to publish and will not be listed in the Project Center.For more information on the failure, visit the My Queue Jobs page or contact your administrator.

    Any help would be appreciated!!!!!


    Thanks regards, Vignesh.

    Thursday, July 3, 2014 11:57 AM

All replies

  • Hi Vignesh,

    This is quite a generic message. You should check for the ULS log message that will provide more details about your issue.

    That being said, which Project Server version and patch level are you using? Is it a custom EPT with a custom workflow? How did you build your workflow?


    Hope this helps,


    Guillaume Rouyre, MBA, MCP, MCTS |

    Thursday, July 3, 2014 12:15 PM
    Moderator
  • hello Rouyre,

    Thanks for ur reply

    Am using 

    Microsoft Project Server 2013


    15.0.4420.1017

    Yes! It is Custom EPT with Custom Workflow(Declarative Workflow) built through VS2012

    after associating the Site workflow with EPT i try creating Projects using my Custom EPT since then am posted on with this error.

    ULS Error:Log

    07/04/2014 10:21:38.03 Microsoft.Office.Project.Server (0x1840) 0x06B8 Project Server                 Queue                         ad3fy Critical Standard Information:PSI Entry Point: <unknown>  Project User: <unknown>  Correlation Id: <unknown>  PWA Site URL:   SA Name: <unknown>  PSError: <unknown> A queue job has failed. This is a general error logged by the Project Server Queue everytime a job fails - for effective troubleshooting use this error message with other more specific error messages (if any), the Operations guide (which documents more details about queued jobs) and the trace log (which could provide more detailed context). More information about the failed job follows. GUID of the failed job: 39cd36d6-3603-e411-b33e-00155d00091f. Name of the computer that processed this job: 3eebbc1d-7558-4050-bf5d-d985b23b89f5 (to debug further, you need to look at the trace log from this computer). Failed job type: ReportWorkflowProj... 2c1ea19c-5849-002d-b89f-50aaf0a752fd
    07/04/2014 10:21:38.03* Microsoft.Office.Project.Server (0x1840) 0x06B8 Project Server                 Queue                         ad3fy Critical ...ectDataSync. Failed sub-job type: ReportWorkflowProjectDataSyncMessage. Failed sub-job ID: 1. Stage where sub-job failed:  (this is useful when one sub-job has more than one logical processing stages). 2c1ea19c-5849-002d-b89f-50aaf0a752fd
    07/04/2014 10:21:38.03 Microsoft.Office.Project.Server (0x1840) 0x06B8 Project Server                 Queue Jobs                     ad3fy Medium   Error is: GeneralQueueJobFailed. Details: Queue Attributes:  39cd36d6-3603-e411-b33e-00155d00091f  3eebbc1d-7558-4050-bf5d-d985b23b89f5  ReportWorkflowProjectDataSync  ReportWorkflowProjectDataSyncMessage  1    2c1ea19c-5849-002d-b89f-50aaf0a752fd  . Standard Information: , LogLevelManager Warning-ulsID:0x000DD158 has no entities explicitly specified. 2c1ea19c-5849-002d-b89f-50aaf0a752fd
    07/04/2014 10:21:38.03 Microsoft.Office.Project.Server (0x1840) 0x06B8 Project Server                 Project Server Database       ah91z Medium   Successfully got the connection string (database name=[ProjectWebApp_Practice], id=1f6004ae-5d8a-41d2-81f9-e424a31484aa, type=Consolidated). Requested access level=ReadWrite: Data Source=XXXX;Initial Catalog=ProjectWebApp_Practice;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15 2c1ea19c-5849-002d-b89f-50aaf0a752fd
    07/04/2014 10:21:38.04 Microsoft.Office.Project.Server (0x1840) 0x06B8 Project Server                 Queue Jobs                     ad3fz Medium   PWA:http://XXXX:10000/PWAPactice, ServiceApp:Project Server Service Application, User:PROJECTSERVER\system, PSI: [QUEUE] receiver http://XXXX:10000/PWAPactice: Group 3bcd36d6-3603-e411-b33e-00155d00091f type = ReportWorkflowProjectDataSync aborted at Message 1, LogLevelManager Warning-ulsID:0x000DD159 has no entities explicitly specified. 2c1ea19c-5849-002d-b89f-50aaf0a752fd
    07/04/2014 10:21:38.04 Microsoft.Office.Project.Server (0x1840) 0x06B8 Project Server                 Queue Jobs                     ad3f2 Medium   PWA:http://XXXX:10000/PWAPactice, ServiceApp:Project Server Service Application, User:PROJECTSERVER\system, PSI: [QUEUE] receiver http://XXXX:10000/PWAPactice: Group 3bcd36d6-3603-e411-b33e-00155d00091f correlation 82705dc5-3603-e411-b33e-00155d00091f type = ReportWorkflowProjectDataSync failed at Message 1 Errors: GeneralQueueJobFailed, LogLevelManager Warning-ulsID:0x000DD15C has no entities explicitly specified. 2c1ea19c-5849-002d-b89f-50aaf0a752fd


    Thanks regards, Vignesh.


    Friday, July 4, 2014 5:41 AM
  • Hi Vignesh, you probably already found this post: http://social.msdn.microsoft.com/Forums/en-US/2a1d0d22-5245-4f7d-be7a-d228028d95af/workflow-start-failed-but-not-blocking-correlation-project-server-workflow-for-demand-management?forum=project2010custprog. Another thing is you should make sure the User Profile Service is configured correctly. Hope this helps.
    Tuesday, July 8, 2014 8:15 AM