Quantcast
Channel: Primavera Online Interaction » PRIVUSER
Viewing all 82 articles
Browse latest View live
↧

prim12076:Error: “The login name you specified was not found. Please use a different login name or choose Cancel to exit the application”

April 6, 2013, 11:26 am
$
0
0
Solution ID: prim12076
Error: "The login name you specified was not found. Please use a different login name or choose Cancel to exit the application"
Status: Reviewed
Version(s): 4.0, 4.1, 5.0

Problem: Error: “The login name you specified was not found.  Please use a different login name or choose Cancel to exit the application”
Problem:

Error: “The login name you specified was not found.  Please use a different login name or choose Cancel to exit the application” logging into MM Oracle database
Cause:

Both PM and MM were created in the same Oracle instance.
Fix: Ensure you are entering a correct username.

A list of users who can log into Project Manager / Project Management can be found by logging in as an Admin Superuser and clicking on Admin, Users.


Alternatively, try running the following query through Query Analyzer or SQL Plus:


select user_name from users where user_id in (select user_id from usereng where db_engine_type=’PM’)
Fix: Solution #2

If both PM and MM were installed into the same Oracle instance, it was necessary to create non-default usernames when creating the MM database.  DBCONFIG.EXE may not have been configured properly for the MMDB connection.   Check to make sure that the Hostname, Database name, and the Oracle Connection string are pointed appropriately.  DBCONFIG also needs to connect to the MM privuser and pubuser accounts for successful connections to occur.  This would include altering Private Database Logins.



Information for performing this can be found in Appendix A of the Admin Guide.

↧
Search

prim12417:Error opening Project Management : “Exception EVirtualTableError in module PM.EXE at XXXXXXXX. TCVirtualTable.OptFieldIndexOf: VTable is not loaded – PROJECT.

April 18, 2013, 9:15 pm
$
0
0
Solution ID: prim12417
Error opening Project Management : "Exception EVirtualTableError in module PM.EXE at XXXXXXXX. TCVirtualTable.OptFieldIndexOf: VTable is not loaded – PROJECT.
Status: Reviewed
Version(s): 3.x, 4.0, 5.0, 6.0

Problem:

Error opening Project Manager after upgrading Oracle database:


Exception EVirtualTableError in module PM.EXE at XXXXXXXX.


TCVirtualTable.OptFieldIndexOf: VTable is not loaded – PROJECT.
Problem: Error opening Project Management after restoring SQL 2005 database.
Cause: Oracle:  This error will occur if selecting ‘admuser’ as the Privileged Database Username:
Fix: Go through upgrade again and:

Oracle:  Select ’PRIVUSER’ as the Privileged Database Username:


Fix: Use DBCONFIG to Administer Private Database Login.  “How to administer the private database logins username and password”
↧
↧

prim13533:”Error: Invalid Database. The database you are connecting to is not a Methodology Manager Database” when logging into MMDB.

April 24, 2013, 8:36 pm
$
0
0
Solution ID: prim13533
”Error: Invalid Database. The database you are connecting to is not a Methodology Manager Database” when logging into MMDB.
Status: Reviewed
Version(s): 3.5, 3.5.1, 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1

Problem: ”Error: Invalid Database. The database you are connecting to is not a Methodology Manager Database” when logging into MMDB.  
Cause: Oracle instance has 2 schemas.  MMDB database login and username was changed to Privuser1.
Fix: Use Database Configuration for Methodology Manager to Administer Private Database Logins.

1.  Go to Start/Programs/Primavera/Help and Utilities/DB Config for Methodology Management.  (for version 5.0, go to Start, Programs, Primavera, Help and Utilities, Database Configuration


2.  Choose “Administer private database logins”



Note: Screen shots for version 4.1 and earlier:
Choose Administration tasks (licenses, passwords, etc)”


Click Next then choose “Administer private database logins”


Note: Screen shot for version 5.0:


3.  Select the database connection.




4.  Change the Username and password.



NOTE:  Blank out the password and type in the new, full password.


5.  Double click in the DB username and Password fields to blank out and re-enter the new username and password.



E.g. in the screengrab below, change privuser to privuser1 and change the password accordingly


6.  Click Finish.
↧

prim13587:What is the Database version for 4.1

April 25, 2013, 4:57 am
$
0
0
Solution ID: prim13587
What is the Database version for 4.1
Status: Reviewed
Version(s): 4.1

Problem: What is the Database version for 4.1
Fix: To find the Database Version run this query:

SQL Server: Connect as PRIVUSER


Oracle: Connect as ADMUSER


Select database_version from prefer:

Fix: The 4.1 database version is:

 PMDB,0410.0001.0001.0002
↧

prim13661:What is the name of the table and field which hold the project status codes ( active, planned, inactive , and what if) which are located within the Projects View/General tab?

April 25, 2013, 2:12 pm
$
0
0
Solution ID: prim13661
What is the name of the table and field which hold the project status codes ( active, planned, inactive , and what if) which are located within the Projects View/General tab?
Status: Reviewed
Version(s): 4.0, 4.1, 5.0

Problem: What is the name of the table and field which hold the project status codes ( active, planned, inactive , and what if) which are located within the Projects View/General tab?
Fix: The table name is Projwbs and the field is status_code

Within query analyzer (SQL) you can run the following select statement logged in as privuser to retrieve a list of the type of status fields:


select distinct status_code from projwbs
↧
↧

prim13721:How to connect Cost Manager / Cost Management to an Oracle Project Manager / Project Management database.

April 25, 2013, 5:20 pm
$
0
0
Solution ID: prim13721
How to connect Cost Manager / Cost Management to an Oracle Project Manager / Project Management database.
Status: Reviewed
Version(s): 3.5.1, 4.1, 5.0, 6.1, 6.2, 6.2.1

Problem: How to connect Cost Manager / Cost Management to an Oracle Project Manager / Project Management database.
Fix: In Windows Explorer, go to the My Documents folder.  Right-click and select New, Microsoft Data Link. 

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



In the Connection tab, enter the data source that is in your TNSNAMES.ORA file (where the PMDB database is located).  Enter the Privuser username and password that you setup the PMDB database with.  Check off Allow saving password option.


 


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

prim14043:Can Windows Authentication Mode in SQL Server be used with Project Manager?

May 7, 2013, 9:36 am
$
0
0
Solution ID: prim14043
Can Windows Authentication Mode in SQL Server be used with Project Manager?
Status: Reviewed
Version(s): 4.0, 4.1, 5.0, 6.0, 6.1, 6.2

Problem: Can Windows Authentication Mode in SQL Server be used with Project Manager?
Fix: Windows Authentication Mode can not be used with Project Manager.  SQL Server must run in Mixed Mode authentication because privuser and pubuser must be able to authenticate to the database.
↧

prim14073:How toadda new license to P6

May 7, 2013, 2:33 pm
$
0
0
Solution ID: prim14073
How to add a new license to P6
Status: Reviewed
Version(s): 4.0, 4.1, 5.0, 6.0

Problem: How to add a new license to P6
Fix: To install a new license, the License and Database Configuration application (available at Start > Programs > Primavera Enterprise) is used.  Run the application and it will open into a wizard.

1.  On the first screen, choose “Do not use INI settings (admin functions only)” and hit Next



2.  Choose Configure Application License and hit Next



3.  Choose “Specify a database alias” and select, from the drop-down list, the relevant database.  Hit Next



4.  Enter the Privuser username and password (the default password is “privuser”) and hit Next



5.  Click “Load from file…”



6.  Search for the file, select it and then hit OK.  You will be asked to confirm.



 7.  Hit Finish
Fix:

This information is also available in the Administrator’s Guides for the following Products (NB each link takes you to the download page for the relevant Administrator’s Guide):
↧
Search

prim14092:How to attach and detach database files in SQL Server / MSDE 2000/SQL 2005?

May 8, 2013, 4:19 pm
$
0
0
Solution ID: prim14092
How to attach and detach database files in SQL Server / MSDE 2000/SQL 2005?
Status: Reviewed
Version(s): 3.5.1, 4.0, 4.1, 5.0, 6.0, 6.1, 6.2

Problem: How to attach and detach database files in MSDE 2000?
Problem: How to attach and detach database files in SQL 2005?
Problem: How to restore mdf and ldf files in MSDE 2000?
Problem: How to restore mdf and ldf files in SQL 2005
Problem: How to move a database to another computer or database server instance?
Problem: How to detach the MDF and LDF files and connect them to another MSDE server?
Problem: How to attach database files to SQL?
Fix:

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.
     
Fix:

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.
Fix:

To delete a database called “PMDB$PRIMAVERA”:



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

prim14139:Cannot open user default database

May 8, 2013, 6:14 pm
$
0
0
Solution ID: prim14139
Cannot open user default database
Status: Reviewed
Version(s): 3.5.1, 4.0, 4.1

Problem: Cannot open user default database
Cause: No default database in Enterprise Manager
Fix: In Enterprise Manager go to Security and then Logins


Right click on the user and assign a default database for Privuser and Pubuser
↧

prim14224:How to backup / restore a Primavera Contractor 4.1 Database?

May 9, 2013, 5:18 am
$
0
0
Solution ID: prim14224
How to backup / restore a Primavera Contractor 4.1 Database?
Status: Reviewed
Version(s): 4.1, 5.0

Problem: How to backup / restore a Primavera Contractor 4.1 Database?
Problem: Primavera Contractor 4.1 Database Backup Utility
Problem: Primavera Contractor 4.1 Database Restore Utility
Fix: SEE ALSO: prim33699 - Are there GUI tools available, to backup / restore Primavera 5.0 databases that run on MSDE 2000?
Fix: SEE ALSO: prim46035 - ”How to backup and restore a Primavera 5.0 database, running on MSDE 2000 (stand-alone)?”
Fix: GUI Method:

DISCLAIMER:

The Primavera Contractor Database Backup & Restore Utilities are 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 apply the Primavera Contractor Database Backup & Restore Utilities do so at their own risk.  Primavera Systems Inc. will not be responsible for any problems resulting from the use of this utility.


NOTE: The Primavera Contractor 4.1 Database Backup & Restore Utilities run with the following default parameters:



Server = localhost
Database = pcondb
SQL User = sa
sa password = sa


If the Microsoft SQL Server Desktop Engine (MSDE) password is not “sa”, please contact Primavera Customer Support.


Primavera Contractor 4.1 Database Backup Utility:



  1. Either:


  • CLICK HERE to download the Primavera Contractor 4.1 Database Backup Utility.
     (or)

  • Locate it on the Contractor 4.1 CD, inside of: <drive>\Support\pmconbackup.exe

  • Once saved / located locally, double-click: pmconbackup.exe
     

  • Click: Browse to select a destination folder for the database backup file.
     

  • If desired, enter a file name.  The default file name is: “pmconbackup.bak”
     

  • Click: Backup to begin the database backup.

    • Primavera Contractor 4.1 Database Restore Utility:



    1. Either:


    • CLICK HERE to download the Primavera Contractor Database Restore Utility.
       (or)

    • Locate it on the Contractor 4.1 CD, inside of: <drive>\Support\pmconrestore.exe
       

  • Once saved / located locally, double-click: pmconrestore.exe
     

  • Click: Browse to select a valid database backup file to restore.
     

  • Click: Advanced Options, and specify the correct Host name, (new) Database name, Username and Password.
     
    NOTE: If you wish to restore over an existing database, please backup the existing database first.
     

  • If you wish to overwrite an existing database, check the “overwrite database” option.
     

  • Click: Restore

    • NOTE: The Primavera Contractor 4.1 Restore Utility is hard-coded to place database files into the following location:



    C:\Program Files\Microsoft SQL Server\MSSQL\Data\


    If the location does not exist or is unavailable, an error will result.
    Fix:

    Script Method:


    Run the following commands from a command prompt:


    BACKUP:



    osql -U sa -P sa -S <machine_name or localhost>\primavera -d pcondb


    1>backup database pcondb to disk = ‘c:\<path>\pcondb.bak’
    2>go


    -where <path> is the directory where the backup file will be created.


    NOTE:  Once the backup file is created, it should be moved to a different location; by default upon running the script again, the “pcondb.bak” file will be appended to, rather than overwritten. To have the backup process overwrite and replace any existing c:\<path>\pcondb.bak file if one exists, modify the backup syntaxas follows (use caution, as once the current file is overwritten it is irreversible):
                     backup database pcondb to disk = ‘c:\<path>\pcondb.bak’ with init


    RESTORE:



    osql -U sa -P sa -S <machine_name or localhost>\primavera


    1>restore database pcondb from disk = ‘c:\<path>\pcondb.bak’ with recovery,
    2>move ‘pcondb_dat’ to ‘c:\Program Files\Microsoft SQL Server\MSSQL$PRIMAVERA\data\pcondb_dat.mdf’,
    3>move ‘pcondb_log’ to ‘c:\Program Files\Microsoft SQL Server\MSSQL$PRIMAVERA\data\pcondb_log.ldf’
    4>go


    1>use pcondb
    2>exec sp_change_users_login ‘Update_One’, ‘pubuser’, ‘pubuser’
    3>go

    1>use pcondb
    2>exec sp_change_users_login ‘Update_One’, ‘privuser’, ‘privuser’
    3>go


    -where <path> is the directory where the backup file is located.


    NOTE: The ‘move’ statements above assume that Contractor was installed using CD’s with a Copyright date in 2005.  If the date was 2004, you may need to remove ”$PRIMAVERA” from both of the ‘move’ statements.  Contact Primavera Support if assistance is needed.
    ↧

    prim14403:Error: “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.” when accessing Project Management

    May 10, 2013, 1:50 am
    $
    0
    0
    Solution ID: prim14403
    Error: "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." when accessing Project Management
    Status: Reviewed
    Version(s): 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1

    Problem:

    How to convert a Concurrent User to a Named User in MSDE 2000.
    Fact: MSDE 2000
    Problem: Error:  “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.” when accessing Project Management.
    Problem: After installing and either selecting to load the sample data or to create a new database, the following error appears:

    “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. )


     
    Problem: Cannot log on new user, maximum number of concurrent user(s) allowed is 0..
    Problem: Named user vs concurrent user.
    Problem: Concurrent users allowed is 0.
    Problem: Maximum number of concurrent user(s) allowed is 0 on standalone installation.
    Problem: Cannot log in new user.
    Cause: The sample database and new databases have the Admin user set with a concurrent user license. However, if the license file applied during the installation does not have any concurrent licenses for Project Management this error will occur.
    Fix:

    There are several ways to correct this problem.  Choose from any of the solutions below:


     


    Solution 1:


     


    Download the attached CONCURRENT.TXT file and apply this new license.  The license contains one concurrent user.  After applying the license, choose Admin, Users and set the Admin user to have a Named license for Project Management.  After making this change, apply your correct license file.



    Click here for detailed instructions on loading a license file.


     


    License file for download:  1NU_1CU_TEMP_exp122009.txt
     


    Note:  This license file expires on 12/31/2009.
    Fix:

    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.

    Fix: Solution 3:

    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. 
    Fix:

    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
    ↧

    prim14482:The User Preference to set Email Protocol is grayed out for most users

    May 10, 2013, 11:03 am
    $
    0
    0
    Solution ID: prim14482
    The User Preference to set Email Protocol is grayed out for most users
    Status: Reviewed
    Version(s): 4.0, 4.1

    Fact: The Email Protocol will only be grayed out for non- Admin Superuser accounts.
    Problem: The User Preference to set Email Protocol is grayed out for most users. With the Email Protocol grayed out, users can not switch from Internet to MAPI or vice versa.
    Fix: This is known problem in Project Management will be corrected in a future release.

    Workaround:


    By default, E-Mail Protocol is set to Internet. To change all users to MAPI, run the following command from a SQL prompt:


    For Oracle, log in as admuser and run the following statement:



    update users set email_type =’ET_MAPI’


    For SQL, log in as privuser and run the following statement:



    update users set email_type =’ET_MAPI’
    ↧
    ↧

    prim15291:API error: “unable to load database instances”

    May 13, 2013, 11:48 pm
    $
    0
    0
    Solution ID: prim15291
    API error: "unable to load database instances"
    Status: Reviewed
    Version(s): 4.1

    Problem: API error: “unable to load database instances”
    Cause:

    The Oracle database being accessed by the API is not using the supported charactersets WE8MSWIN1252 and UTF8,
    Fix:

    Workaround 1:  Change the P3e Oracle character Set to a supported one.
    Fix:

    Workaround 2:  If using characterset WE8DEC please follow the instructions below


    1. Copy the attached Jar file to your \J2SDK1.4.1.03\Jre\lib\ext folder.


    2. Log into SQL*plus as Privuser and run the attached db_to_iana_charset.sql script.


    3. Restart the API server.


    prm-csprovider.jar

    DB_TO_IANA_CHARSET.SQL
    ↧

    prim15292:Can the characterset WE8DEC be used on an Oracle databas?

    May 14, 2013, 12:37 am
    $
    0
    0
    Solution ID: prim15292
    Can the characterset WE8DEC be used on an Oracle databas?
    Status: Reviewed
    Version(s): 4.1

    Problem: Can the characterset WE8DEC be used on an Oracle databas?
    Problem: The API will not support using the character set WE8DEC.
    Fix: You can use the character set, although only charactersets  WE8MSWIN1252 and UTF8 were tested and supported and the API will not support using the character set WE8DEC. 

    Workaround:


    To use the characterset WE8DEC with the API


    1. Copy the attached Jar file to your \J2SDK1.4.1.03\Jre\lib\ext folder.


    2. Log into SQL*plus as Privuser and run the attached db_to_iana_charset.sql script.


    3. Restart the API server.


    prm-csprovider.jar


    DB_TO_IANA_CHARSET.SQL
    ↧
    Search

    prim15689:How to change an Application User’s Password and how to get a list of users without logging into Project Management

    June 17, 2013, 11:57 pm
    $
    0
    0
    Solution ID: prim15689
    How to change an Application User’s Password and how to get a list of users without logging into Project Management
    Status: Reviewed
    Version(s): 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1, 7.0



    Problem: How to change an Application User’s Password
    Problem: How to get a list of users without logging into Project Management
    Problem: How to change Admin password for Project Management
    Fix: Go to Start/Programs/Primavera/Help and Utilities/DB Config for Project Management

    1. Welcome screen, select next



    2. What would you like to do screen.  Select the radio button next to Administration tasks (licenses, passwords, etc.)



    3. Select Administration Task Screen.  Select Change an application users’s password



    4. Select Database Alias screen.  Select the database alias of the database the user needs to access.



    5.  Log on as Administrative User screen, enter in the privuser username and password and select next.



    6.  Change application password screen.  Select the username whose password needs to be changed, then enter a new password and confirmation, and click Next.



    7.  If successful you will see the following window:



    8.  On the next screen select finish.
    ↧

    prim15885:Error(s): “Database ‘PMDB’ cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.” / “Cannot associate files with different databases.”

    June 19, 2013, 12:09 am
    $
    0
    0
    Solution ID: prim15885
    Error(s): "Database ‘PMDB’ cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details." / "Cannot associate files with different databases."
    Status: Reviewed
    Version(s): 4.0, 4.1, 5.0



    Problem: Error: “Database ‘PMDB’ cannot be opened due to inaccessible files or insufficient  memory or disk space.  See the SQL Server errorlog for details.”
    Problem: Msg 5173, Level 16, State 1, Server CCC-IL-FS1, Line 1
    cannot associate files with different databases.
    Msg 945, Level 14, State 2, Server CCC-IL-FS1, Line 1
    Database ‘PMDB’ cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
    Log file ‘E:\MSSQL\Data\PMDB_LOG.LDF’ does not match the primary file. It may be from a different database or the log may have been rebuilt previously.

     
    Problem: Symptom #2

    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
    Cause: The LDF file may have become too large, or corrupted.
    Fix:

    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.
    Fix:

    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
    ↧
    ↧

    prim15921:How toload an incremental license

    June 19, 2013, 5:33 am
    $
    0
    0
    Solution ID: prim15921
    How to load an incremental license
    Status: Reviewed
    Version(s): 3.5, 3.5.1, 4.0, 4.1, 5.0, 6.0, 6.1, 6.2



    Problem: How to load an incremental license
    Problem: How to apply an incremental license file
    Problem: How to apply a product license and/or an incremental license file.
    Fix: To see if the license file is an Incremental license file, open the license.txt file in MS Notepad to view a readable summary. The License File Type will show “Incremental License” eg. :

    // COMPANY NAME
    // US
    // Serial number: ########
    // Licensed for Release(s): INCR
    // License issued for :- Primavera
    // License File Type :- Incremental License
    // Database Vendor :- NONE
    // Licensed Issued to :- Customer
    // Project Management NU(0), CU(1)
    // Portfolio Analysis NU(0), CU(1)
    // Timesheets NU(0), CU(0)
    // myPrimavera Portfolios NU(0), CU(0)
    // myPrimavera Projects NU(0), CU(0)
    // myPrimavera Resources NU(0), CU(0)
    // Methodology Management NU(1), CU(0)
    // Contractor NU(0), CU(0)
    // ContractorMaxDomains(0), MaxTasksPerDomain(0)
    // Integration API NU(0), CU(0)


    Note: To load the incremental license file the product license file must be loaded first. The following procedure is the same for either type file.


    After the product license has been loaded, incremental licenses are loaded to bump up the license counts accordingly. 


    1. Go to Start, Programs, Primavera, Help and Utilities, DBConfig. 


    2. Click Next to get started, then choose Administrative tasks.  Click Next.


    3. Choose Configure Database license and click Next. 


    4. Select which database connection to use. 


    5. Accept the default administrative username and password of privuser (unless you have changed the default settings). 


    6. Select the “OPEN” button. Browse to the location of the file, highlight the file and click the “Open” button. 


    7. After receiving the license summary, choose Finish.


    After you are done with the procedure, please check the license summary within the client application and confirm that the incremental quantities were added to the original license file quantities (Open the application and select Help, About Primavera and review the Contact tab or System tab). If there are any problems, please contact Primavera Support.
    ↧

    prim16054:Event Code VTRUD-1790-4

    June 20, 2013, 12:04 am
    $
    0
    0
    Solution ID: prim16054
    Event Code VTRUD-1790-4
    Status: Reviewed
    Version(s): 4.0, 4.1



    Fact: Running Project Architect in MyPrimavera/Primavision/
    Problem: event code VTRUD-1790-4
    Cause: The Methodology Manager setting in the Primavision Administrator are not correct. 
    Fix: Open the Primavision Administrator.

    Open the folder, Custom -> Primavera Configuration -> Database -> Instance -> Methodology Management.



    Set:


    URL to point to the Methodology Manager database


    Check the UserName and Password for Privuser is correct.


    BDEAlias – needs to be set to a BEDAlias on the Job Services server connecting to the Methodology Manager database.


    Save the changes.


    Restart the Primavision Server. 

    ↧

    prim16119:Error: ‘DDL failed to complete. Invalid object name ‘privuser.projshar’

    June 20, 2013, 11:06 am
    $
    0
    0
    Solution ID: prim16119
    Error: ‘DDL failed to complete. Invalid object name ‘privuser.projshar’
    Status: Reviewed
    Version(s): 4.0, 4.1



    Problem:

    Error: ‘DDL failed to complete. Invalid object name ‘privuser.projshar’. CREATE VIEW projshar_bl_view as select ps.proj_id, session_id, access_level, load_status from privuser.project p, privuser.projshar ps where ps.proj_id = p.proj_id union select ps.proj_id, session_id, access_level, load_status from privuser.project p, privuser.projshar ps where ps.proj_id = p.orig_proj_id’ when installing a SQL server database using the Database Wizard.
    Fix: If tip “Error: ’DDL failed to complete. Invalid object name ’privuser.projshar’ when installing a SQL server database using the Database Wizard” does not work, launch SQL Enterprise Manager, go to Security folder, click on Logins, right-click on the PRIVUSER and PUBUSER accounts individually and choose delete.  Go through configasst process again and the utility will recreate the users and create the database.
    ↧
    Viewing all 82 articles
    Browse latest View live
    Search