Microsoft KB Archive/883709

= FIX: You receive an &quot;Unspecified error&quot; error message when you use the OLE DB Provider for SQL Server to modify a table row =

Article ID: 883709

Article Last Modified on 5/18/2007

-

APPLIES TO


 * Microsoft Data Access Components 2.8, when used with:
 * Microsoft Windows XP Professional

-





SYMPTOMS
When you try to modify a record in a table by using the Microsoft OLE DB Provider for SQL Server (SQLOLEDB), you receive the following error message:

Run-time error'-2147467259 (80004005)':

Unspecified error

You receive this message when all the following conditions are true:
 * The table contains a trigger, and the trigger uses a FETCH command.
 * The computer has Microsoft Data Access Components (MDAC) 2.8 installed.
 * The FETCH command does not use its optional INTO clause.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



Steps to reproduce the problem
To reproduce the problem, create an update trigger that uses the FETCH command, and then create a Microsoft Visual Basic 6.0 project:  Start SQL Query Analyzer, and then connect to an instance of SQL Server 2000. On the Query menu, click Change Database. The Select Database of  dialog box appears.

Note  is a placeholder for the name of the instance of SQL Server 2000 that you are connected to. In the Name column, click pubs, and then click OK.  In SQL Query Analyzer, run the following Transact-SQL statement: CREATE TRIGGER jobs_Trigger1 ON dbo.jobs FOR UPDATE AS

BEGIN

DECLARE   @job_id int DECLARE job_inserted_cursor CURSOR LOCAL FAST_FORWARD FOR Select job_id FROM inserted

OPEN job_inserted_cursor

FETCH NEXT FROM job_inserted_cursor   /*  The error occurs. */ /* FETCH NEXT FROM job_inserted_cursor INTO @job_id       The error does not occur. */

CLOSE job_inserted_cursor DEALLOCATE job_inserted_cursor

END  Start Microsoft Visual Basic 6.0. In the New Project dialog box, click Standard EXE, and then click Open. By default, a form that is named Form1 is created.</li> In Project Explorer, right-click the Form1 form, and then click View Code.</li>  Paste the following code in the code window of the Form1 form: Dim cn Dim rs

Private Sub Form_Load Set cn = CreateObject(&quot;ADODB.Connection&quot;) cn.Open &quot;Provider=SQLOLEDB;Pwd= ;UID= ;Initial Catalog=pubs;Data Source=, , and   are placeholders for the password, the user name, and the data source for your environment. </li> On the Run menu, click Start. You notice the error message that is mentioned in the &quot;Symptoms&quot; section.</li></ol>

<div class="references_section">