It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×3,953

question asked: May 09 '11, 4:23 p.m.
question was seen: 4,239 times
last updated: May 09 '11, 4:23 p.m.

Related questions

reports fail

0
Doug James (21●5●4) | asked May 09 '11, 4:23 p.m.
Our reports are failing. Every time we try to run the Requirements Specification report it aborts and we not get a report. It appears that it is just the requirements artifact type that cause the problem, specifically the 'https://:443/rdm/publish/requirements' URL. Using Poster, If I get 'https://:443/rdm/publish/resources?resourceURI=rrc1548' then I get XML in the response but if I get 'https://:443/rdm/publish/requirements?resourceURI=rrc1548' then I get 'Response:500 Internal Server Error null' as the response. Additionally, I tested the '/resources' API versus '/processes', '/usecasediagrams', '/glossaries', '/usecases', and '/uisketches' without any problems.

Do we have a problem with our requirement artifacts or is it larger? How do we fix the problem so our reports run?

Thank you for your assistance.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Brian King (46) | answered May 17 '11, 1:50 p.m.
JAZZ DEVELOPER
Is this an issue occuring on v.2? If so, it is recommended that you open a problem ticket with Support so that they can gather some additional data and advise you on a resolution.

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.