|
Below is a list of known issues in the different areas of version 4.0
Language Support
- Version 4.0 is only supported on English operating systems. This international language support issue will be addressed in a subsequent version.
Timesheets
- Overtime costs may not spread correctly when containing negative values.
- When filtering on activity codes, the Not Equal To criteria may not yield an accurate result.
- For user-defined fields on Steps, Indicators are not available through timesheets.
- An error occurs when assigning resources to new activities through timesheets given the following scenario:
1) Add an activity with no resource assignments in Project Manager
2) Log in to timesheets and attempt to assign a resource to that activity. The activity is removed from the screen and the resource is not assigned. This error appears in the Event Viewer.
- The Percent Complete field is editable in timesheets given the following scenario:
1) Set the Admin Preference to ‘Log Hours on Activities Before the Activity Start Date’ option to False
2) Set the option ‘Resources Can Edit Activity Assignment Percent Complete’ in Projects, Resources
3) Restart Group Server service
4) Add an activity and assign a resource
5) Set an Actual Start date on the activity
6) Log in to timesheets
7) Open a timesheet for a time period before the Activity Start Date
8) Select the activity
9) Select the Resource tab
10) Change the Percent Complete value
Given this scenario, an error message appears every time a user clicks the activity assignment. As a workaround, change the Percent Complete value only when the activity is opened in the correct Timesheet Period when the ‘Log Hours on Activities Before the Activity Start Date’ option is false.
- When sorting, resource details may not always correspond to the selected resource.
Project Manager
- Timescale Logic Diagrams (TSLD) — Performance
By default, the TSLD will not rearrange more than 3,000 activities in a single node, and it will not calculate for more than five (5) seconds on a single node. This default behavior can be changed by adding the following entry to the PM.INI file (located in the ‘Project Manager’ directory of your Primavera installation):
[TSLD]
MaxTSLDCount=n (n = the number of items to be collapsed. -1 overrides the setting and collapses any number of activities.)
MaxTSLDTime=n (n = number of seconds to calculate. -1 overrides the setting and calculates as long as necessary.)
- Language translations are not complete for the Set Language option.
- When running Job Services/Batch Reports, formatting issues exist for user-defined fields.
Import/Export
- When importing version 3.5 XER files into version 4.0, user-defined fields with a null value in 3.5 may import with a value of 0 (zero) in 4.0.
- For MSP and XER exports, users must have the View Resource Costs global privilege to export Resource Price/Units data. If a user without this privilege exports a project in XER format, all Resource Price/Units may be deleted when the project is imported back to Project Manager.
- For MSP and XER exports, users must have the View Project Costs/Financials project privilege to export cost data.
- Microsoft Data Access Components (MDAC) should be installed on any machine importing/exporting data to/from Microsoft Project. Machines that do not have MDAC installed may encounter problems when exporting projects to Project Manager. In most cases, MDAC is automatically installed when you install Microsoft Project. If MDAC is not installed on your machine, visit www.microsoft.com to download the latest version.
Job Services
The default behavior of the Primavera Job Service has been modified to address some performance issues. If desired, the default behavior can be changed by adding any of three new [Options] settings in PRMJOB.INI (normally located in C:\WINNT\system32 or C:\Windows\System32).
- To improve performance when summarizing large jobs, the job service commits data intermittently during the EPS summary instead of committing all data at the end of the summary. By default, data is committed after every 1000 rows. To modify this setting, add the following entry to the INI file:
EnterpriseCommit=n (where n is the number of rows of data to commit).
- If the database connection is lost during the summarization process, the connection is automatically reestablished. By default, the job service will attempt to reconnect ten (10) times before stopping. To modify this setting, add the following entry to the INI file:
MaxRetries=n (where n is the number of retry attempts).
- The default delay between retry attempts (see previous item) is 60000 milliseconds (one minute). To modify the retry delay, add the following entry to the INI file: RetrySleep=n (where n is the number of milliseconds to wait before retrying the connection attempt).
|