Monday, March 19, 2012

Error 7356 - do we have to live with that?

To resolve a well know issue with quering a linked server:
(OLE DB provider 'SQLOLEDB' supplied inconsistent metadata. An extra column
was supplied during execution that was not found at compile time.
OLE DB error trace [Non-interface error: OLE DB provider returned an extra
column at execution time: ProviderName=.....)
I change the table name to a view returning all columns of the same table.
I have been doing this since SQL 7.0.
1. Is it an unfixable bug we have to live with?
2. Is there a better way of fixing the problem other than creating a view?
Thanks,
-StanHi Stan,
What is your SQL Server version? Is it SQL Server 7.0 SP4 or SQL Server
2000 SP3?
From your post, I am not sure about the steps to reproduce the problem.
Could you post it so that I can check further?
Bill Cheng
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--
| From: "Stan" <nospam@.yahoo.com>
| Subject: Error 7356 - do we have to live with that?
| Date: Fri, 12 Sep 2003 14:15:35 -0400
| Lines: 20
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <OjwKinVeDHA.616@.TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: 12.148.36.131
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:306189
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| To resolve a well know issue with quering a linked server:
|
| (OLE DB provider 'SQLOLEDB' supplied inconsistent metadata. An extra
column
| was supplied during execution that was not found at compile time.
| OLE DB error trace [Non-interface error: OLE DB provider returned an
extra
| column at execution time: ProviderName=.....)
|
| I change the table name to a view returning all columns of the same table.
|
| I have been doing this since SQL 7.0.
|
| 1. Is it an unfixable bug we have to live with?
|
| 2. Is there a better way of fixing the problem other than creating a view?
|
| Thanks,
|
| -Stan
|
|
||||Hi Stan,
I have found several articles regarding error "OLE DB provider 'SQLOLEDB'
supplied inconsistent metadata. An extra column was supplied during
execution that was not found at compile time." However, for SQL Server 7.0,
there is an article.
266337 PRB: Some SQL Server 7.0 Service Pack 2 Updates Must be Added
Manually
http://support.microsoft.com/?id=266337
However, I did not find any known issue regarding the same error on SQL
Server 2000. According to your description, it seems that the problem also
occurs on SQL Server 2000. Am I right? Since the problem randomly occurs,
it is very difficult to troubleshoot. However, please try the following
steps first:
1. The output from running "sp_helpserver" from the SQL Server 2000 machine
and the name of the linked server which encounters the problem.
2. Does dropping the linked server and adding it back work?
3. The output from the Component Checker from SQL Server 2000.
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-
BF53-14332EF092C9&displaylang=en
Bill Cheng
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--
| From: "Stan" <nospam@.yahoo.com>
| References: <OjwKinVeDHA.616@.TK2MSFTNGP11.phx.gbl>
<zOPgrT2eDHA.3900@.cpmsftngxa07.phx.gbl>
| Subject: Re: Error 7356 - do we have to live with that?
| Date: Mon, 15 Sep 2003 08:02:11 -0400
| Lines: 71
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <ejcAJF4eDHA.1712@.TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: 12.148.36.131
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08|||Bill,
> However, I did not find any known issue regarding the same error on SQL
> Server 2000. According to your description, it seems that the problem also
> occurs on SQL Server 2000. Am I right?
It ocurrs in the query on SQL Server 2000 against SQL Server 7.0 linked
server.
So, the culprilt is probably SQL Server 7.0
> 2. Does dropping the linked server and adding it back work?
No, it does not
Thanks!
-Stan|||Bill,
> However, I did not find any known issue regarding the same error on SQL
> Server 2000. According to your description, it seems that the problem also
> occurs on SQL Server 2000. Am I right?
It ocurrs in the query on SQL Server 2000 against SQL Server 7.0 linked
server.
So, the culprilt is probably SQL Server 7.0
> 2. Does dropping the linked server and adding it back work?
No, it does not
Thanks!
-Stan|||Hi Stan,
According to my research, we need to install Service pack 4 and also apply
the Instcat.sql manually.
Bill Cheng
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--
| From: "Stan" <nospam@.yahoo.com>
| References: <OjwKinVeDHA.616@.TK2MSFTNGP11.phx.gbl>
<zOPgrT2eDHA.3900@.cpmsftngxa07.phx.gbl>
<ejcAJF4eDHA.1712@.TK2MSFTNGP11.phx.gbl>
<noEhU9LfDHA.1388@.cpmsftngxa06.phx.gbl>
<#OO9DMRfDHA.2320@.TK2MSFTNGP12.phx.gbl>
<0fWgE0dfDHA.2588@.cpmsftngxa06.phx.gbl>
| Subject: Re: Error 7356 - do we have to live with that?
| Date: Thu, 18 Sep 2003 15:34:12 -0400
| Lines: 69
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <eNgonvhfDHA.1732@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: 12.148.36.131
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:307320
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Bill,
|
| No, we don't have the hotfix on 7.0. Woudn't be better to put the latest
| service pack for SQL 7.0 (I guess it SP4)?
|
| ""Bill Cheng [MSFT]"" <billchng@.online.microsoft.com> wrote in message
| news:0fWgE0dfDHA.2588@.cpmsftngxa06.phx.gbl...
| > Hi Stan,
| >
| > Have you tried the methods in 266337? I have not found any known issue
| > regarding this in SQL Server 2000.
| >
| > Has the error occurred after you apply 266337 on SQL Server 7.0? If so,
| > could you let me know what operations you have performed before the
error
| > occurs?
| >
| >
| > Bill Cheng
| > Microsoft Online Partner Support
| >
| > Get Secure! - www.microsoft.com/security
| > This posting is provided "as is" with no warranties and confers no
rights.
| > --
| > | From: "Stan" <nospam@.yahoo.com>
| > | References: <OjwKinVeDHA.616@.TK2MSFTNGP11.phx.gbl>
| > <zOPgrT2eDHA.3900@.cpmsftngxa07.phx.gbl>
| > <ejcAJF4eDHA.1712@.TK2MSFTNGP11.phx.gbl>
| > <noEhU9LfDHA.1388@.cpmsftngxa06.phx.gbl>
| > | Subject: Re: Error 7356 - do we have to live with that?
| > | Date: Wed, 17 Sep 2003 07:57:59 -0400
| > | Lines: 21
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| > | Message-ID: <#OO9DMRfDHA.2320@.TK2MSFTNGP12.phx.gbl>
| > | Newsgroups: microsoft.public.sqlserver.server
| > | NNTP-Posting-Host: 12.148.36.131
| > | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| > | Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:306904
| > | X-Tomcat-NG: microsoft.public.sqlserver.server
| > |
| > | Bill,
| > |
| > | > However, I did not find any known issue regarding the same error on
| SQL
| > | > Server 2000. According to your description, it seems that the
problem
| > also
| > | > occurs on SQL Server 2000. Am I right?
| > |
| > | It ocurrs in the query on SQL Server 2000 against SQL Server 7.0
linked
| > | server.
| > | So, the culprilt is probably SQL Server 7.0
| > |
| > | > 2. Does dropping the linked server and adding it back work?
| > | No, it does not
| > |
| > |
| > |
| > | Thanks!
| > |
| > | -Stan
| > |
| > |
| > |
| > |
| >
|
|
|

No comments:

Post a Comment