It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,861

question asked: Jul 23 '11, 10:10 p.m.
question was seen: 4,011 times
last updated: Jul 23 '11, 10:10 p.m.

Related questions

Cannot cancel pending scheduled build

0
Sterling Bates (231●16●12) | asked Jul 23 '11, 10:10 p.m.
We had an unusual licensing exception thrown when a pending build request was being handled by a JBE, leaving it in a state where no build engine sees it as pending. (The exception said the build user did not have a license permitting it to refresh or read a workspace. It did have the license, but there may have been a timeout.)

I want to cancel this request, but when I do so the Team Advisor opens saying "Not authorized to cancel pending build request." The only role permitted to cancel any request is Administrator, which both myself and another user have (the other user being the build user), and neither can cancel it.

When I click the "Why did this happen" link the "Permissions" section does identify the Administrator role as one that can cancel.

Any idea how I can get this pending request out? We're running RTC 3.0 iFix 1.

3 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Jul 24 '11, 12:51 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Sometimes, those error messages are only somewhat accurate.
When debugging this kind of thing, I often just go in and assign the
user all possible roles, and try the operation again. If it works,
then I know it is some role based thing, and I look more carefully at
the roles in the Process Configuration tab, to see what roles have what
permissions. If I still can't figure it out, I start removing roles
from the user, and see which role is apparently needed, and investigate
that role in more detail.

Cheers,
Geoff

On 7/23/2011 10:23 PM, sbates wrote:
We had an unusual licensing exception thrown when a pending build
request was being handled by a JBE, leaving it in a state where no
build engine sees it as pending. (The exception said the build user
did not have a license permitting it to refresh or read a workspace.
It did have the license, but there may have been a timeout.)

I want to cancel this request, but when I do so the Team Advisor opens
saying "Not authorized to cancel pending build request."
The only role permitted to cancel any request is Administrator, which
both myself and another user have (the other user being the build
user), and neither can cancel it.

When I click the "Why did this happen" link the
"Permissions" section does identify the Administrator role
as one that can cancel.

Any idea how I can get this pending request out? We're running RTC
3.0 iFix 1.
0
permanent link
Sterling Bates (231●16●12) | answered Jul 24 '11, 8:53 p.m.
Hi Geoff,

I had the same thoughts, and did exactly what you are suggesting, including giving the user all roles. It didn't help. I even tried removing the Administrator role and re-adding it, thinking perhaps there was a bad link between the user and the role. Throughout this time I've also been on the "Administrators" list for the project area. (The build in question is associated with the project area.)
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Jul 25 '11, 12:12 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Something else to try is to submit a build, and then cancel it before it
gets picked up by some build engine.
If that works, then it is probably something strange about that one
build job.

Cheers,
Geoff

On 7/24/2011 9:23 PM, sbates wrote:
Hi Geoff,

I had the same thoughts, and did exactly what you are suggesting,
including giving the user all roles. It didn't help. I even tried
removing the Administrator role and re-adding it, thinking perhaps
there was a bad link between the user and the role. Throughout this
time I've also been on the "Administrators" list for the
project area. (The build in question is associated with the project
area.)

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.