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