4 Replies Latest reply: Jan 28, 2009 11:14 AM by 690399 RSS

    P5 / P6

    690399
      Did you have any problem migrating from p5 to P6?
        • 1. P5 / P6
          690399
          Well, here's what we found (10 concurrent users, 100
          web users new in P6 installation)
          <br
          />The changes in the Project Manager client are
          small enough that users can continue their jobs
          without additional training.
          <br
          />The database upgraded very smoothly on both SQL
          2000 and SQL 2005 with a couple of caveats: SQL 2005
          must be in SQL 2000 compatibility mode (so much for
          2005 "compatibility"), and ARITH_ABORT must be set to
          true for the upgrade to complete.
          <br
          />Most of the extra features (like reflection
          projects) can be phased in over time.<br
          />
          There is STILL no documented way to
          preset Project Workspace views or change the default
          settings in the web app, although there are ways
          around this if you're a brave soul with some DB
          experience.

          EVERYTHING in the
          old version except the database must be completely
          uninstalled and reinstalled: Job Services, Timesheets,
          web application, Project Manager and Methodology
          Manager clients (if you're doing an unattended
          installtion), and probably your web server app if it's
          been upgraded. Primavera needs to do some SERIOUS work
          on their installation routines.
          <br
          />Database connections on clients, even if the
          password has not changed, have to be rebuilt from
          scratch in the P6 installer or configuration wizard.
          This is not an issue if you only have one connection
          name, but if you have test db connections, sample db
          connections, multiple db connection names, or multiple
          databases as many installations do, this is a
          problem.

          P6 cannot upgrade P5
          in an unattended installation (although it can if you
          run it manually). P5 must be fully uninstalled first,
          which includes manually removing some files and
          folders because the uninstaller doesn't work well. The
          P5 uninstaller also doesn't remove old db connections,
          so if you have some named inconsistently, just adding
          the P6 ones will confuse your users.
          <br
          />In some cases, previous versions of P5 didn't
          upgrade correctly to SP4, leaving SP2 fragments in the
          registry. This cause the uninstall scripts to fail on
          some machines.

          P6.1 Timesheets
          now requires the web app server for approvals even if
          you use the full client. This little tidbit is not
          very well advertised by Primavera and could complicate
          upgrades in shops with no web server.<br
          />
          These are the main things we found
          here.... It sounds like a lot, but it can all be dealt
          with. In general, I think the bug fixes and feature
          additions, particularly in the web app, are well worth
          the upgrade. However, you do want to skip 6 and go to
          6.1 if you can (keeping in mind the Timesheets web
          server requirement above) as it also contains a number
          of significant bug fixes and feature additions.<br
          />
          Hope this helps!
          • 2. P5 / P6
            690399
            Hello every body I'm preparing for testing Primavera
            P6 but don't know what kind of test scripts I have to
            carry out before testing areas such as Reports, Basic
            Planning, Timesheet,Aministration.
            Can some
            of you help me?

            regards Kurt
            • 3. P5 / P6
              690399
              "Database connections on clients, even if the password
              has not changed, have to be rebuilt from scratch in
              the P6 installer or configuration wizard. This is not
              an issue if you only have one connection name, but if
              you have test db connections, sample db connections,
              multiple db connection names, or multiple databases as
              many installations do, this is a problem."<br
              />
              I disagree with the above statement.
              If you leave the below file and registry entries in
              tact when you uninstall P5, your existing alias
              connections should still work after the P6
              upgrade.

              C:\Program
              Files\Common Files\Borland
              Shared\DBExpress\DBXConnections.ini<br
              />HKEY_LOCAL_MACHINE\SOFTWARE\Primavera\Databases\PM\Aliases<br
              />HKEY_CURRENT_USER\Software\Primavera\Databases\PM\CurrentAlias
              • 4. P5 / P6
                690399
                Kurt,

                What kind of testing you
                run is dependent on how your organization utilizes the
                software. Prior to our recent upgrade to P61 SP1 (from
                P5 various client SPs) we ran through some standard
                tests in the application. My company does not
                currently utilize Timesheets or the Webapp so
                everything we tested was specific to the client.<br
                />
                Below is an excerpt from out Test
                Plan documentation:

                Items:
                Verify the following features are functional and
                available:<br
                />1.     Login
                and out successfully<br
                />2.     Schedule
                (F9)<br
                />3.     Add
                an activity<br
                />4.     Delete
                an activity<br
                />5.     Views
                are available: Reports, Resources, Projects<br
                />6.     Add
                an activity code<br
                />7.     Delete
                an activity code<br
                />8.     Export
                a project<br
                />9.     Import
                a project<br
                />10.     Delete
                a project<br
                />11.     Copy/Paste
                schedules (single and integrated)<br
                />12.     Copy/Paste
                an activity<br
                />13.     Refresh
                (F5)
                Steps:
                •Steps for the above
                features are located in the respective Primavera
                Project Management Reference Manual.
                <br
                />Expected Results: All above listed features
                function properly within the application.<br
                />
                Regards,
                Dave Cruz