Microsoft KB Archive/919159

= Error message when you use the Analysis Services Parallel Process Utility to process a partition of SQL Server 2000 Analysis Services: &quot;Run-time error '380': Invalid property value&quot; =

Article ID: 919159

Article Last Modified on 11/21/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Analysis Services

-





SYMPTOMS
When you use the Analysis Services Parallel Process Utility to process a partition of Microsoft SQL Server 2000 Analysis Services, you receive the following error message:

Run-time error '380':

Invalid property value

This problem is likely to occur when the following conditions are true:
 * You set the value of the Fact Table Size property of a cube to 1 in Analysis Manager.
 * You process the default partition of the cube by using the Analysis Services Parallel Process Utility.



CAUSE
This problem occurs because the row count number of the partition of the cube is set to 1. The Parallel Process Utility cannot process such a partition.

When you specify the value of the Fact Table Size property of a cube to 1 in Analysis Manager, the row count number of the default partition of the cube inherits the value that you set for the Fact Table Size property of the cube.



WORKAROUND
To work around this problem, correct the row count number of the default partition of the affected cube. To do this, use one of the following methods.

Note To count the correct row number of the default partition in Analysis Manager, click .. in the Fact Table Size property in Cube Editor. Then, click Yes to count the row number.

Method 1: Use the Partition Aggregation Utility
The Partition Aggregation Utility is included with Microsoft SQL Server Accelerator for Business Intelligence (SQL Server Accelerator for BI). You can use this utility to correct the row count number. To do this, follow these steps:
 * 1) Run the Partition Aggregation Utility.
 * 2) Connect to the instance of SQL Server 2000 Analysis Services.
 * 3) Expand the affected cube, right-click the default partition of the cube, and then click Manage Partition Count.
 * 4) Type the correct value in the Set to Count column, and then click Save.

Method 2: Use the Decision Support Object (DSO) script
You can use the DSO script to correct the row count number. To do this, use code that resembles the following code examples.

Microsoft Visual C# code
//Use DSO. Server dsoServer = new ServerClass; dsoServer.Connect(&quot;&quot;); Database dsoDB = (Database)dsoServer.MDStores.Item(&quot; represents the name of the server,   represents the name of the database,   represents the name of the cube,   represents the name of the partition, and   represents the correct row count number.

Visual Basic .NET code
'Imports DSO Dim dsoServer As New ServerClass dsoServer.Connect(&quot;&quot;) Dim dsoDB As Database = CType(dsoServer.MDStores.Item(&quot;&quot;), Database) Dim dsoCube As Cube = CType(dsoDB.MDStores.Item(&quot;&quot;), Cube) Dim dsoPar As Partition = CType(dsoCube.MDStores.Item(&quot;&quot;), Partition) dsoPar.EstimatedRows =  dsoPar.Update dsoServer.CloseServer



STATUS
Microsoft has confirmed that this is a problem in the Analysis Services Parallel Processing Utility.

