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

Cannot delete RRC custom artifact type

I tried to create a custom Artifact in RRC.  During save a the login pop-up appeared and I was prompted to re-authenticate.  I got an error while saving the artifact after logging back in (I did not save this error).  I hit the cancel button, logged out and closed my FireFox browser.  I opened a new browser, logged in and successfully created the new Artifact type.  However, now there are two artifact types with the same name -- the one I successfully created and the one that errored on the previous attempt.

When I try to remove the "bad" artifact type, I get the following error:

ID CRRRW7553E  A message that was received from the server indicates an error with no specific handler.
Unable to load https://rrc.xcelenergy.com:9443/rm/types?oauth_token=631a98712d1741b6b6a3940a7036242b&request_token_secret=undefined&oauth_provider=undefined/&dojo.preventCache=1407511530973 status:400
_28d@https://rrc.xcelenergy.com:9443/rm/web/_js/?include=A~&etag=HUGQN05no0j_en_US&_proxyURL=%2Frm&ss=EzQE7:15:83482 _286/func@https://rrc.xcelenergy.com:9443/rm/web/_js/?include=A~&etag=HUGQN05no0j_en_US&_proxyURL=%2Frm&ss=EzQE7:15:82215 _286@https://rrc.xcelenergy.com:9443/rm/web/_js/?include=A~&etag=HUGQN05no0j_en_US&_proxyURL=%2Frm&ss=EzQE7:15:82499

URL: https://rrc.xcelenergy.com:9443/rm/types?oauth_token=631a98712d1741b6b6a3940a7036242b&request_token_secret=undefined&oauth_provider=undefined/

Error 400: Bad Request

com.ibm.rdm.fronting.server.exception.BadRequestException (More info found at entry [ec3b48d607f1e5b] in the RM application server log)
Requirements Management/4.0.1

How can I remove this artifact type?

I have had this problem before, where an error occurs during the creation of a new artifact type (or attribute or attribute type) and you are left with what appears to be artifact types that seem to be partially created.  How can we prevent this from occurring, and how can we resolve it when it does?


Thanks,
Mike

0 votes



One answer

Permanent link
Hi Mike,

Support has a utility that can be used to fix this problem.  I would suggest creating a PMR and requesting the utility (called "RepairTypeRdfAbout").  This was fixed in the 5.0 release:

Invalid resource URI with oauth token (86820)

Hope it helps,

0 votes

Comments

Thanks Benjamin for the quick reply.  I have opened a PMR for the RepairTypeRdfAbout utility.

1 vote

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
× 6,122

Question asked: Aug 08 '14, 12:20 p.m.

Question was seen: 4,432 times

Last updated: Aug 08 '14, 4:14 p.m.

Confirmation Cancel Confirm