Professional Documents
Culture Documents
0
Release Date: June 2007
==========================
CONTENTS
========
NEW FEATURES
INSTALLATION INFORMATION
KNOWN ISSUES IN P6
ISSUES RESOLVED IN THIS VERSION
CONTACTING PRIMAVERA SYSTEMS
NEW FEATURES
==============
For a complete list and description of new features, refer to the "What's New in
the Project
Management module" topic in the Project Management Help.
INSTALLATION INFORMATION
========================
If you previously installed the Beta version of Primavera 6.0, YOU MUST UNINSTAL
L THE
BETA VERSION BEFORE INSTALLING PRIMAVERA 6.0.
For complete installation instructions, refer to the updated Primavera Administr
ator's
Guide (adminguide.pdf) on the Documentation CD-ROM (CD3).
Also refer to the testedcfg.htm file in the \Documentation\Technical Documentati
on\Tested Configurations
folder on CD 3 for more information on supported system configurations.
KNOWN ISSUES IN P6
==================
- For stand-alone installations, you may receive the following message after log
ging
into the Project Management module: "Licensed named users is less than configu
red Named
users. Please use the User's dialog under the Admin menu in Project Management
to correct
the problem. Please see readme.txt for more information."
When you install the stand-alone version of the Project Management module, the
re are
one or more sample users installed with Named user licenses. Due to the sample
users,
there may be more licensed users than is allowed by your license.
STEPS TO RESOLVE THIS ISSUE:
1. In the Project Management module, choose Admin, Users.
2. Click the Licensing tab.
3. If your license specifies Concurrent users, select each sample user, then c
lear the
checkbox in the Named column. If desired, you can mark the checkbox in the
Concurrent
column for each sample user.
If your license specifies Named users, select each sample user, then clear
the
checkbox in the Named column. You do not have to remove all named sample us
er licenses,
but you must remove enough to meet the requirements of your license.
- When P6 Project Management connects to a SQL Server 2000 database, it automati
cally
sets the database transaction isolation level to READ UNCOMMITTED (dirty read
s)
to reduce concurrency issues. This is no longer necessary for SQL Server 200
5
but is still done automatically by the P6 Project Management module.
If you are connecting to a SQL Server 2005 database, you should set the Allow
DirtyReads
key in the Database section of the PM.ini file to False. Setting this key to
false
causes SQL Server 2005 connections to use the default setting for this databa
se,
which is READ COMMITTED SNAPSHOT.
STEPS TO RESOLVE THIS ISSUE:
Follow these steps to configure any client machines using the P6 Project Mana
gement
module to connect to a SQL Server 2005 database:
1. Using a text editor, open the PM.ini file located in the Primavera\Project
Management
installation directory.
2. If the [Database] section does not exist, add it to the bottom of the file
.
3. If the AllowDirtyReads key does not exist, add it to the [Database] sectio
n and set
it to FALSE. For example:
[Database]
AllowDirtyReads=FALSE
4. Save the file. If necessary, restart the P6 Project Management module.