Artifact not found in the repository
Has anyone come across the error CRRRW7823E in Requirements Management (RDNG if you will), version 6.0.3, saying that an "artifact, <artifactURL>, was not found in the repository"? A further elaboration excuses that "The project that contains the artifact might have been deleted or archived, you might not be a member of the project, or the artifact might not be visible in the current configuration. Verify that the artifact exists, that you are using an appropriate configuration, and that you are a member of the project."
This happens when either attempting to view an artifact in a module, or a module itself. Strangely, the rich hover successfully displays our artifact when mousing over in the module, but no dice when you try to open it.
We're pretty certain we're good with all three of the fixes the error suggests, but perhaps we haven't checked if the configuration is appropriate. (what does that mean?) We reindexed the server, and that seemed to fix the missing artifacts, but then whole modules started disappearing in another project area, giving this same error.
Not a lot of help elsewhere on the web, so we hope a jazz user has the power to help us out here. This is on a test environment, but we'd freak if this error showed up in production, so any help is greatly appreciated!
-- Ryan
|
2 answers
|
Turns out this is most likely our problem. Being a sandbox project area, we have many duplicate data types and artifact types.
|
We had the same issue on 6.0.3 (production environment), the issue occurs when we trying to open some specific artifacts, example when we are trying to open “Use Case Diagram” artifact then we had same error message.
Here is want we have done,
<o:p> </o:p> 1. Reboot server will fix the issue sometimes, but after some time it occurred again (two weeks later) 2. We have re-indexed RM, but still same issue occurred in after sometime. 3. What we have observed is, if system memory usage reaches maximum it occurs the issues, so we have increased our system memory size. 4. And then we have upgraded our systems to 6.0.4 5. We have upgraded DNG from 6.0.3 to 6.0.4 and then re-indexed RM 6. Now, server is stable and no issues. (past one month)
I think this info will helpful for you.
<o:p> </o:p> |
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.