// COMPANY NAME
// US
// Serial number: ########
// Licensed for Release(s): INCR
// License issued for :- Primavera
// License File Type :- Incremental License
// Database Vendor :- NONE
// Licensed Issued to :- Customer
// Project Management NU(0), CU(1)
// Portfolio Analysis NU(0), CU(1)
// Timesheets NU(0), CU(0)
// myPrimavera Portfolios NU(0), CU(0)
// myPrimavera Projects NU(0), CU(0)
// myPrimavera Resources NU(0), CU(0)
// Methodology Management NU(1), CU(0)
// Contractor NU(0), CU(0)
// ContractorMaxDomains(0), MaxTasksPerDomain(0)
// Integration API NU(0), CU(0)

Note: To load the incremental license file the product license file must be loaded first. The following procedure is the same for either type file.

After the product license has been loaded, incremental licenses are loaded to bump up the license counts accordingly. 

1. Go to Start, Programs, Primavera, Help and Utilities, DBConfig. 

2. Click Next to get started, then choose Administrative tasks.  Click Next.

3. Choose Configure Database license and click Next. 

4. Select which database connection to use. 

5. Accept the default administrative username and password of privuser (unless you have changed the default settings). 

6. Select the “OPEN” button. Browse to the location of the file, highlight the file and click the “Open” button. 

7. After receiving the license summary, choose Finish.

After you are done with the procedure, please check the license summary within the client application and confirm that the incremental quantities were added to the original license file quantities (Open the application and select Help, About Primavera and review the Contact tab or System tab). If there are any problems, please contact Primavera Support.

NOTE:  Using a create script, only creates the database tables and structure.  The application data must be loaded into the tables separately.  This can only be done using the configasst.exe utility.

For InterBase users: replace the pmdb.gdb with the sample PMDB.gdb file from the ‘Documentation’ CD.

For MS SQL, MSDE, or Oracle database users follow the procedure listed below.

Use Configasst.exe to load application data into the new database.  This utility is found on the main installation CD in the Database/Install folder.

NOTE:  Loading application data will overwrite any existing application data in the database.

1.  Choose to Create a new Primavera Database

2.  Select Database Type. 

NOTE:  On this screen you can also choose to install sample data.  If you do not want sample data, uncheck the “Include sample project data” option.

3.  Select the Application Database

4.  Select ”Load application data only”. 

NOTE:  On this screen you can also load the license into the database in the same step.  If you choose not to load the licence at this time you will need to run the dbConfig wizard at a later stage to load the licence. It is recommended to load the licence at this stage.

5.  Log on as Privileged User.  Enter your privileged database login username and password.  Enter the Oracle connect string for Oracle instance.

6.  Follow through the rest of the wizard.

Note:  Already registered from the same machine.

When launching Schedule Analyzer from within Project Management, you may received one of the following errors:

1.  

     The application and database versions do not match.

2.  ERROR MESSAGE:  Could not find the main class.  Program will exit

3.  

An application event has been intercepted. Please note the event code for reference Event Code FF90A8FE

Clicking on the More button reveals the following information:

Once this is installed open the registry by running REGEDIT from Start | RUN

Scroll down to Hkey_Current_User\Software\Primavera\Shared\External Applications\Schedule Analyzer and modify the Application key in the right window to point to the new javaw.exe file. By default this should read C:\Program Files\Java\j2re1.4.2_01\bin\javaw.exe

Please contact your Sales Representative to correct this problem.

NU(x) means that there are x named users available.

CU(y) means that there are y  concurrent user licenses.

For example, using pubuser or privuser to login to the SDK will cause this error.

1.    First, install LDAP as described in the Administrator’s Guide. This will allow you to import the names and passwords into the Project Manager database.
2.    Run the LDAPCfgWiz.exe again and switch the mode back to “NATIVE”.
3.    Login to Project Manager and pick one of the newly imported users and assign the user access to Project Manager / Management by selecting Admin, Users   
      
       Note: Select named or Concurrent as appropriate for your license agreement.

Overview

The Microsoft Project Plugin allows users to use Microsoft Project (MSP) as their daily tool to status projectsand at the same time allow the data to appear in project manager.It also allows them to use the resource pool from project manager.Project Manager users can see but not make changes to projects managed in MSP.

For installation instructions, please see:

Solution PRIM20373:  How to install Project Link

Details:

The project toolbar will be added to MSP and contains options to Open from Primavera, Save to Primavera and Access Resources from primavera.Users will also be able to logout and set some options.Here is a screen shot of the new toolbar.

When first accessing the Enterprise database the user will be prompted to login to Project Manager:

When selecting Open from Primavera users will see only MSP managed projects they have access to.

When saving to primavera, if the project is new,the user will choose an EPS to save the project under.A template can be selected containing the import options the user wishes to use.We will not honor the Activity/Task ID settings, schedule after import, export notebooks. When saving an existing project, the EPS node will be grayed out.

Restrictions:

Projects must be saved locally in MPP format before sending to primavera, and if the project is open in PM, we cannot save the project.The user must have rights to import global data and must have rights to the EPS Node the project is under.Only one user can check-in/check-out a project at a time.Most items will be read only in Project Manager.  WPs/Docs and Codes are the only items that can be changed in Project Manager.

Project Management

A new flag visible in the projects view displays whether a project is PM managed or MSP managed.You can change from MSP to PM managed but can never go back.For MSP managed projects the MPP file is stored as blob in DB.It uses the work location (where the project was saved to locally), the Project ID and the Project GUID to match projects when saving changes.

When checking out a project, the user and date are stored.When saving MSP managed projects we will use the MSP task ids as the Activity ID in Project Manager so that we can match the following activity level items: Global Activity codes, activity WPs & Docs, Project Codes, and Project WPS and Docs.These assignments will not be removed during the save.WBS will be matched on WBS Code and Parent WBS

Security

Privileges needed to access MSP Managed project in PM:

Global:Edit Global Activity Codes, Edit Project and Resource Codes

Project:Edit project details except financials, edit project work products and docs, edit project WBS except financials, add/edit project activities except relationships, edit project activity codes, edit EPS except financials (to edit WP and Docs at WBS level)

Privileges needed to import/ check in MSP managed project via the plug-in:

Global:Import Global Information

Project:Create project within EPS, Checkin/Checkout project

Privileges needed to open an MSP managed project via the plug-in:

Global and project: View Only

Privileges needed to add Resources via the plug-in: Global:Edit Resources

Version 4.1:
To use Project Link, there must be a Team Member license assigned in Admin/Users/Licensing tab within Project Manager (as shown below).

To find out if there is a license for Team Member, go to Help/About/System in Project Manager and scroll down to the “License” section.  You must have a “Timesheet Entry” license.  This will enable you to select “Team Member” in the Licensing tab within Project Manager. 

Ex:  Timesheet Entry NU(10), CU(0), No Expiration Date

If there is not a license for Team Member (Timesheet Entry) the following error will be displayed:  “Team Member – Total Named Uses exceed Licensed maximum users.”

The only use of the Primavera SDK with Contractor is for integration with Expedition 8.5.  For more information on this, see:

Solution ID: 2001718164510 ”How to link a Project Manager schedule to an version 8.5 Expedition project and import Expedition activities into a Project Manager project.”

DISCLAIMER: Users who implement the SDK with the Contractor database do so at their own risk. Oracle|Primavera Systems Inc. will not be  responsible for any problems or data loss resulting from the use of the SDK with Contractor.  Additionally, most license agreements prohibit the direct modification of Data in the database, and as such, direct modification may void your  warrantee.

1. Select: Start, Programs, Primavera, Netset and enter the appropriate password (default is “netset”).


2. From within Netset select: Options, Current users, which will produce the screen below:
    

This displays the list of users who are currently using a P3 serial number.  If you think a user is listed in error, contact one of the listed users to clarify whether that user is still actively using the application, or whether they simply have it open without using it.

Assign a ’Named User’ License in Project Manager

” Licensed named users is less than configured Named users.  Please use the Users dialog under the Admin menu in to correct the problem.  Please see the readme.txt for more information. “

When trying to close the Users screen, the following message is displayed:

” Project Manager / Project Management - Total Named Users exceeds Licensed maximum users! “

Message: ‘Total named users exceed licensed named users’ 

prim57375 ”Error ’Total Named Users exceeds Licensed maximum users’ on clicking close in the Admin, Users dialogue.” 

Oracle license files (temporary and permanent) now contain unlimited licensing which will resolve most of the root causes of receiving this error message.
To obtain an Oracle Primavera unlimited temporary licnese or pemanent license, please see  http://licensecodes.oracle.com         Customers are still bound by their purchase agreement to use only the number of licenses purchased under contract.

For futher information on different causes and solutions for this error message see the fix statements below.

Cause 1:

When installing P6 and selecting to include sample data, the sample data installer creates 3 sample users (Bruce, Jeff and Chuck) which are assigned Named User licensing for Project Management, Team Member, myPrimavera Projects, myPrimavera Portfolios and myPrimavera Portfolios.  If a license is applied to the database that doesn’t have sufficient Names Users to account for the Sample Users this error will appear when logging in or when going to the  Admin > Users window since the 3 sample users have Named licenses applied by default.

Fix 1:  (See License Note above)

To remove licenses from these default users:

• Go to the users menu via Admin, Users.


• Highlight one of the users (Bruce, Chuck, or Jeff) and click on the licensing tab.


• Remove all checkboxes for each of these users.

Cause 2:

The license has concurrent licensing for Project Management and the Admin login has a check mark in the Named User column.

Fix 2:  (See License Note above)

Go to Admin > Users window and place a check mark in the Concurrent User column and remove the one in the Named User column.

This message is displayed when the number of  assigned ‘Named User’ licenses contained within the Application license has been exceeded.

To find out the total number of ‘Named User’ licenses availabe in the Application license for Project Manager, go to ‘Help, About Project Manager’.
On the ’Contact’ Tab, look for the line that begins ‘Project Manager’. The Total number of ‘Named User’ licenses contained within the Application license is shown in the ‘NU(n)’ parenthesis.

In the example below, there are 20 named users.

Compare this number to the number of named users assigned access to Project Manager under Admin, Users, Licensing tab.

Fix 3:  (See License Note above)

1. Open Project Management / Methodology Management and choose Admin, Users.

2. Click on the Licensing tab.

3. Highlight each name at the top, and uncheck any unnecessary named user licenses. 

 

4. Choose Close.

Run through the above steps until you no longer receive the message.  If all extra licenses are not unassigned from users, the logged in user will get stuck in Users dialog box until the PM session is ended using Task Manager.

To determine the number of Named licenses available in your database, follow the steps below:

1. Go to Help, About Project Manager / Primavera.

2. Click on the System tab.

3. Scroll down and view the License section (specifically where “NU” (X)) to determine how many named user licenses you have.

For example, if you have 4 Named User licenses for Project Management, there should only be 4 users identified in the Users dialog.

NOTE: If you require more named user licenses, additional licensing  may be purchased by contacting your Primavera sales representative.

Cause 4:

An older version of DBConfig.exe was used to apply the license.

Fix 4:

Make sure the DBConfig.exe being used to apply the license matches with your current version of Primavera.
For example: Do not use a DBConfig.exe from 4.1 to apply a license to a 5.0 database.

Cause 5:

A new license, that has been loaded into the database, has fewer licenses than were previously assigned.  As a result, the users in the database have licenses assigned that are no longer available.

Fix 5: (See License Note above)

a) Remove the excessive licensing assigned to users via Admin, Users.  If this does not work, then reload the previous license  file (see solution prim18011 ) if possible.  Next, go to Admin, Users and remove the extra licenses from the users.  Load the new license back into the database.

or

b)  If fix step ”a” does not work, it may be necessary to remove the extra licensing via the backend in the database:

Run the following queries on the backend of the database

Note: Backup the database before running any queries.

Delete the assigned licenses from the USERENG table pertaining to the license(s) that you want to remove.  Now the licenses should be removed from the users.  Go back into Project Manager / Project Management and assign the right licenses to users.

SQL users: Log into Query Analyzer as privuser

Oracle users: Log into SQL + as admuser

InterBase users: Log into ISQL as sysdba


1. Query the USERENG table for all the licenses in use:

select * from usereng

2. Determine which licenses you want to remove based on your available licenses (Help, About Project Manager / Primavera , System tab has license information ).  Depending on which licenses you want to remove run the following queries:

Note: If you want to do this only for certain users, then find out what the user’s user_id is from the USERS table and add that to the where clause:
         select user_id from users where user_name = ‘user name’

         delete from usereng where db_engine_type = ‘ ‘  OR
         delete from usereng where db_engine_type = ‘ ‘ and user_id = ‘user_id from above query’

Possible values for “db_engine_type” include the following:

PM             Project Manager

PA             Portfolio Analyst
 
TS             Progress Reporter / TeamPlayer / Timesheets ( 4.1 )
 
WU            Primavision Portfolios / myPrimavera Portfolios

WEB_PM    Primavision Projects / myPrimavera Projects
 
WEB_RM    Primavision Resources / myPrimavera Resources

INT_API     Integration API

Note:  Make sure not to remove the row that pertains to the admin superuser PM priviledge.  If you do, you could get locked out of the database.  If that happens, refer to solution prim9123

NOTE: The resource must be linked to a User account which has been assigned a license to use Timesheets.

1. 
   Launch Primavera Contractor


2. 
   Click on Help – Registration to be presented with this screen.


3. Click on REGISTRATION FILE
   
   
    


4. When you are prompted for the license file, you MUST click on the down arrow for Files of type:, and choose License Files (*.ldf). 


5. Browse to your license file, and click “Open”
   
   

For Contractor 5.0

1.Detach the license file sent via e-mail, remembering the location that the file was saved to.

2.  Start Primavera Contractor.

3.Once the registration dialog appears, click on the License File button at the bottom of the dialog.

Note:You can also access the registration dialog by using the Help, Registration menu option in Primavera Contractor.

4.An Open dialog will ask you to locate the license file on your machine (same file and location as step 1).

5.Click on the license file, hit the Open button.

This attachment has been moved or deleted.  Do you want to delete this row?

The attachment displays the ‘Cannot open attachment’ icon:

• The attached document has been moved or deleted.
   


• The path to the attached document indicates a directory location to which the Contract Management Web/Application server does not have access.
   


• The Contract Management service does not have the required Domain User Account login established in the service properties.
   


• The attachment location directory must consist of UNC mapping if the directory resides on a network share and not directly on the Contract Management Web/Application server machine.

The Path indicates where the file existed at the time it was attached.  Verify that the path is accessible from the Contract Management Web/Application server and that the file exists in this location.

For example, in the screen shot below, the license.txt file would need to exist in D:\My Documents\ on the Contract Management  Web/Application server machine to be accessed.