Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Does anyone have Auto-Publish Rule Working? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have PPM2010 Server, SP1, patched to August 2011 CU level.  I have setup a rule to auto-publish any task updates when I push the "Run Selected" button.  However, only a few, if any, projects actually publish.  The draft DB is updated because I see the posted hours for the specific tasks.  I have had an open ticket with Microsoft for the past 6 weeks and no luck.  They have had us put traces on the SQL to see if there are deadlocks causing the issue.  So far, no solution.  Nice feature that doesn't seem to work for us.

    Tom

    Wednesday, December 21, 2011 6:30 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Works fine for me. Glad to see you have open a ticket with MSFT support.
    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Thursday, December 22, 2011 2:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Christophe,

    When you say it is working for you...Are you updating/publishing multiple tasks for multiple projects, submitted from multiple resources via single-entry mode timekeeping, at one time? 

     

    Thursday, December 22, 2011 12:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I use it for task update that come accross from multiple dev resources that are making work item updates in Team Foundation Server (using the connector between the two).
    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Thursday, December 22, 2011 6:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Christophe,

    We use task updates from single-entry mode timesheets.  On a given Monday we will process close to 1,000 tasks on nearly 300 projects.  However, the failure to auto-publish using the rule can occur on even a small set of tasks/projects.  I continue to work this open incident with the support team now 7 weeks in duration.

     

    Friday, December 23, 2011 1:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Tom,

    We are also seeing some irregular activity with auto-publish.

    Can I ask what build you are on? We are using SP1 + Aug CU.

    Did you reach any conculsions or success with Premier Support?

    Thanks,

    Shane

    Shane O'Hanlon (Accenture)

    Thursday, February 9, 2012 12:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
     

    Shane,

    The rule has not worked effectively for us.  If I had 10 projects to publish, using the rule I would only see one or two actually publish.  The rest failed.  What irregularities have you seen?

    We are on SP1 | Aug 2011 CU as well.

    After 3 months of effort with MS Support, they have pushed it to the developers for a fix, because they were able to repro the issue in their lab.   If it doesn’t create havoc on others, then we will get a private fix sometime in the next month or so.  Later they will provide the fix in a CU.

    Thanks for your reply,

    Tom

    Thursday, February 9, 2012 4:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We are facing the similar issue, but the auto approval rule approves Status Updates for some PMs and the rule is not working for some PMs. We are on SP1, with SEM enabled.

    Tom, did you get any update from MS Team regarding the fix you mentioned in your post?

    Wednesday, April 11, 2012 3:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The issue was sent to the developers and the fix is to be part of the April 2012 CU.  I plan to install this on our test system to see if all is well.

    Tom

    Monday, April 16, 2012 4:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Tom

    I suggest you should check this add-on:

    http://www.ms-addons.com/Auto-Publish

    You can pre-define an automatic publishing for a day or days in a week, specific hours etc.

    Works great!

    Ofir Marco , MCTS P.Z. Projects

    Thursday, April 19, 2012 6:56 AM
  • Question
    Sign in to vote
    2
    Sign in to vote
    FYI the April CU is out!

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    Friday, April 27, 2012 4:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the update.

    I think that the CU is this http://support.microsoft.com/kb/2598272.

    Best Regards
    ARM



    Friday, April 27, 2012 5:01 PM
  • Question
    Sign in to vote
    2
    Sign in to vote
    Our official announcement: http://blogs.technet.com/b/projectadministration/archive/2012/04/27/microsoft-project-server-and-sharepoint-server-2007-and-2010-april-2012-cu-announcement.aspx

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    Saturday, April 28, 2012 12:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Tom, have you been able to install the April 2012 CU to test the issue with Auto Publish/Approve? If so, what were you findings? Did the CU resolve the block between running the approve and publish function?

    Thanks for the update.

    Friday, May 11, 2012 2:56 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Michael and all,

    It appears that the April CU has fixed the auto-publish issue.  I continue to test on our lab machine using backed up files from our production system in which there are a lot of task updates waiting approval and publishing.  The auto-publish rule will approve, accept, and publish all pending task updates appropriately saving our planners 15 - 45 minutes of time every Monday.  I plan to update our production system with the April CU the end of May, providing my continued testing doesn't have a failure.

    Wednesday, May 16, 2012 12:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry you had to wait so long for us to get to the bottom of this one Tom, and I'm sure others will be glad you brought this to our attention and got it fixed.

    Best regards,

    Brian.

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    Thursday, May 17, 2012 11:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    and just some background that might help others to see if this will fix any auto-publish problems they are having - the issue was that if while cycling through the updates that needed auto publishing we came across a checked-out plan - we stopped the updates, rather than just skipping to the next plan.

    Brian.

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    Thursday, May 17, 2012 11:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I still don't think that the auto-publish rule is completely working as it intended.  In my test environment, it does process all the projects with updates except for any on projects that are currently checked out.  The note in the status update history indicates that the project that is checked out will be updated once it's checked back in.  When that project is checked back in, the update is left unprocessed though and it stays in that steady state.  It will be processed once another update is pushed through on the project file. 

    So, either the note on the stuatus history is incorrect or the auto-publish is still not working as designed. 

    Friday, June 1, 2012 4:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Can you clarify what you mean by 'processed' Tyler?  Any pending updates should be applied when a plan is checked back in - and I am not aware of any scenarios where that does not occur.  Or are you saying the auto-publish isn't happening when these updates get applied?  The note in status history only relates to the status update being applied - and I would probably expect, like you, that the auto-publish should kick in when that happens - perhaps that is the peice that isn't working?  If you can confirm waht you are seeing I'll check on the design expectations.

    Best regards,

    Brian.

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    Friday, June 1, 2012 4:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Brian.

    Sorry for the lack of clarity - I hope this helps.

    When a project is checked out and an update on that project is accepted with a rule that has the auto-publish box checked, the update on the project gets marked as "Pending" in the Status column.  A note in the Info column that accompanies the update is "These task updates have not been applied to the plan or communicated to the team member.  They will be applied as soon as possible once the project is checked in."  When I go and check in the project and check the status history again, the "Pending" status is now "Unpublished" and the note is gone.  My expectation is that the update would have been published when the project is checked back in. 

    Perhaps this is just my misunderstanding of the function but it would be nice to have the project published once it was checked back in so that there aren't unpublished updates sitting around where people would not be aware of.

    -TJ

    Friday, June 1, 2012 4:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks TJ, I'll make some enquiries here and find out what should be happening.  Like you I'd expect the auto-publish to happen whenever the updates get applied - either immediately or once the plan is checked in.

    Best regards,

    Brian.

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    Friday, June 1, 2012 4:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Brian and Tyler,

    I had the same question, but in testing found that checking in the checked-out project(s) only completes the status update...not the publish.  Therefore, I have all planners check the Approval History page after running the rule to look for any tasks that were not published.  The information message is helpful since it points out what the planner needs to do before attempting another publish.  The best advice I give them all is to make sure all of their projects are checked in BEFORE they run the rule.

    Best wishes,

    Tom

    Friday, June 1, 2012 5:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Tom, and just reviewing the Edit/Create rules page and this appears to confirm the behavior TJ is seeing as 'by design'.  In the automatic updates section it says:

    "Indicate whether to automatically run this rule and publish the updates. If the
    project is checked out to someone else, the updates are published after the
    project is checked in and another update comes through or after you publish the
    project."

    So the publish will happen after the project is checked in AND another update comes through.  I learn something new every day.

    Best regards,

    Brian.

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    • Proposed as answer by TylerGJ Friday, June 1, 2012 5:25 PM
    Friday, June 1, 2012 5:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Great - Thanks Brian!

    Hi Tom,

    Oh how I wish I could get comliance like that.  We have about 600 projects at any given time and about 100 different project owners.  It gets hairy pretty quickly even when people are aware of what needs to happen.  We ended up just putting a script in place that publishs everything at night.  It creates it's own issues but at least everything makes it into the reporting database!  :)

    -TJ

    Friday, June 1, 2012 5:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ah perfect - Thanks for the clarfication Brian!

    Friday, June 1, 2012 5:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    On this topic of auto-publish please check this recent PowerShell script published by Paul : Project Server 2010 - Publish all projects

    http://gallery.technet.microsoft.com/scriptcenter/Server-2010-Publish-all-45ba385b/view/Reviews

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    Tuesday, June 5, 2012 6:31 AM