| Event Id | 128 |
| Source | MSSQLServerOLAPService |
| Description | Error during lazy aggregation of partition <Partition name> in cube <Cube name>: |
| Event Information | According to Microsoft : CAUSE This problem occurs because the counter for the number times that the lazy aggregation process is suspended for the same partition is not reset. This counter is not reset when the lazy aggregation process cannot finish because of a cancel request that is generated by another process on the server. Analysis Services uses background threads to rebuild flexible aggregations for a partition. This occurs after an incremental update to a changing dimension caused the aggregation to be dropped. The server keeps an internal count of the number of times that the lazy aggregation thread tries to process aggregations for a partition. By default, the lazy aggregation thread tries to process the missing aggregations for a partition three times. Then, the lazy aggregation thread reports an error for the aggregation-building process and marks the partition as being unable to be indexed. RESOLUTION Hotfix information for Microsoft SQL Server 2000 Service Pack 4 (SP4) A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix. |
| Reference Links | Event ID 128 may be logged if the lazy aggregation process is suspended multiple times in SQL Server 2000 Analysis Services |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.