Schema Change of a Progress DB causes Linked Server to Fail

We use SQL Server 2000 and have a Linked Server to a Progress 9.1E Database. Everything works fine until a schema change is made in the Progress database. We then get an error message similar to the following:

OLE DB provider 'MSDASQL' supplied inconsistent metadata.
An extra column was supplied during execution that was not found at compile time.[Non-interface error: OLE DB provider returned an extra column at execution time: ProviderName='MSDASQL', ColumnName=<column name>',
Rowset="pub"."tablename"]."

After researching this at the progress site I did find an article (P35634) that basically explains the following cause and fix.

Cause:
Microsoft Linked Server instance caches metadata for faster query resolution. This does not get properly refreshed when the Progress Database resides on a remote server. If Progress Database resides on the same machine as Linked Server instance, problem does not occur.


Fixes:
Drop and readd Linked Server instance in the Enterprise Manager. Contact Microsoft for more information.

We do Drop and readd the Linked Server however the same problem persists. What am I missing? Is there a different way to delete the cache and force a refresh of the linked server?

Thank you.
.

Relevant Pages

  • RE: Schema Change of a Progress DB causes Linked Server to Fail
    ... Check to see if the System DSN that was used to create the linked server is ... must make sure that the driver name in the provider string is correct. ... Schema Change of a Progress DB causes Linked Server to Fail ... If Progress Database resides on the ...
    (microsoft.public.sqlserver.connect)
  • Re: Verbindungsserver ...inkonsistente Metadaten... bei manchen Sy
    ... Microsoft Linked Server instance caches metadata for faster query ... This does not get properly refreshed when the Progress Database ...
    (microsoft.public.de.sqlserver)
  • Re: Is 5.0.7 ready for production?
    ... >> the database is started. ... Spent six hours on that server last night and this morning. ... does kick in and reboot the server if I wait. ... Progress to start up, but if a wait a while the machine locks instantly ...
    (comp.unix.sco.misc)
  • Re: Performance Issues
    ... I need your help in resolving performance issues. ... >> I am newly hired in a company that uses Progress Server ver. ... >> and run on one database located on one system. ...
    (comp.databases.progress)
  • Re: Trouble with JDBC
    ... These exceptions are due to no proper connection with the database ... Make sure to which version of Progress database you are connecting to ... because Progress 8.3B doesn't support Java(no jdbc drivers). ...
    (comp.databases.progress)
Loading