Monday, July 09, 2012 4:30 PM
I've created a model containing a customer entity with various domain based attributes. I've populated the entities via a combination of manual entry and the staging tables. In the source system I have approx 950 customer records, all of which fail validation on the source system as some of the attributes will be maintained only in MDS and are not in the source systems I'm pulling the initial data from.
I ran the MDSModelDeploy.exe to create a package containing data on the source system. I then ran the package to apply the package using the -deployclone option on my target system. I piped the output into a flat file for review.
Here is the error I'm receiving.
MDSModelDeploy operation failed. Elapsed time: 00:01:00.2314612
A clone of the "Subzero_1" model cannot be deployed.
An error occurred while processing message request type 'EntityMembersMergeRequest'. See exception details for more information.
Package deployment failed with 344 errors
The attribute value is not valid.
The attribute value is not valid. (repeated 344 times)
Any ideas what the issue might be? I have tried verbose logging as well and did not find anything that would point me in the direction of the problem. The end result was that the model was not deployed to the target.
I have also created a package without data, deployed that, then applied the data. This gets the model to the target and the data also appears to be there but I did receive this error on the deployupdate.
This is on SQL Server 2012.
Monday, July 16, 2012 7:50 PMDo have file type attribute in your model?
Yang Wang (Microsoft SQL Server Master Data Services)
Monday, July 16, 2012 8:39 PM
I don't believe I did. If there were it was by accident as I'm not presently planning any attributes of that type.
I did some additional analysis and I believe the problem was related to a domain attribute I had on the entity. At this point I don't have the problem. Of course I've made numerous changes so I can't really pinpoint what might have resolved it. It did seem to go away after I made some data changes, vs. schema changes to the model. Thanks for looking. I'm hoping I don't see it in the future.
Friday, August 31, 2012 12:55 PM
I am experiencing exactly the same issue, and I would like see the "exception details" that are mentioned in the error message as above to try to debug this problem. Where exactly can these "exception details" be found?
Thursday, September 13, 2012 9:58 PMModerator
To get more detailed logging, please follow these steps:
1. Launch Notepad.exe as elevated administrator.
2. Then in notepad, File > Open and point to the location of your MDS Deployment Wizard COnfiguration file...
C:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration\MDSModelDeploy.exe.config
3. Uncomment the one line, by removing the comment markers on this line item. Remove the comments prefix <!-- and suffix -->
<add name="LogFileListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="MdsModelDeployTrace.log" traceOutputOptions="DateTime"/>
4. Change the logging level to ALL by replacing the word Off in this line.
<source name="MDS" switchType="System.Diagnostics.SourceSwitch" switchValue="All">
5. Now save the edits. Close out of MDSModelDeploy.exe if you still have it running. The application must start again from scratch to get the logging output.
6. Repeat the original failure using the MDSModelDeploy.exe command line.
7. Now locate the log output and review the details.
C:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration\MdsModelDeployTrace.log
8. Later, you may reverse the logging setting changes to the config file by commenting out the LogFileListener line item (add <!-- and --> to surround the XML tag) and reverting back to the switchValue="OFF"
Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance