Web Deployment Failure: Illegal Symbols en route

Building a deployment package for a website is great for me, but not for other team members.

Error from one of my teammates:

Package in C: \ tfs-public \ SLL - Tolkportalen \ Main \ Source \ Deploy \ SysTest \ OrderPortal.SysTest.zip. C: \ Program Files (X86) \ MSBuild \ Microsoft \ VisualStudio \ v10.0 \ Web \ Microsoft.Web.Publishing.targets (3009.5): Error. Failed to complete network deployment task. (An object of type manifest and the path 'C: \ tfs-public \ SLL - Tolkportalen \ Main \ Source \ Deploy \ SysTest \ OrderPortal.SysTest.SourceManifest.xml "cannot be created.)

An object of type 'manifest' and path 'C: \ tfs-public \ SLL - Tolkportalen \ Main \ Source \ Deploy \ SysTest \ OrderPortal.SysTest.SourceManifest.xml "cannot be created. One or more entries in the manifest" sitemanifest "is invalid Illegal characters in transit. Package failed to execute.

When checking, the OrderPortal.SysTest.SourceManifest.xml file was actually created at the specified path, despite the error message.

One of the fail-safe machines has a source verified in the same place as on my machine, so it should not be a problem with hard coding.

There is another SO question that looks similar, but the error message is not identical, and since I am creating a package (which will be copied to the server for deployment), it should not be the same: Internet publishing package - enable IIS settings from IIS Manager. Deploy Deployment Package

EDIT

The package is configured using the wpp.targets file. If it is deleted, it works on other machines, so there may be something with the settings.

Edit

The error has now been highlighted in the runCommand operator in wpp.targets, which has inline quotes:

<path>net start "Topsi Schedule Service $(Configuration)"</path> 

Removing spaces in the service name and quotation marks resolves the issue. Still don't know why this is not failing on my machine.

+4
source share
2 answers

The website deployment tool must be installed on your computer:

http://technet.microsoft.com/en-us/library/dd569059(v=WS.10).aspx

+2
source

Try to keep track of what he is trying to do with Sysinternals Procmon .

+1
source

Source: https://habr.com/ru/post/1446442/


All Articles