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

Event Code: TRPCS-2887-6

The RPC server is unavailable

Choosing ‘Ignore’, then selecting to import/export Microsoft Project file, the import/export process will hang, then return the following error:

Event Code: AVAA0-0143-C

Access violation at address 00ADFD75 in module ‘PM.exe’. Read of address 00000004

The screen shot below shows that in some situations the Expense is not ‘spread’ at the same time as the milestone is scheduled:

This situation occurs when the milestone is scheduled at the beginning or end of work time.

In the screen shot above, the milestone is scheduled at the end of work time - e.g. 5 pm.
The Expense is spread at 8 am the following morning.

This known problem in Project Management has been corrected in version 5.0.

Note: Any user specific layouts, filters, etc. will not be available for the new user. Do not delete the original user until all items have been either recreated, copied or imported.

Another variation of the error encountered is AVAA0-3688-4

Steps to duplicate the problem:

1. Display the Resource Usage Profile.
2. In the Display menu of the right side of the profile, uncheck Show All Projects.
3. On the left side of the profile, select a resource and check the Time Period box.
4. Click on a time period on the profile, then click the Assign Resources by Role button to the right of the Gantt chart.

The above error will occur.

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.”

Whenever a user, without administrator rights, logs into a Windows PC and tries to access the application, the user can run into any combination of the following error messages:

The file C:\Program Files\Primavera\Project Management\PM.ini cannot be set to read-write status.

AVAA0-1004-5 Access violation at address 004a2940 in module PM.exe

Event Code UTWTF-2224-4

The instruction at 0x004a2b05 referenced memory at 0×000. The memory could not be read.

These errors are a result of the user not having access rights to the proper directories and registry keys.

Fix:

Have an administrator log into the PC and give the user Read and Write access to the Borland directory, the \Program Files\Primavera directory, the Java bootstrap file (C:\Program Files\Common Files\Primavera Common\Java\BREBootStrap.xml) and the user’s Temp directory.  Additionally, the administrator has to go into REGEDT32 and give the user full permissions to the Borland registry key and the Primavera registry key found in HKEY_LOCAL_MACHINE/SOFTWARE. Note the machine must be restarted after making these changes. When running Primavera as a Published Web Application – grant the group “Anonymous’ the permissions above.

To grant Primavera users the required permissions,  refer to the options below:

Option 1

Add user accounts to the Local Administrator group (must be logged in as an Administrator).

1. Go to Start, Settings, Control Panel.
2. Click on the Users and Passwords icon.
3. Highlight the user and click on ‘Properties’
Notice that there may be two User Names’ that are the same. One may be a local account specific to the PC and the other is a domain account. The account that is going to be used daily, typically the domain account, is the one that you want to be part of the Power Users or Administrators Group.
4. On the Group Membership window, click on ‘Other’ and choose Administrator.

Option 2

Add user account to the Power Users group.
Follow the same steps as Option 1, except in step 4 click on ‘Standard user’ on the Group Membership window.

Option 3

Give user Full Control of Borland key and the Primavera key in registry.
NOTE: Always Backup the registry prior to making changes.

1. Logged in as an administrator, select Start, Run and type in REGEDT32
2. Highlight the HKEY_LOCAL_MACHINE\Software\Borland key and the KEY_LOCAL_MACHINE\Software\Primavera
3. Click on the Security menu and choose Permissions.
4. Highlight the user account and check the Allow box for Read and Full Control. If the user account is not displayed in the Name window, click the Add button to get a full list of local user accounts and domain accounts that can be added to the Name window. Once this is complete click OK.

Note: Allowing the Everyone group Read and Full Control to the Borland key and the Primavera key will give all users the proper access.

The final step for all options is to log off the PC with the administrator account and log back in with the user account.

1. go to http://<servername>:7001/console and login. 


2. Then look for Services on the left side, click on it and look for JDBC. 


3. Click on JDBC and look for Connection Pools. 


4. Click on Connection Pools and on the right side you will see 3 connection pool names: datamartTargetPool, eadbPool, and evolveCoreTargetPool. 


5. Under the URL column, check to see if the database names are correct.  If not, you will need to correct the name by clicking on the name of the connection pool and updating the URL field.  Then click on Apply at the bottom.
    

NOTE: for WorkSiteMP database restore, please refer to prim19365, “Restoring the ‘primavera’ WorkSiteMP knowledge collaboration database in Primavera”

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

Executable:    PM.exe
Application:   Project Manager
Event Code:    CNS-2377-A
Message:  Capability not supported.

Context:
  1: TfrmMain.actToolsApplyActualsExecute
  2: TfrmMain.actAdminCategoriesExecute
  3: TfrmAdminPreferences.FormCreate
  4: TfrmMain.actAdminPreferencesExecute
  5: TfrmAdminPreferences.FormCreate
  6: TfrmMain.actAdminPreferencesExecute
  7:
  8:
  9:
  10:

Detail:
  Type:  EDBEngineError
  Object Type: TCUltraButton

Database Error:
1:Capability not supported.
   Category:          48
   Error Code:        12289
   Sub Error Code :1
   Server Error Code: 0

The recommended approach is to create an export from the 8i database, create a new 9i instance and import the 8i export file into the new 9i instance.

Please note:  These steps should be performed by an Oracle DBA.

Receive the following error connecting to the SDK:

Run-time error ‘-2147467259(80004005)’:

[ATI][OpenRDA ODBC] RDA error: Resource not available ?Connect error

da=PMSDK;Driver=PrimaveraSDK;engine=PM;lf=C:\temp\PMSDK.LOG;lo=terse;pg=1;pp=pubuser;pu=pubuser;.

VDB.Connect; hResult=0×80040003 (PMSDK_E_INTERNALERR: internal driver error); EOleSysError=Invalid return value from CreateAppVDB

Note:  You cannot have a connection to both Project Management and the SDK open at the same time from the same client.

There are 4 different types of summary data that are created and stored in the PM database.

Project/WBS level summary- data contains information about the project and WBS levels (Earned Value, Performance type of information).
EPS level summary- data contains information about the EPS levels (Earned Value, Performance type of information).
Resource/Role per project summary- data contains resource usage information per resource/project combination.
Enterprise Resource/Role summary- data contains one record which reflects the resources usage across all projects in the database.

NOTE: All registry keys in this article are DWORD keys and are located in HKEY_LOCAL_MACHINE\SOFTWARE\Primavera

Where is the data stored?

Project/WBS level and EPS level summary data is stored in the TASKSUM table.
Resource per project and Enterprise resource summary data is stored in the TRSRCSUM table.

Summarizing through Project Management, Job Services or myPrimavera will always create summary data for the Project/WBS levels. To update/create summary data for the other types of summary data, certain conditions must exist.

Summarizing through Project Management client:

1. In Project Manager, go to Tools, Summarize, then choose Open Projects, All Projects, or Summary Only Projects.

2. In the Projects View, right click on a project or EPS node, then choose Summarize Project.

Project/WBS level summary
no special condition must exist

EPS level summary
EnterpriseSummaries=1 must exist in the registry (by default the setting does not exist)

Resource/Role per project summary
ResourceSummaries=1 in the registry or DOES NOT exist in registry (by default the setting does not exist)

Enterprise Resource/Role summary
All of the following conditions must be met:
User is AdminSuperuser
EnterpriseSummaries=1 must exist
ResourceSummaries=1 in the registry or DOES NOT exist in registry

Summarizing through creating a Job Service summary job in the PM client:

Project/WBS level summary
no special condition must exist

EPS level summary
no special condition must exist

Resource/Role per project summary
no special condition must exist

Enterprise Resource/Role summary
One of the following two conditions must be met:
User running the job must be AdminSuperuser
OR
The Job Service server must have the registry setting ForceSuperUserRecurringSummJob=1

Event Code: CVRJC-2214-A while importing a project in Project Management

*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          15-Jun-07 12:29 PM

Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    CVRJC-2214-A
Message:      
  TCCustomVirtualRow.getJoinedColItems: TASKACTV row
  has blank task_id

Context:
  1: TfrmWizImport.wizImportFinish
  2: TfrmWizImport.wizImportBeforeShowPage
  3: TfrmWizImport.RunImportWizard
  4: TfrmMain.actHomeExecute
  5: TfrmMain.actFileImportExecute
  6: TCFormManager.SetToolbar
  7: TfrmLogin.FormCreate
  8:
  9:
  10:

1. Download / Launch the xerFileParser&Builder.xls utility.
    
   SEE: Solution ID: prim4145 - ”How to use the XER Parser utility”
    


2. Click: Load XER file… (button on the ‘General’ tab)
   Browse to the file in question.
    


3. Once the XER is loaded, click: Diagnostics… (button on the ‘General’ tab)
    


4. Set the ‘xer File Parser & Builder’ dialog box to contain the following criteria:
    

• Select Diagnostics: ‘cross check FK’


• Select Table: ‘TASK’


• Select Field(s): ’TASK_ID’


• Select Secondary Table: ’TASKACTV’


• Select Secondary Field(s): ’TASK_ID’
   
  The screen should look like this:
   
  
   

Once complete, the ‘Diagnostic’ tab will list instances where ’TASK_ID’ values appear in the TASKACTV table, but not in the corresponding parent record (TASK table).
 

 

If the above fix does not work or you receive errors when performing the diagnostic, the steps below describe how to perform the diagnostic actions manually:

The orphaned records need to be removed.  The orphaned records are often associated with the same tasks orphaned in the UDFVALUE table. If you went through solution prim16871 already, please keep that orphaned task list and skip to step 6 below.

1. Use the xerFileParser&Builder.xls to repair the XER file.  More information can be found in solution prim4145: How to use the XER Parser utility.

Once the XER is open, Click on TASK.

2. Then highlight the task_id field.

Then copy and paste this column into a new Excel spread sheet.

3. Then go to the General tab and click on the TASKACTV table.

Click and highlight the task_id column.

Copy this column into the second column of the new Excel spread sheet that already has the TASK task_id column.

4. Then type the following formula into the second row of the third column. 

=VLOOKUP(B2,$A$2:$A$#,1,0)  Where B is the TASKACTV task_id column, A is the TASK task_id column and # is the row number of the last TASK task_id item for column A. 

Then double-click on the bottom right corner of that cell so that it automatically places the formula in the rest of the cells below.

5. Go to Data, Filter, and choose AutoFilter.  This will give you a drop down menu to choose a group of rows.  Look for all of the rows that have #N/A (may have to filter for a custom value).  These are the orphaned records. 

6. Now, delete the rows with matching task_id values on the TASKACTV  tab in the xerFileParser&Builder.xls. 

Finally, on the general tab, click the Build XER button.

Choose a new name for the “fixed” XER file.

Re-import the file.

Full Exception report:

*****************************************************
* EXCEPTION REPORT *
*****************************************************
Date: 04-Feb-05

Executable: PM.exe
Application: Primavera Project Management
Event Code: FVRVE-1992-6
Message:
Field value required.
validation error for column COST_LOAD_TYPE, value “***
null ***”
Context:
1: TfrmMain.actFileOpenExecute
2: TfrmMain.actProjectsExecute
3: TfrmMain.actFileImportExecute
4: TCFormManager.SetToolbar
5: TfrmLogin.FormCreate
6:
7:
8:
9:
10:

Detail:
Type: EDBEngineError
Object Type: TCVirtualQueryGrid
Database Error:
1: Field value required.
Category: 38
Error Code: 9732
Sub Error Code : 4
Server Error Code: 0

2: validation error for column COST_LOAD_TYPE, value “*** null ***”
Category: 51
Error Code: 13059
Sub Error Code : 3
Server Error Code: -625

The ‘COST_LOAD_TYPE’ field in Primavera Project Manager / Project Management is equivalent to MS Projects’ ‘Fixed Cost Accrual’ field.  This determines how the cost is spread over the activity. Valid values are ‘Start’, ‘Prorated’ and ‘End’ which are equivalent to Primavera’s ‘Accrual Type’ values of: ‘Start of Activity’, ‘Uniform over Activity’ and ‘Finish of Activity’.

Project Manager / Project Management is attempting to import the ‘Fixed Accrual Type’ as a blank row – which is not permitted.

To rectify the issue:

1. Delete the ‘blank rows’ from within the MSP schedule as shown below:
   


2.  Re-save the MSP project file.


3.  Re-import the MPP file into project Manager / Project Management.

Linking a PM schedule to an Expedition project:

• Open Expedition and highlight the project to link to PM.  Go to Define, Project Preferences.


• Click on the schedule tab and choose PM if using Expedition 8.x.


• Click in Database and select PRIMAVERASDK. This is the default alias for the SDK install. Choose the alias you created during the PM SDK install.


• Click in Project. You will be prompted for the Logon for Primavera Data Provider. Enter the PM username and password.


• Choose the PM project that you want to link to the Expedition project.

Expedition 8.x:

Exit Project Preferences by clicking on OK.

Open PM and open the project you want to link to your Expedition project.  Choose Enterprise, External Applications.

Add a new application for your PM project.  Select Expedition from the menu in the Application Name field and enter the path to the EXPWIN.EXE executable in the Application Executable field on the General tab.

Select the Login tab.  Enter your Expedition User ID in the Login Name field and your Expedition Password into the Password field. The Login Name and Password is the same one you use to log into Expedition. Our default username is used for this example: EXP for the Login Name and exp for the Password.

Select the Data tab, enter the Expedition project abbreviation for the External Project name (In this case, we used the DEMO project). For the External Database Path or Database Alias, use the Expedition group name if you are connected locally (for example: EXPWIN). If you are connected to a server, use the servername.groupname (for example: EXPSRVR.EXPWIN)

Note: To find the server and group name, look at the title bar in Expedition.
As you see below Expedition — [EXPWIN:…..
EXPWIN is the group in this case where we are setup as a standalone system. If you were connected to a server, then after the bracket, this would be Servername.Groupname (for example: Expedition – [EXPSRVR.EXPWIN:……………. )

Click Close on the right side of the external applications window when completed filling in all the appropriate fields.

Select File, Import From Expedition and select the items you wish to import and choose Import.

When prompted, select Commit Changes. Your Expedition activities should now appear.

Open the activities screen. At the bottom, right click on the General Tab and select Customize Activity Details.

Double-click on Expedition Docs in the Available Tabs section. This will add it to the Display Tabs column. Click OK to close the windows.

This will add a new tab called Expedition Docs to your Activity Details Window.

Click Refresh on the bottom of the activity details to bring in any Expedition documents that have been linked to this activity. The view button will launch the default Expedition form for the document that is highlighted.

Select File, Open. Click on the project name to highlight it. On the bottom of the window, click on the checkbox to ‘Retrieve Expedition Documents’ and choose Open.

NOTE:  Import only works with numeric activity IDs that are left justified. If you have any numeric activity IDs that are showing as centered, select the activity as if to edit it so they left justify automatically.

Workaround:

Enter a valid Planned Start and Finish on activities.