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

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

To successfully launch myPrimavera from within Expedition Professional 10.1 when myPrimavera is connecting to a NAMED INSTANCE of MSDE or Microsoft SQL Server, edit the ODBC system data source on the Expedition Professional Web/Application server.

NOTE: Configuring the ODBC system data source is not required to launch myPrimavera from within Contract Manager 11.0.

Note: Creating the SQL Server alias prior to configuring the system DSN will not resolve this issue. The SQL Server alias must be created by modifying the client connection parameters in the system DSN.

1. On the Expedition Professional Web/Application server go to Start > Run and type ODBCAD32 and click OK.

2. Go to the SYSTEM DSN tab of the ODBC Data Source Administrator and select the system data source created when Expedition Professional was linked to the P5 Schedule.  To verify the data source name, review the following Solution:

Solution ID: prim28360 ”How to link a Project management and myPrimavera MSSQL database to Contract Manager / Expedition.”.

NOTE: In this example, the name specified is TEST_EXP. (Expedition will always add the _EXP designation by default to the ODBC name specified in Server Configuration).

3. Click Configure:

4. Specify the machine name of the SQL Server you are connecting to and click Next.

5. Click on the Client Configuration button to enter in the details of the SQL Server connection.

6. Select TCP/IP under Network Libraries and enter in the machine name of the SQL server in the Server Alias and Server Name fields. Enter the port number being used to connect to the MSDE instance.

NOTE: The find out what port number is being used by the MSDE database server please see the following Solution:

Solution ID: prim48201 ”How to determine the port number of a MSDE named instance.”

7. After returning to the Server DSN Configuration window, provide login credentials for this SQL server connection. The default username/password is privuser/privuser. Click Next.

8. Verify that the default database is set to the name of your Project Management database. In this example it is PMDB$PRIMAVERA. Click Next.

9. At the final screen choose Finish.

10. A summary of the connection settings specified will be displayed with the option to test the data source connection. To test the connection, click on the Test Data Source Button.

11. After successful connection, click OK and close out of the ODBC Data Source Administrator.

12. Log in to Expedition Professional and launch myPrimavera.

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

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

To successfully launch myPrimavera from within Expedition Professional 10.1 when myPrimavera is connecting to a NAMED INSTANCE of MSDE or Microsoft SQL Server, edit the ODBC system data source on the Expedition Professional Web/Application server.

NOTE: Configuring the ODBC system data source is not required to launch myPrimavera from within Contract Manager 11.0.

Note: Creating the SQL Server alias prior to configuring the system DSN will not resolve this issue. The SQL Server alias must be created by modifying the client connection parameters in the system DSN.

1. On the Expedition Professional Web/Application server go to Start > Run and type ODBCAD32 and click OK.

2. Go to the SYSTEM DSN tab of the ODBC Data Source Administrator and select the system data source created when Expedition Professional was linked to the P5 Schedule.  To verify the data source name, review the following Solution:

Solution ID: prim28360 ”How to link a Project management and myPrimavera MSSQL database to Contract Manager / Expedition.”.

NOTE: In this example, the name specified is TEST_EXP. (Expedition will always add the _EXP designation by default to the ODBC name specified in Server Configuration).

3. Click Configure:

4. Specify the machine name of the SQL Server you are connecting to and click Next.

5. Click on the Client Configuration button to enter in the details of the SQL Server connection.

6. Select TCP/IP under Network Libraries and enter in the machine name of the SQL server in the Server Alias and Server Name fields. Enter the port number being used to connect to the MSDE instance.

NOTE: The find out what port number is being used by the MSDE database server please see the following Solution:

Solution ID: prim48201 ”How to determine the port number of a MSDE named instance.”

7. After returning to the Server DSN Configuration window, provide login credentials for this SQL server connection. The default username/password is privuser/privuser. Click Next.

8. Verify that the default database is set to the name of your Project Management database. In this example it is PMDB$PRIMAVERA. Click Next.

9. At the final screen choose Finish.

10. A summary of the connection settings specified will be displayed with the option to test the data source connection. To test the connection, click on the Test Data Source Button.

11. After successful connection, click OK and close out of the ODBC Data Source Administrator.

12. Log in to Expedition Professional and launch myPrimavera.

Steps:

1. Right Click My Computer, Properties, go to the Advanced Tab,Click settings under Performance section.

2. Select Data Execution Prevention.

3. The default setting is “Turn on DEP for All progams and services except those I select:”

4. Under the exclusion box, click Add and Browse to ConfigAsst.exe off your CD drive. ConfigAsst.exe is located on CD1 under the Install, Database folder.

5. Click Apply, OK – You may have to Reboot your Server.

6. Run Primavera Setup OR ConfigAsst.exe again.

NOTE:

To determine if you do have Service Pack 1 installed on your Windows 2003 server, go to Start, Run and type in, WINVER:

2. Click the box to Convert Database and Proceed.

3.  All Sybase connections have to be terminated.

4. Browse to the location of the Database to be converted.

5. Enter in the Administrative User Name and Password default is EXPADMIN for both.

6. Click OK and your Database will be converted to 8.5 format.

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

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:

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.

MSDE 5.0 Database Creation Steps:

1. Copy the msde_create_script.sql script attached below to a local drive on the MSDE PC.

2. Edit the msde_create_script.sql script in notepad.

Look for the following in the script:<<CHANGE TO A VALID PATH>>.This path is the location on where the Data and Log files will be created.

3. Open a Command Prompt on the PC where MSDE is installed.

4. Run the following command (make sure you edit for a valid SA password and the path to where the  msde_create_script.sql script is stored):

Note: Default 5.0 password for SA is prima.

osql -U sa -P <<password for SA >> -S <<server name>>\primavera -i <<path to sql script>>\msde_create_script.sql

This will create a MSDE database shell that can be used as the CollabLibrary.

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

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.

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

The alias used to connect to the MM database, when launching Project Architect, is located in the following registry key:

HKEY_CURRENT_USER\Software\Primavera\Databases\MM\CurrentAlias

NOTE: This key (‘AliasName’ field) represents the alias used during the last successful login to MM.

NOTE:  If you do not have access to the registry, use the Database Configuration Utility and select the MM alias to use.  Selecting the alias and clicking ‘Next’ through the wizard will change the current MM alias for the client.

Project Manager looks in the PM.INI file for the Methodology Manager alias.

To change to a new Methodology Manager database, edit the PM.INI and update the Methodology Manager database alias line as shown below:

[MethodDatabase]
Alias=
Username=
Password=

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. 

NOTE: The schema validation utility requires admuser to have full DBA rights to function with an Oracle database. If logging in with ‘admuser’ (to Oracle) and Schema Validation crashes, please ask the Database Administrator to make sure that ‘admuser’ is assigned the DBA Role.

1. Download the following file: P5database.zip
   
   These files are the database files for 5.0 SP4/5 but the Schema validation utility is backwards compatible.
    


2. Unzip the file to a location on a local hard drive.
    


3. Open Windows Explorer and navigate to the \database folder created inside the folder used in Step 2.
    


4. Refer to the steps below, begin with Step 3.

If using the Validate Schema tool from Primavera 5.0 base release CD’s:

1. Insert: “CD 1″.
    


2. Open: Windows Explorer and navigate to following subfolder on CD 1:  \install\database
    


3. Run: ValSch.exe
    


4. Select the correct RDBMS type (Oracle, SQL Server or Interbase)
    
       
   
   
    


5. Complete the Login dialog box.  The Username and Password are the schema owner (Oracle default is Admuser, SQL default is Privuser).  Click: Connect
    


6. Set the schema preferences:
   
   Select the correct schema type.  (‘PM’ vs ‘MM’)
   

   IMPORTANT: Use the pull-down menu to set the ‘Choose Schema’ selection. 
   This would be identical to the ’Database Version Label is’ value. 
    
   




7. Click: Run

NOTE: The default configuration entries for a standalone installation are localhost\primavera for the server host name and PMDB$primavera for the database name.

FIX 1:
Click back to the Database Configuration and correct the database name.

CAUSE 2:
Connecting to an existing MSDE instance and there were no network protocols enabled for the MDSE instance.

FIX 2:  
Enable the TCP/IP and Named Pipes in SQL Server Network Utility:

1. Click Start, and then click Run.


2. In the Run dialog box, type Svrnetcn in the Open box, and then click OK. 
   
   
   
    Note:  By default, the Svrnetcn.exe file is available in the following folder: 
    Installation Drive/Program Files/Microsoft SQL Server/80/Tools/BINN
    


3. Click OK.


4. In the Server Network Utility dialog box, click the General tab.
   
   
   
    


5. Select your instance of Microsoft SQL Server 2000 Desktop Engine (Windows) or select your instance of MSDE 2000 SP3a or SQL Server 2000 from the Instance(s) on this server list.


6. In the Disabled Protocols list box, select TCP/IP, and then click Enable.


7. Again in the Disabled Protocols list box, select Named Pipes, and then click Enable. 
   
   
    


8. In the Enabled Protocols list box, select TCP/IP, and then click Properties.
   
   
   
    


9. In the <Server Name> – TCP/IP dialog box, type 1433 in the Default Port box (or any unused port) , and then click OK.


10. In the Server Network Utility dialog box, click OK.
    Note:   You may receive a message that states that the changes made will be saved but the changes will take effect only after you restart the SQL Server service. 


11. In the Server Network Utility message box, click OK.


12. Restart the windows service of MSDE or SQL Server 2000 via Control Panels > Administration Tools > Services    (MSSQL$PRIMAVERA) 

FIX 3:
Disable the firewall setting on the XP machine (ensure the machine has other anti-virus/firewall software) which has the MSDE database installed. You will then find the connection will be successful.

FIX 4:
Replace ‘localhost’ with the actual machine name in the db alias connection information

FIX 5:
Enter the server name correctly.  (Example: “localhost\primavera”)

1. GoTo Start, Run and type “cmd” and hit <Enter>


2. At the command prompt, type: “osql -U sa -P prima -S localhost\primavera” and hit <Enter>


3. At the 1> prompt, type: “select name from sysdatabases” and hit <Enter>


4. At the 2> prompt, type: “go” and hit <Enter>


5. This will return a list of all databases on the server.  If databases were created successfully, you should see “pmdb$primavera” and “mmdb$primavera”

FIX 6:
Run ConfigAsst.exe from CD1 to create databases:  (See admin guide pg. 36)

FIX 7:
Start the database windows service for the MSSQL instance

Set the service to Automatic so it will restart after a shutdown of the machine.

If running full SQL 2000, Authentication setting is set to “Windows Only”. 

FIX 8:

Within Enterprise Manager, right click on servername, go to “Properties”.  On Security tab, set Authentication to “SQL Server and Windows”

The SQL port was changed on the server and either: 1.) the new port is not dynamcially resolving, or 2.) there is already a static port specified on the client machine.

FIX 9:  (to be done from the machine that can’t connect to the database)

1. Click: Start, Run.


2. Type: cliconfg, Click: OK.


3. In the SQL Server Client Network Utility, click: ‘Alias’ (tab)


4. If an alias is already defined, and its name matches the server name being used while configuring a Primavera Project Management connection, adjust the port number and close.  Otherwise, proceed to the next step:
    


5. Click: ‘Add’ (button), TCP/IP.


6. Type a name in ‘Server alias’.


7. ‘Server name’ must match the database location.
   NOTE: Specify the instance name, if there is one.


8. ‘Dynamically determine port’ should NOT be checked.


9. ‘Port number’ must match the new port of the SQL Service.


10. Click: OK, Apply, OK.

The application was installed using the “Client Applications” whereas the intention was to install the Stand-alone version of the software, which installs a database locally for the client to connect to.

FIX 10:

Uninstall the software and re-install, choosing Stand-alone rather than Client applications

The client machine and database server are on different domains.

FIX 11:

Use the Database Server’s IP address, when prompted for ‘Host Name’.

The SQL Database Server TCP port was changed and the Server was never restarted.

FIX 12:

Restart the SQL Server.

NOTE: The default configuration entries for a standalone installation are localhost\primavera for the server host name and PMDB$primavera for the database name.

FIX 1:
Click back to the Database Configuration and correct the database name.

CAUSE 2:
Connecting to an existing MSDE instance and there were no network protocols enabled for the MDSE instance.

FIX 2:  
Enable the TCP/IP and Named Pipes in SQL Server Network Utility:

1. Click Start, and then click Run.


2. In the Run dialog box, type Svrnetcn in the Open box, and then click OK. 
   
   
   
    Note:  By default, the Svrnetcn.exe file is available in the following folder: 
    Installation Drive/Program Files/Microsoft SQL Server/80/Tools/BINN
    


3. Click OK.


4. In the Server Network Utility dialog box, click the General tab.
   
   
   
    


5. Select your instance of Microsoft SQL Server 2000 Desktop Engine (Windows) or select your instance of MSDE 2000 SP3a or SQL Server 2000 from the Instance(s) on this server list.


6. In the Disabled Protocols list box, select TCP/IP, and then click Enable.


7. Again in the Disabled Protocols list box, select Named Pipes, and then click Enable. 
   
   
    


8. In the Enabled Protocols list box, select TCP/IP, and then click Properties.
   
   
   
    


9. In the <Server Name> – TCP/IP dialog box, type 1433 in the Default Port box (or any unused port) , and then click OK.


10. In the Server Network Utility dialog box, click OK.
    Note:   You may receive a message that states that the changes made will be saved but the changes will take effect only after you restart the SQL Server service. 


11. In the Server Network Utility message box, click OK.


12. Restart the windows service of MSDE or SQL Server 2000 via Control Panels > Administration Tools > Services    (MSSQL$PRIMAVERA) 

FIX 3:
Disable the firewall setting on the XP machine (ensure the machine has other anti-virus/firewall software) which has the MSDE database installed. You will then find the connection will be successful.

FIX 4:
Replace ‘localhost’ with the actual machine name in the db alias connection information

FIX 5:
Enter the server name correctly.  (Example: “localhost\primavera”)

1. GoTo Start, Run and type “cmd” and hit <Enter>


2. At the command prompt, type: “osql -U sa -P prima -S localhost\primavera” and hit <Enter>


3. At the 1> prompt, type: “select name from sysdatabases” and hit <Enter>


4. At the 2> prompt, type: “go” and hit <Enter>


5. This will return a list of all databases on the server.  If databases were created successfully, you should see “pmdb$primavera” and “mmdb$primavera”

FIX 6:
Run ConfigAsst.exe from CD1 to create databases:  (See admin guide pg. 36)

FIX 7:
Start the database windows service for the MSSQL instance

Set the service to Automatic so it will restart after a shutdown of the machine.

If running full SQL 2000, Authentication setting is set to “Windows Only”. 

FIX 8:

Within Enterprise Manager, right click on servername, go to “Properties”.  On Security tab, set Authentication to “SQL Server and Windows”

The SQL port was changed on the server and either: 1.) the new port is not dynamcially resolving, or 2.) there is already a static port specified on the client machine.

FIX 9:  (to be done from the machine that can’t connect to the database)

1. Click: Start, Run.


2. Type: cliconfg, Click: OK.


3. In the SQL Server Client Network Utility, click: ‘Alias’ (tab)


4. If an alias is already defined, and its name matches the server name being used while configuring a Primavera Project Management connection, adjust the port number and close.  Otherwise, proceed to the next step:
    


5. Click: ‘Add’ (button), TCP/IP.


6. Type a name in ‘Server alias’.


7. ‘Server name’ must match the database location.
   NOTE: Specify the instance name, if there is one.


8. ‘Dynamically determine port’ should NOT be checked.


9. ‘Port number’ must match the new port of the SQL Service.


10. Click: OK, Apply, OK.

The application was installed using the “Client Applications” whereas the intention was to install the Stand-alone version of the software, which installs a database locally for the client to connect to.

FIX 10:

Uninstall the software and re-install, choosing Stand-alone rather than Client applications

The client machine and database server are on different domains.

FIX 11:

Use the Database Server’s IP address, when prompted for ‘Host Name’.

The SQL Database Server TCP port was changed and the Server was never restarted.

FIX 12:

Restart the SQL Server.

Error: Unable to resolve privileged username and password

Failed Logon:com.jnetdirect.jsql.u:

TCP/IP connection failed to host:java.net.ConnectException: Connection refused.

connect url:jdbc:JSQLConnect://localhost:1433/database=PMDB

Error: Unable to resolve privileged username and password

Failed Logon:com.jnetdirect.jsql.u:

TCP/IP connection failed to host:java.net.ConnectException: Connection refused.

-or-

An unchecked buffer exists in an encryption function.  A buffer overrun can occur as a result and can be used to either cause the SQL Server service to fail, or to cause code to run in the security context of the server that is running SQL Server.

For more information about this problem, please refer to the following URL

http://support.microsoft.com/kb/322853/en-us

http://www.microsoft.com/downloads/details.aspx?FamilyID=9552d43b-04eb-4af9-9e24-6cde4d933600&displaylang=en

http://www.microsoft.com/technet/prodtechnol/sql/2000/downloads/servicepacks/sp3.mspx

1.  Ensure that you have a full and current backup of the Project Management database.

2.  Run the following query against the database (substituting the name of the admuser in the PMDB schema if necessary).  Please be aware that any rows returned from that query are orphaned task records.

select * from admuser.task where proj_id not in (select proj_id from admuser.project);

3.  If the users of the Project Management software feel that their projects are complete and are working correctly, delete the orphaned records, using the following SQL statement:

delete from admuser.task where proj_id not in (select proj_id from admuser.project);

To resolve this issue with Interbase:

1.  Make a backup of the database.

2.  Open the Interbase Console by going to Start, Programs, Interbase, Interbase Console.

3. Log into the Interbase Console by right clicking the local server and selecting login.  Enter sysdba as your username and masterkey as your password.

4.  Expand the local server, right click database and select register.  When the box comes up select the location of your gdb file, and again enter sysdba and masterkey as the username and password.

5.  Go to the Tools menu, and select Interactive SQL.

6.  Enter the following line into the command window:

7.  Run a delete statement to get rid of the task_id’s for the invalid proj_id’s:

Delete from Task where task_id = <task_id that was returned in the previous select statement>;

    delete all the task_id’s that came back from the select statement

8.  Go to the Transactions menu, and choose Commit.

You will now be able to upgrade the database.

ex: DELETE FROM ADMUSER_1.PROJISSU WHERE PROJ_ID = :PROJ_ID and (WORKSPACE_ID IS NOT NULL)

Enabling Server Roles for privuser has the effect of changing the logical delete views used by Privuser to filter out logically deleted records from displaying in the application. 

Missing Logical Delete Views could also cause the application to look directly at the physical tables.

The “PRIVATE” database User is incorrectly configured as ADMUSER, rather PRIVUSER.

If ADMUSER is accessing the tables it looks DIRECTLY at the table and sees ALL records including logically deleted records.
If PRIVUSER is accessing the tables it uses the privuser VIEWS of the table that filter out the logically deleted records.

Multiple PMDB Schemas located in the same Oracle Instance.  PRIVUSER has GRANT SELECT, INSERT,UPDATE, DELETE for all tables in both schemas. 

Fix 1:

Make sure, in SQL Server Enterprise Manager, that security logins privuser and pubuser are not granted Server Roles.

To verify and correct this issue:

1. Log into SQL Server Enterprise Manager as an administrator.
    


2. Expand the Security folder and highlight Logins.
    


3. Right click on Privuser and select Properties.
   
   
    


4. Go to the Server Roles tab and uncheck ALL boxes for server roles:
   
   
    

See also Solution ID prim44013 - What roles and rights should PRIVUSER and PUBUSER have for Microsoft SQL Server?

Run Schema Validation to check for missing Logical Delete Views. Recreate missing logical delete views with the statements found in the create scripts in the install\database\scripts directory for the type of database being used.

SEE ALSO: prim29487 - ”How to validate a PMDB / MMDB database schema?”

Administer Private database logins to change the DB User to the ‘privuser’ User account.

SEE ALSO: Solution ID prim24867 - ”How to administer the private database logins username and password”  for instructions on changing the private database login.

Revoke the SELECT, INSERT, UPDATE, DELETE privilege for PRIVUSER for the incorrect schema. 

FOR EXAMPLE:

Schema1′s Users  – ADMUSER, PRIVUSER and PUBUSER. ( Correct Schema )

Schema2′s Users – ADMUSER_1, PRIVUSER_1 and PUBUSER_1. ( Incorrect Schema )

REVOKE SELECT, INSERT, UPDATE, DELETE ON ADMUSER_1.ACCOUNT to PRIVUSER;

The revoke statement needs to run for every table in the schema.  You can use the ordp_grn.sql script found on CD1 in the  \install\database\scripts\install\or\drop\pmdb directory.

This script will need to be edited to add the schema owner (admuser_1.) before the name of each table. 

The PRIVUSER will still have the SELECT, INSERT, UPDATE, DELETE privilege on the ADMUSER SCHEMA. 

Here are the steps to use the Alphablox Repository to repoint Alphablox to a new or restored Alphablox database:

1. IMPORTANT: Make sure Primavera Service/BEA Weblogic is stopped.


2. Go to Start -> Programs -> IBM DB2 Alphablox -> AlphabloxAnalytics -> Utilities -> Repository Conversion Utility OR run the following file: <db2alphablolx_dir>/Tools/convert/ConvertRepository.exe where <db2alphablox_dir> is the directory in which DB2 Alphablox is installed.  It will look like a DOS window.


3. Select #6 “Change DB2 Alphablox to use a different repository”


4. Select #2 “Database repository is the target”
   
   
   FOR MSSQL:
   5.  Select #1 “Microsoft SQL Server”
   6.  Enter the server host name where the Alphablox database is located
   7.  Enter the port #
   8.  For Catalog, enter the name of the Alphablox database (ex: AlphabloxDB)
   9.  For Schema, just hit return
   
   FOR ORACLE:
   5.  Select #1 “Oracle”
   6.  Enter the server host name where the Alphablox database is located
   7.  Enter the port #
   8.  For SID, enter the name of the instance where the Alphablox database resides
   9.  For Schema, enter the name of the Alphablox database (ex: AlphabloxDB)

10.  For User, enter the user to connect to the DB, ex: sa or pvuser.
11.  Enter the password for the User.
12.  Then enter a 1 if everything has been entered correctly.
13.  Once finished, restart the Primavera Service.
14.  Check the server log to make sure Alphablox says it started:

<Notice> <WebLogicServer> <BEA-000355> <Thread “ListenThread.Default” listening on port 7001, ip address *.*>
DB2 Alphablox (AlphabloxAnalytics) started (02/07/07 17:14:44)

Primavera 4.1 and earlier: Used Borland technology where the aliases were stored in C:\Program Files\Borland\Common Files\BDE\IDAPI32.cfg file (viewable in Borland BDE Administrator control panel), and referenced in the PM.ini file by Alias Name, public user name, password and group id.  The client login window Database Name field is populated with the alias references stored in the PM.ini file.

Primavera 5.0: Uses Borland DBXpress technolgy to store and manage the database aliases. The alias information is stored in Windows registry keys and in Borland DBExpress initialization files.

The client login window Database Name field is populated with the alias stored in the Windows registry keys.

HKEY_LOCAL_MACHINE\Software\Primavera\Databases
and/or
HKEY_CURRENT_USER\Software\Primavera\Databases

The registry keys reference all aliases that are created on the PC where the application resides.  The keys hold the database connection Public username, password and group id information to connect to the DB.

HKEY_CURRENT_USER\Software\Primavera\Databases\[PM | MM ]\CurrentAlias stores the last alias that was used by a user to login into the client application:

From the DBExpress side instead of storing aliases in an IDAPI32.cfg, Borland DBExpress uses two INI files. 

• C:\Program Files\Common Files\Borland Shared\DBExpress\DBXConnections.ini  (connection information)


• C:\Program Files\Common Files\Borland Shared\DBExpress\DBXDrivers.ini  (driver information)
   

Under HKEY_LOCAL_MACHINE\SOFTWARE\BORLAND there are two registry keys that point to these two INI files that store dbExpress aliases (DBXConnections.ini) and driver information (DBXDrivers.ini).

You can manually edit the DBXConnections.ini file to remove aliases.

Primavera 5.0 Service Pack 1 or later has been tested with Windows 2003 Service Pack 1.

See the following solution for links to download:
- an installer for Primavera 5.0 Service Pack 1 for the desktop client applications that includes an updated driver.

- replacement files for the CD1:\install\database directory,  including the ConfigAssist database wizard and LDAP ConfigWizard along with an updated driver (only needed if you are experiencing issues upgrading a SQL SERVER database or creating a new SQL SERVER database on a Windows 2003 SP1 SERVER)

Solution ID: prim45999 ”Primavera Project Management version 5.0 Service Pack 3″

NOTE: A remastered Primavera 5.0 SP1 CD 1 is available that includes the updated files and installers. Please contact Primavera Support if you would like the remastered CD shipped to you.

Ensure that all instances of the dbexpsda.dll has been replaced with the newer version.