Successful Build Returning Error (ServerRuntimeError.log)

Does the user account that the JBE logs in with in fact have "View Build
Artifacts" privileges in the team/process area that owns that build
engine? If not, give it the role that has that privilege, and try again.

Cheers,
Geoff

On 7/21/2011 2:53 PM, bcourt wrote:

Hi, I have a build that is completing successfully and the output of
the build is being attached to the build record in RTC properly.
However, in the logs section of the build record there are 17 copies
of the ServerRuntimeError.log file attached that all contain java
exceptions with variants on the following:

com.ibm.team.repository.common.LicenseNotGrantedException: CRRTC3016E:
The client access licenses assigned to you do not allow for the
following operation: View Build Artifacts.

My JBE is running on linux and the build itself is being run via
Maven. Has anyone else seen this issue? I can't figure out where
these exceptions are coming from as the build itself appears to be
completing ok. Any help that anyone here can provide to aid in
troubleshooting this issue would be greatly appreciated. Thanks!

Thanks, I see a lot of different build privileges (Request Build, Save Build Definitiion,Control The Build Lifecycle,...) but I don't see one for View Build Artifacts. Am I missing something?

I dug through the exception trace in the log file and found the following listed as the root cause.
com.ibm.team.repository.common.LicenseNotGrantedException: CRRTC3016E: The client access licenses assigned to you do not allow for the following operation: View Build Artifacts.
Caused by: com.ibm.team.repository.common.LicenseNotGrantedException: An error response was received from the Jazz Team Server. Status=400. Message: CRJAZ1381I The user has a "Contributor" client access license assigned that would normally allow this operation, but the license expired on Jun 24, 2011 10:29 PM. You can install a permanent client access license to re-enable this operation.
Caused by: com.ibm.team.repository.common.LicenseNotGrantedException: An error response was received from the Jazz Team Server. Status=400. Message: CRJAZ1381I The user has a "Contributor" client access license assigned that would normally allow this operation, but the license expired on Jun 24, 2011 10:29 PM. You can install a permanent client access license to re-enable this operation.

That doesn't really make sense to me as the account used has "Developer-Floating" license and the Team Member role which should have rights for all the build actions.

Does the user account that the JBE logs in with in fact have "View Build
Artifacts" privileges in the team/process area that owns that build
engine? If not, give it the role that has that privilege, and try again.

Cheers,
Geoff

On 7/21/2011 2:53 PM, bcourt wrote:

Hi, I have a build that is completing successfully and the output of
the build is being attached to the build record in RTC properly.
However, in the logs section of the build record there are 17 copies
of the ServerRuntimeError.log file attached that all contain java
exceptions with variants on the following:

com.ibm.team.repository.common.LicenseNotGrantedException: CRRTC3016E:
The client access licenses assigned to you do not allow for the
following operation: View Build Artifacts.

My JBE is running on linux and the build itself is being run via
Maven. Has anyone else seen this issue? I can't figure out where
these exceptions are coming from as the build itself appears to be
completing ok. Any help that anyone here can provide to aid in
troubleshooting this issue would be greatly appreciated. Thanks!

Based on those error messages, it is not a role-based permissions issue,
but rather a licensing issue. You might want to work directly with
Rational support on this, but the kind of things to look for are: -
verify that the account that the build is running under really is the
account that you think it is.
- open up the user profile of that user, and verify that it really has
been assigned a floating Developer license.

Cheers,
Geoff

On 7/22/2011 10:08 AM, bcourt wrote:

Thanks, I see a lot of different build privileges (Request Build, Save
Build Definitiion,Control The Build Lifecycle,...) but I don't see one
for View Build Artifacts. Am I missing something?

I dug through the exception trace in the log file and found the
following listed as the root cause.
com.ibm.team.repository.common.LicenseNotGrantedException: CRRTC3016E:
The client access licenses assigned to you do not allow for the
following operation: View Build Artifacts.
Caused by: com.ibm.team.repository.common.LicenseNotGrantedException:
An error response was received from the Jazz Team Server. Status=400.
Message: CRJAZ1381I The user has a "Contributor" client
access license assigned that would normally allow this operation, but
the license expired on Jun 24, 2011 10:29 PM. You can install a
permanent client access license to re-enable this operation.
Caused by: com.ibm.team.repository.common.LicenseNotGrantedException:
An error response was received from the Jazz Team Server. Status=400.
Message: CRJAZ1381I The user has a "Contributor" client
access license assigned that would normally allow this operation, but
the license expired on Jun 24, 2011 10:29 PM. You can install a
permanent client access license to re-enable this operation.

That doesn't really make sense to me as the account used has
"Developer-Floating" license and the Team Member role which
should have rights for all the build actions.

gmclemmwrote:
Does the user account that the JBE logs in with in fact have
"View Build
Artifacts" privileges in the team/process area that owns that
build
engine? If not, give it the role that has that privilege, and try
again.

Cheers,
Geoff

On 7/21/2011 2:53 PM, bcourt wrote:
Hi, I have a build that is completing successfully and the output
of
the build is being attached to the build record in RTC properly.
However, in the logs section of the build record there are 17
copies
of the ServerRuntimeError.log file attached that all contain java
exceptions with variants on the following:

com.ibm.team.repository.common.LicenseNotGrantedException:
CRRTC3016E:
The client access licenses assigned to you do not allow for the
following operation: View Build Artifacts.

My JBE is running on linux and the build itself is being run via
Maven. Has anyone else seen this issue? I can't figure out where
these exceptions are coming from as the build itself appears to be
completing ok. Any help that anyone here can provide to aid in
troubleshooting this issue would be greatly appreciated. Thanks!

It might be 137679: User with an expired Developer trial license and a valid license both assigned is unable to save work items. I know this originally was for work items, but we've had several defects written against the Build component dup'd to that defect. It was fixed for the 3.0.1 release, but if you need it for a previous release, you should contact support.

Brent Ulbricht
RTC Build Lead

So is this problem solved after JTS restart ?

I'm facing exactly similar issue with the build.

It might be 137679: User with an expired Developer trial license and a valid license both assigned is unable to save work items. I know this originally was for work items, but we've had several defects written against the Build component dup'd to that defect. It was fixed for the 3.0.1 release, but if you need it for a previous release, you should contact support.

Brent Ulbricht
RTC Build Lead

We started having the problem today. Builds have been running fine, and not permission were changed. Restarted server, stopped/restarted agent/engine and still having problem. On version 3.1 ifix1.

Is there a fix? or did we do something wrong?

Mel

So is this problem solved after JTS restart ?

I'm facing exactly similar issue with the build.

It might be 137679: User with an expired Developer trial license and a valid license both assigned is unable to save work items. I know this originally was for work items, but we've had several defects written against the Build component dup'd to that defect. It was fixed for the 3.0.1 release, but if you need it for a previous release, you should contact support.

Brent Ulbricht
RTC Build Lead