It's all about the answers!

Ask a question

Print PDF feature for a particular test plan not working


Sandipq Mukhopadhyay (1666) | asked Jul 27 '11, 10:32 a.m.
Friends, for one of our particular RQM projects for a particular test plan , print PDF feature(Detailed test plan) is not working. Other test plans for the same project can be easily done using print PDF features. But for that particular test plan, error message 'HTTP 500 Internal Server Error' is displayed . That test plan is opening though. Can anyone throw some light on this issue ?

Appreciating your help.

Regards,
Sandy

6 answers



permanent link
John Nason (2.4k1012) | answered Jul 27 '11, 1:23 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi Sandy,
For the "problem" Test Plan, try going through each section. In every section that has a rich text editor with text content (i.e. Business Objectives or Test Objectives) put it into edit mode. There is a toolbar button when in edit mode at the very end with a "bug" looking icon called "Validate Content". Do this for each rich text field in the Test Plan and see if any validation errors are reported. That could cause a problem printing a PDF. These issues usually arise from pasting content from some versions of MS Word, due to the data they put onto the windows clipboard.
If that does not resolve your error, see if there are any errors in the log from when you try to do the PDF print and attach them here.

permanent link
Michael Triantafelow (4513) | answered Jul 27 '11, 3:24 p.m.
Friends, for one of our particular RQM projects for a particular test plan , print PDF feature(Detailed test plan) is not working. Other test plans for the same project can be easily done using print PDF features. But for that particular test plan, error message 'HTTP 500 Internal Server Error' is displayed . That test plan is oepning though. Can anyone throw some light on this issue ?

Appreciating your help.

Regards,
Sandy


Start by doing a "Current Artifact" print of that Test Plan. We want to isolate whether the problem is in the Test Plan itself or one of the child artifacts. "Current Artifact" only includes the Test Plan, while "Detail" includes the Test Plan, its Test Cases, and their Test Scripts.

The root problem is likely in only one of those artifacts.

permanent link
Sandipq Mukhopadhyay (1666) | answered Jul 29 '11, 6:26 a.m.
None of the reports are running.
Friends, for one of our particular RQM projects for a particular test plan , print PDF feature(Detailed test plan) is not working. Other test plans for the same project can be easily done using print PDF features. But for that particular test plan, error message 'HTTP 500 Internal Server Error' is displayed . That test plan is oepning though. Can anyone throw some light on this issue ?

Appreciating your help.

Regards,
Sandy


Start by doing a "Current Artifact" print of that Test Plan. We want to isolate whether the problem is in the Test Plan itself or one of the child artifacts. "Current Artifact" only includes the Test Plan, while "Detail" includes the Test Plan, its Test Cases, and their Test Scripts.

The root problem is likely in only one of those artifacts.

permanent link
Karen Steele (1.2k4139148) | answered Jul 29 '11, 11:43 a.m.
None of the reports are running.
Friends, for one of our particular RQM projects for a particular test plan , print PDF feature(Detailed test plan) is not working. Other test plans for the same project can be easily done using print PDF features. But for that particular test plan, error message 'HTTP 500 Internal Server Error' is displayed . That test plan is oepning though. Can anyone throw some light on this issue ?

Appreciating your help.

Regards,
Sandy


Start by doing a "Current Artifact" print of that Test Plan. We want to isolate whether the problem is in the Test Plan itself or one of the child artifacts. "Current Artifact" only includes the Test Plan, while "Detail" includes the Test Plan, its Test Cases, and their Test Scripts.

The root problem is likely in only one of those artifacts.

the 500 error can also mean that the server properties for the maximum page size to print is too low ... its not necessarily a formatting issue in the artifact ... if you still have the issue, ask your server / tools administrator to increment the print pagesize value

permanent link
Michael Triantafelow (4513) | answered Aug 09 '11, 2:26 p.m.
Sorry for the delay, I was on vacation last week.


the 500 error can also mean that the server properties for the maximum page size to print is too low ... its not necessarily a formatting issue in the artifact ... if you still have the issue, ask your server / tools administrator to increment the print pagesize value


Actually, that is not correct. If you are trying to print a report that has too many links the report will still be generated but it will be truncated. A message appears on the first page of the report to tell you that it has been truncated. You should not receive an error 500.

None of the reports are running.


That's good news. That means that the Test Plan itself is probably causing the issue. What version of RQM are you using?

permanent link
Sandipq Mukhopadhyay (1666) | answered Aug 13 '11, 4:16 a.m.
I am using 2.0.1.1 iFix 2 (I20110215_1523) version of RQM.


Sorry for the delay, I was on vacation last week.


the 500 error can also mean that the server properties for the maximum page size to print is too low ... its not necessarily a formatting issue in the artifact ... if you still have the issue, ask your server / tools administrator to increment the print pagesize value


Actually, that is not correct. If you are trying to print a report that has too many links the report will still be generated but it will be truncated. A message appears on the first page of the report to tell you that it has been truncated. You should not receive an error 500.

None of the reports are running.


That's good news. That means that the Test Plan itself is probably causing the issue. What version of RQM are you using?

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.