Project and Portfolio Management Practitioners Forum
cancel

error on work plan

Highlighted
eata
Super Contributor.

error on work plan

One of the project manager faced with this error when she clicks on edit work plan button on project summary screen :
An unknown exception has occurred. Please reload the page you were editing and try again.
The following is a stack trace of the exception:
com.kintana.core.server.RuntimeBaseException:
An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=A794C09D-F460-C1B3-063D-FE881CCC2323

She claimed that she got error when she selected filter for tasks completing in option. since then she can not open that work plan. she is able to open workplans in other projects. Also I added new project managers. the new added project managers can open the work plan.
Could you help me to make work plan editable again for the project manager.

13 REPLIES
Jason Nichols K
Acclaimed Contributor.

Re: error on work plan

Since newly added PMs can open the Work Plan, have you tried removing and then re-adding her?

Erik Cole
Acclaimed Contributor.

Re: error on work plan

Also, have the new PMs tried using the same filter? Maybe its a specific task that is causing it...

eata
Super Contributor.

Re: error on work plan

Hi Jason;

Yes I have removed the project manager with problem and re add her. And the same error occured again.

eata
Super Contributor.

Re: error on work plan

Hi eric;

No I did not make the same filter again since the same error might occur in production.

Also the project manager is not remembering the configuration. Let me test in test environment first to find out the filter combination with problem.

 

TurboMan
Honored Contributor.

Re: error on work plan

Hi eata,

 

I had this kind of problems before, and it drove me crazy.

Make sure you have the right periods  in the request and project.

 

TM

MONA-A
Valued Contributor.

Re: error on work plan

Since the error is occuring for one specific user, it maybe a data specific issue

 

Check if the given SQL returns any rows:

 

SELECT *
FROM itg_settings_attributes
WHERE name = 'PAGE_SIZE_OPTION'
AND classtype IS NULL

eata
Super Contributor.

Re: error on work plan

hi mona;

The query returned no row.

 

SELECT *
FROM ppmasya_usr.itg_settings_attributes
WHERE name = 'PAGE_SIZE_OPTION'
AND classtype IS NULL

Pogonchev
Micro Focus Expert

Re: error on work plan

Hi Eata,

 

What is the full stack trace of the error in the server log?

You can find it by searching for "GUID=A794C09D-F460-C1B3-063D-FE881CCC2323"

Also what is your current version of PPM?

 

Regards,

 

Nikola

HPE Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Pogonchev
Micro Focus Expert

Re: error on work plan

Hi Eata,

 

Perhaps you are experiencing the following known issue:

 

QCCR1L44586 When user set only FROM value in the "Task completeing in" in workplan view is getting exception when editing the workplan

 

http://support.openview.hp.com/selfsolve/document/FID/DOCUMENTUM_QCCR1L44586

 

There is a hotfix available for PPM 9.12, please open a new case with HP PPM Support to request it.

 

I hope this helps.

 

Best regards,

 

Nikola

HPE Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
eata
Super Contributor.

Re: error on work plan

Hi Nikola;

 

here the log:

ERROR JSESSIONID=B2531AD50B1B072C2167076D3C803E33.ASYA_PPM_PROD,USERNAME=:http-0.0.0.0-80-Processor35:com.kintana.core.server:2012/03/19-10:35:59.852 EET: User with unsupported locale is accessing this instance, use system language as default
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET: An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=A794C09D-F460-C1B3-063D-FE881CCC2323
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET: nested detail:null
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:


STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET: An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=A794C09D-F460-C1B3-063D-FE881CCC2323
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.mercury.itg.common.web.ITGExceptionHandler.execute(ITGExceptionHandler.java:125)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.mercury.itg.common.web.PortletTilesRequestProcessor.process(PortletTilesRequestProcessor.java:53)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.mercury.itg.servlet.ActionMonitorFilter.doFilter(ActionMonitorFilter.java:86)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.mercury.itg.servlet.HibernateSessionFilter.doFilter(HibernateSessionFilter.java:88)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.kintana.core.web.filter.MLUFilter.applyFilter(MLUFilter.java:111)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.kintana.core.web.filter.stinger.ValidationFilter.applyFilter(ValidationFilter.java:145)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.kintana.core.web.filter.stinger.ValidationFilter.doFilter(ValidationFilter.java:80)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.kintana.core.web.filter.MultipartRequestFilter.applyFilter(MultipartRequestFilter.java:81)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.kintana.core.web.filter.ControlFilter.applyFilter(ControlFilter.java:861)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.kintana.core.web.filter.ControlFilter.doFilter(ControlFilter.java:1378)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.mercury.itg.servlet.I18NFilter.doFilter(I18NFilter.java:40)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.kintana.core.web.filter.Log4jFilter.applyFilter(Log4jFilter.java:51)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:  at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET: Caused by: java.lang.NullPointerException
STATUS JSESSIONID=DB7462A97FF809CFE607A21CF7E393BC.ASYA_PPM_PROD,USERNAME=6737VACE server:http-0.0.0.0-80-Processor12:SystemErr:2012/03/19-10:36:11.993 EET:
 Filtered Out 48 Stack Trace Lines.
ERROR server:com.kintana.crt.server.CRTExecutionManager Batch ID: 63586:com.kintana.core.executions.commands:2012/03/19-10:40:49.361 EET: KNTA_EXECUTION.SET_PARAMETER_TOKEN(
1:  VARCHAR P_PARAMETER_PREFIX => REQD,
2:  VARCHAR P_MODIFIER => P,
3:  INTEGER P_PRIMARY_ID => 40130,
4:  VARCHAR P_TOKEN_NAME => SECURITY_USER,
5:  VARCHAR P_NEW_VALUE => 35250,
6:  VARCHAR P_NEW_VISIBLE_VALUE => JULIDE BASAK UNAL,
7:  VARCHAR P_TYPE => null,
8:  VARCHAR P_DATE_FORMAT => null,
9:  INTEGER P_LAST_UPDATED_BY => 35264,
10: INTEGER P_USR_DBG => 70,
11: INTEGER O_MESSAGE_TYPE => l_o_message_type,
12: VARCHAR O_MESSAGE_NAME => l_o_message_name,
13: VARCHAR O_MESSAGE => l_o_message);

ERROR server:com.kintana.crt.server.CRTExecutionManager Batch ID: 63586:com.kintana.core.executions.commands:2012/03/19-10:40:49.361 EET: O_MESSAGE     :  value: null sqlType: VARCHAR
O_MESSAGE_NAME:  value: null sqlType: VARCHAR
O_MESSAGE_TYPE:  value: 0 sqlType: INTEGER

ERROR server:com.kintana.crt.server.CRTExecutionManager Batch ID: 63586:com.kintana.core.executions.commands:2012/03/19-10:40:49.376 EET: KNTA_EXECUTION.SET_PARAMETER_TOKEN(
1:  VARCHAR P_PARAMETER_PREFIX => REQ,
2:  VARCHAR P_MODIFIER => P,
3:  INTEGER P_PRIMARY_ID => 40130,
4:  VARCHAR P_TOKEN_NAME => CREATED_BY_TEMP,
5:  VARCHAR P_NEW_VALUE => 35264,
6:  VARCHAR P_NEW_VISIBLE_VALUE => ABDULKADIR CINAR,
7:  VARCHAR P_TYPE => null,
8:  VARCHAR P_DATE_FORMAT => null,
9:  INTEGER P_LAST_UPDATED_BY => 35264,
10: INTEGER P_USR_DBG => 70,
11: INTEGER O_MESSAGE_TYPE => l_o_message_type,
12: VARCHAR O_MESSAGE_NAME => l_o_message_name,
13: VARCHAR O_MESSAGE => l_o_message);

ERROR server:com.kintana.crt.server.CRTExecutionManager Batch ID: 63586:com.kintana.core.executions.commands:2012/03/19-10:40:49.376 EET: O_MESSAGE     :  value: null sqlType: VARCHAR
O_MESSAGE_NAME:  value: null sqlType: VARCHAR
O_MESSAGE_TYPE:  value: 0 sqlType: INTEGER

ERROR server:com.kintana.crt.server.CRTExecutionManager Batch ID: 63586:com.kintana.core.executions.commands:2012/03/19-10:40:49.392 EET: KNTA_EXECUTION.SET_PARAMETER_TOKEN(
1:  VARCHAR P_PARAMETER_PREFIX => REQ,
2:  VARCHAR P_MODIFIER => REQ,
3:  INTEGER P_PRIMARY_ID => 40130,
4:  VARCHAR P_TOKEN_NAME => CREATED_BY,
5:  VARCHAR P_NEW_VALUE => 37026,
6:  VARCHAR P_NEW_VISIBLE_VALUE => Created_by,
7:  VARCHAR P_TYPE => null,
8:  VARCHAR P_DATE_FORMAT => null,
9:  INTEGER P_LAST_UPDATED_BY => 35264,
10: INTEGER P_USR_DBG => 70,
11: INTEGER O_MESSAGE_TYPE => l_o_message_type,
12: VARCHAR O_MESSAGE_NAME => l_o_message_name,
13: VARCHAR O_MESSAGE => l_o_message);

ERROR server:com.kintana.crt.server.CRTExecutionManager Batch ID: 63586:com.kintana.core.executions.commands:2012/03/19-10:40:49.392 EET: O_MESSAGE     :  value: null sqlType: VARCHAR
O_MESSAGE_NAME:  value: null sqlType: VARCHAR
O_MESSAGE_TYPE:  value: 0 sqlType: INTEGER

ERROR JSESSIONID=A7D168282E3B3CF466B6349B8ACD5A52.ASYA_PPM_PROD,USERNAME=:http-0.0.0.0-80-Processor37:com.kintana.core.server:2012/03/19-10:44:39.839 EET: User with unsupported locale is accessing this instance, use system language as default
STATUS JSESSIONID=A7D168282E3B3CF466B6349B8ACD5A52.ASYA_PPM_PROD,USERNAME= server:http-0.0.0.0-80-Processor37:SystemOut:2012/03/19-10:44:51.214 EET: ---------------------------------debug QCIM1L45615 begin-----------------------------
STATUS JSESSIONID=A7D168282E3B3CF466B6349B8ACD5A52.ASYA_PPM_PROD,USERNAME= server:http-0.0.0.0-80-Processor37:SystemOut:2012/03/19-10:44:51.214 EET: workplan project ids is[42926, 46406, 38468, 37575, 43787, 38807, 44927, 36918]
STATUS JSESSIONID=A7D168282E3B3CF466B6349B8ACD5A52.ASYA_PPM_PROD,USERNAME= server:http-0.0.0.0-80-Processor37:SystemOut:2012/03/19-10:44:51.229 EET: projectAndStaffingProfileInfo project ids [42926, 46406, 38468, 43787, 37575, 38807, 44927, 36918]
ERROR JSESSIONID=69A61BBCE4E2F599A2414184E964B66D.ASYA_PPM_PROD,USERNAME=6208CAYD:http-0.0.0.0-80-Processor34:com.mercury.itg.rsc.resource.web.AnalyzeAssignmentLoadUtil:2012/03/19-10:45:28.572 EET: Error getting data for Analyze Assignment Load portlet
java.lang.IllegalArgumentException: Unknown encoded value: 3

 

We are using PPM 9.13

I am checking the hotfix.

regards

eata
Super Contributor.

Re: error on work plan

Hi Nikola;

How can I download and install hotfix?

Pogonchev
Micro Focus Expert

Re: error on work plan

Hi Eata,

 

The stack trace is exactly the same, so it seems the exact same issue.

To get the hotfix please submit a new case to HP PPM Support team and request it.

It should resolve the issue.

 

Best regards,

 

Nikola 

HPE Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
kintanadan
Super Contributor.

Re: error on work plan

@eata

 

As Pogonchev pointed out, this is a known issue when using either the “Tasks starting in..” or “Tasks completing in..” Filter option.  The error will occur if you do not specify BOTH dates in the Filter.  You can confirm this by adding the filter to a Work Plan in a Dev/Test system using only a single date, and use the below query to confirm and fix the error.  Of course, it is not recommended to update the backend directly, so use at your own risk.

 

You can find this Work Plan filter in the ITG_SETTING_ATTRIBUTES table for the problem user using a query similar to the following:

 

select last_update_date, last_updated_by, value

from itg_settings_attributes

where last_updated_by=<your problem user id>

and name = 'filter'

order by 1 desc

 

You should see the ‘value’ attribute contain something similar to the following: (In this example, the user did not specify the ‘startFilterEndDate’)

 

filterType=12&constraintType=&resourceIds=&roleIds=&startFilterStartDate=1338786000000&startFilterEndDate=&completeFilterStartDate=&completeFilterEndDate=&occurFilterStartDate=&occurFilterEndDate=&actualsDate=

 

Again, it is not recommended to update the backend directly, but you can confirm the issue is related to the date(s) by updating the VALUE attribute, adding the ‘startFilterEndDate’ shown here:

 

filterType=12&constraintType=&resourceIds=&roleIds=&startFilterStartDate=1338786000000&startFilterEndDate=1338786000000&completeFilterStartDate=&completeFilterEndDate=&occurFilterStartDate=&occurFilterEndDate=&actualsDate=

 

At this point, you’ll be able to open the Work Plan without error.

 

Regards