Resolving the '0 file(s) transferred successfully' error in Release Management

Posted by Daniel Mann - October 17, 2014


I had a client that was receiving an error message when trying to do a release from Release Management to a server that was configured to transfer the binaries over HTTP.

After 0 file(s) transferred successfully, file createTable.sql did not

We couldn't figure out what the problem was -- we looked at everything: The agents, permissions, the database, the file shares. Transferring directly via UNC path was working fine!

We finally figured out a solution:

Log in to the Release Management server (not the deployer server!) and make sure the "Release Management Monitor" service is running. If that service isn't running, it can't serialize the files over HTTP.

Topics: Blog, InRelease

Recent Posts

Webinar: What is MLOps & Why is it Important?

read more

Webinar: Getting Started with Containers & Azure Kubernetes Service (AKS)

read more

InCycle Wins Two Microsoft Awards - Extends Win Streak to Five Years

read more