update link server error | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

update link server error

I am trying to do an update on a linked server, which is a development server. I get this error everytime. when I remove the update code everything works fine.<br /><br />Error:_________________________________________________________<br /><br />Server: Msg 7306, Level 16, State 2, Procedure transfer_documents, Line 42<br />Could not open table ‘"rds"."dbo"."uploadtable"’ from OLE DB provider ‘SQLOLEDB’. The provider could not support a row lookup position. The provider indicates that conflicts occurred with other properties or requirements.<br />[OLE/DB provider returned message: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.]<br />OLE DB error trace [OLE/DB Provider ‘SQLOLEDB’ IOpenRowset:<img src=’/community/emoticons/emotion-3.gif’ alt=’:O’ />penRowset returned 0x80040e21: [PROPID=DBPROP_BOOKMARKS VALUE=True STATUS=DBPROPSTATUS_CONFLICTING], [PROPID=DBPROP_COMMANDTIMEOUT VALUE=600 STATUS=DBPROPSTATUS_OK], [PROPID=Unknown PropertyID VALUE=True STATUS=DBPROPSTATUS_OK], [PROPID=DBPROP_IRowsetLocate VALUE=True STATUS=DBPROPSTATUS_CONFLICTING], [PROPID=DBPROP_IRowsetChange VA…<br /><br /><br />Code:__________________________________________________________<br />create procedure update_loaddate <br />@id int<br />as <br />update techwebdev.rds.dbo.uploadtable<br /> set uploaddate = getdate()<br /> where id [email protected]<br /><br /><br /><br />does anyone have any ideas, I have never seen this before. could it be the development server?<br /><br />Thanks,<br />Wolffy
BOL refers:
This error message indicates the status of each OLE DB property that was requested on the rowset opened against the table being updated. This information indicates that all properties required by SQL Server to perform this query, except the DBPROP_IRowsetChange property, were satisfied by the provider.

Use OpenQuery or OpenRowset function
Satya SKJ

or better yet create a stored procedure on the target server and call it from the source server Cheers