July 11, 2017 | Kliment Klimentov
When building an .update package with TDS Classic, the build might fail with no additional information about the problem. The logs will show only:
Done building project "<Project Name>.scproj" -- FAILED.
Look at the Sitecore log
These errors usually point to a problem on the target Sitecore instance; Sitecore is throwing an error when TDS Classic communicates with the service. There could be additional information about the problem in the Sitecore log.
Increase log verbosity
You can see more details about the problem by changing the logging verbosity to "normal" or "detailed" - in most cases "detailed" will flood you with too much information, so we recommend that you begin with "normal". Changing the log verbosity depends on how you are building the TDS Classic Project - specifically, whether you are using a build server or performing a local build.
Most build servers have settings to configure the build log verbosity. You can also accomplish it by passing the /v:normal or /v:detailed parameter to MS Build.
If you're performing a local build, the verbosity can be changed as described in our post on increasing build log verbosity.
In most cases this will display enough information to see the root of the problem. However, as TDS Classic relies on the Sitecore API to report errors, the logged information is not always helpful.
Use validators to minimize the chance of getting such error
Another common cause for this type of error are illegal characters (usually 0x03) in your items. You can catch such exceptions by enabling the validator for illegal characters.