Version 5.0:

1. Per the Administrator’s Guide, follow the steps in “Creating Unattended Setup Files” to create one alias for PMDB and/or MMDB database(s).
    


2. (OPTIONAL) From the same machine, configure additional aliases as necessary.
    


3. Log in to the primary (most common) database once, then log out.
    


4. Per the Administrator’s Guide, follow the steps in “Running an Unattended Setup“.
    


5. Export / push each of the applicable items, detailed in Solution ID prim48718 - ”Where does Primavera store alias connection information?”, to client machines.

The Unattended Install by default will only point to one PMDB and one MMDB database.  If you want to create an Unattended Install that points to multiple databases for PMDB and MMDB you will need to do the following:

1. Create an Unattended Install for one PMDB and MMDB database.
    


2. Do a client install and then create the other aliases that are required.
    


3. Copy the idapi32.cfg (located by default in the BDE folder), the PM.ini (located by default in the Project Manager folder), the MM.ini (located by default in the Methodology Manager folder), and the PA.ini (located by default in the Portfolio Analyst folder) into the Unattended Install folder.
    


4. Create a Batch file that will first run the auto_inst.exe and then copy the idapi32.cfg, pm.ini, mm.ini, and pa.ini saved in the Unattended Install folder to overwrite the files just installed by the user.

You can learn about batch files on the Microsoft website at http://support.microsoft.com/default.aspx?scid=kb;en-us;173529 and other sites as well.

When creating any type of calendar, the following error occurs:

 *****************************************************

* EXCEPTION REPORT *

*****************************************************

Date: 27-Oct-04

Executable: PM.exe

Application: Primavera Project Management

Event Code: VTFRN-0683-B

Message:

TCVirtualTable.FindRowNewIndex: Adding row

(CALENDAR – Calendar: 4078 – ZOU YANPING

.) conflicts with existing unique key: (XXXX).

Context:

1: TCArcturusAssignMgr.AssignAndAddNewRowToVDBE

2: TCArcturusAssignMgr.InsertClndrRow

3: TfrmBaseCalendar.cmdAddClick

4: TfrmMain.actConfigureCalendarsExecute

5: TfrmMain.actConfigureResourcesExecute

6: TfrmMain.actReportsReportsExecute

7: TfrmMain.actProjectsExecute

8:

9:

10:

Detail:

Type: Exception

Object Type: TCUltraButton

Components

==========

ORI: ORI Win32 #

ORI/DB: PMDB,0410.0001.0001.0002

IMG: IMG Win32 #1000

Run the following queries against the database:

select max(clndr_id) from calendar;

select key_seq_num from nextkey where key_name=’calendar_clndr_id’;

You will see that the first query returns a number that is higher than the second query. Run the following query to correct this.

NOTE: Replace XXXX to be a higher value than the first query returned.

update nextkey set key_seq_num=XXXX where key_name=’calendar_clndr_id’;

When attempting to remove one selection, the following error is received:

“One Default value is required”

To download the latest Service Pack, see:
Solution ID PRIM29780:  Primavera Project Management Version 4.1 Service Pack 4 (SP4)

It has been reported this issue is still happening in 4.1 SP3.  Also tested with 4.1 SP4 and it is still an issue.  Fixed in 5.0.  Version 5.0 will not allow the multiple default calendars.   

Note:  There are no additional 4.1 Service Packs scheduled at this time (11/2005).

Workaround:

Run the following queries against a BACKUP of the database before running on the production database.

For Oracle, launch SQLPlus and login to your PMDB database as ADMUSER .

For SQL, launch Query Analyzer and login to your server as PRIVUSER.  Make sure the PMDB database is selected.

select * from calendar where default_flag = ‘Y’;

(this should return 2 records (each default calendar), take note of the clndr_id for the one that should not be the default global calendar)

Option 1:  When the first option is selected,  resources which have a custom unit of measure in a user defined field and allow overtime will be converted to nonlabor resources with overtime allowed.  If this option is not selected, these resources will be converted to material resources and the overtime will be removed.

Option 2:  Selecting the second option lets you convert resources that use one of the custom units of measure shown (entered by the user) to a nonlabor resource instead of a material resource.

Option 3:  Selecting the third option lets users mark User Defined Field columns as “unused.”  Unused columns are treated as if they were dropped, even though their column data remains in the table’s rows.  This feature is useful when you want to remove the columns from regular access instead of dropping them, which will reduce the amount of time needed for the upgrade.  Selecting this option does not remove any data from the application.  The user defined fields have been moved to their own tables since they are now unlimited.  The setting only affects what happens to the columns in the database that are no longer needed because of the new tables.

Note:  Data affected by enabling the SET UNUSED option can be removed later, if desired.

Drop the table spaces and the user from the database instance, run the new edited  orpm_ins.sql script to re-create the schema

NOTE: Loading application data through ConfigAsst.exe will delete all existing data from the database.

1.  Go to File, Open and select a Project Management Chart and click open.

2.  In the database connect dialogue, select ‘Add ODBC’.

3.  Select the ‘Machine Data Source’ Tab, highlight the line item ‘Primavera SDK’ and click OK.

4.  Enter login information (Project Management login and password) and click OK

5.  Enter a name for this database connection and click OK.

Example:  PMDB

6.  The database connection name entered in the previous step should now be listed.  Click OK to open the chart.

To identify which projects contain the expense categories to be deleted, query the PMDB database through SQL PLUS(Oracle) or QUERY Analyzer(MSSQL) by doing the following:

1. Log in to SQL PLUS as admuser or privuser for MSSQL

2. Execute select * from costtype and identify the cost_type_id that corresponds to the cost_type that needs to be deleted.

3. Execute select * from projcost where cost_type_id = <cost_type_id from step 2>.  In this result set, you can identify which proj_id(s)  contain the Expense Categories that you wish to permanently delete.

4. Then query the PROJECT table to determine the project name(s) by executing select proj_short_name from PROJECT where proj_id = <proj_id from previous query>.   This result set will provide the Project ID (as seen through Project Management / Manager).  At this point, you can use Project Management / Manager to determine who has access to check-in / check-out or import into these projects.

If using xer imports to update projects or using Project Architect, follow the instructions below:

1. During the Import process, click Modify on the Update Project Options dialog box.

2. Select the Action to Keep Existing for Project Expenses.

> *****************************************************
> * EXCEPTION REPORT *
> *****************************************************
> Date: 09-Feb-05
>
> Executable: PM.exe
> Application: Primavera Project Management
> Event Code: NSIS-2739-6
> Message:
> No such interface supported
>
> Context:
> 1: TfrmMain.actProjectActivitiesExecute
> 2: TCFormManager.SetToolbar
> 3: TfrmLogin.FormCreate
> 4:
> 5:
> 6:
> 7:
> 8:
> 9:
> 10:
>
> Detail:
> Type: EOleException
> Object Type: TCUltraButton
>
>
> Components
> ==========
> ORI: ORI Win32 #
> ORI/DB: PMDB,0410.0001.0001.0002
> IMG: IMG Win32 #1000
>
> System Info
> ===========
> Username: DBonner Hostname: HOU-AS-0001
> OS Version: Windows NT ver 5.0, build 2195, Service Pack 4 (Intel Pentium)
> BDE Version: 500 (1901-5-11) OTHER
> BDE Ini file: M:\Program Files\Borland\Common Files\BDE\IDAPI32.CFG

This is a known issue cause by a Microsoft security patch for the following discontinued releases:

• Contractor 4.1


• Project Management version 3.5.1


• Project Management version 4.0


• Project Management version 4.1

Service packs are no longer available for these products.

The latest available versions are available for download from http://edelivery.oracle.com

Primavera would like to ensure that all customers are using the most current version of our software. Primavera was required to rewrite portions of our software to conform to Oracle抯 policies and standards.   Because older versions do not conform to Oracle development policies, they are not approved for distribution by Oracle. Now that Primavera is an Oracle owned company, we can no longer distribute these files.

If you would prefer not to install the latest version of Primavera software, refer to the workaround below to remove the Microsoft Security Patch.

Optional Workaround

Note: You must be logged onto the system as a member of the Administrators group to perform these steps. 

1. Choose Start, Settings, Control Panel and choose Add/Remove Programs. (Note for Windows XP users: Check the box at the top labeled ‘Show Updates’)


2. Select the Windows HotFix KB891781 and click ‘Remove’.


3. Reboot PC.

Note: If Automatic Updates is enabled, the KB891781 update will be continually downloaded. Change Automatic Updates properties at Control Panel\Automatic Updates. Uncheck the setting “Automatically download updates”

For more information on this specific hotfix, please see:

For Win98 SE only, perform the following steps.

To remove the MS Security update (KB891781) in Win98 SE:

1. Go to Start/Control Panel/ Add|Remove Programs

2. Scroll to Internet Explorer Q891781 and click Remove.

3. Choose “Yes” to remove the update and restore the previous working configuration.

MMDB –> Invalid alias name: MMDB

“ Event Code:   WIINE-2130-C
   Message:      TfrmWizImport.wizImportNext: Error executing ConvertXERFile:…”

or

“Event Code:    WIINE-0433-8
Message:         TfrmWizImport.wizImportNext: Error executing ConvertXERFile:” 

Example of the full Error report:

*****************************************************
*                EXCEPTION  REPORT               *
*****************************************************
Date:          2005-02-09 
Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    WIINE-2130-C
Message:      
  TfrmWizImport.wizImportNext: Error executing
  ConvertXERFile:
  463,1,Y,Y,Y,Y,N,Y,N,N,N,Y,.,CP_Units,M3GNY,,,,597,,1000
  ,10,10,2,3,500,,0,0.00,,,,,,,,,,,0.00,0.00,0.00,0.00,0.00,0.00,
  0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,”2005-02-01
  00:00″,”2004-09-01 00:00″,,”2006-12-30
  08:01″,”2004-09-01
  00:00″,,,,,,,,DT_FixedDUR2,A,XKLkb0PNcU2A1w4WwomB
  gx,QT_Hour,admin,,,,,,,,,COST_PER_QTY,N,Y,TT_Task,Y,C
  T_TotFloat,N,7,Y,
 Context:
  1: TfrmWizImport.wizImportNext
  2: TfrmWizImport.RunImportWizard
  3: TfrmMain.actHomeExecute
  4: TfrmMain.actFileImportExecute
  5: TCFormManager.SetToolbar
  6: TfrmLogin.FormCreate
  7:
  8:
  9:
  10:
Detail:
  Type:        Exception
  Object Type: TCUltraButton
Components
==========
ORI: ORI Win32 #
ORI/DB: PMDB,0410.0001.0001.0002
IMG: IMG Win32 #1000
DLL: (failed to query C:/PROGRAM FILES/PRIMAVERA/PROJECT MANAGEMENT/../COMMON/BIN/XERCONVERTERLIB.DLL)
System Info
===========
Username: pdecort Hostname: paul2000
OS Version: Windows NT ver 5.1, build 2600, Szervizcsomag 1 (Intel Pentium)
BDE Version: 500 (1901-5-11) OTHER
BDE Ini file: C:\Program Files\Borland\Common Files\BDE\IDAPI32.CFG

Non English Regional Settings: Specific Regional Settings that are known to cause this error are:

• Norwegian


• Hungarian

Workaround:

Set the regional settings to ‘English’ before opening Project Management.  Once the XER file has been imported the regional settings may be returned to their original settings.

Note:  This is only an issue when attempting to import an XER file from a previous version of the software.  Importing same-version XER files does not cause an error.

Choose ‘Create a new Primavera database’, enter the Product key and click ‘Next’.

Choose ‘Microsoft SQL Server or MSDE’ and check the ‘Include sample project data’ box.  Click ‘Next’.

Choose ‘Project Management Database (PMDB).  Clilck ‘Next’.

Choose ‘Create database and load application data’. 

Be sure the ‘Load license key file’ box is checked. 

Click the folder button and browse to the CD and select the ‘pmdb.lic’ file located on the root of the CD. 

Click ‘Next’.

Enter the SQL Server administrative username and password (The Admin Name is ‘sa’ by default.  The Admin password was defined when installing MSDE). 

Enter the Server Name (This is the full computer name and can be found by right clicking on My Computer and selecting ‘Properties’.  For Windows 2000, select the ‘Network Identification’ tab.  For Windows XP, choose the ‘Computer Name’ tab.  Localhost can also be used as the Server Name.)

Click ‘Next’.

Manually enter the Database name of ‘PCONDB’ (This is the only database name that Contractor will be looking for). 

Click ‘Next’.

Choose ‘YES, I want to create database tables and structure’. 

Click ‘Next’.

Structure is being created……..

Click ‘Next’ to Load Application Data

Loading Application Data…….

Click ‘Finish’ to complete the database creation.

Click “More” then the following error screen will be displayed.

com.primavera.integration.server.ServerFacade.getDBInstances(ServerFacade.java)

com.primavera.integration.client.LocalSession.getDatabaseInstances(LocalSession.java)

sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

java.lang.reflect.Method.invoke(Unknown Source)

com.primavera.integration.client.Session.getDatabaseInstances(Session.java)

com.primavera.integration.app.schedcomp.gui.x.<init>(LoginDlg.java)

com.primavera.integration.app.schedcomp.gui.CompareProjectsDlg.main(CompareProjectsDlg.java)

User name = admuser

Password=admuser(This is the default password; if does not work. Please check with your Oracle DBA).

By default the ‘Recovery model’ value should be set to ‘Simple’.

1. Launch MS SQL Server 2005 Management Studio.


2. Right-click on the database and select ‘properties’.


3. Select the ‘Options’ page.


4. Select ‘Simple’ from the ‘Recovery model’ drop-down list:

1. Click ’OK’.


2. Close the Management Studio.


3. Go to start, (Settings), Control Panel, Administrative Tools, Services


4. Stop and Restart SQL SERVER to insure changes will take effect.

1. Launch MS SQL Server 2000, Enterprise Manager.


2. Right-click on the database and select ‘properties’.


3. Select the ‘Options’ tab.


4. Select ‘Simple’ from the ‘Recovery model’ drop-down list:
   
   
    


5. Hit ‘OK’.


6. Close Enterprise Manager.


7. Launch Settings, Control Panel, Administrative Tools, Services


8. Stop and Restart MSSQLSERVER to verify settings will take effect.
   
       

Note:  It is acceptable for the Database Administrator to change this to ‘full’ recovery, as long as a plan to deal with the expanding log file is also implemented.

For information on how to shrink the LOG file, see:

Solution ID: 200363104250 ”How to shrink the SQL log file for Project Management?”

Table does not exist. ORA-00943: table or view does not exist 

Because you are modifying data in the database, you have to use the privuser (or equivalent) user name and password.

1. Copy the database files from your documentation CD.


2. Apply your license to the database.


3. Create a connection to your new database.

1.  Copy the database files from your documentation CD:

• Browse to the Interbase\pmdb folder on the documentation CD.


• Copy the pmdb.gdb file, then paste it in a folder on your hard drive.


• Once it is copied, right-click on the pmdb.gdb file on your hard drive and choose properties.  Remove the read only attribute by unchecking read only.

2.  Create a connection to your new database:

 To learn how to create a connection to your database, view How to create a database alias.

3.  Apply your license to the database:

To learn how to apply a license, view How to load a license file into the database

ORA-01631 Max # Extents(nnn) reached in table (xxx)

Where nnn = # of Extents and xxx = PMDB table name

For each table a maximum number of extents can be specified.  This error means that in order to accommodate some new data, Oracle needed to extend a table but could not because the maximum number of extents have been reached.  The error reports back both the current (maximum) number of extents and the table name.

This error is often also symptomatic of the next extent size being too small.

NOTE: The following steps should be performed by the Oracle DBA:

Increase the maximum number of extents allowed for the table, i.e:

alter table <table-name> storage (maxextents 500);

or alternately remove the limit on the number of extents, i.e.:

alter table <table-name> storage (maxextents unlimited);

*****************************************************

*EXCEPTIONREPORT*

*****************************************************

Date:21-Mar-05

Executable:PM.exe

Application:Primavera Project Management

Event Code:GSQLE-1009-D

Message:

General SQL error.

internal error

Context:

1: TfrmWizImport.wizImportFinish

2: TfrmWizImport.wizImportBeforeShowPage

3: TfrmWizImport.RunImportWizard

4: TfrmMain.actHomeExecute

5: TfrmMain.actFileImportExecute

6: TfrmMain.actProjectsExecute

7: TCFormManager.SetToolbar

8:

9:

10:

Detail:

Type:EDBEngineError

Object Type:TCUltraButton

Database Error:

1: General SQL error.

Category:51

Error Code:13059

Sub Error Code :3

Server Error Code: 0

2: internal error

Category:51

Error Code:13059

Sub Error Code :3

Server Error Code: -303

Components

==========

ORI: ORI Win32 #

ORI/DB: PMDB,0410.0001.0001.0002

IMG: IMG Win32 #1000

System Info

===========

Username: DominicHostname: DGILLESPIEXP

OS Version: Windows NT ver 5.1, build 2600, Service Pack 1 (Intel Pentium)

BDE Version: 500 (1901-5-11) OTHER

BDE Ini file: C:\Program Files\Borland\Common Files\BDE\IDAPI32.CFG

Workaround:

Remove the Documents section of the XER that deals with Collaboration, save the XER and then the XER will import in to Interbase.