It's all about the answers!

Ask a question

Lifecycle project creation failed at RRC project creation with custom template


Pablo Silva (16157) | asked Jan 28 '14, 10:31 a.m.
edited Jan 28 '14, 10:34 a.m.
So i have created a custom LPA template (i downloaded the Analyst - developer one and customized it) , i have added both of my custom Process template and Project Area Template (CCM and RRC). Take a look:

Process template CCM

RTC XML

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.)

Custom Template RRC

And the XML:
RRC XML

Now.... whenever i try to create a Lifecycle project i get this :
error

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



permanent link
Benjamin Silverman (4.1k610) | answered Jan 28 '14, 1:54 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I can't see the whole configuration, but I created a video on this when 3.0.1 was released and just tested the same steps on my 4.0.5 install and it worked for me.  Can you have a look and see if you might have missed something?  I see your RRC "Custom Template" matches, so it looks like it should work for you.  Can you confirm that you can create an RRC project from that template through RRC first?  Otherwise, I'd suggest looking at the rm.log for the entry specified in the error message to see the related error from RRC.

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
Pablo Silva commented Jan 28 '14, 2:33 p.m. | edited Jan 28 '14, 2:35 p.m.

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/


Benjamin Silverman commented Jan 28 '14, 3:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Hi Pablo,

Can you provide the attachment another way?  I can't see it in the link you sent.  Thanks,


Pablo Silva commented Jan 29 '14, 7:58 a.m.

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.


1
Benjamin Silverman commented Jan 29 '14, 8:43 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

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.


Pablo Silva commented Jan 29 '14, 9:44 a.m.

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 ?


permanent link
Benjamin Silverman (4.1k610) | answered Jan 29 '14, 4:54 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I have to tell you I'm stumped on this one...  I went through this on a few 4.0.4 servers today instead of the 4.0.5 server I was previously using and it still worked fine for me.  I'm not sure what to make of the logs from 12/30 that indicate the server was set up using /rdm as the context root...but it seems like that was the case at one point and may be contributing to the problem.

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. 

Your answer


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