Note:  If the option ‘Microsoft Data Link’ is not available, see:

Solution ID: prim6765 ”How to create a Microsoft Data Link UDL file for Cost Manager/Cost Management.”

In the Provider tab, select ‘Microsoft OLE DB Provider for SQL Server’:

In the Connection tab, select the SQL Server name (where the PMDB database is located) from the drop-down list.  Select ‘Use a specific user name and password’ and enter the privuser’s username and password.  Make sure Allow saving password option is checked on.   Finally, select the database from the drop-down list (i.e. PMDB):

Select ‘Test Connection’ to make sure the UDL is setup correctly, and you should receive a ‘Test connection succeeded’ message.

Re-launch Cost Manager / Cost Management and you should see the new UDL in the Source Browser.

or:

“Error: Invalid Database. The database you are connecting to is not a Methodology Manager database’ when connecting to a database via Methodology Manager.”

 The database can be connected to successfully when configuring the database connection.

However, on a single-instance oracle installation the issue is likely to be caused by the ‘Private database logins’ being incorrectly configured.

For security purposes there are three database level usernames and passwords that are used for various purposes within the application. These are:

• Admuser – This is used to create the tables/table spaces etc. and administer the database instance. Only to be used by an experienced DBA.


• pubuser  – This is used by the ‘end user’ to ‘connect’ to the database.


• privuser  – This is used by the application to connect to the tables within the database to read and write data.

When a client logs into the Project Manager application, the application connects to the database using ‘pubuser’ and reads the ‘private’ database user details.
The application then logs in (at the database level) using the private username and password, ‘privuser’ which is associated with the ‘pubuser’ username.
By default, in a single instance configuration, ‘privuser’ is associated with the ‘PMDB’ – Project Manager’ database.  Therefore, by logging into the database as ‘privuser’ the application connects to the PMDB schema.

When a client logs into the Methodology Manager application, the application connects to the database using ‘pubuser1‘ and reads the ‘private’ database user details.
The application then logs in (at the database level) using the private username and password, ‘privuser1‘ which is associated with the ‘pubuser1‘ username.
By default, in a single instance configuration, ‘privuser1‘ is associated with the ‘MMDB’ – Methodology Manager’ database.  Therefore, by logging into the database as ‘privuser1‘ the application connects to the MMDB schema.

The issue above can occur when the database names get ‘confused’.

E.g. If the ‘pubuser1‘ login becomes associated with the ‘privuser’ database login then an error will occur.

Please follow the instructions below to resolve the issue.

1. Launch the ‘DBConfig for Project Manager’.


2. Hit the Next button at the ‘welcome’ screen.


3. Select the ‘Administration’ radio-button, and hit ‘Next’.


4. Select the ‘Administer Private database logins’ radio button and hit next.


5. Ensure the correct alias is selected and hit the ”Next’ button on the ‘select or create alias’ screen.
   Note: if the incorrect alias is selected, please:
    




1. Close the DBConfig wizard.


2. Launch Project Manager and select the correct alias.


3. Close the Project Manager and re-launch the DBConfig wizard.
    


6. On the ‘Login as Administrative user’ screen select to login as ‘privuser’ with the associated password.


7. Hit ‘Next’ on the ‘Administer private database users’ information page.


8. Ensure that:

• The ‘Public group id’ = 1


• The ‘DB username’ is ‘privuser’


• The ‘Password’ is the appropriate password for ‘Privuser’
  
  
   

From Methodology Manager:

1. Launch the ‘DBConfig for Methodology Manager’.


2. Hit the Next button at the ‘welcome’ screen.


3. Select the ‘Administration’ radio-button, and hit ‘Next’.


4. Select the ‘Administer Private database logins’ radio button and hit next.


5. Ensure the correct alias is selected and hit the ”Next’ button on the ‘select or create alias’ screen.
   Note: if the incorrect alias is selected, please:
    




1. Close the DBConfig wizard.


2. Launch Methodology Manager and select the correct alias.


3. Close Methodology Manager and re-launch the ‘DBConfig for Methodology Manager’ wizard.
    


6. On the ‘Login as Administrative user’ screen select to login as ‘privuser1′ with the associated password:
   
    


7. Hit ‘Next’ on the ‘Administer private database users’ information page.


8. Ensure that:

• The ‘Public group id’ = 1


• The ‘DB username’ is ‘privuser1‘


• The ‘Password’ is the appropriate password for ‘Privuser1‘
  
  
   

Receive the following two event codes when attempting to run the Size & Complexity Wizard within Project Architect:

Event Code: VTRRS-1450-C

Message:

TCVirtualTable.Refresh: RSRC: Invalid field name.

ORA-00904: “R”.”USER_NUMBER2″: invalid identifier

Context:

1: TfrmSelectBaseMethodology.FormLeave

2: TfrmSelectBaseMethodology.vqsTEMPLATERowChange

3: TfrmSelectBaseMethodology.vqsTEMPLATERowChange

4: TfrmWizDomain.RunNewDomainWizard

5: TCArcturusAssignMgr.InsertPROJWBSRow

6: TfrmSelectBaseMethodology.vqsTEMPLATERowChange

7: TfrmWizDomain.RunNewDomainWizard

8:

9:

10:

Detail:

Type: EDBEngineError

Object Type: TCUltraButton

Database Error:

1: Invalid field name.

Category: 39

Error Code: 10038

Sub Error Code : 54

Server Error Code: 0

2: ORA-00904: “R”.”USER_NUMBER2″: invalid identifier

Category: 51

Error Code: 13059

Sub Error Code : 3

Server Error Code: 904

AND:

Event Code VQCVD-1349-E. TCVirtualQuery. Check VDBEngine Assigned VDBEngine is not currently active.

If the versions are the same:

2.  Edit the MM.INI and check the database alias for Methodology Manager.  Then look at the PM.INI for:

[MethodDatabase]

Alias=MMDB (this will be the name of the MM alias)

These two should be the same.

1. Launch Project Manager, Portfolio Analyst, or Methodology Manager.
2. In the Database field, click on the Ellipse button.
3. Click Add.
4. Click Next.
5. Enter an alias name in the Database Alias field and select the database type in the Driver Type field. Valid options are Oracle, MS SQL, or Interbase.
6a. If you select Oracle, type the Oracle connect string and net protocol. To configure the driver setting, click the version of Oracle
you are using.

6b. If you select MS SQL Server, type the database name and server machine name.

6c. If you select Interbase, enter the path and name of the .GDB file that you wish to connect to.
     For example: C:\PROGRAM FILES\PRIMAVERA P3ec for Construction\DATABASE\PMDB\PMDB.GDB or
     C:\PROGRAM FILES\PRIMAVERA P3ec for Construction\DATABASE\MMDB\MMDB.GDB.

7. Enter pubuser as the username and password for the Public logon info.

8. Click Next and then Finish to complete the wizard.

Notes:

• Please backup a copy of your database prior to running the below SQL statements.


• It is suggested that a DBA or equivalent user execute the queries below.

Have the database administrator perform the following instructions.

NOTE: It is advisable to always create a backup of the database prior to making modifications with manual scripts.

1. Log into the affected database:
    
   For Oracle:  Log into the instance with the administrative user for the schema (e.g. “admuser”)
    
   For SQL Server:  Launch Microsoft Query Analyzer and login as “privuser”
    
   For MSDE:  Open a dos command window (Start > Run >  type ‘cmd’, hit OK)  and log into the instance with OSQL with the following command:
    
               osql -U sa -P password -S server\instance -d database
    
               (where ‘password’ is the administrative password,
                           ’server’ is the name of the MSDE server,
                           ’instance’ is the instance name if applicable,
                           ‘database’ is the name of the database’)
    
   For Interbase:  Launch the Interbase Console, connect to the database in question and login as sysdba/masterkey
    
   
2. Delete the user preferences by running the following script:
    
   Update userdata set user_data = null where topic_name = ‘pm_settings’ and user_id in (select user_id from users where user_name = ‘<username>’)

-where <username> is the user’s login id for Project Management

Note: This will cause the user account to lose all user defined preferences within the software – they will be reset to default settings ( durations in days, show time, etc)  User baselines, layouts, filters, etc. will still be there.

Project Management Instructions:

1. Go to Query Analyzer.


2. Login using the privuser username/password.


3. Type: Select * from users where user_name =’admin’ and run the statement. NOTE: REPLACE admin with DESIRED LOGIN NAME and note the user_id for the user in question.  
   
   
   
    


4. Type the following: Delete from userdata where user_id=<number found in step 3> and topic_name=’pm_settings’  Run the statement. 


5. Login to Project Management as the user, and the user preferences will be re-created as default.

myPrimavera/P6 Web Instructions:

1. Go to Query Analyzer.


2. Login using the privuser username/password.


3. Type: Select * from users where user_name =’admin’ and run the statement. NOTE: REPLACE admin with DESIRED LOGIN NAME and note the user_id for the user in question.


4. Type the following: Delete from userdata where user_id=’<number found in step 3>’ and topic_name=’pweb_settings’  Run the statement. 


5. Login to myPrimavera/P6 Web as the user, and the user preferences will be re-created as default.

Note: This will cause the user account to lose all user defined preferences within the software – they will be reset to default settings ( durations in days, show time, etc)  User baselines, layouts, filters, etc. will still be there.

To delete a user’s preference settings in Oracle, do the following:

Project Management Instructions:

1. Run SQL*Plus.


2. Login in as admuser or equivalent Oracle user.


3. Type: Select * from users where user_name =’admin’ and run the statement. NOTE: REPLACE admin with DESIRED LOGIN NAME and note the user_id for the user in question.


4. Type the following: Delete from userdata where user_id=’<number found in step 3>’ and topic_name=’pm_settings’  Run the statement.


5. Login to Project Management as the user, and the user preferences will be re-created as default.

myPrimavera/P6 Web Instructions:

1. Run SQL*Plus.


2. Login in as admuser or equivalent Oracle user.


3. Type: Select * from users where user_name =’admin’ and run the statement. NOTE: REPLACE admin with DESIRED LOGIN NAME and note the user_id for the user in question.


4. Type the following: Delete from userdata where user_id=’<number found in step 3>’ and topic_name=’pweb_settings’  Run the statement.


5. Login to myPrimavera/P6 Web as the user, and the user preferences will be re-created as default.

To delete a user’s preference settings in MSDE (for Project Management 5.0 stand-alone), do the following:

Project Management Instructions:

• 
  

  Open a MS-DOS Command Prompt window





• Login to osql by typing the following:

osql -U sa -P prima -S localhost\primavera -d pmdb$primavera

• If the login is successful, you will get to a 1> prompt


• Type:

1>delete from userdata where user_id =25 and topic_name=’pm_settings’
        Then hit <Enter>
2>go 
        Then hit <Enter>

Where user_id = the user_id of the user that is corrupt.  See step 3 in first fix statement above.

• Login to Primavera as the user, and the user preferences will be re-created as default.

myPrimavera/P6 Web Instructions:

• 
  

  Open a MS-DOS Command Prompt window





• Login to osql by typing the following:

osql -U sa -P prima -S localhost\primavera -d pmdb$primavera

• If the login is successful, you will get to a 1> prompt


• Type:

1>delete from userdata where user_id =25 and topic_name= ‘pweb_settings’  
        Then hit <Enter>
2>go 
        Then hit <Enter>

Where user_id = the user_id of the user that is corrupt.  See step 3 in first fix statement above.

• Login to myPrimavera/P6 Web as the user, and the user preferences will be re-created as default.

Note: This will cause the user account to lose all user defined preferences within the software – they will be reset to default settings ( durations in days, show time, etc)  User baselines, layouts, filters, etc. will still be there.

1) Verify that the alias information is correct, including Database Name, Database Server, Public Login Id and password, Public Group Id (or if using Oracle the Database Connection String).

2) Check to be sure the SQL service is installed and running.  Check for the service in Start Menu > Control Panel > Administrative Tools > Services.  The Status should be “Started” and the Startup Type should be “Automatic”.

     For PM 5.0 (standalone), service name = MSSQL$PRIMAVERA

     For PM 6.0 and higher (standalone), service name = SQL Server (Primavera)

3) Check to make sure the PM and/or MM database(s) exist on the server. 

     For full SQL 2000:

     Use SQL Enterprise Manager to look for PMDB and MMDB databases.

     For MSDE:

       1.  Open a command prompt window

       2.  At the prompt, type: osql -U sa -P <sa password> -S <server>, press Enter

            NOTE – Default 5.0 Standalone sa password is “prima” and server is “localhost\primavera”

       3.  If logged in correctly, you should receive a 1> prompt.  At the 1> prompt, type: select name from sysdatabases, press Enter

       4.  At the 2> prompt, type: go, press Enter

       5.  This should return a list of databases that are on the server.  Look for the PMDB and MMDB database names.

            NOTE – If the databases do not exist, you will need to create them using the ConfigAsst.exe Utility found on CD1

     For SQL 2005 Express:

       1.  Launch SQL Server Management Studio Express from Start/Programs/Microsoft SQL Server 2005/SQL Server Management Studio Express.

       2.  Connect to the <machine name>\primavera with Windows Authentication.

       3.  Expand the “Databases” folder on the left side.   Look for the PMDB and MMDB database names.

            NOTE – If the databases do not exist, you will need to create them using the ConfigAsst.exe Utility found on CD1

*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          11-Aug-2004 05:15 PM

Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    UCVFR-2024-2
Message:      
  Unique Constraint violated. Field rsrc_id is null.

Context:
  1: TfrmWizImport.wizImportFinish
  2: TfrmWizImport.RunImportWizard
  3: TfrmMain.actProjectsExecute
  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,0350.0005.0004.0002
IMG: IMG Win32 #1000
DLL: (failed to query D:/PRIMAVERA ENTERPRISE 3.5.1/PROJECT MANAGER/../COMMON/BIN/DBCFGLIB.DLL)

System Info
===========
Username: Stuartw   Hostname: STUARTWILLIAMS
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

%T TASKRSRC
%F taskrsrc_id  task_id  proj_id  work_flag  cost_qty_link_flag  role_id  acct_id  rsrc_id 
%R 7014           33521    278       Y                Y                            337       1179     3 

This row references rsrc_id 3.  Compare that to an extract of the table RSRC.

F rsrc_id parent_rsrc_id clndr_id
%R 1169   1209                 590  
%R 1170   1222                 597  
%R 1171   1208                 597  
%R 1172   1221                 597 

However, resource with an ID of 3 does not exist in the RSRC table.

So the row:

%T TASKRSRC
%F taskrsrc_id  task_id  proj_id  work_flag  cost_qty_link_flag  role_id  acct_id  rsrc_id 
%R 7014           33521    278       Y                Y                            337       1179     3 

Would need to be removed from the XER file.

The gbak command-line tool allows both back up or restore of an Interbase database. Only sysdba or database owner can backup a database. gbak is installed in :

[Primavera Install Folder]\Intrbase\bin\gbak.exe

To backup an Interbase database called PMDB.gdb :

          1. At the command prompt navigate to the Intrbase\bin folder

          2. Type the following command :

                    gbax -b -user [username] -password [password] [database] [target]

                    For example : gbak -b -user sysdba -password masterkey c:\databases\pmdb.gdb c:\databases\backups\pmdbbackup.gbk

To restore an Interbase database called pmdbbackup.gbk :

         1. At the command prompt navigate to the Intrbase\bin folder

          2. Type the following command :

                    gbax [-c|-r] -user [username] -password [password] [source] [database]

                    For example : gbak -c -user sysdba -password masterkey c:\databases\backups\pmdbbackup.gbk  c:\databases\pmdb.gdb

                    Note : Using -c will create a new database file, using -b will attempt to restore over an existing file

SQL Server: Connect as PRIVUSER

Oracle: Connect as ADMUSER

Select database_version from prefer:

 PMDB,0410.0001.0001.0002

Note:  If the option ‘Microsoft Data Link’ is not available, see:

In the Provider tab, select ‘Oracle Provider for OLE DB’ 

Note: DO NOT SELECT ‘Microsoft OLE DB Provider for Oracle’.   We do not support this selection for connecting to a Project Manager/Project Management database from Cost Manager/Cost Management.  If you do not have ‘Oracle Provider for OLE DB’ as an option, see Solution ID: prim5265 ”Getting error message during install of Oracle Drivers from the Cost Manager CD” to see how you can go about getting it.

ALSO NOTE: A bug in the latest Oracle Providers for OLE DB (10.1.0.4 or later) prevents successful imports from an Oracle 10g Project Management database.   Use of a supported 9i driver is required when interfacing with a 10g PM database.  Also, the client driver can be 10.2.0.3 or later.  Alternatively, an 11g client driver can be used also.

E.g.

<CD>:\Interbase\PMDB                      :  Project Management Database with the Sample Data
<CD>:\Interbase\PMDB_empty          :  Project Management Database without the Sample Data
<CD>:\Interbase\MMDB                     :  Methodology Management Database with the Sample Data
<CD>:\Interbase\MMDB_empty         :  Methodology Management Database without the Sample Data

SQL 2005

Detaching the Database:

1. Open SQL management Studio Express.


2. Expand Databases and right click on the database to be detached.


3. Go to Tasks->Detach
   


4. Verify all 3 checkboxes are checked and click ok to detach it
   
   
    


5. Copy \ Move the database files to their new location (remember that each database contains a LDF and MDF file).
    
   Default location:
   C:\Program Files\Microsoft SQL Server\MSSQL$PRIMAVERA\Data

Attaching the database

1. Open the Management Studio. Right click Database and choose attach
   
   


2. Click the Add button
   
   
   
    


3. Browse to the .mdf file and click ok
   
   
   
    


4. Verify the database name you are attaching does not conflict with any other databases, then click ok.
   
   
    


5. Resynch the users. Click the New Query button
   
   
    


6. Change the drop down menu to the name of your database, in this example it’s PMDB$PRIMAVERA
   
   
    


7. Copy/Type the following in the Query area:
   
   
    


8. Click the Execute button.
   
   
    


9. Once is has completed create the alias pointing  to the new database.
    

SQL 2000/MSDE

The data and transaction log files of a database can be detached and then moved and\or reattached to another server, or even the same server.  Detaching a database removes the database from SQL Server but leaves the database intact in the data and transaction log files that compose the database.

1. Log into the OSQL Utility, through DOS:
    
   Click: Start, Run
   Type: cmd
   Click: OK
    
   C:\>osql -U sa -P <sa password> -S <machine_name>\<instance_name>
    
   Example (5.0 stand-alone):
   C:\> osql -E -S .\primavera
   
   This will bring up a ” 1> ” prompt.
     


2. Detach the database.
   (In the example, the database will be called “PMDB$PRIMAVERA”.)
    
   1> EXEC sp_detach_db ‘PMDB$PRIMAVERA’
   2> go
    


3. Copy \ Move the database files to their new location (remember that each database contains a LDF and MDF file).
    
   Default location:
   C:\Program Files\Microsoft SQL Server\MSSQL$PRIMAVERA\Data
    


4. Attach the database.
   (In the following example, “PMDB$PRIMAVERA” is the new database name, and “C:\Program Files\Microsoft SQL Server\MSSQL$PRIMAVERA\Data” is the folder where the physical files were moved to in Step 3.)
    
   1> EXEC sp_attach_db @dbname = ‘PMDB$PRIMAVERA’,
   2> @filename1 = ‘C:\Program Files\Microsoft SQL Server\MSSQL$PRIMAVERA\Data\pmdb$primavera_dat.mdf’,
   3> @filename2 = ‘C:\Program Files\Microsoft SQL Server\MSSQL$PRIMAVERA\Data\pmdb$primavera_log.ldf’
   4> go
    
   NOTE:  The MDF and LDF files need to reside on the local server.  They cannot be located on a network drive.
    
   NOTE:  If error “Cannot associate files with different databases.” results, see:
   Solution ID prim15885 - Error(s): ”Database ’PMDB’ cannot be opened due to inaccessible files or insufficient  memory or disk space.” / ”Cannot associate files with different databases.” 
    


5. Resync the ‘privuser’ and ‘pubuser’ passwords.
    
   1> use PMDB$PRIMAVERA
   2> EXEC sp_change_users_login ‘Update_One’,'pubuser’,'pubuser’
   3> EXEC sp_change_users_login ‘Update_One’,'privuser’,'privuser’
   4> go
    


6. (OPTIONAL) Repeat as necessary for the MMDB$PRIMAVERA database.

NOTE: If attaching via SQL Enterprise Manager, you will be prompted for the user account to attach as the owner. Select ‘sa’ user account.

To delete a database called “PMDB$PRIMAVERA”:

After detaching PMDB$PRIMAVERA (Step 2 above), delete pmdb$primavera.mdf and pmdb$primavera.ldf files.

“A problem has occurred with your application license:  Cannot log on new user, maximum number of concurrent user(s) allowed is 0.  Click OK if you would like to see a license summary.”

Receiving the above error message after loading a new license file.

After clicking OK, the following message appears: “License key Summary: ( License Data not valid. )

Solution 2:

Run a script at the database level to change the Admin user from a Concurrent license to a Named license. 

Please follow the steps below to change the ‘admin’ user or user_id = 25 to have a Named User license.
1. Create a folder on your local C drive called PRIMA. e.g. C:\PRIMA

2. Download the UpdatetoNamed.zip file to that newly created folder called PRIMA. (UpdatetoNamed.zip located below) 

UpdatetoNamed.zip

3. Unzip the file and Extract the two files to that PRIMA folder. (Two files should be nulicenseUpdate.sql and changetoNamed.bat)

NOTE: changetoNamed.bat file will have to be edited for your SA password, server name, and database name if they differ. Right click on .bat file, then click on Edit.

- For Version 5.0 Standalone edit the bat file to correct the password, server name and the database name as follows: 
   e.g. osql -U sa -P prima -S localhost\primavera -d pmdb$primavera -i C:\PRIMA\licenseUpdate.sql

- For Version 6.0 Standalone edit the bat file to correct the password, server name and the database name as follows:
   e.g.  sqlcmd -U sa -P Prima123Vera -S localhost\primavera -d pmdb$primavera -i C:\PRIMA\licenseUpdate.sql

4. Double click on the changeName.bat file in the PRIMA folder.

5. After double clicking file screen will flash quickly and close. Now you should be able to log back in with the ‘admin’ user.

For MSDE: use osql commands to switch to a named user from concurrent.

1. Go to Start, Run and type cmd
    


2. At the C:\<machine name> prompt, type:
    
   osql  -U privuser  -P privuser  -S localhost\primavera  -d PMDB$primavera 
    
   The server name, which should be entered after the -S, should be the same as that which is listed in SQL Service Manager (double click the SQL server icon in the bottom right corner of the screen).  In previous versions this has been the machine name only, but now it should be followed by the Instance name \primavera.
    
   
    


3. The cursor should then change to 1>, then type:
    
   update privuser.usereng set named_user_flag =’Y’ where user_id=25
    


4. The cursor should then change to 2>, then type:
    
   go
    
   The output should appear similar to that below.
    
   
    


5. Once these steps are complete, launch Project Management and the login should be successful.

For full Microsoft SQL Sever:

1. Open Enterprise Manager


2. expand the tree to show Databases


3. select the database required (PMDB by default). 


4. Expand the database and select Tables.


5. Select the USERENG table, right click and select ‘open table’ ’return all rows’.


6. In the row where user_ID = 25, change the next column named_user_flag from N to Y. 

Solution 4:

Attached is a zip of a utility to update the licenses in the DB. 

Run the utility, enter correct db connection information.  It is currently set to the 5.0 standalone defaults.

1.  Choose Get.

2.  Highlight the admin user.

3.  Select the Named button. 

4.  Select the Set button to commit to the DB.

licUtil

Some users may get errors regarding msflxgrd.ocx not being registered.

Download the attached msflxgrd.ocx and copy it to the c:\windows\system32 folder, and register with regsrv32.

 msflxgrd.ocx

Auditing User Login \ Logout information in the PMDB database

udopen: operating system error 32(The process cannot access the file because it is being used by  another process.)

FCB::Open Failed: could not open device c:\program files\microsoft sql server\mssql$primavera\data\pcondb_dat.mdf

1. Login to database server instance.
     


2. Detach the database.
    
   Example:
     1> EXEC sp_detach_db ‘PMDB’, ‘true’
     2> go
    


3. Locate the LDF file on the database server.
   (Example location: “C:\Program Files\Microsoft SQL Server\MSSQL\Data\PMDB_LOG.LDF”)
    


4. Rename the LDF file, through Windows Explorer.
   (Example: Change it from “PMDB_LOG.LDF” to “PMDB_LOG_OLD.LDF”)
    


5. Attach the database:
    
   Example:
     1> EXEC sp_attach_db @dbname = N’PMDB’,
     2> @filename1 = N’C:\Program Files\Microsoft SQL Server\MSSQL\Data\PMDB_DAT.MDF’
     3> go
   
   NOTE: It’s both normal, and expected to get a error/warning that a new “LDF” file has been created, after running the command above (Step 5).
    


6. Resync the pubuser and privuser logins.
    
   Example:
     1> use PMDB
     2> EXEC sp_change_users_login ‘Update_One’, ‘pubuser’, ‘pubuser’
     3> EXEC sp_change_users_login ‘Update_One’, ‘privuser’, ‘privuser’
     4> go
    


7. Attempt to connect to the database.

Solution #2

The Windows service MSSQL$PRIMAVERA may have failed to start.  Another program, such as an antivirus or backup software, may have had exclusive access to the file(s) at the time the service attempted to start. 

• Check the SQL Server Log file for error


• Check the Windows Event Viewer for error


• Restart the Windows Service MSSQL$PRIMAVERA

1) Go to Start, All Programs, Primavera, Help and Utilities, Database Configuration

2) Choose Configure my database connections, then choose either Project Management or Methodology Management database

3) Select a database alias.  You can choose whatever name you would like to call it

4) Enter your database name and host name.  For P5 and P6 stanadalone installations the default host name is localhost\primavera and the database name is pmdb$primavera. Choose next.

5) Enter public logon information.  If the defaults have not been changed, pubuser will be the username and password and they should already be entered for you.

6) Click next on Validate Database Connection and Choose finish.Database connections can also be created at the P5 or P6 login screen. Click the ellipse (square) button to the right of database

Choose “Add” and then follow steps 3 through 6 above.

NOTE: Project Management allows users to create multiple database connections. For example it is possible to create a database connection to a networked database on a corporate server and also create a connection for a standalone database running on a laptop for remote use.

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

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

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

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

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

1.  Choose to Create a new Primavera Database

2.  Select Database Type. 

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

3.  Select the Application Database

4.  Select ”Load application data only”. 

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

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

6.  Follow through the rest of the wizard.