Description:
The PMO Accelerator Project Manager Schedule Dashboard tab has two portlets and both portlets are showing Error 500 messages.
It must be specific data causing the problem because we can set the option not to display results until we filter and put in specific filter and get results back for some data and get error messages for other data.
We are using Microsoft SQL Server in our implementation.
Steps to Reproduce:

1. Login to Clarity with PMO Accelerator Add-In installed

Home > Project Manager Tab

Expected Result: Both portlets should appear without error
Actual Result: Both portlets appear with Error 500 message
Solution:
The issue with the portlet was the scheduled end date on the project. There are certain admin projects within our application that have schedule end dates of 12/31/9999. The application allows the user to enter these dates, but SQL server cannot cast these dates to ‘smalldatetime’ forexample. (6/6/2079 is the max for small datetime in MSSQL Server).
Somewhere in the COP_GET_ETC_FCT scalar function, it cannot cast the date to a ‘varchar’ and this is causing the error 500.
RESOLUTION:
Examine the dates for the Projects and adjust it within the maximum allow able date.
Several development issues have been logged regarding the ability to enter dates beyond 2079 within Clarity date fields.
This impacts several different areas such as identified in the database and within scheduler integrations. It has been decided that the Clarity application will NOT have a restriction for future dates. The third-party integrations, databases and schedulers will change overtime and when the year 2079 arrives, Clarity won’t have a restriction.
In addition to the MSSQL date restrictions, the date range that is supported in Microsoft Project (MSP) is different from OpenWorkBench (OWB). MSP 2007 date range is 1984 – 2049 whereas OWB date range is1900 – 2079.

“Solutions provided by CA Technologies”