FIX: Writeback Fails with "Relational data provider reported error: []." Error Message (320736)



The information in this article applies to:

  • Microsoft SQL Server 2000 Analysis Services

This article was previously published under Q320736
BUG #: 12814 (plato7x)

SYMPTOMS

If Analysis Services hotfix build 562, 571, 573, 588 or 590 has been installed, a writeback to non-Microsoft SQL Server data sources will fail.

Additionally, the following error message will appear in the Application Event Log numerous times:

Event Type: Error
Event Source: MSSQLServerOLAPService
Event Category: Server
Event ID: 124
Date: 3/6/2002
Time: 1:47:01 PM
User: N/A
Computer: MyServer
Description: Relational data provider reported error: [].

CAUSE

A problem with the data source object in Analysis Services hotfix builds 562, 571, 573, 588 and 590.

RESOLUTION

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 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix should have the following file attributes or later:
 Date         Time       Version         Size              File name   
 -----------------------------------------------------------------------

 03/19/2002   01:57 PM       8.0.0.601   4,043,328 bytes   Msmddo80.dll
 03/19/2002   01:56 PM       8.0.601.0   1,008,192 bytes   Msmdgd80.dll
 03/19/2002   12:53 PM       8.0.601.0   1,774,148 bytes   Msmdsrv.exe
 03/19/2002   01:57 PM       8.0.601.0   2,024,016 bytes   Msolap80.dll
 04/18/2001   12:23 AM   2000.80.382.0     815,676 bytes   Sqldata.dll
 03/19/2002   01:56 PM   2000.80.534.0     590,396 bytes   Sqlsort.dll  
				
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server 2000 Analysis Services versions mentioned in this article.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

Modification Type:MajorLast Reviewed:6/25/2004
Keywords:kbSQLServ2000sp3fix kbbug kbfix kbSQLServ2000preSP3fix KB320736