Compilation error due to Filename too long (name = repeated), who knows why??
Hi all,
Everytime we try to publish to our production server using Teamcity, we get an error as follows:
(i'd like to mention that when we publish it to our test server, also using Teamcity, everything goes smooth)
Does someone know how to troubleshoot this?
- C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(951, 5): error MSB4018: The "FilterByItems" task failed unexpectedly. System.InvalidOperationException: The item metadata "%(FullPath)" cannot be applied to the path "_p\Archive\Content\C_C\PackageTmp\_p\Archive\Content\C_C\PackageTmp\_p\Archive\Content\C_C\PackageTmp\Plugins\Plugin.AddonProduct.Insurance\BeBuild.Mail.Templates\OrderApprovalCanceledToOwner\Subject.en-US.cshtml". _p\Archive\Content\C_C\PackageTmp\_p\Archive\Content\C_C\PackageTmp\_p\Archive\Content\C_C\PackageTmp\Plugins\Plugin.AddonProduct.Insurance\BeBuild.Mail.Templates\OrderApprovalCanceledToOwner\Subject.en-US.cshtml at Microsoft.Build.Shared.ErrorUtilities.ThrowInvalidOperation(String resourceName, Object[] args) at Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInvalidOperation(Boolean condition, String resourceName, Object arg0, Object arg1, Object arg2) at Microsoft.Build.Shared.FileUtilities.ItemSpecModifiers.GetItemSpecModifier(String currentDirectory, String itemSpec, String definingProjectEscaped, String modifier, String& fullPath) at Microsoft.Build.Evaluation.BuiltInMetadata.GetMetadataValueEscaped(String currentDirectory, String evaluatedIncludeBeforeWildcardExpansionEscaped, String evaluatedIncludeEscaped, String definingProjectEscaped, String name, String& fullPath) at Microsoft.Build.Execution.ProjectItemInstance.TaskItem.GetBuiltInMetadataEscaped(String name) at Microsoft.Build.Execution.ProjectItemInstance.TaskItem.GetMetadataEscaped(String metadataName) at Microsoft.Build.Execution.ProjectItemInstance.TaskItem.GetMetadata(String metadataName) at Microsoft.Web.Publishing.Tasks.FilterByItems.Execute() at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
Please sign in to leave a comment.
Hi Jonathan, sorry for the delay. What are the differences in the build between deploying to production or test? Only the remote address? What kind of build step are you using (Visual Studio, MSBuild...), does this step know somehow the difference? (building different targets that might have different configurations, etc).
If none of that helps, it might be useful if you could send us a build log for the same commit for production and test, to see the differences. Please use the Submit a request button above to send them to us privately.
Hi Denis, Thanks for your response. A complete reinstall / upgrade to the latest TC version fixed the issue (so far).
Hi Denis, it occurs again. I will do as you said and submit a request.