none
playbook restore error RRS feed

  • Question

  • Hi

    We have upgraded 2007 databases to 2010

    Note: these were prior 2003 databases that have been in production 2007 for years

    Now we have a DEV and a QA  2010 environment each from the original production 2007 databases – each upgraded in the exact same fashion, each with the same exact build out of SW/etc…

    We make modifications to PWA configuration in DEV and need to push that into QA to validate…

    We use Playbooks or even Solution Starter DM Import / Export or the new FluentBooks…

    We can extract all the new (and even existing) PWA configuration just fine out of DEV.

    However, when we try to write the changes into QA – all the updates (well, nearly all) fail!

    In particular – it seems that we cannot write any look up tables, hence most all else fails.

    I have tried to extract ONLY the look up tables and they will not import.

    PSI give an error – like an unhandled exception – but no meaningful debug information.

    Thanks in advance

    Cheers

    Michael Damaschke


    Kind regards Michael Damaschke

    Friday, August 31, 2012 9:08 PM

Answers

  • Hi Andrew

    Thanks. I was asking for some else in this forum.

    He resolved it in the way that he deleted a double entry of the same lookup table. (deleting the lookup table).

    He screwed it up by using different tools to do the same work ...

    Sorry and thanks for your help.

    Regards

    Michael 


    Kind regards Michael Damaschke

    • Marked as answer by ShareTHEpoint Friday, September 21, 2012 11:40 AM
    Friday, September 21, 2012 11:40 AM

All replies

  • I don't think the upgrade is related, as Playbooks shouldn't be impacted
    by that.  Are you using the 2010 version of Playbooks?  Running it on the
    server?
     
    Does it restore to a blank instance?
     
     

    Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky
    Saturday, September 1, 2012 6:23 PM
    Moderator
  • Hi Andrew

    Thanks. I was asking for some else in this forum.

    He resolved it in the way that he deleted a double entry of the same lookup table. (deleting the lookup table).

    He screwed it up by using different tools to do the same work ...

    Sorry and thanks for your help.

    Regards

    Michael 


    Kind regards Michael Damaschke

    • Marked as answer by ShareTHEpoint Friday, September 21, 2012 11:40 AM
    Friday, September 21, 2012 11:40 AM