Error while trying to load the mining model in the mining model viewer

I get the following error when I try to load the mining model in the mining model viewer

Query (1, 6) The '[System].[Microsoft].[AnalysisServices].[System].[DataMining].[NeuralNet].[GetAttributeValues]' function does not exist.

I get a similar error when I try to load the Load Mining Accuracy Chart

Failed to execute the query due to the following error:

Query (1, 6) The '[System].[Microsoft].[AnalysisServices].[System].[DataMining].[AllOther].[GenerateLiftTableUsingDatasource]' function does not exist.

I have OWC 11 installed. What am I missing here?

Thanks

These are Analysis Services stored procedures that are suppposed to be installed with your server. Would you please start Management Studio and coonect to the Analysis Services instance you are using? After you connected, click the Assemblies in the object Explorer, you should be able to find System listed there. Right click system, and select properties. You will have a list of properties of this the system assembly.

At first, please verify your assemly exisits. The location of the assembly is list under general->Source. And it looks something like this:

C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\bin\msmdspdm.dll

Please verify this file is not deleted by accident

Second, please check Security Settings. Usually, it should work fine for the following settings:

Impersonation Info ImpersonateServiceAccount

Permission Set Unrestricted.

Good luck,

|||

I installed SQL Server and SSAS in D drive. For some reason, the System assembly source property still points to the C drive. I can't change it either from the property screen or rerun the XMLA script. I also copied the folder from D: to C:. It does not work either.

Do you know how to resolve it?

Thanks a lot.

|||

On possible solution (if you don't have any sensitive data in Analysis Services): stop the service, rename your Data folder to something like Data.bak (%ProgramFiles%\Microsoft SQL Server\MSSQL.2\OLAP\Data), then restart the service. This might fix the incorrect path issue.