- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 10-23-2020 07:10 PM
1. Generally, the first level of troubleshooting can be made by selecting Project Diagnostics in the Related Links section of the Project. *Available to any Project Managers. This will illuminate any invalid parents or incorrectly associated tasks or any discrepancy dates.
For example, if the top_task value is incorrect or anything other than the expected Project (that is the top Project), users need to address this.
2. Planning console not load for any project make sure pm_console table having all valid records and Planning console configuration of Project is valid.
3. Planning console WBS is not sorted order then check, is there any other column configured for sorting order in planning console display column related list.
4. Project tasks WBS is starting like XX.1, XX.2, XX.3 instead of 1, 2, 3 then project WBS might be corrupted. The issue will be fixed by resetting the project wbs and wbs_order with empty space and then run the Recalculate in Project diagnostics.
5. If dates are not recalculating then make sure that pm_project and pm_project_task tables are not added to the planned_task_recalculation_exclusions table.
6. Client-Side planning console does not support the Scheduling if it's defined as 6.5 or 7.5 or 8.5 hours so use the Server-side planning console in this case.
7. If any column data is displaying as 'undefined' in the Planning console then make sure the type of column configuration is valid in the Planning console display column related list of planning console.
8. Planning Console Depth is showing Read-Only rather than selectable Levels - make sure Level is populated to all project tasks and valid under the project.
9. If the user sees the "An error occurred while saving the preference" error message on the planning console while saving then make sure the user has the planning_console_user role.
10. If the user can not see the relations on the Planning console then make sure Load relations field is enabled in the planning console configuration.
11. Predating a task is allowed from Paris. Till Orlando, adding a task whose start date is before the project's planned start date is restricted.
12. If the Planned dates will not take earlier year dates, the associated Project schedule entries have a year later than the desired year.
For example, if the desired Planned start date is in the year 2020, then the associated Project schedule's Start date-time (coming from the Schedule entry) should be 2019.
13. "Unexpected error encountered. Contact System Administrator" error on the Planning Console and "Can not read property "status" from null” in logs- Most probable cause for this is incorrect States rollup due to incorrect dictionary override attributes. The States Dictionary override could have incorrect Attributes when compared to Out of the Box. To configure the custom State follow this link.
14. “Recursive relationship error in Project Planning console” - Service now will not allow the creating Cyclic relationship under Project apart from importing the project from an external source. Remove the cyclic relationship in the Project before performing any action on the planning console. You can find the cyclic relationship by running the “Check for tasks with cyclic dependencies” action in Project diagnostics.
- 2,869 Views