[closed] RRC WEB UI error: The requested content could not be generated
We have CLM v.3.0.1.5 installed on single Windows Server 2008 R2 Enterprise x64 using bundled Apache Tomcat running windows service 64 bit. Database is Oracle 10g.
The same issue is also happening in another of our production distributed environment. These servers are also at v.3.0.1.5 on Windows Server 2003 R2 Enterprise x64
Browser is FF 10ESR or IE8
When editing and saving a RRC artifact, the server returns the following error:
The requested content could not be generated
ID CRRRW8010E A server error prevented the generation of the content. Refresh your browser to generate the content again. If the problem persists, there might be an issue with the server. Ask your administrator to check the server status.
The RRC add-on is properly installed so we have no problems editing the diagram or sketch.
We have looked at many posts regarding this issue and all seem to point to issues with the RRC converter.war on Linux – not on Windows.
Any idea if there is a solution for this issue for a Windows environment.
Thanks in advance.
Pierre
The question has been closed for the following reason: "Problem is not reproducible or outdated" by svandijk Jun 05 '13, 2:32 p.m.
Comments
Stef van Dijk
FORUM MODERATOR / JAZZ DEVELOPER May 16 '13, 1:41 p.m.Hi Pierre,
The converter is something that runs on the server and is only responsible for "view" mode whereas edit is controlled by the browser plugin. And you are correct that most issues encountered with the converter occur on Linux. It's rare to see an issue on Windows.
These problems are most typically environment or configuration related, so addressing them via the forum isn't typically the best approach. If possible I would recommend reporting the issue through IBM Support.Then we can arrange for a remote session to take a look at what's going on with your situation more directly. Here is the link: http://www-01.ibm.com/software/rational/support/contact.html.
All that said, I'd suggest looking in both the rm.log and converter.log files for possible clues to the issue. You could also see what happens when accessing the converter url: https://{host:port}/converter/htmlgen
Pierre Friend
May 27 '13, 1:34 p.m.Thanks for the information.
We upgrade from Tomcat to Webshpere and the error message no longer appears. I suspect their was something wrong with the Tomcat installation/configuration.
Pierre