This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 14074 (Plato7x)
If real-time ROLAP cubes are stressed, access violations may occur. The following errors are typically logged in the Event Viewer:
Event ID 124: Relational data provider reported error: [sp_trace_setfilter].
Event ID 134: An error occurred while opening a connection to SQL Server to receive real-time updates (error code 3166).
Event ID 134: An error occurred while opening a connection to SQL Server to receive real-time updates (error code 41).
Event ID 124: Relational data provider reported error: [Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.].
Note Because of these access violations, mini-dump files are created in Analysis Services Service Pack 3 (SP3) or later.
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
SQL Server 2000 Analysis Services 64-bit
For additional information about a hotfix build that was designed to be applied on a server that is running SQL Server 2000 Analysis Services 64-bit, or to find out if a fix is scheduled to be included in SQL Server 2000 Analysis Services 64-bit Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
822672 FIX: Hotfix Information for Build 8.0.826.0 of SQL Server 2000 Analysis Services 64-bit
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.