Error in RRC for user viewing dashboard
CLM v4.0
tomcat
derby
Win 2008 R2 - 64bit
3 users on machine
Created 3 users for MTM demo. Each user is:
JazzAdmin
-ScrumMaster
-Test Team Member
-Administrator
We all logged in to JKE Banking (Requirements) and two people see the dashboard fine. The other gets an error across the top about not being able to display Reviews:
ID CRRRW7217E The server request to obtain the review listing information could not be completed. There might be a heavy load on the server, causing the request to time out.
_50.firstChild is null
@https://clmdemo.company.com:9443/rm/web/_js/?exclude=A~B~C~D~E~F~G~H~I&include=com.ibm.rdm.web.pages.ResourcesPage.js~com.ibm.rdm.web.search.QuickSearchProvider.js~jazz.ui.SearchBox.js&_proxyURL=%2Frm&locale=en-us:56732 @https://clmdemo.company.com:9443/rm/web/_js/?exclude=A~B~C~D~E~F~G~H~I&include=com.ibm.rdm.web.pages.ResourcesPage.js~com.ibm.rdm.web.search.QuickSearchProvider.js~jazz.ui.SearchBox.js&_proxyURL=%2Frm&locale=en-us:56671 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _102@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _100@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:20121 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:20127 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _102@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _100@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _102@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _100@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _102@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _100@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:6860 _102@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _100@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _102@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 _100@https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15 @https://clmdemo.company.com:9443/rm/web/_js/?include=A~&etag=DEp3obMuNzo_en_US&_proxyURL=%2Frm:15
Accepted answer
Hi Sterling,
This was discussed on this thread. It sounds like the user getting the error is using FireFox 14.This is being tracked in Reviews widget gets stuck in loop and throws error on RM Dashboard (62408).
This was discussed on this thread. It sounds like the user getting the error is using FireFox 14.This is being tracked in Reviews widget gets stuck in loop and throws error on RM Dashboard (62408).