I've created a CLR Analysis Server assembly that uses the ADOMD Client DLL. When I import the Assembly into my AS Server I don't receive any errors. But when I attempt to call the assembly I receive a #Error as the return. Hovering over the error it says
that it can't find the Microsoft.AnalysisServices.AdomdClient.
When I try to add the ADOMD Client DLL, I get "The main assembly has the same public key as the components installed by SQL Server Setup, you cannot use it as the main file in a CLR Assembly Object. (Microsoft.AnalysisServices)"
So looks like a Catch 22 to me. What am I missing? If AS detects that the assembly already exists in the server, why doesn't it simply use the one that is installed instead of throwing the 2nd error stating that I can't import it either???
Clearly I am missing something in my interpretation of the error, has anyone ever seen this before and how can I get around the problem???
View Complete Post