Unable to launch a RPE report for RRC since upgrade to CLM4.0.3
CLM 4.0.3
RPE 1.1.1.2 I just wanted to do some more development on a Report I had made with 4.0.1 and was not able to connect anymore My dsx type=Generic XML url=https://server/rm/publish/resources?projectURI=_juUEACTLEeGUGJlb_SQL7w authentication=OAuth1a CRRPE3011E Error in engine Cannot retrieve data from https://server/rm/publish/resources?projectURI=_juUEACTLEeGUGJlb_SQL7w. Server returned: Can not get the OAuthentication security URL to post the user name and password. I've searched and found no solution. all I found was about authentication type; but not in the launcher I tried with OAuth CRRPE3011E Error in engine Errors occurred when processing C:\Users\kunze\AppData\Local\Temp\RPE\temp\url_1378912488901_81218624.tmp Original source context https://server/rm/publish/resources?projectURI=_juUEACTLEeGUGJlb_SQL7w Error is: The entity name must immediately follow the & in the entity reference. Has something changed? What do I wrong? I did Upgrade to 1.2.0.1 and changed to OAuth as suggested below Now the error is: com.ibm.rational.rpe.common.utils.RPEException: An invalid XML character (Unicode: 0x43) was found in the prolog of the document No clue what the prolog of the document is. I created a new specification from scratch; did not help |
Accepted answer
Hi Erwin
Seems that you got problems with the authentication. Does your server uses form authentication? Could you try using "auto" as authentication method ? Besides the rename of OAuth1a to OAuth nothing has changed. Regards. Erwin Kunz selected this answer as the correct answer
Comments
Erwin Kunz
commented Sep 12 '13, 4:44 a.m.
Hi Jorge
Erwin Kunz
commented Sep 12 '13, 4:53 a.m.
RPE1.2.0.1
Erwin Kunz
commented Sep 12 '13, 4:56 a.m.
and the report is deployed and works fine in 4.03
Jorge Flores
commented Sep 12 '13, 4:43 p.m.
Does the included reports work on that environment ? Rather than updating RPE I would recommend you to migrate to 4.0.4. It is already out and includes a fix for a 1.2 plugin problem. Are you using links with embedded content ?
Erwin Kunz
commented Sep 17 '13, 5:13 a.m.
Hi Jorge
|
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.