Data Collection (ETL) jobs failing in RTC 4.0?

Naren S

(11●1●2●1) Aug 28 '12, 5:59 a.m.

I keep getting the following error when trying to run all the datawarehouse jobs....

RTC 4.0 in WAS 8.0 64 bit (Windows 2008 server 64 bit OS)

SQL server 2008 server DB

RRDI in WAS 8.0 64 bit and Win 2008 Server 64 bit OS.

Exception from the JTS-etl.log file...

2012-08-28 21:51:31,520 [ jts: AsynchronousTaskRunner-4] DEBUG ervice.internal.common.CommonRemoteSnapshotService - ETL: ***Started Build Contributor at 28/08/12 9:51 PM***
2012-08-28 21:52:02,098 [ jts: AsynchronousTaskRunner-4] ERROR ervice.internal.common.CommonRemoteSnapshotService - com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1417E: The HTTP status '401' and the message is 'Unauthorized'.
java.sql.SQLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1417E: The HTTP status '401' and the message is 'Unauthorized'.
at com.ibm.rational.drivers.jdbc.xml.BaseRDSResultSet.fetchMoreData(BaseRDSResultSet.java:2101)
at com.ibm.rational.drivers.jdbc.xml.BaseRDSResultSet.next(BaseRDSResultSet.java:1472)
at com.ibm.team.datawarehouse.service.XdcResultSet.next(XdcResultSet.java:176)
at com.ibm.team.datawarehouse.service.internal.common.etlbuild.Contributor.execute(Contributor.java:94)
at com.ibm.team.datawarehouse.service.internal.common.CommonRemoteSnapshotService.updateSnapshot(CommonRemoteSnapshotService.java:128)
at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService$1.run(AbstractRemoteSnapshotService.java:211)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$5.run(RemoteDatabaseService.java:254)
at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:381)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:244)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy66.write(Unknown Source)
at com.ibm.team.datawarehouse.service.internal.RemoteDataWarehouseProvider.write(RemoteDataWarehouseProvider.java:29)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy1231.write(Unknown Source)
at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService.updateData(AbstractRemoteSnapshotService.java:206)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy284.updateData(Unknown Source)
at com.ibm.team.datawarehouse.service.internal.InternalDataWarehouseService.updateAllRemoteSnapshotDataFromTask(InternalDataWarehouseService.java:898)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy282.updateAllRemoteSnapshotDataFromTask(Unknown Source)
at com.ibm.team.datawarehouse.service.internal.SnapshotRunnerTask.transactionSucceeded(SnapshotRunnerTask.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy289.transactionSucceeded(Unknown Source)
at com.ibm.team.repository.service.internal.AsynchronousTaskSchedulerService$2.transactionSucceeded(AsynchronousTaskSchedulerService.java:828)
at com.ibm.team.repository.service.internal.AsynchronousTaskSchedulerService$2.executeTask(AsynchronousTaskSchedulerService.java:837)
at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:136)
at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:99)
at java.lang.Thread.run(Thread.java:769)

1 vote

Comments

ankur sharma

JAZZ DEVELOPER Aug 28 '12, 8:27 a.m.

Is the Data collector licence assigned to the user id running the data collection jobs? Also, ensure that password for that user id is correct and not locked or expired.

4 answers

12,974 views

1 vote

Accepted answer

Permanent link

Rafael Hayama

(159●2●6) Jul 30 '13, 1:26 p.m.

This behaviour is resultant of password changes sometimes requiring new keys.

The steps provided in the Resolving the Problem field of the follow up technote should address this issue.

http://www-01.ibm.com/support/docview.wss?uid=swg21591743

Regards, Rafael.

Rosa Naranjo selected this answer as the correct answer

2 votes

Comments

Sean G Wilbur

JAZZ DEVELOPER Nov 09 '13, 9:42 p.m.

Worked for me, thanks for the post!

Leandro Leal

Aug 28 '14, 3:00 p.m.

Very Thanks Rafael, worked for me, maybe because the user collector have password with special characters.....

Georg Kellner

Sep 03 '14, 7:42 a.m.

Is this way also valid for the change from internal user management to LDAP?

Francesco Chiossi

Sep 03 '14, 8:21 a.m.

You can follow the steps 18 to 28 of the technote above but with the following changes: XDC Authentication = Form Data Collection User or Consumer Key = the user ID of the LDAP user that exists already in CLM Data Collection User or Consumer Key = the password of the user above

3 other answers

Permanent link

Pancha Gyaneswari Yelika

(45●8●11) Dec 21 '12, 5:39 a.m.

Hi..
I am also facing the same issue.
The Data Collector license is assigned to the user running the Data collection jobs.

Please let me know if you have the solution.

0 votes

Permanent link

Michele Pegoraro

(1.8k●14●119●103) Jan 25 '13, 11:00 a.m.

Hi, I also have this error. Password is correct (user is defined on LDAP domain) the user (etl_user) has JazzDWAdmins and he has the Data Collector license.

But I still have the error.

Michele.

0 votes

Comments

James Cole

Jan 28 '13, 9:05 a.m.

Hi Michele, Have you checked the user mappings in the WAS configuration? Is it in more than one mapping? Also, make sure you have set the base distinguished name for users and groups correctly. i.e can both WAS and RTC Setup find the user correctly? Regards James

Michele Pegoraro

Jan 28 '13, 10:01 a.m.

We use tomcat. Has the mapping be set also in tomcat-user.xml? Is not sufficient the LDAP configuration in advanced properties? Thanks, Michele.

Michael A.

Jul 01 '13, 11:08 a.m.

Hi, I just upgraded to 4.0.3 and we are also seing that error in the logs. We are on a Tomcat environment and we are using the Tomcat User Registry. Did you guys find a solution that the problem? Regards Michael

Permanent link

Sumant Renukarya

(1.1k●2●33●39) Mar 07 '14, 5:45 a.m.

The user id running the data collection jobs not only needs to have the Data Collector license assigned but also needs to have JazzAdmins permission:

http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.rational.rcpr.help.doc%2Ftopics%2Ft_running_the_data_collection_jobs.html

These needs to be verified.

0 votes

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.

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

rational-team-concert

× 43,080

troubleshooting

× 6,082

rrdi

× 403

× 94

× 53

× 7

× 2

Question asked: Aug 28 '12, 5:59 a.m.

Question was seen: 12,974 times

Last updated: Sep 03 '14, 8:21 a.m.

Data Collection (ETL) jobs failing in RTC 4.0?

Comments

4 answers

12,974 views

1 vote

Accepted answer

Comments

3 other answers

Comments

Your answer

Follow this question

Question details

Related questions