TFS build - VSDBCMD.EXE cannot find deploymanifest

Question

I have the following problem.

I am trying to customize default TFS build process by adding a step where a database is deployed using the database project. I strictly followed these steps, the only difference is that I've done it in another part of the workflow. However, DB deployment always fails with the following error: *** The deployment manifest file Database.Project.Name.deploymanifest does not exist.

Here is the command line that is executed:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VSTSDB\Deploy\VSDBCMD.EXE /a:Deploy /dd+ /dsp:Sql /cs:"Data Source=DB-Server;Initial Catalog=DB.Name;User Id=username;Password=password;" /manifest:Database.Project.Name.deploymanifest

I've double-checked several things - VSDBCMD.EXE utility does exist on the specified path on the build server, Database.Project.Name.deploymanifest file does exist in the build drop directory, and BuildDetail.DropLocation (which is set as the Working Directory in the workflow) field does point to this directory. So it looks like everything should work - but it doesn't. What might be other possible causes of this problem? Thanks in advance.

Just a guess: Have you tried using the full path to the deploymanifest file in /manifest:? — Duat Le
– Duat Le, Commented May 20, 2011 at 13:41
Unfortunately it is not possible to set full path declaratively. This is because each drop folder (where the deploymanifest is located) has different name, something like BuildName_Date.BuildNumber. — Andrei
– Andrei, Commented May 20, 2011 at 13:47
You can use vbscript in the workflow to set these things programmatically. For example, in the command arguments activity parameter, you can build up that string programmatically using hte BuildDetail.DropLocation value. — Dylan Smith
– Dylan Smith, Commented May 20, 2011 at 22:57
@Dylan Smith: Thanks for the reply. Tried that - the same error. — Andrei
– Andrei, Commented May 23, 2011 at 9:53

Andrei · Accepted Answer · 2011-05-23 09:56:53Z

1

Finally I've found a workaround. Instead of BuildDetail.DropLocation I am using Build Agent's working directory. Please note that this is just a workaround, not a complete solution to the problem, and I still have no idea about why the deploymanifest file was not available. However, this approach at least works...

answered May 23, 2011 at 9:56

Andrei

56.8k10 gold badges92 silver badges114 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Andrei Over a year ago

@Alfred, lost that project unfortunately, but as far as I remember I've just figured out absolute path of the Build Agent's working directory and specified it in workflow's Workspace property. Not the best approach of course (hardcoding is always bad) but at least it worked.

Collectives™ on Stack Overflow

TFS build - VSDBCMD.EXE cannot find deploymanifest

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related