CA PPM: Exception Error when Saving a Project back from OWB

Document ID : KB000113682
Last Modified Date : 17/09/2018
Show Technical Document Details
Issue:
When attempting to save a project back to PPM, the following exception error is thrown:
 
'Unable to save project CA PPM\<project Id>. An exception occured. '

The OWB Console log also contains the following error: 
 
09:57:14.221 ProjectExporter.saveAssociatedObjects(): Saving 38 assignment object(s) 
null 
java.lang.NullPointerException 
at com.abtcorp.io.repostream.exporters.AssignmentExporter.isTracked(Unknown Source) 
at com.abtcorp.io.repostream.exporters.AssignmentExporter.isSaveException(Unknown Source)

This error occurs for any user attempting to save this particular project. However, other projects are able to save back to OWB without an error.
Cause:
This error usually indicates that the Track Mode on one (or more) resource on the project team is being sent to OWB as null.
Resolution:
As of PPM 14.3, OWB now requires that all resources have a Track Mode. If a resource does not have a track mode, a track mode of None, Other or PPM will need to be entered for that resource. 

To find the resource missing a Track Mode:
1. Open the affected project in OWB
2. Go to the Project tab
3. Click on 'Edit View'
4. Select the 'Tracking Mode' under the Resource Information
5. Add this field to the Resource section of the View and click OK
Additional Information:
KB000014905: Why does an exception occur when a project is saved in Open Workbench for some users but not for others?