Synchronizing Attributes on tasks
We've added an additional attribute on our Task work item, and we are trying to "Check attributes usage in repository" feature within RTC client. It says there are 400 items that do not have all configured custom attributes. When I click on the "Synchronize Attributes" button, I am getting an error message...
Error running operation 'Synchronizing Attributes'
CRJAZ0368E a database query could not run on the server.
Any way to find out more about this?
RTC 4.0.4
RTC Windows Eclipse Client
Error running operation 'Synchronizing Attributes'
CRJAZ0368E a database query could not run on the server.
Any way to find out more about this?
RTC 4.0.4
RTC Windows Eclipse Client
Accepted answer
Hi Aaron
You need check the below details:
1) Check the eclipse log file.
2) Maybe the server is running out of resources while sync.
3) Verify using the process template the number of custom attributes.
4) Verify you are using a 64-bit 4.0.4 eclipse client(Help> About RTC> Installation details).
5) Try increasing the Xmx value and restart eclipse the eclipse client.
Alternatively, create a query to list the workitems in eclipse client. Right click on the first column of the workitem view and synchronize attribute in group of 20.
If this answers/assist your question please do mark it as accepted.
You need check the below details:
1) Check the eclipse log file.
2) Maybe the server is running out of resources while sync.
3) Verify using the process template the number of custom attributes.
4) Verify you are using a 64-bit 4.0.4 eclipse client(Help> About RTC> Installation details).
5) Try increasing the Xmx value and restart eclipse the eclipse client.
Alternatively, create a query to list the workitems in eclipse client. Right click on the first column of the workitem view and synchronize attribute in group of 20.
If this answers/assist your question please do mark it as accepted.
Comments
Lily Wang
Jul 09 '14, 7:52 p.m.Hi Aaron,
Aaron Chorpenning
Jul 10 '14, 10:59 a.m.I did try a server restart, but that was not enough apparently. Thanks for the suggestion.