none
Adding enterprise resource in Project Pro results in Project failing to open in subsequent attempts RRS feed

  • Question

  • We recently had an issue with a project failing to open in Project Pro 2010 from Project Server 2010. The project would appear to be loading: Project Pro would start, it would display "opening ..." in the status bar, but then it would just stop and not load the project.

    In researching the problem, we stumbled upon an enterprise resource in the MSP_PROJECT_RESOURCES table that had RES_TYPE of -4 where all the other Enterprise Resources were 2 or 20 (Work or Generic Work, respectively). As it was, that resource was added to the project right before the problem started happening.

    No other projects had this problem and no other projects had named resources with a RES_TYPE of -4. (ALL projects have one resource with NULL RES_NAME and RES_TYPE of -4)

    We removed this resource from the project using Project Web App's Build Team and the project would open without problem. We then added the resource back to the project from Build Team in Project Pro, and the resource showed up in the MSP_PROJECT_RESOURCES table with RES_TYPE -4. We removed the resource again and then added her back from Project Web App's Build Team and she was registered as RES_TYPE 2.

    We use Build Team in Project Pro quite a bit and have never had this problem before (over 7 months of Project Server 2010 use).

    Anyone else have a similar issue or occurrence that might shed light as to why this is happening?

    Thank you

    Monday, July 23, 2012 3:42 PM

Answers

  • Hi Jim,

    This does sound very much like an issue we are addressing in the August 2012 CU.  Another symptom, and the main reason the plan will not open, is that another field in that same table contains duplicate values.  The field that gets duplicated is RES_OPTINDX.  I'd suggest opening a support incident with us to assist in gettings that plan in a better state.  The behavior you are seeing is the same as we tend to see with that workaround of un-assigning in PWA - that ithe problem will return with the next assignment made using Build Team.  You could also try removing the plan from your local cache (making sure the plan is saved and checked in) and then fixing in PWA and then opening in Pro to see if this allows the use of Build Team again.

    The August CU is due out on the last Tuesday of August - and if you do open an incident this particular bug can be referred to as Office QFE 33562 when talking to our support engineer.

    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

    • Marked as answer by Jim Blain Friday, July 27, 2012 10:44 PM
    Monday, July 23, 2012 8:07 PM
    Owner

All replies

  • Hi Jim,

    This does sound very much like an issue we are addressing in the August 2012 CU.  Another symptom, and the main reason the plan will not open, is that another field in that same table contains duplicate values.  The field that gets duplicated is RES_OPTINDX.  I'd suggest opening a support incident with us to assist in gettings that plan in a better state.  The behavior you are seeing is the same as we tend to see with that workaround of un-assigning in PWA - that ithe problem will return with the next assignment made using Build Team.  You could also try removing the plan from your local cache (making sure the plan is saved and checked in) and then fixing in PWA and then opening in Pro to see if this allows the use of Build Team again.

    The August CU is due out on the last Tuesday of August - and if you do open an incident this particular bug can be referred to as Office QFE 33562 when talking to our support engineer.

    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

    • Marked as answer by Jim Blain Friday, July 27, 2012 10:44 PM
    Monday, July 23, 2012 8:07 PM
    Owner
  • Thanks for the information. We haven't seen a recurrence as of yet, but if we do, we will open a support case. Thank you.
    Friday, July 27, 2012 10:45 PM