Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Dashboard modifications are not allowed while an application is being upgraded

Questions
Tags
Users
Badges
Ioan Jones
(30●3●7) edited
Aug 16 '12, 12:40 p.m.

Wondered if anyone has seen this before...

We successfully completed an upgrade of our 3.0.1.2 CCM/RM/JTS test environment (WAS 7.0.0.17 & Derby) to 4.0.  Now, we see the following error message when trying to save a dashboard:

There was a problem saving the dashboard: HTTP/1.1 403 Forbidden
Dashboard modifications are not allowed while an application is being upgraded
Unable to load https://mycompany.com:9443/jts/dashboards/1?contentType=application%2Frdf%25xml status:403
Prior to the upgrade, we were able to save dashboards succesfullly.   We're able to create Work Items - this seems limited to Dashboards only.  Mortal users and admins see the same message.  Same message for personal and team dashboards.
From the error message I'm assuming there's some flag somewhere that blocks dashboard updates while some process runs as part of the upgrade.  For some reason, this flag wasn't reset after the successful completion of the upgrade.
Thanks for any help! 

1 vote

3 answers
5,052 views
1 vote

3 answers

Permanent link
Krzysztof Kaźmierczyk
(7.5k●4●80●103) Sep 14 '12, 6:42 a.m.
I had the customer with the same issue. You must check your jts,ccm,qm and rm.log. We had following error message:

ERROR ronting.server.services.discov ery.DiscoveryService  - Server Error: Entry [5eac0b15f37d1132]
com.ibm.rdm.fronting.server.ex ception.ServiceUnavailableExce ption: Server state invalid: REQUIRES_MIGRATION

After finishing migration of RRC the issue has been fixed.

1 vote

Permanent link
Ioan Jones
(30●3●7) Sep 19 '12, 4:56 p.m.

After opening an PMR, support came back right away with the solution (as did Krzysztof)... unfortunately for me it was RTFM:

I failed to run the RRC Migration steps (see the Migrating Requirements Composer section of the Upgrading to version 4.0 Interactive Guide).  After running the migration tool at https://hostname.example.com:port/rm/web/projects/migration and restarting WebSphere the problem was solved.

1 vote

Permanent link
Jared Burns
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER (4.5k●2●9) Aug 16 '12, 4:44 p.m.
This sounds like it could be a defect. If you haven't already, you should consider filing a workitem against Web UI -> Dashboards.

0 votes

Your answer

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

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 2,357

Question asked: Aug 16 '12, 12:39 p.m.

Question was seen: 5,052 times

Last updated: Sep 19 '12, 4:56 p.m.

Confirmation Cancel Confirm