Hi Everybody,
We have an OTM setup (migrated from v5.0 to v5.5 and newly installed with CU3 installer). On these systems these are the issue which we have encountered -
- From default Order Release menu link, if we select a record and click on "Set Appointment" action, throws java.lang.NullPointer excepton.
The Error Stacktrace mention as below -
<stack_trace>java.lang.NullPointerException
java.lang.NullPointerException at glog.webserver.managerlayout.WritePresentationToFi le.escapeGidForFile(WritePresentationToFile.java:6 23)
at glog.webserver.custscreens.CustScreenUtil.formatJs pPath(CustScreenUtil.java:294)
at glog.webserver.custscreens.CustScreenUtil.getStyle SheetEditString(CustScreenUtil.java:147)
at glog.webserver.custscreens.CustScreenManagementSer vlet.getStyleSheetEditString(CustScreenManagementS ervlet.java:231)
Here now since you see the CustScreen management functionality, we cross verified to the screenset to check if the Managerlayout are selected or not and found to be selected.
From the stacktrace can anybody give me an hint what could be the cause of this issue. I coluld have argued that in migration there is a chance of failure. However on a freshly installed OTM too has the same problem.
Regards,
Suresh
We have an OTM setup (migrated from v5.0 to v5.5 and newly installed with CU3 installer). On these systems these are the issue which we have encountered -
- From default Order Release menu link, if we select a record and click on "Set Appointment" action, throws java.lang.NullPointer excepton.
The Error Stacktrace mention as below -
<stack_trace>java.lang.NullPointerException
java.lang.NullPointerException at glog.webserver.managerlayout.WritePresentationToFi le.escapeGidForFile(WritePresentationToFile.java:6 23)
at glog.webserver.custscreens.CustScreenUtil.formatJs pPath(CustScreenUtil.java:294)
at glog.webserver.custscreens.CustScreenUtil.getStyle SheetEditString(CustScreenUtil.java:147)
at glog.webserver.custscreens.CustScreenManagementSer vlet.getStyleSheetEditString(CustScreenManagementS ervlet.java:231)
Here now since you see the CustScreen management functionality, we cross verified to the screenset to check if the Managerlayout are selected or not and found to be selected.
From the stacktrace can anybody give me an hint what could be the cause of this issue. I coluld have argued that in migration there is a chance of failure. However on a freshly installed OTM too has the same problem.
Regards,
Suresh
Comment