CA Clarity Tuesday Tip - System Error Installing PMO 3.1 on Clarity 13.1

Discussion created by Connie_Fu on Sep 18, 2012
Latest reply on Mar 29, 2013 by nathanarp
Getting this out for the early adopters of Clarity 13.1, a KB is not yet published

"Status Report Listing" is a new portlet (and query) so it will get applied when the Add-In is initially installed. However when you go to the Add-In admin page and apply everything you will get a system error.

The workaround is not to select either of the two items on the page when applying, we will address the error in a future version.

The root cause is that the file name in the dependency file for the query and the portlet are incorrect:

<portlet code="cop.prjStatusReportListing fileName="cop.prjStatusReportListing.xml"
<query code="cop.prjStatusReportListing" fileName="cop.prjStatusReportListing.xml"

The first period in the file name should be an underscore. When the system tries to process these it can't find the file and a null pointer happens.

Following is the error found from the app log:
ERROR 2012-09-07 18:00:46,732 [http-bio-80-exec-7] niku.xql2 (clarity:none:none:none) Internal Processing exception
com.niku.xog.XOGException: Failed to parse input null with resource component csk path C:\niku\\runtime\META-INF\content\xog\csk\queries/cop.prjStatusReportListing.xml
at com.niku.xog.client.XOGAdminClient.processFileDescriptors(

Steps to reproduce:
1) Install 13.1 and PMO 3.1
2) Grant all access rights to the admin user
3) Go to Add-In page and drill into PMO 3.1
4) Use checkbox at top to select everything
5) Click apply

Result: System error is thrown