RE: Undeclared tag ID % is used in a FOR XML Explicit Query
From: John Bell (JohnBell_at_discussions.microsoft.com)
Date: 11/17/04
- Next message: Da VIncy: "SQLDumpExceptionHandler"
- Previous message: Kevin Lorimer: "RE: Previous Working Days"
- In reply to: Glynn Zeederberg: "Undeclared tag ID % is used in a FOR XML Explicit Query"
- Next in thread: Glynn Zeederberg: "Re: Undeclared tag ID % is used in a FOR XML Explicit Query"
- Reply: Glynn Zeederberg: "Re: Undeclared tag ID % is used in a FOR XML Explicit Query"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 17 Nov 2004 04:48:01 -0800
Hi
There seems to be quite a few posts regarding the problem, this seems to be
the most succinct! http://tinyurl.com/4vlyd.
As you have a test environment you should be able to test the change
although I don't think it should cause you problems in whatever environment
(OS) you are running.
You may also want to look at the recently released (26/10/2004) service pack
3 for SQLXML 3.0
John
"Glynn Zeederberg" wrote:
> Hi all,
>
> My apologies if I am asking a question that has popped off the bottom of the
> post list.
> But some help would be greatly appreciated.
>
> We had a SQL 2000 Enterprise Edition SP3 (not 3a) Cluster, running on
> Windows 2000 SP3.
> The For XML Explicit Stored procs have never given a problem while running
> on that platform,ever.
>
> In fact we have multiple SQL environment running the same config and Query,
> and no Problems.
> Please note that these dev and QA environments are running (SQL2000 SP3a).
>
> A week, ago, we migrated onto a new Cluster, running Windows 2003, and SQL
> Ent SP3a.
> Since then, we intermittently get the following error: "Undeclared tag ID 9
> is used in a FOR XML EXPLICIT query"
>
> The way we fix the problem, is to flag the tables to recompile any query
> that accesses it again. The effectively recompiles for stored proc, and
> alleviates the problem.
> However, it occurs again.
>
> Now,
>
> Below are 2 references to the same problem I'm having that I found on the
> net.
>
> http://www.mcse.ms/message709443.html
>
> In this post, I couldn't find where the OS and Version was stipulated, sop I
> wasn't sure if the config was the same as mine.
> His symptoms and resolution however are identical to mine.
>
> http://www.mcse.ms/post2588494.html
>
> In this post, again the symptoms and resolution are the same. This time
> however, the OS is stipulated. He also infers that he ONLY gets this error
> on the SQL server running on Windows 2003.
>
> Also, in this post, the MSFT, says that it has nothing to do with the OS
> level, but is in fact a bug in SQL sever.
> The questions I have however are the following:
>
> If it is a SQL bug, how come it appears to only manifest on a Windows 2003
> machine?
>
> If it is a bug in SQL 2000, was it introduced in one of the service packs,
> or has it been there since the first version?
>
> If this bug in fact is documented in occurring on a Windows 2000 platform,
> is it the way a machine is built or the hardware configured that could be
> causing this problem?
>
>
> When we hit these problems, we rolled back to 2 databases that were causing
> this to the old machine and all was well. Those 2 databases are the only 2
> that use for XML explicit queries.
>
> Thanks in advance.
>
> Glynn
>
>
>
>
>
>
- Next message: Da VIncy: "SQLDumpExceptionHandler"
- Previous message: Kevin Lorimer: "RE: Previous Working Days"
- In reply to: Glynn Zeederberg: "Undeclared tag ID % is used in a FOR XML Explicit Query"
- Next in thread: Glynn Zeederberg: "Re: Undeclared tag ID % is used in a FOR XML Explicit Query"
- Reply: Glynn Zeederberg: "Re: Undeclared tag ID % is used in a FOR XML Explicit Query"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
