The DeployNew command failed (MDSModelDeloy)

Question

I am trying to deploy the sample .pkg's using the defaults and it is failing.  Could someone please tell me why ?

Tried changing  –service “MDS1” to  –service “MDS_1” and I got the same error

******These commands:************

"C:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration\MDSModelDeploy" listservices

rem this errs out
"C:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration\MDSModelDeploy" deploynew –package “C:\Program Files\Microsoft SQL Server\110\Master Data Services\Samples\customer_en.pkg” –model “Customer” –service “MDS1”

******Yield the following error:*******************

c:\MDS_Presentation>"C:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration\MDSModelDeploy" listservices
MDS services (Service, Website, Virtual Path):
MDS1, Default Web Site, MDS_1

MDSModelDeploy operation completed successfully. Elapsed time: 00:00:09.7083660

c:\MDS_Presentation>rem this errs out

c:\MDS_Presentation>"C:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration\MDSModelDeploy" deploynew –package “C:\Program Files\Microsoft SQL Server\110\Master Data Services\Samples\customer_en.pkg” –model “Customer” –service “MDS1”

MDSModelDeploy operation failed. Elapsed time: 00:00:00.3883468
Error:
The DeployNew command failed because either there is a missing - option or the name is not in quotes. All names that contain spaces must be enclosed in quotation marks.

 

---

Mark

Answer 1

Hi Mark,

Did you perhaps copy and paste the command from a web page or Word document?  This often results in the hyphen character being replaced with some other similar character that is not recognized by MDSModelDeploy.exe's parser.

If this is the case, I recommend that you try replacing the "-"'s in the command by typing them manually.

Let me know if that does not solve the issue for you.

Thanks,
Mark

---

This posting is provided "AS IS" with no warranties, and confers no rights

Answer 2

I re-typed the command as you advised and also tried it on another server...and it ran fine.

I suspect the root case was the old server's install, but do appreciate the help Mark.

Regards

---

Mark

Answer 3

Worked for me too :-)