Hi,
In the ‘Match Data’ step (step 25) of the MSDN EIM tutorial:
http://technet.microsoft.com/en-us/library/jj819738.aspx
I get the following error dialog:
--
"The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs."
--
I have re-tried using a separate DQS Knowledgebase, different entities etc., but get the same error.
I was able to use the DQS Knowldege base to perform matching within DQS itself as part of the earlier lesson of the same tutorial.
I also, as part of the tutorial, had no trouble importing data into MDS via the Excel MDS Add-in,
and then subsequently viewing it through the MDS Web Application
The difficulty seems to be accessing the DQS Matching from Excel MDS Add-In
At the bottom of this post I have included MDS logs from when it happens.
Excel MDS Ad-In versions:
- Microsoft.MasterDataServices.ExcelAddIn.dllFile Version: 11.0.2100.60
- Microsoft.MasterDataServices.ExcelAddInCore.dll File Version: 11.0.3393.0
I am using Excel 2013 64-bit (15.0.4615.1000).
My OS is WIndows 8.1 Enterprise.
The MDS Excel Add-in was installed following
http://www.microsoft.com/en-us/download/details.aspx?id=35581
Thanks
Martin
MDS Logs:
------------
2014-05-16T14:58:15.388 5964 EXCEL.EXE EXCEL.EXE Generic EventType: Information, Message: DataQualityMatchingOperationStartOperation end
2014-05-16T14:58:15.389 5964 EXCEL.EXE EXCEL.EXE Generic EventType: Error, Message: Async executer exception System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.MasterDataServices.ExcelAddInCore.MDSService.IService.EndDataQualityMatchingOperationCreate(IAsyncResult result)
at Microsoft.MasterDataServices.ExcelAddInCore.Types.Operations.DataQualityMatchingOperationCreateOperation.EndOperation(IAsyncResult ar)
at Microsoft.MasterDataServices.ExcelAddInCore.Operations.SequenceOperationExecuter.<Body>d__0.MoveNext()
at Microsoft.MasterDataServices.AsyncEssentials.AsyncExecuter`1.Advance()