Microsoft KB Archive/296929

Knowledge Base

FIX: Creation of Ad Hoc Data Mining Models Fails with Mining Execution Location=3

Article ID: 296929

Article Last Modified on 11/21/2006

---

APPLIES TO

• Microsoft SQL Server 2000 Analysis Services

---

This article was previously published under Q296929

BUG #: 11428 (Plato7.x)

SYMPTOMS

When you attempt to create an ad hoc data mining model, with the Mining Execution Location set to server (3), a message similar to one of the following messages appears:

-2147467259 The operation has failed because of an error in the COM component (Microsoft(r) OLE DB Provider for Data Mining Services) The model 'Test17_20' does not exist

-or-

-2147467259 The operation has failed because of an error in the COM component (Microsoft(r) OLE DB Provider for Data Mining Services) No such interface supported

CAUSE

If the Mining Execution Location property of the connection is set to the server, statements are sent to the server without pre-parsing and checking the type of statement.

RESOLUTION

To resolve this problem, obtain the latest service pack for the Microsoft SQL Server 2000 (the Analysis Services Components - Sql2kasp1.exe). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

STATUS

Microsoft has confirmed that this is a problem in SQL Server 2000 Analysis Services version 8.0. This problem was first corrected in the Analysis Services Components of Microsoft SQL Server 2000 Service Pack 1.

MORE INFORMATION

Only SELECT statements may be executed remotely. Data Definition Language commands cannot be executed remotely. Commands that use the Data Definition Language, executed remotely, result in the following error message:

-2147467259 : The operation has failed because of an error in the COM component (Microsoft(r) OLE DB Provider for Data Mining Services) Only SELECT statements can be executed remotely on the Analysis Server (use DSO for model creation/maintenance). Check Mining Execution Location property.

Steps to Reproduce Behavior

1. Create a new Microsoft Visual Basic Standard EXE project.
2. Add a reference to the Microsoft Active Data Objects Library.

3. Add the following code to the Form_Load method of Form1:

   Private Sub Form_Load()
      Dim ado_dbConnection As ADODB.Connection
      Dim sConnectString As String
      Set ado_dbConnection = New ADODB.Connection
      ado_dbConnection.Open "Provider=MSOLAP.2; Mining Execution Location=3;" & _
         "Data Source=localhost;Initial Catalog=FoodMart 2000;"
   
      ado_dbConnection.Execute "Create Mining Model Test17_20(CaseID long key, " & _
                                   " x1 double continuous," & _
                                   " x2 double continuous," & _
                                   " x3 double model_existence_only continuous predict," & _
                                   " x4 double model_existence_only continuous predict ) using microsoft_clustering (Cluster_count = 2)"
   
      'ado_dbConnection.Execute "Select Measures.Members on columns, {[Store].[All Stores].[USA].Children} on rows from sales"
           
     If Not ado_dbConnection Is Nothing Then
       If ado_dbConnection.State = adStateOpen Then
         ado_dbConnection.Close
       End If
     End If
   End Sub
                       

4. Run the Visual Basic project, and note the error message that occurs.

5. Replace the ado_dbConnection.Execute statement from the code snippet with the following statement:

   ado_dbConnection.Execute "Select Measures.Members on columns, {[Store].[All Stores].[USA].Children} on rows from sales"
                       

6. Run the Visual Basic project and note that no error message occurs.

Additional query words: DATA MINING EXECUTION LOCATION OLAP -2147467259

Keywords: kbbug kbfix kbsqlserv2000sp1fix kbssas800sp1fix KB296929

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.