Lifecycle project creation failed at RRC project creation with custom template
OK so as you can see Process template ID in RTC and the process template ID on the XML , they check, now RRC (the one with the problem.)
And the XML:
Now.... whenever i try to create a Lifecycle project i get this :
Notice that the error says that the Template ID : "Custom Template" does not exist.....
I am using CLM 4.0.4
Help any one please!
2 answers
Here's the link to the video:
http://publib.boulder.ibm.com/infocenter/ieduasst/rtnv1r0/index.jsp?topic=/com.ibm.iea.rrc/rrc/3.0.1/Usability/rrc_custom_lpa/rrc_custom_lpa_viewlet_swf.html
Comments
I did create a project with the RRC template, it worked just fine , also checked your video , haven't miss any single step.
the log says :
2014-01-28 09:13:23,255 [ http-bio-9443-exec-145] ERROR dm.fronting.server.services.process.ProjectService - Server Error: Entry [7e3d9e2ed35b12df]
com.ibm.rdm.fronting.server.exception.BadRequestException: CRRRS3760E The project template with the following ID does not exist: Custom Template.
Complete XML :
http://jsfiddle.net/ViceroyRojo/4cZ5h/embedded/result/
Hi Pablo,
Can you provide the attachment another way? I can't see it in the link you sent. Thanks,
Try this google drive link , there you can find the whole XML plus the RM log
https://drive.google.com/folderview?id=0B4eH426pi0CQX2J0eFBfR05YTWM&usp=sharing
Thanks.
The problem seems caused by a bad request to https://localhost:9443/rm/projects
What is your context root? I see in your rm.log that the server was installed with context root /rdm and was changed later on to /rm. How was this changed? That may help explain why you're having this problem, because it looks like everything is configured properly from the custom template side.
1 vote
To be perfectly honest with you Benjamin I did pretty much Next Next Next .... on the installation process, so my root context is : default 3.X/4.X root context ... meaning that that the context for RRC is /rm, havent change a thing.
Assuming this is whats wrong what should i do ?
I would suggest contacting support and providing the ISALite logs after you've reproduced the problem. That way someone can spend some time looking in to the various server logs to see what might be causing this problem.
Otherwise, I would suggest doing a new install if this is just a demo server (as I suspect it may be since you're just using "localhost" as your public URI). I wouldn't expect to see the problem on a new install as I have three 4.0.4 servers here with the standard Next/Next/Next install as you described, and none of them have this problem.