It's all about the answers!

Ask a question

Failed to retrieve categories after trying to add widget to RRC Dashboard


Matthew Owenby (23811) | asked Jan 14 '15, 3:31 p.m.
After upgrading RRC from version 4.0.7 to version 5.0.2, we get the following error when trying to add a widget to the Project dashboard.  Is this working as designed or are there not any RRC widgets?

Accepted answer


permanent link
Mike Jaworski (1.4k6) | answered Jan 15 '15, 11:47 a.m.
JAZZ DEVELOPER
Ok then, it sounds like you're definitely running into defect 92120. In order to work around this, I would suggest editing the httpd.conf file for your IHS installation, and changing the DefaultType setting to "none". This setting tells IHS what to set the "Content-Type" header to whenever an HTTP response does not contain any data for this header. For example, if httpd.conf reads "DefaultType text/plain", then whenever an HTTP response does not contain a Content-Type header, IHS will add "Content-Type: text/plain" to the HTTP response headers list. Changing this setting to "none" tells IHS to NOT add this header if it doesn't exist, and allows the RRC/DNG web client to successfully parse the response data as RDF+XML content.

ex) DefaultType none
Matthew Owenby selected this answer as the correct answer

Comments
Matthew Owenby commented Jan 15 '15, 11:58 a.m.

Thanks Mark.  That did the trick.

One other answer



permanent link
Mike Jaworski (1.4k6) | answered Jan 14 '15, 3:42 p.m.
JAZZ DEVELOPER
Hi Matthew,

Could you post a screenshot, or else give a little more description on the error? This sounds very similar to a recent defect we discovered: RM Widget Catalog does not display properly in FF and Chrome when response content type is text/plain (92120), which has since been fixed in the code for version 6.0. As far as I know, this error is only applicable in environments where IHS is used, and the "DefaultType" property in the httpd.conf file is set to something other than "application/xml", "application/rdf+xml", or "none". It's possible that other environmental combinations are affected, but this is all I am aware of at this time.

If this defect seems applicable to your environment, then you should be able to work around this error by using Internet Explorer instead of Firefox or Chrome.

Hope this helps,
Mike Jaworski

Comments
Matthew Owenby commented Jan 15 '15, 11:29 a.m.

I am indeed using FF and/or Chrome.  Issue is not present in IE.  Is there anything that you recommend regarding IHS which is currently serving our environment?  We use IHS and the WebSphere Plugin. No Categories FF and Chrome

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.