Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Why am I receiving Error 400: Bad Request in DNG when apply tag to a requirement

I am using RRC/DNG 6.0.3 .

When I try to apply an existing tag to a requirement I get the following error: (note:  I am able to apply tag to some requirements)

An error has occurred while processing a server request. The server returned this error code: 400.

hide details

ID CRRRW7553E  A message that was received from the server indicates an error with no specific handler.

URL: https://rtc.esadev.dol.gov/rm/tags/_HrsP8ecpEeasGsQR0tCalA?taggedResources

Error 400: Bad Request

Process Area must not be null (More info found at entry [2b03268838cdf0db] in the RM application server log)

0 votes


Accepted answer

Permanent link

It appears to show the exact same error message as in the "unreproducible" defect, in a different use case, but also about "shared tags".
http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1PI58416

If the error keeps coming up, I suggest you contact Support.

Bob Ferguson selected this answer as the correct answer

0 votes


One other answer

Permanent link

This turned out to be a bug when migrating.  I turned this over to our Rational admins and they worked with IBM.

We migrated from 3 to 4 then 4 to 5 and then 5 to 6.  I do not know when the error was introduced but I do know if we created a tag in version 3 and did not modify the requirement since we could not add or modify tags.

This was fixed with an update.

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Mar 09 '17, 1:01 p.m.

Question was seen: 4,910 times

Last updated: Oct 19 '17, 6:37 a.m.

Confirmation Cancel Confirm