Hi all,

I have TFS2012 and run several projects.

We encounterwed with such an error while using Build server.

Overall Build Process
Initial Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory = 
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments = 
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory = 
TestResultsSubdirectory = 
Verbosity = Diagnostic

00:00
Get the Build

00:00
Update Build Number
Initial Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Final Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Result = Ephone_DIT_Deploy_20150424.1

01:56
Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
Initial Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=

00:00
Get the Build Directory
Initial Property Values
Result = d:\temp\217\CTI\Ephone_DIT_Deploy

01:53
If Not String.IsNullOrEmpty(ConfigurationFolderPath)
Initial Property Values
Condition = True

01:53
Run TfsBuild for Configuration Folder
Initial Property Values
BinariesSubdirectory = 
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments = 
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory = 
TargetsNotLogged = 
TestResultsSubdirectory = 
ToolPath = 
ToolPlatform = Auto
Verbosity = Diagnostic
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp" 

00:08
Getting sources

00:02
Labeling sources

00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.

00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.

00:19
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.

00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor

00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:10
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor

00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
 CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
 CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
 CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
 CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll","x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.

00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.

00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll","x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll","x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll","x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll","x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.

00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll","x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll","x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.

00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
 CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
MSBuild Log File

00:08
Generating list of changesets

00:20
Built Skins\SkinEPhone.cs for default targets.
 Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
 C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
 C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
 C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
 Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
 C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
 C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
 C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
 C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
 C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
   at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
   at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
   at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
   at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()

00:03
Creating work item
 
 Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
Exception Stack Trace:    at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
   at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
   at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Final Property Values
BinariesSubdirectory = 
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments = 
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory = 
TargetsNotLogged = 
TestResultsSubdirectory = 
ToolPath = 
ToolPlatform = Auto
Verbosity = Diagnostic
Final Property Values
Condition = True
Final Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
Final Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory = 
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments = 
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory = 
TestResultsSubdirectory = 
Verbosity = Diagnostic

Please have a look and guide where to find a problem

Thanks ahead

In all other inputs to TFS (Team Explorer, TWA, etc.), System.State data is manipulated on input and forced to a specific case (e.g. 'Closed', 'Active', etc. - i.e. Pascal Case With Spaces), but when using Excel Bulk Update, TFS allows the System.State data to be saved in any case chosen by the user (e.g. 'closed', 'cLoSEd', 'aCTIVE', etc.)

There doesn't seem to be any negative impact to TFS other than cosmetic, since the TFS API typically treats those values as case insensitive.  However, it has caused problems for us since we have built custom tools and reports while being unaware of this issue and are now uncovering sleeping bugs when the case of System.State data becomes 'corrupted' in this manner.

Is this a known issue or bug?  If so are there any plans to change this behavior to be consistent with the other TFS UIs?

How do I delete a top level folder inside a project in source control?

For example, if I want to delete the folder "bar" in the project "foo", how can I remove a folder once it has been created?

Can I rename "bar" to something else, like "oranges"?

Can I move "bar" to some other folder in the tree?

How do I rename a team project? The name of the project has to be renamed and I would like to do this with the least amount of pain as possible.

Is it possible to mix local and server workplaces on the same TFS server?

Some of our applications are on devices that only an older version of Visual Studio can publish onto. (This is in a corporate environment, and changing or upgrading the devices is not an option.)

We also have an ERP which is not compatible with anything beyond an older version of Visual Studio.

TFS local workplaces, to my understanding, works only with VS 2012 and later.

Hence, is it possible to mix local and server workplaces on the same TFS server? Would having multiple collections, some designated as local workplace, and some designated as server workplace, be an option? Or is there a best practice for combining the differing workplace options?

I have defined a new state for product backlog items. Now I want to see the PBIs with this state in product backlog main page. But default query for this page just shows New, Approved and Committed states. How can I change this default?

Recently we created new TFS server 2013.4 on Windows server 2008 R2 in Domain A. We connected to this machine from Domain B using Win 7 RDC.

From VS 2013 of domain B  machine, we were able to craete a new Team project in default Collection.

Now we are unable to connect to TFS server (Domain A) using VS 2013 ( Domain B). Error code we get is TF400324.

RDC ( from Domain B) is working fine to go to TFS server machine( Domain A).

Web access ( from Domain B) of TFS is also working fine. Able to create new users / see repository etc..

Please suggest

Is there a  Team Foundation Server Power tools for 2015 yet?

---

@simon_sabin - SQL Know How - SQL Server Consultancy and Real world training - SQLBits - Largest SQL Server Conference in Europe and its free

HI ,

I have written post process program(.NET) for TFS to handle automatic update of the work item field values depends on the conditions in program . So for that values are not reflecting in work item fields unless we refresh the browser :( .

So for that i need  to initiate auto-Refresh after each  post-process .Please anyone help me how to implement Automatic refresh in TFS .

I am getting 2 errors through the event viewer that prevents TFS 2013 authentication for local domain users, also this error started appearing after having TFS upgraded to [ 12.0.30723.0 (Tfs2013.Update3) ].

1st Error (from administrative events):

The Execute method of job definition Microsoft.SharePoint.Administration.SPUsageImportJobDefinition (ID a51a0244-765d-433b-8502-0bb0540ad1fd) threw an exception. More information is included below.

Access to the path 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS' is denied.

Tried so far:-

- changed the path to another folder from "Diagnostic Logging" in another drive, but still getting the same error.

2nd Error (from application server):

DistributedCOM error

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{000C101C-0000-0000-C000-000000000046}
 and APPID 
{000C101C-0000-0000-C000-000000000046}
 to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Which I already got fixed using the following steps on a thread I opened before (but still getting the same error).

https://social.technet.microsoft.com/Forums/windows/en-US/3896e35c-b99a-4d30-b662-f92d337c8d6f/windows-servers-components-services-and-regedit-permissions-are-grayed-out-for-my-admin-account?forum=winservergen

Other Fixes I tried

- Found on another topic that it is not sharepoint that is causing the problem, but it is the generated ASP.NET web pages used for testing is causing the memory to fill up due to cashing on RAM, the fix suggested to change IIS cashing from RAM to HD to prevent loading up using w3wp.exe from processes. 

Concern

- by checking other topics for people having the same problem, it was mentioned that this error appeared after the lastest TFS update, is there is a fix for it ?

Hi ,

we are having TFS 2013 version ..we need to migrate only TFS database server to new server. Please let me know the steps for doing this ..need to restore databases from existing server to new server and Need to point TFS application to Point to New Data Base Server (we don't use Share Point) where to chance the connection string to point to new server..

Regards,

Naveen M

Hi There,

I've configured SMTP services to TFS and alerts settings for workitem in version control.
When our teams are trying to create or made changes in workitems they are not getting any email alerts though everything is been configured perfectly.

please help me out of this issue

thanks in advance

-hariiesh

Hello

I have been asked to add our on premises TFS server to the trusted servers in Azure.  I cannot find any documentation around this, does anyone know how to achieve this?

We have an Office 365 tenant and are using ADFS in Azure for authentication.  We are using dirsync on premises to synchronise Active Directory objects.

Regards

Jonathan

Hey folks--

I spent a bunch of time trying to search the forums for this but it did not prove to be fruitful.

I am a new user to TFS and my previous system had an amazing search capability. Now I understand I can build awesomely powerful queries using the query editor. I do this already. The problem I am facing, however, deals with ad-hoc queries. I am constantly searching for items due to my role in my development team. I cannot be stuck into the Query Editor UI whenever I am looking for something because I am changing the fields all the time.

My questions are as follow:

1. Why do I have to search system.areapath:text while I can search title:text instead of system.title:text?
2. Is there a backend change that can be made such that I only have to search areapath:text?

This is a problem as whether or not the prefix is required seems to be random. To make matters worse, some of the prefixes are totally ridiculous.

For example, if I want to find items whose RequirementType is Customer, I cannot search requirementtype:customer. I have to searchMicrosoft.VSTS.CMMI.RequirementType:customer. The only way I even figured these things out was to build some queries, run them with Fiddler open, and look at the SQL statement.

I apologize if I missed some MSDN article or something here but I have been fighting this for weeks and really need a way to solve this.

Thanks,

newTfsUser

Hi , 

I am trying to access all the testcases of a test plan in the below manner it works for the initial set of plan in the loop but for one the test plan , it gives te below error

 ITestPlanCollection trgtPlan = targetProject.TestPlans.Query("Select * From TestPlan where PlanName ='" + srcplan.Name + "'");
                            if (trgtPlan.Count > 1)
                            {
                                sb.AppendLine(string.Format("This target suite is duplicated:  Plan Name = {0} and Plan ID = {1}", trgtPlan[0].Name, trgtPlan[0].Id));
                            }
                            else
                            {

                                if (trgtPlan.Count == 0)
                                {
                                    sb.AppendLine("This Source Suite is Missed in target : Source Suite name =" + srcplan.Name);
                                }
                                else
                                {
                                    ITestCaseCollection srcTestCases = srcplan.RootSuite.AllTestCases;
                                    foreach (ITestCase srctstCase in srcTestCases)
                                    {

                                        Console.SetCursorPosition(origCol, origRow + 10);
                                        Console.Write("Processing test case :" + srctstCase.Id);
'trgtPlan[0].RootSuite.AllTestCases'
after the above line the below error occursException Message : The given key was not present in the dictionary.
 threw an exception of type 'Microsoft.TeamFoundation.TestManagement.Client.TestManagementServerException'
	Microsoft.TeamFoundation.TestManagement.Client.ITestCaseCollection
{Microsoft.TeamFoundation.TestManagement.Client.TestManagementServerException}

Can any one please help me with this ?

I've found some information on upgrading TFS to Update 4 that says you can only upgrade by uninstalling/reinstalling the server.  Is a Service Pack or similar available?

Really just looking for confirmation as we did not anticipate this.

If I have to uninstall/reinstall are there any special considerations or actions that I should take or is it pretty seamless?

Thanks

We are having issues with the job “Team Foundation Server Periodic Identity Synchronization”.

Within the cycle duration not all Tfs groups are being synchronised. We have investigated the process and think we have a good understanding of how it all hangs together, but we cannot figure out why it is behaving as it is. Below I will firstly summarise our understanding of the process (obtained by testing on our test environment – trial and error) and then explain the issue we are having.

“Team Foundation Server Periodic Identity Synchronization” Job

The settings/details for this job can be found in 2 main SQL tables in the Tfs_Configuration database.

Table - tbl_RegistryItems

#\Service\Integration\Settings\               IdentitySyncCycleDuration\       1.00:00:00

#\Service\Integration\Settings\               IdentitySyncCycleStart\               04/27/2015 03:04:41

#\Service\Integration\Settings\               IdentitySyncFull\                             False

Field - IdentitySyncFull

This can be True or False.

True                      a FULL synchronisation is actioned i.e. all Tfs Groups are synchronised.

False                     an incremental synchronisation occurs every time the job is run

Field - IdentitySyncCycleDuration

As it says, this is the cycle duration.  The default is 1 day. Therefore every day the synchronisation process starts again from the beginning.

Table - tbl_jobschedule

This table shows how often each job is run.  For “Team Foundation Server Periodic Identity Synchronization” the “Interval” field is set to 3600 which is 1 hour.

Therefore according to default settings the job runs incrementally every hour.

The Tfs groups which are synchronised each hour can be seen in the table tbl_group. Only active groups are synchronised and Tfs groups seem to be synchronised in SID order (for each Tfs group see the lastsync field).

Our issue is as follows

We have approx. 700 active tfs groups.  Each day the process starts from the beginning and synchronises Tfs groups in SID order. Each hour a small number of Tfs groups are synchronised.  Note only about 10-15 at a time.  Therefore as the job only runs 24 times within the one day cycle duration, only about ½ our Tfs groups are getting synchronised.  The other ½ are never getting synchronised.  The only way to get all the Tfs groups synchronised would be to run a FULL sync.

I must emphasize that the job is running successfully each hour, with no errors. I can see this via the TFS Job Monitoring and also via Event Viewer.

We have a number of questions about the overall process.

1. Why are all Tfs groups (and thus users) not being synchronised within the cycle duration?
2. The number of Tfs groups synchronised varies each hour.  What determines how many Tfs groups are synchronised each hour? The answer to this question may also answer question 1.

Any feedback/advice would be much appreciated.

Thanks

Thomas

HI,

we have requirement to change TFS Database server to other server. Application server remains the same.

Followed Following steps described in blog

http://blogs.msdn.com/b/tfssetup/archive/2014/05/15/migrating-team-foundation-server-databases.aspx#comments

we have Taken DB Backups from OLD server and restored In new server.

Executed following Command for Remapping the DB's below one is success

TFSConfig RemapDBs /DatabaseName:ServerName;DatabaseName/SQLInstances:ServerName1,ServerName2
[/AnalysisInstance:ServerName] [/AnalysisDatabaseName:DatabaseName]

Question 1:

Next Used following Below Syntax to change owners of TFS DB's.. Got success message but When I checked the TFS DB properties its showing the owner of user who done Restore of DB (But not the User Name who executed this command in application server)

Syntax:TFSConfig Accounts /ResetOwner /SQLInstance:ServerName/DatabaseName:DatabaseName

what exactly the above command will do where can I check result of above command?

Question 2: in above blog requested to execute below command to Update service account for TFS.. But my TFS Service account is Mentioned as "Network Service" when checked in "Application Tier Summary"

Syntax : TfsConfig Accounts /add /AccountType:ApplicationTier/account:AccountName
/SQLInstance:ServerName /DatabaseName:DatabaseName　

For me it's not needed to execute this command right? because my TFS service account is Network Service it's not a custom account?

please help me on this.

Regards,

Naveen M

Hi All

How do I add Definition of Done in TFS 2013 ? 

Thanks

Anu

---

Anu Viswan : www.AnuViswan.blogspot.com

Hi all,

First, I've gone through many docs, links, etc to get a test Build Server up and running along with a successful first Build Definition using both the default and a customized template.  I say this because the question(s) I'm about to ask may have been buried in all that information that is now swirling around my head.

First it might be advantageous to quickly look at what we do now.  In our script we have Major, Minor, Build, and Revision variables that are manipulated both manually and in code.  Let's say we are creating a version 10 of our product.  I will go in and edit the Major (10), Minor (0) and Build (0) numbers manually before that versions first script run.  The Revision number is bumped by 1 with each subsequent build.  So, build one of v10 will be 10.0.0.1, then 10.0.0.2, etc.

This 4 segment version is then used to set the PRODUCT version of the compiled files.

Later in the build script, we do a dance to get three position version number for our Windows Installer packages since Microsoft only utilizes #.#.# in that realm.  It's basically Build# * 256 + Revision# or something to that effect.  This is then passed in to the package.  I guess this part of it could or will need to be handled with an external script and InvokeProcess, which is fine.

My main concern deals with how versioning works within the confines of a TFS Builds.  I believe I read something about tokens that may be the answer.  What I would like to happen is that all FILE versions are bumped automatically with each build.  I don't know if there is a setting that can be utilized within each solution/project that could handle that or not.  Then I'm hoping I can somehow get the Major, Minor, Build and Revision numbers for script use, etc.

Is there a canned way of going about this or should all of this be scripted in some way with maybe  Pre MSBuild/compile script set up in the Build Definition.

Any help/guidance with this would be greatly appreciated!

THANKS IN ADVANCE!!!