Quantcast
Channel: Primavera Online Interaction » PMDB
Viewing all 92 articles
Browse latest View live

prim21982:Error “Table does not exist. Invalid object name ‘PROJCOST’.”

0
0
Solution ID: prim21982
Error "Table does not exist. Invalid object name ‘PROJCOST’."
Status: Reviewed
Version(s): 4.0, 4.1



Problem: Creating new databases in SQL, during the dataload, getting the Error  “Table does not exist. Invalid object name ‘PROJCOST’.”

Fix: Verify that SQL Server Authentication is “SQL Server and Windows”

Stop the SQL Server Service. Open SQL Server Enterprise Manager, right-click on the local server registration and click on Properties to open the window ‘SQL Server Properties (Configure) – (local)’ and click on the ‘Security’ tab. If Authentication is set to ‘Windows only’, click to select ‘SQL Server and Windows’ and click OK. Re-Start SQL Server Service.


Delete the partially completed PMDB database in SQL Enterprise Manager and restart the database create process.



prim22440:Error was received while running the Resync Script after attaching the PMDB_DATA.mdf and PMDB_LOG.ldf files were attached to the MSDE 2000.

0
0
Solution ID: prim22440
Error was received while running the Resync Script after attaching the PMDB_DATA.mdf and PMDB_LOG.ldf files were attached to the MSDE 2000.
Status: Reviewed
Version(s): 3.5, 3.5.1, 3.5.2, 4.0, 4.1, 5.0



Problem: Error when running the Resync Script after attaching the PMDB_DATA.mdf and PMDB_LOG.ldf files were attached to the MSDE 2000.

Server: Msg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 96
Terminating this procedure. The Login name ‘pubuser’ is absent or invalid.



Server: Msg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 96
Terminating this procedure. The Login name ‘privuser’ is absent or invalid.

Cause: The machine had never hosted a Primavera database.
Fix:

  1. Log in to the MSDE server as an administrator.  This is most commonly accomplished using the OSQL utility via DOS.
     
    Examples:

    C:\>osql -E -S localhost\primavera
      (or)
    C:\>osql -U sa -P prima -S localhost\primavera
     

  2. Run the scripts to create the necessary users in the database instance: ‘privuser’ and ‘pubuser’.
     
    Example:
     
    1>EXEC sp_addlogin ‘privuser’,'privuser’
    2>EXEC sp_addlogin ‘pubuser’,'pubuser’
    3>go

     

  3. Specify the database name.
     
    Examples:
     
    1>use pmdb$primavera
      (or)
    1>use pcondb
     

  4. Run the scripts to resync the users.
     
    Example:
     
    2>EXEC sp_change_users_login ‘Update_One’, ‘PUBUSER’,'PUBUSER’
    3>EXEC sp_change_users_login ‘Update_One’, ‘PRIVUSER’,'PRIVUSER’
    4>go

prim22467:Event Code Error: ‘CVRJC-3802-1′ when importing an XER

0
0
Solution ID: prim22467
Event Code Error: ‘CVRJC-3802-1′ when importing an XER
Status: Reviewed
Version(s): 4.0, 4.1, 5.0



Problem: “Event Code Error: ‘CVRJC-3802-1′ when importing an XER”
Problem:

Event Code Error: ‘CVRJC-3802-1: TCCustomVirtualRow.getJoinedColItems: UDFVALUE row has blank fk_id’ when importing an XER


Cause: This is caused by orphaned records in the database being extracted into the XER file during export, then the error is received when importing an XER file that contains these orphaned records.  Orphaned records can happen for a variety of reasons. 

Note: 
- One known cause is if multiple users are in a project and user 1 runs a global change or fill down for a user defined field and user 2 is deleting an activity at the same time.  The activity is successfully deleted but leaves
an orphaned UDF value. (Note:  Primavera recommends running these type of changes in “Exclusive mode”. )
- This particular cause  of orphaned records has been fixed in Project Management 5.0 SP1
and 4.1 SP4.  Applying these releases will not fix pre-existing orphaned records in databases or XER files but will prevent new orphaned records from being created by this scenario.  Therefore, the error will continue to happen if the XER being imported contains orphaned UDFs. (see the delete_orphaned_UDFVALUE scripts below for database cleanup of orphaned records.)

** Other scenarios that cause orphaned records may still exist. **

Fix: This known problem in Project Management has been corrected in version 5.0 Service Pack 2.  

To download the latest Service Pack, see:


Solution ID: prim29265 揥hat are the latest Service Packs for Primavera version 5.0??/A>

Fix: Workaround:

Run database queries/scripts on the source database (the database where the XER was exported from).  See steps below.


PROJECT MANAGEMENT FIX:


Run the appropriate script below on the database that the XER was exported from
     – For Microsoft SQL Server, run the script as PRIVUSER
     – For Oracle , run the script as ADMUSER
     - For MSDE Primavera 5.0 Standalone installation, save the appropriate script to the root of the C:\ drive and run the following from a DOS command prompt:
       (Start > Run > type ‘cmd’ and click OK):  osql -U sa -P prima -S localhost\primavera -d pmdb$primavera -i c:\delete_orphaned_UDFVALUE_##.sql

CONTRACTOR FIX:

      - For Contractor 5.0, save the delete_orphaned_UDFVALUE_50 script to the root of the C:\ drive and run this from the DOS command prompt:
       (Start > Run > type ‘cmd’ and click OK):  osql -U sa -P prima -S localhost\primavera -d PCONDB -i c:\delete_orphaned_UDFVALUE_50.sql


Note:  RUN THIS SCRIPT ON A BACKUP OF THE DATABASE FIRST!


For Project Management 4.1 databases:  delete_orphaned_UDFVALUE_41.sql


For Project Management 5.0 databases: delete_orphaned_UDFVALUE_50.sql


 If the script seems to hang at the section where the script attempts to delete UDF data which has no corresponding entry in the TASK table, please replace it for:


delete from udfvalue a


where exists (


select 1 from udftype b


where b.udf_type_id = a.udf_type_id


and b.table_name = ‘TASK’


)


and not exists (


select 1 from task c


where c.task_id = a.fk_id


);


Fix:

Workaround 2:


If the source database is not accessible, the XER file can be fixed.  Please see:


 PRIM16871: Receiving Event Code:  CVRJC-3802-1 while importing a project with orphaned rows in UDFVALUE table


 

Fix: Workaround 3:

If a 5.0 SP2 or higher implementation is available (both client application and database patched) the project may be imported and then re-exported to XER format to remove the Orphaned Records causing this problem.  It may then be imported into a pre SP2 database.

prim22594:Event Code Error: “GSQLE-1534-A”

0
0
Solution ID: prim22594
Event Code Error: "GSQLE-1534-A"
Status: Reviewed
Version(s): 3.5, 3.5.01, 3.5.1, 3.5.2, 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1, 7.0



Problem: Event Code Error: “GSQLE-1534-A” when working in Project Manager / Management connected to an Oracle database


*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          04/15/2005


Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    VTDCF-1615-F
Message:      
  TCVirtualTable.DoCalcField:
  PROJECT.other_user_exclusive: General SQL error.
  ORA-00028: your session has been killed


Context:
  1: TfrmEPS.FormReloadData
  2: TfrmMain.actProjectsExecute
  3: TfrmMain.actProjectActivitiesExecute
  4: TCFormManager.SetToolbar
  5: TfrmLogin.FormCreate
  6:
  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


System Info
===========
Username: Jerry   Hostname: JERRYWXP
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

Problem: This error can be caused by terminating an Oracle session at the database level.  This can be done from the Oracle Enterprise Manager Console.

Fix: Close Project Manager / Management, then re-launch and log in again.  If you cannot log in contact your DBA.

prim22599:Script Error “Unknown error line: 271, column: 6″ when connecting to PMDB database in Cost Management.

0
0
Solution ID: prim22599
Script Error "Unknown error line: 271, column: 6" when connecting to PMDB database in Cost Management.
Status: Reviewed
Version(s): 4.1



Problem: Script Error “Unknown error line: 271, column: 6″ when connecting to PMDB database in Cost Management.

Problem: Error connecting to Project Management UDL in Cost Management.
Fix: This known problem in Cost Management 4.1 has been corrected in Cost Management 4.1 service pack 1 (SP1).

Workaround:


Close the Interface Mapping window and re-link to the PMDB database.

prim22607:Can Primavera Contractorconnect directly withthe full suite’sdatabase?

0
0
Solution ID: prim22607
Can Primavera Contractor connect directly with the full suite’s database?
Status: Reviewed
Version(s): 4.1, 5.0



Problem: Can Primavera Contractor connect to a Primavera Project Management database?
Problem: Can Primavera Contractor connect directly with the full suite’s database?
Fix: No you are not licensed to connect to anything but a contractor database.

 Attempting to login to a PMDB database you will get a dialog box explaining:


 You are not authorized to run the application. Please contact your administrator.


Fix: This issue is an existing Enhancement Request. It will be considered for a future release

prim23796:How to connect to the SDK through JDBC connection

0
0
Solution ID: prim23796
How to connect to the SDK through JDBC connection
Status: Reviewed
Version(s): 3.5.1, 4.0, 4.1, 5.0



Problem: How to connect to the SDK through JDBC connection
Fix:

To connect to the SDK via a JDBC connection, you will need to use the JDBC-ODBC bridge


import java.sql.Connection;
import java.sql.DriverManager;


/***********************
* Connecting to SDK via JDBC *
***********************/
public class PrimaveraTest {


 


// Set the Database URL to be jdbc:odbc:<<DSN NAME>>
private static String url = “jdbc:odbc:PrimaveraSDK”;
private static String username = “admin”;
private static String password = “admin”;



public static void main(String[] args) throws Exception {


try{


    // Load the JDBCODBC driver included with 1.4.x JDK’s
   
Class.forName(“sun.jdbc.odbc.JdbcOdbcDriver”);
    System.out.println(“Connecting to ” + url + ” with username/password = “+username+”/”+password);
    System.out.println(“Found Driver”);


    //Make a connection the the database URL, send username and password
    Connection conn = DriverManager.getConnection(url, username, password);
    System.out.println(“Connected to Primavera”);


    conn.close();
    conn = null;
    System.out.println(“Disconnected from Primavera”);

}


catch(java.lang.ClassNotFoundException e) {


    System.out.println(“SQL Driver not found “);
    e.printStackTrace();
}


}
 


The integration API can also be used to connect Java applications to the PMDB.


DISCLAIMER: The code listed above is provided for the convenience of the User and is not provided under warranty or supported as part of Primavera System Inc.’s Maintenance and Support Program. Users who implement the code do so at their own risk. Primavera Systems Inc. will not be responsible for any problems or data loss resulting from the use of this application.  

prim24375:Receiving an “Event Code: CIIUB-3936-B Message: Connection is in use by another statement.” after waiting to save a layout.

0
0
Solution ID: prim24375
Receiving an "Event Code: CIIUB-3936-B Message: Connection is in use by another statement." after waiting to save a layout.
Status: Reviewed
Version(s): 4.0, 4.1



Problem: Receiving an “Event Code: CIIUB-3936-B Message: Connection is in use by another statement.” after waiting to save a layout.
Problem: Receiving the following error when attempting  to ‘save’ a layout as a global layout.

The ‘save’ action does not complete for 10 minutes, after which time the error below is generated:


*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          18-Mar-05

Executable:    PM.exe
Application:   Primavera Project Manager
Event Code:    CIIUB-3936-B
Message:      
  Connection is in use by another statement.

Context:
  1: TfrmMain.actFileOpenExecute
  2: TCFormManager.SetToolbar
  3: TfrmLogin.FormCreate
  4:
  5:
  6:
  7:
  8:
  9:
  10:

Detail:
  Type:        EDBEngineError
  Object Type: TTimer

Database Error:
1: Connection is in use by another statement.
   Category:          42
   Error Code:        10771
   Sub Error Code :   19
   Server Error Code: 0


Components
==========
ORI: ORI Win32 #
ORI/DB: PMDB,0350.0005.0004.0001
IMG: IMG Win32 #1000

System Info
===========
Username: assmith   Hostname: BBTSRVMDS37
OS Version: Windows NT ver 5.0, build 2195, Service Pack 3 (Intel Pentium)
BDE Version: 500 (1901-5-11) OTHER
BDE Ini file: C:\Program Files\Borland\Common Files\BDE\IDAPI32.CFG

Cause: There may be a variety of causes.
e.g. a corrupted layout means the layout never completes the save thus maintaining a connection to the database.
Therefore an error is generated at some stage when a second connection is made to the database.

The Connection in use appears to be a secondary error not the primary cause of the application failure.

Fix:

To prevent the error:



  1. Open the ‘Classic Schedule’ layout

  2. Use the ‘Save As’ to create a new layout.

  3. Tailor the layout as required.

  4. Delete the original layout which is corrupted.

prim24459:Dragging the split bar between activity table and Gantt chart causes Exception Error VTDCF-3254-8

0
0
Solution ID: prim24459
Dragging the split bar between activity table and Gantt chart causes Exception Error VTDCF-3254-8
Status: Reviewed
Version(s): 3.5.1, 4.0, 4.1, 5.0



Problem: Dragging the split bar between activity table and Gantt chart causes Exception Error VTDCF-3254-8
Problem:

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


*EXCEPTIONREPORT*


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


Date:27-May-2005


 


Executable:PM.exe


Application:Primavera Project Manager


Event Code:VTDCF-3254-8


Message:


TCVirtualTable.DoCalcField: TASK.complete_pct: Access


violation at address 0040463C in module ‘PM.exe’. Read of


address 75434350


 


Context:


1: TfrmMain.actProjectActivitiesExecute


2: TCFormManager.SetToolbar


3:


4:


5:


6:


7:


8:


9:


10:


 


Detail:


Type:Exception


Object Type: TCVirtualQueryGrid


 


 


Components


==========


ORI: ORI Win32 #


ORI/DB: PMDB,0350.0005.0004.0001


IMG: IMG Win32 #1000

Cause: Corrupt layout
Fix: Switch to a different layout and if necessary re-create the layout in use when this error occurs.

prim24477:Event Code: SQLSE-1746-7 or Error: “SQL Server Error: Invalid object name ‘QUERYLIB’.” when launching Project Management after installing version 5.0

0
0
Solution ID: prim24477
Event Code: SQLSE-1746-7 or Error: "SQL Server Error: Invalid object name ‘QUERYLIB’." when launching Project Management after installing version 5.0
Status: Reviewed
Version(s): 5.0



Fact: 5.0
Problem: Event Code:SQLSE-1746-7 when logging into Project Management

Problem: Error: “SQL Server Error: Invalid object name ‘QUERYLIB’.” when launching Project Management after installing version 5.0

Cause: This error can happen when a 5.0 Primavera Project Management client is connecting to a 4.x database.
Fix: Connect Project Management to 5.0 database.  Ensure that the application and database version match.

You may need to upgrade your database to version 5.0 using the CONFIGASST.EXE utility found on the 5.0 CD1\INSTALL\DATABASE folder.

Fix: The following is the recommended procedure for upgrading from version 4.x to 5.0:

  1. Backup your Project Management and Methodology Management databases before beginning the upgrade process to ensure you will not lose any data due to unexpected problems

  2. Uninstall the current version of Primavera

  3. Install the new client version of Primavera

  4. Run the Database wizard to upgrade your existing PMDB and MMDB

  5. Test the new databases to ensure the upgrade succeeded

  6. Install the new Group Server and any additional components as described in the Administrator’s Guide

The version 5.0 Administrator’s Guide is available here:  Primavera 5.0 Administrator’s Guide

prim24490:Error importing MPP file “Cannot insert the value NULL into column ‘clndr_name’”

0
0
Solution ID: prim24490
Error importing MPP file "Cannot insert the value NULL into column ‘clndr_name’"
Status: Reviewed
Version(s): 4.0, 4.1, 5.0



Problem: Error importing MPP file “Cannot insert the value NULL into column ‘clndr_name’”
Problem:

The detailed error messgae during MPP file import as following:-


Executable:PM.exe


Application:Primavera Project Management


Event Code:GSQLE-3605-0


Message:


General SQL error.


Cannot insert the value NULL into column ‘clndr_name’,


table ‘PMDB.privuser.CALENDAR’; column does not allow


nulls. INSERT


fail&Agrave;


Context:


1: TfrmWizImport.RunImportWizard


2: TfrmMain.actHomeExecute


3: TfrmMain.actFileImportExecute


4: TCFormManager.SetToolbar


5: TfrmLogin.FormCreate


6:


7:


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: Cannot insert the value NULL into column ‘clndr_name’, table ‘PMDB.privuser.CALENDAR’; column does not allow nulls. INSERT


Category:51


Error Code:13059


Sub Error Code :3


Server Error Code: 515


3: fail&Agrave;


Category:51


Error Code:13059


Sub Error Code :3


Server Error Code: 0

Cause:

 The Microsoft Project file in question had some resources without a “Resource Name” defined (Under View/Resource Table).


  

Fix: Remove the rows without resource names in Microsoft Project and now the project can be imported into the Project Management module without any problem.

prim24699:GIOOR-4067-1 error when entering Page Setup

0
0
Solution ID: prim24699
GIOOR-4067-1 error when entering Page Setup
Status: Reviewed
Version(s): 4.0, 4.1, 5.0



Problem: GIOOR-4067-1 error when entering Page Setup
Problem: AVAAO-2542-7 error when entering Page Setup
Problem: *****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          22-Jun-05 11:25 AM

Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    GIOOR-4067-1
Message:      
  Grid index out of range


Context:
  1: TfrmMain.actProjectActivitiesExecute
  2: TCFormManager.SetToolbar
  3:
  4:
  5:
  6:
  7:
  8:
  9:
  10:


Detail:
  Type:        EInvalidGridOperation
  Object Type: TfrmMain



Components
==========
ORI: ORI Win32 #
ORI/DB: PMDB,0410.0001.0001.0002
IMG: IMG Win32 #1000

Cause: The layout in use is corrupt
Fix: Please switch to a different layout, delete the layout in which this problem arises and re-create it.

prim28983:’Database PMDB$Primavera exists on server’ when upgrading to Primavera 5.0

0
0
Solution ID: prim28983
‘Database PMDB$Primavera exists on server’ when upgrading to Primavera 5.0
Status: Reviewed
Version(s): 5.0



Problem: Upgrade Interbase stand-alone database to Primavera version 5.0
Problem: Error upgrading database to 5.0:

‘Database PMDB$Primavera exists on server’


Cause: When upgrading an Interbase database, the upgrade wizard automatically names the new MSDE database PMDB$Primavera.  If that database already exists, the upgrade will not be successful.

Note:  The standalone install of Primavera 5.0 creates the default database PMDB$Primavera.

Fix: Rename the existing PMDB$Primavera database to a new name.

  • Open a DOS window

  • Login to OSQL using the following command:  osql -U sa -P prima -S localhost\primavera <enter>

  • Execute the following rename db command:  EXEC sp_renamedb ‘pmdb$primavera’, ‘pmdb_sample’ <enter>

  • Type go <enter>

The results should be similar to the picture below.


Fix: See also Solution Prim27027: How to upgrade multiple Interbase databases using CALM

prim29013:What database field maps to the application screen information?

0
0
Solution ID: prim29013
What database field maps to the application screen information?
Status: Reviewed
Version(s): 4.1, 5.0, 6.0, 6.1, 6.2



Problem: What database field maps to the application screen information?
Problem: What database field has the Project Name?
Problem: Where can I find Project Management database field mapping documentation?
Problem: Where is the database schema docs for 5.0, 6.1, 6.2?
Fix: proj_short_name is on the PROJECT table.
Fix: There are database schema documentation on the CDs:

Primavera 4.1 – CD2:\EC\Documentation\[PMDBSchemaDocHtml.zip | MMDBSchemDocHtml.zip]
Primavera 5.0 – CD3 – Documenation:\Documentation\Documentation\Technical Documentation\Schema Docs\[PMDBSchemaDocHtml.zip | MMDBSchemDocHtml.zip]
Primavera 6.1 – CD3 – Documentation:\Documentation\English\Technical Documentation\Schema Docs - Download 6.1 Schema Here
Primavera 6.2 – P62_Documentation\<Select Language>\Technical Documentation\Schema Docs - Download 6.2 Schema Here


There is also data mapping documentation:


Primavera 4.1 – CD2:\[EC|IT|MT|NP]\Documentation
Primavera 5.0 – CD3 – Documenation CD:\Documentation\Documentation\Technical Documentation\Data Mapping Docs
Primavera 6.1 – CD3 – Documentation CD:\Documentation\English\Technical Documentation\Data Mapping Docs
Primavera 6.2 – P62_Documentation\<Select Language>\Technical Documentation\Data Mapping Docs

Fix:

The 5.0 XER data mapping documents are:


XERprojects.pdf
XERresources.pdf
XERroles.pdf

prim29141:Error: “Could not stop the Primavera Job Service (JSDB) service on Local Computer….”

0
0
Solution ID: prim29141
Error: "Could not stop the Primavera Job Service (JSDB) service on Local Computer…."
Status: Reviewed
Version(s): 4.0, 4.1, 5.0



Problem: Error: “Could not stop the Primavera Job Service (JSDB) service on Local Computer.
The service did not return an error.  This could be an internal Windows error or an internal service error.
If the problem persists, contact your administrator.”

Cause: The PMDB (default) database is not available when attempting to stop Job Services.
Fix:

If using SQL Server:



  1. Login to the machine running SQL Server.
     

  2. Use either ‘SQL Server Service Manager’ or ‘SQL Server Enterprise Manager’ to confirm the server is ‘Running.’
    Without an active database service, the JSDB service can’t stop.
Fix:

If using Oracle:



  1. Login to the machine running Oracle Server.
     

  2. Check Windows Services to see if the Listener Service is running.
    Without a Listener Service, to check for client connections to PMDB (default), the JSDB service can’t stop.

prim29157:”Unable to resolve privileged username and password” when using Database Configuration for myPrimavera 5.0

0
0
Solution ID: prim29157
"Unable to resolve privileged username and password" when using Database Configuration for myPrimavera 5.0
Status: Reviewed
Version(s): 5.0



Problem: How to Connect MyPrimavera to a named instance of MS SQL Server
Fact: MSDE
Problem: Error during myPrimavera database configuration.
Problem:

Receive error connecting to 5.0 standalone (MSDE) database.


“Unable to resolve privileged username and password” when using Database Configuration for myPrimavera 5.0


 


Error: Unable to resolve privileged username and password


Failed Logon:com.jnetdirect.jsql.u:


TCP/IP connection failed to host:java.net.UnknownHostException: <servername>\primavera


url:jdbc:JSQLConnect://<servername>\primavera:<port>/database=<database name>$primavera



Problem: MyPrimavera Database Configuration fails when connecting to an instance of MSDE
Fix: Database Configuration screen should have the following information:

  1. Username and Password = pubuser

  2. Database Name:  pmdb$primavera  Note: pmdb$primavera is the 5.0 default database name, this may be different.

  3. Database Host Address:  Server Machine name or IP address (or ”localhost” if everything is installed on one machine)   Note: \<SQL instance name> is not needed.

  4. Database Host Port:  To determine the Database Host Port, see instructions below.


To determine the Database Host Port:


Go to Start/Run and type svrnetcn.  Click OK.



Select the \PRIMAVERA instance, highlight TCP/IP and click ‘Properties’.



This is the Default port # for this SQL Instance.


 


 Another alternative to finding the host port is the following:


1.  Log into Project Management.


2.  Go to Help, About Primavera.  Go to the System tab.


3.  Find the port number under the BRE database section:


Fix: This error was also observed in the following scenario:

Customer’s machine name included “\” characters. The JSQLConnect function appears to parse the connect string as “<servername>\<instance>…”.  Any slashes in the servername part cause the connect string to be wrongly interpreted.


The workaround is ensure that the server name does not contain “\” characters.

prim29259:How to install MSDE 2000 using the Primavera 5.0 CDs.

0
0
Solution ID: prim29259
How to install MSDE 2000 using the Primavera 5.0 CDs.
Status: Reviewed
Version(s): 5.0



Problem: How to install MSDE 2000 using the Primavera 5.0 CDs.
Fix: There is no seperate MSDE 2000 folder on the 5.0 CDs as there was on the 4.1 CDs.

To install MSDE 2000, use 5.0 CD 1 and choose to perform a standalone install option and then optionally uninstall the Primavera client that will be installed along with MSDE.


NOTE:  The Primavera 5.0 Standalone installer creates MSDE with the following defaults:


Named instance: MSSQL$Primavera  (For configuring connections for the client, the Server Name = <server>\primavera)
Administrator username/password for Primavera Instance:   sa / prima
Default database name:   PMDB$PRIMAVERA

Fix: Alternatively, You can find the download for MSDE at :

http://www.microsoft.com/downloads/details.aspx?familyid=90dcd52c-0488-4e46-afbf-acace5369fa3&displaylang=en


Download the file called “sql2kdesksp3.exe”. Extract the files to a folder and follow the instructions in Solution PRIM4498 to install it.

prim29314:ERROR when launching Project Management 5.0, or P6 (Project Management 6.0 or 6.*) standalone: “Unable to connect to the database. Would you like to configure the database connection now?”

0
0
Solution ID: prim29314
ERROR when launching Project Management 5.0, or P6 (Project Management 6.0 or 6.*) standalone: "Unable to connect to the database. Would you like to configure the database connection now?"
Status: Reviewed
Version(s): 5.0, 6.0, 6.1, 6.2, 6.2.1



Problem: Error: “Unable to connect to the database.  Would you like to configure the database connection now?”

Problem: What are the default Database Configuration settings for Primavera Project Management 5.0 and P6 (Project Management 6.0 or 6.1) Standalone?
Fix: Click ‘Yes‘ to configure.

Enter a user-defined Database alias.  


NOTE:  This is typically the same as the database name.


Select the driver type. 


NOTE:  5.0 standalone uses Microsoft SQL Server/MSDE. 



Enter the Database Host name.  <machinename>\primavera. 


NOTE:  ”\primavera” represents the SQL instance that is created upon installation of 5.0 standalone.  “localhost\primavera” may also be used.


Enter the Database name. 


NOTE:  “pmdb$primavera” is the name of the database that is created upon installation of 5.0 standalone.  “$primavera” would not be needed if connecting to any other database.



Enter the Public Login Information. 


Username=pubuser.  Password=pubuser.  Public Group ID=1



Click ‘Next’ to validate connection.



Click ‘Finish’.


prim29344:Error running actualizer with non-US regional settings.

0
0
Solution ID: prim29344
Error running actualizer with non-US regional settings.
Status: Reviewed
Version(s): 4.1, 5.0



Problem: Error running actualizer with non-US regional settings.

*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          10-Oct-05

Executable:    actualizer.exe
Application:   Primavera Project Management
Event Code:    PRMDB-0142-B
Message:      
  PRM DBAccess Error: SQL Server Error: There are fewer
  columns in the INSERT statement than values specified in
  the VALUES clause. The number of values in the VALUES
  clause must match the number of columns specified in the
  INSERT statement.

Context:
  1: TfrmLogin.FormCreate
  2:
  3:
  4:
  5:
  6:
  7:
  8:
  9:
  10:

Detail:
  Type:        EprmDBSQLExecutionFailure
  Object Type: TCUltraButton

Database Error:
   Error Code:     0

Components
==========
ORI: ORI Win32 #
ORI/DB: PMDB,0500.0024.0001.0002
IMG: IMG Win32 #1000

System Info
===========
Username: George   Hostname: Fornby
OS Version: Windows NT ver 5.0, build 2195, Service Pack 4 (Intel Pentium)

Fix: The ability for Timesheet Actualizer to work with Non-US regional settings is an existing Enhancement Request.  It will be considered for a future release
Fix:

Workaround:


a) Change the ‘decimal’ symbol to ‘.’ e.g. a ‘Full Stop’ or ‘Period’ symbol; and
b) Change the ‘thousand separator’ to ‘,’ e.g. a ‘Comma’ symbol.

prim29439:DOCUMENTATION CORRECTION: Running MMDB and PMDB In a Single Oracle Instance / Error: “Database logon failed. Check the public group ID. Bad private username or password. SQL Server Error: ORA – 10107: invalid username/password; logon denied”

0
0
Solution ID: prim29439
DOCUMENTATION CORRECTION: Running MMDB and PMDB In a Single Oracle Instance / Error: "Database logon failed. Check the public group ID. Bad private username or password. SQL Server Error: ORA – 10107: invalid username/password; logon denied"
Status: Reviewed
Version(s): 4.0, 4.1, 5.0



Fact: PMDB AND MMDB in the same oracle instance
Fact: pmdb and mmdb in 1 oracle instance
Problem: Error: “Database logon failed.  Check the public group ID. Bad private username or password.  SQL Server Error: ORA – 10107: invalid username/password; logon denied”
Problem: MMDB Database validation unsuccessful
Cause: The admin guide documentation contains typos between pages 489 – 491
Fix:

  1. Please ignore screenshots in steps 6,7,8 on pgs 489-490.  The text is correct, please accept the defaults.
     

  2. Disregard the SQL script at the bottom of page 490 and very top of page 491.  (It won’t hurt to run, but is unnecessary)
     

  3. Go to start -> programs -> primavera -> help and utilities -> database configuration
     

  4. On the welcome screen, select next
     

  5. On the following sceen select administrative tasks, and hit next



     

  6. On the following screen choose administer private database logins and select next
     

  7. Select Methodology Manager database, and your MMDB alias.  Select next.



     

  8. Enter the default username and password as privuser1  , select next.



     

  9. Select next on the following screen


     

  10. Verify that the private DB Username and password is privuser1 and select finish



     

  11. Follow the remaining steps on pages 493 – 496 to finish the setup of the alias. 
Viewing all 92 articles
Browse latest View live




Latest Images