none
All PS2013 Queue Jobs Show Status "Waiting To Be Processed" Forever... RRS feed

  • Question

  • RTM SP2013/PS2013 farm.

    Nothing fancy.

    Restored PWA/contentdb from a working PS2010 implementation.

    Times sync is perfect on all servers (yes, including DB), have restarted ps queue service about a million times, have run repair-spprojectwebinstance (or whatever it's called) to requeue jobs, have checked database logs for errors (there are none), have checked ULS and event viewer (don't see anything remotely relevant), WF/SB service is installed and verified to be working (no idea if that's important or not, but I figured I would point that out)

    In fact, the only things I see that are the least bit unexpected are the lack of queue jobs, the fact that when I go to CA -> Manage Service Applications -> Project Services Service Application and click the down arrow next to my provisioned PWA the only options are "Retry" and "Manage" (which seems odd), and when I open my PWA or project site in SPD, I don't see Project 2013 Workflows in the list of options when I create a new workflow...

    I'm open to any ideas anyone has at this point... Thanks!

    Friday, March 8, 2013 12:53 PM

All replies

  • Hello Ramz_dc

    Did you install workflow manager and configure PWA go use it.  Workflow is not built in PS2013 like it was in PS2010.

    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

    Friday, March 8, 2013 10:38 PM
    Moderator
  • To answer your points:

    1. Lack of options in CA for the Project Provisioning - I have seen this when you go in on an account that does not have the correct privs. If you have full control, you should see Edit / Manage / View & Delete.

    2. As for the queue, check out this thread with some great tips from Brian Smith http://social.technet.microsoft.com/Forums/en-US/projserv2010setup/thread/9d32cbad-07bf-4042-a884-69d7c45a57c5. I would also consider doing another test migration to make sure all the steps, including the permission / set-spsite etc were all followed exactly.

    3. As Michael points out, to use SPD2013 to build Project Server workflows you need to install and configure Workflow Manager and associate it with your Project Server instance, details are located http://technet.microsoft.com/en-us/library/jj658588.aspx

    However, another common misconception is that workflow is no longer built in, this is not quite true. SharePoint 2013 and Project Server 2013 still have the ability to use the old 2010 based workflow engines which are there by default. In fact if you open SPD up you will see you can still build 2010 SharePoint workflows. It's the introduction of Project Server support in SPD that requires the workflow manager, you can still continue to build 2010 PS workflows with Visual Studio or other third party products should you require.

    Let us know how you go.


    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    Friday, March 8, 2013 11:42 PM
    Moderator