OWB Error: "Unable to open project XXXXX. The expected data type from the stream was different from what the stream contained."

Products

• Clarity PPM On Premise

Issue/Introduction

Steps to Reproduce:

1. Open any plan from Clarity into Open Workbench (OWB)

Expected Results: Project is opened in to OWB

Actual Results: The error "Unable to open project XXXXX. The expected data type from the stream was different from what the stream contained" is received and the plan is not launched to OWB

Cause

• This can happen due to an issue with a custom lookup including:
  • If a custom attribute on the project object has an associated lookup that is a number based lookup, but the actual lookup had CODE as its hidden key which is character based.
  • The standard lookup SELECT query that is built to retrieve the lookup values links the select data value id to the lookups hidden key.
  • This causes database data type mismatch error (ORA-01722 Invalid Number) which halts any plan from opening

Environment

Release: All Supported Releases
Component: Clarity Open Workbench

Resolution

1. Delete the custom attribute and recreate, ensuring that the correct lookup data type is configured.

2. To track down the problem lookup, one thing that can help is checking for any lookups recently created or updated since the issue started happening. 

3. To narrow down the issue to the project object

• Create a new project with no tasks or team, and see if the issue happens there. 
• If not, then add one team member and see if the error happens. 
• If not, then add a task to the project and see if it happens there
• If it doesn't happen in the above scenarios, then add an assignment to the task and see if then appears. 

 

Additional Information

See KB: 141061 for tips on how to optimize use of Self Service for Clarity