no log file created

May 13, 2014 at 7:47 PM
We're attempting to use TFS aggregator for the first time - we're attempting to rollup the hours on all tasks to the story level. Our server support person has uploaded the Aggregator.xml file shown below to the Plugins folder. He has created a new username and password solely for TFS aggregator and granted project admin rights to the project. The user was also added to the appropriate TFS group. Can you please take a look at XML below and advise if anything looks incorrect / should be changed?

The file's been uploaded to the Plugins folder. When we look at the backlog, we don't see the hours being rolled up, nor do we see an error log. Need assistance in determining where to look or what could be wrong.

Thanks in advance for your help.

<?xml version="1.0" encoding="utf-8"?>
<AggregatorItems tfsServerUrl="http://tfs2012qa:8080/tfs/FirstCollection" username="TFS-Aggregator-QA" password="xxxxx" loggingVerbosity="Diagnostic">
<!--Add the remaining work from the tasks up to the parent --> <AggregatorItem operation="Sum" linkType="Parent" linkLevel="1" workItemType="Task">
    <TargetItem name="Remaining Work"/>
    <SourceItem name="Remaining Work"/>
</AggregatorItem>
<!--Add the original estimate from the tasks up to the parent --> <AggregatorItem operation="Sum" linkType="Parent" linkLevel="1" workItemType="Task">
    <TargetItem name="Original Estimate"/>
    <SourceItem name="Original Estimate"/>
</AggregatorItem>
<!--Add the completed work from the tasks up to the parent --> <AggregatorItem operation="Sum" linkType="Parent" linkLevel="1" workItemType="Task">
    <TargetItem name="Completed Work"/>
    <SourceItem name="Completed Work"/>
</AggregatorItem>
</AggregatorItems>
May 28, 2014 at 8:41 PM
I am having potentially similar problem. Did you ever figure out your issue? If so what was it and how did you resolve it?
May 29, 2014 at 11:10 AM
Unfortunately, we have not been able to resolve the issue. We are not seeing anything being logged, either, so no way for us to determine what is causing the error. Our server support person is trying a few things to further debug the issue - so far, he hasn't had any luck. If we're able to figure it out, I'll post the resolution.