none
project server 2010 psi issue? RRS feed

  • Question

  • Hi :

    We are currently on project server 2010, Sharepoint 2010 and sql server 2008 r2.  I created a project to update actual work in assignment using psi call.  I ran into an issue with two projects.  I stepped through the project.  It updated the expenses. But it never published the project.  I received the following error message. 

    <?xml version="1.0" encoding="utf-16"?>
    <errinfo>
      <dataset name="ProjectDataSet">
        <table name="Assignment">
          <row ASSN_UID="xxx" PROJ_UID="xxx">
            <error id="1047" name="ProjectActualsAreProtected" uid="xxx" />
          </row>
        </table>
      </dataset>
      <general>
        <class name="Queue">
          <error id="26000" name="GeneralQueueJobFailed" uid="xxx" JobUID="xxx" ComputerName="xxx" GroupType="ProjectUpdate" MessageType="ProjectUpdateMessage" MessageId="2" Stage="" />
        </class>
      </general>
    </errinfo>

    The strangest thing is if we go into pwa.  Then go to server setting.  Select Task Setting and Display.  Under protect user updates.  If we uncheck Only allow Task udpates via Tasks and Timesheets.   The project will run with no problem.  If we enable it again.  We will keep on receiving the error message that is shown above.   It only happened on these two projects.  The rest of the projects are fine.   We are not sure whether we should enable it or disable it.    Any ideas?  Is there something we need to change within these two projects ? What will cause this issue?

    Thanks,

    kkmick

     

     


     

     

    Monday, October 17, 2011 10:11 PM

Answers

  • Hi,

    The behavior you see is as expected, when you enable the Server Setting to 'Protect Actuals' by only allowing updates from task updates and timesheets, then if you have any existing actuals on any projects you will not be able to manually change those actuals and publish those projects again. That is exactly the purpose of that setting (know as protected actuals).

    In your case if you need to update actuals through other means (PSI) then you will need to disable this setting or at least remove any projects with protected actuals.

     

    HTH,


    Martin Laukkanen (Project Server Blog - www.nearbaseline.com/blog)
    • Marked as answer by kkmick Tuesday, October 18, 2011 2:01 AM
    Monday, October 17, 2011 11:09 PM

All replies

  • Hi,

    The behavior you see is as expected, when you enable the Server Setting to 'Protect Actuals' by only allowing updates from task updates and timesheets, then if you have any existing actuals on any projects you will not be able to manually change those actuals and publish those projects again. That is exactly the purpose of that setting (know as protected actuals).

    In your case if you need to update actuals through other means (PSI) then you will need to disable this setting or at least remove any projects with protected actuals.

     

    HTH,


    Martin Laukkanen (Project Server Blog - www.nearbaseline.com/blog)
    • Marked as answer by kkmick Tuesday, October 18, 2011 2:01 AM
    Monday, October 17, 2011 11:09 PM
  • Thank you very much. 
    Tuesday, October 18, 2011 2:02 AM
  • Hi, where do you disable Protected Actuals?

    Todd.


    Todd Klost

    Tuesday, March 19, 2013 7:47 PM