locked
Project Server 2010 BCM RRS feed

  • Question

  • We had an issue with Microsoft Project Server 2010 right after we migrated it from 2007.  We had put the system in backward compatibility mode and when we turned off BCM we had file corruption in the schedules when they were opened with Project Pro 2010 and it had something to do with workflow controlled fields.  I found a blog that  wrote that seems to be pretty much the same issue that we encountered but the blog is not about 2 years old so I'm wondering if anyone knows if Microsoft ever patched this issue.  http://nearbaseline.com/blog/2011/12/disabling-backwards-compatibility-mode-results-in-corruption/


    XRXSA

    Wednesday, July 9, 2014 7:48 PM

Answers

  • Hi Mike -

    The only logical reason for using BCM is that you still have some users that have not yet converted to v2010 clients.  We were hoping to be in BCM only a few weeks, it turned out to be a few months.  The mix of 2007 and 2010 starts to create problems.  The people that know 2007 features rebel at the 2010 features and pine for their 2007 client to return.  Because you are forcing the 2010 client to function without all of the 2010 features all kinds of errors start to occur for which this forum or documentation does not have all the answers.  You are going to get very good at explaining to people the concept of "Save for Sharing".

    A big hit for us was that when you transition from 2007 to 2010 the Format/Bar Styles will add at the bottom of each and every view all of the preferred Microsoft symbols for things like manual tasks, inactive tasks, duration only, etc.  All of that stuff is disabled while you are in BCM because 2010 features are not yet enabled, but it is in the Format Bar Styles for each and every view.  The day you turn off BCM all of that stuff suddenly becomes enabled; we had lots and lots and lots of complaints that suddenly symbols were disappearing --- this was because the Microsoft-inserted symbols and fields for 2010 started to become dominant that were before in hiding.  The other thing you will notice is that in all of your views start will be substituted with scheduled start, finish with scheduled finish, baseline estimated start for baseline start, and baseline estimated finish for baseline finish.  This is because start/finish/BL start/BL finish can now handle free text and nulls.  The new fields, Scheduled Start, etc., are date-only and use an algorithm that I am still trying to quantify.  You may need to go into each view after transition from BCM and revert schededuled start/finish to the old start/finish, and baseline estimated start/finish back to the old baseline start/finish.

    Good luck, you are going to need it!

    Chris

    Tuesday, July 15, 2014 11:12 AM

All replies

  • We had a Server that made the jump earlier this year from v2007 to v2010.  We used BCM as an intermediate step while we waited for some of the users to get 2010 clients.  What a disaster!  We had all sorts of unforseen problems.  I was soooooo glad the day we turned off BCM.  Most of our corruption issues were with SharePoint Deliverables and links to those deliverables.  It took a number of weeks of my life to resolve the corruption in that area.  I can share with you some tips if you seeing problems with SharePoint links.

    Make sure that you have all your users on SP2.  We encountered many problems with some users not on a SP2 baseline.  One of the bigger problems were tasks not always staying at 100% and it seemed to be isolated to the users on SP1 clients.

    Friday, July 11, 2014 12:20 PM
  • Thanks Chris, any tips appreciated

    Mike


    XRXSA

    Monday, July 14, 2014 7:11 PM
  • Hi Mike -

    The only logical reason for using BCM is that you still have some users that have not yet converted to v2010 clients.  We were hoping to be in BCM only a few weeks, it turned out to be a few months.  The mix of 2007 and 2010 starts to create problems.  The people that know 2007 features rebel at the 2010 features and pine for their 2007 client to return.  Because you are forcing the 2010 client to function without all of the 2010 features all kinds of errors start to occur for which this forum or documentation does not have all the answers.  You are going to get very good at explaining to people the concept of "Save for Sharing".

    A big hit for us was that when you transition from 2007 to 2010 the Format/Bar Styles will add at the bottom of each and every view all of the preferred Microsoft symbols for things like manual tasks, inactive tasks, duration only, etc.  All of that stuff is disabled while you are in BCM because 2010 features are not yet enabled, but it is in the Format Bar Styles for each and every view.  The day you turn off BCM all of that stuff suddenly becomes enabled; we had lots and lots and lots of complaints that suddenly symbols were disappearing --- this was because the Microsoft-inserted symbols and fields for 2010 started to become dominant that were before in hiding.  The other thing you will notice is that in all of your views start will be substituted with scheduled start, finish with scheduled finish, baseline estimated start for baseline start, and baseline estimated finish for baseline finish.  This is because start/finish/BL start/BL finish can now handle free text and nulls.  The new fields, Scheduled Start, etc., are date-only and use an algorithm that I am still trying to quantify.  You may need to go into each view after transition from BCM and revert schededuled start/finish to the old start/finish, and baseline estimated start/finish back to the old baseline start/finish.

    Good luck, you are going to need it!

    Chris

    Tuesday, July 15, 2014 11:12 AM
  • Mike - one more thing... make sure that you are on SP2 --- SP1 is very buggy.

    Chris

    Tuesday, July 15, 2014 11:13 AM
  • Really appreciate the input, thanks Chris

    XRXSA

    Tuesday, July 15, 2014 12:52 PM