FIX: Error message when you use a label after a Transact-SQL query in SQL Server 2005: "Incorrect syntax near 'X'" (925335)
The information in this article applies to:
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition
Bug #: 50000268
(SQL Hotfix) Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. SUMMARYThis article describes the following about this hotfix
release:
- The issues that are fixed by the hotfix package
- The prerequisites for applying the hotfix
package
- Whether you must restart the computer after you apply the
hotfix package
- Whether the hotfix package is replaced by any other hotfix
package
- Whether you must make any registry changes after you apply the
hotfix package
- The files that are contained in the hotfix
package
SYMPTOMSWhen you use a label after a Transact-SQL query in Microsoft SQL Server 2005, the query may not run. Additionally, you may receive an error message that resembles the following on the first character of the label: Msg 102, Level 15, State 1, Line 3
Incorrect syntax near 'X'.
For example, you experience this problem when you run statements that resemble the following statements. SELECT * INTO TMP FROM SYS.SYSPROCESSES
IF 1=1
SELECT * FROM TMP WHERE 1=1
LABEL:
DROP TABLE TMP
GO
RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. Prerequisites- SQL Server 2005 Service Pack 1 (SP1)
For information about how to obtain SQL Server 2005 SP1, click the following article number to view the article in the Microsoft Knowledge Base:913089 How to obtain the latest service pack for SQL Server 2005
Restart information You do not have to restart the computer after you apply this hotfix. Registry information You do not have to change the registry.
Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.SQL Server 2005, 32-bit versions |
Logread.exe | 2005.90.2192.0 | 398,112 | 19-Sep-2006 | 15:10 | x86 | Microsoft.analysisservices.adomdclient.dll | 9.0.2192.0 | 543,520 | 19-Sep-2006 | 15:11 | x86 | Microsoft.analysisservices.deploymentengine.dll | 9.0.2192.0 | 138,016 | 19-Sep-2006 | 15:09 | x86 | Microsoft.analysisservices.dll | 9.0.2192.0 | 1,215,264 | 19-Sep-2006 | 15:10 | x86 | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2192.0 | 75,552 | 19-Sep-2006 | 15:08 | x86 | Microsoft.sqlserver.sqlenum.dll | 9.0.2192.0 | 908,064 | 19-Sep-2006 | 15:10 | x86 | Msgprox.dll | 2005.90.2192.0 | 197,920 | 19-Sep-2006 | 15:09 | x86 | Msmdlocal.dll | 9.0.2192.0 | 15,609,632 | 19-Sep-2006 | 15:11 | x86 | Msmdredir.dll | 9.0.2192.0 | 3,990,304 | 19-Sep-2006 | 15:11 | x86 | Replprov.dll | 2005.90.2192.0 | 547,616 | 19-Sep-2006 | 15:11 | x86 | Replrec.dll | 2005.90.2192.0 | 782,112 | 19-Sep-2006 | 15:10 | x86 | Sqlaccess.dll | 2005.90.2192.0 | 347,936 | 19-Sep-2006 | 15:10 | x86 | Sqlagent90.exe | 2005.90.2192.0 | 319,264 | 19-Sep-2006 | 15:10 | x86 | Sqlservr.exe | 2005.90.2192.0 | 28,962,136 | 19-Sep-2006 | 15:12 | x86 | Xpstar90.dll | 2005.90.2192.0 | 292,640 | 19-Sep-2006 | 14:02 | x86 | Xpstar90.rll | 2005.90.2192.0 | 152,864 | 19-Sep-2006 | 15:10 | x86 |
SQL Server 2005, 64-bit version |
Logread.exe | 2005.90.2192.0 | 522,528 | 19-Sep-2006 | 14:23 | x64 | Microsoft.analysisservices.adomdclient.dll | 9.0.2192.0 | 543,520 | 19-Sep-2006 | 14:23 | x86 | Microsoft.analysisservices.adomdclient.dll | 9.0.2192.0 | 543,520 | 19-Sep-2006 | 15:11 | x86 | Microsoft.analysisservices.deploymentengine.dll | 9.0.2192.0 | 138,016 | 19-Sep-2006 | 15:09 | x86 | Microsoft.analysisservices.dll | 9.0.2192.0 | 1,215,264 | 19-Sep-2006 | 15:10 | x86 | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2192.0 | 91,424 | 19-Sep-2006 | 14:21 | x64 | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2192.0 | 75,552 | 19-Sep-2006 | 15:08 | x86 | Microsoft.sqlserver.sqlenum.dll | 9.0.2192.0 | 875,296 | 19-Sep-2006 | 14:20 | x86 | Msgprox.dll | 2005.90.2192.0 | 259,360 | 19-Sep-2006 | 14:22 | x64 | Msmdlocal.dll | 9.0.2192.0 | 15,609,632 | 19-Sep-2006 | 15:11 | x86 | Msmdredir.dll | 9.0.2192.0 | 3,990,304 | 19-Sep-2006 | 15:11 | x86 | Replprov.dll | 2005.90.2192.0 | 745,248 | 19-Sep-2006 | 14:20 | x64 | Replrec.dll | 2005.90.2192.0 | 1,008,416 | 19-Sep-2006 | 14:21 | x64 | Sqlaccess.dll | 2005.90.2192.0 | 355,104 | 19-Sep-2006 | 14:23 | x86 | Sqlagent90.exe | 2005.90.2192.0 | 390,944 | 19-Sep-2006 | 14:23 | x64 | Sqlservr.exe | 2005.90.2192.0 | 39,350,048 | 19-Sep-2006 | 14:21 | x64 | Xpstar90.dll | 2005.90.2192.0 | 540,960 | 19-Sep-2006 | 14:23 | x64 | Xpstar90.rll | 2005.90.2192.0 | 153,376 | 19-Sep-2006 | 14:21 | x64 |
SQL Server 2005, Itanium architecture version |
Logread.exe | 2005.90.2192.0 | 1,095,456 | 19-Sep-2006 | 13:52 | IA-64 | Microsoft.analysisservices.adomdclient.dll | 9.0.2192.0 | 543,520 | 19-Sep-2006 | 13:51 | x86 | Microsoft.analysisservices.adomdclient.dll | 9.0.2192.0 | 543,520 | 19-Sep-2006 | 15:11 | x86 | Microsoft.analysisservices.deploymentengine.dll | 9.0.2192.0 | 138,016 | 19-Sep-2006 | 15:09 | x86 | Microsoft.analysisservices.dll | 9.0.2192.0 | 1,215,264 | 19-Sep-2006 | 15:10 | x86 | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2192.0 | 163,104 | 19-Sep-2006 | 13:50 | IA-64 | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2192.0 | 75,552 | 19-Sep-2006 | 15:08 | x86 | Microsoft.sqlserver.sqlenum.dll | 9.0.2192.0 | 875,296 | 19-Sep-2006 | 13:52 | x86 | Msgprox.dll | 2005.90.2192.0 | 542,496 | 19-Sep-2006 | 13:51 | IA-64 | Msmdlocal.dll | 9.0.2192.0 | 48,585,504 | 19-Sep-2006 | 13:53 | IA-64 | Msmdredir.dll | 9.0.2192.0 | 6,237,472 | 19-Sep-2006 | 13:53 | IA-64 | Replprov.dll | 2005.90.2192.0 | 1,617,184 | 19-Sep-2006 | 13:52 | IA-64 | Replrec.dll | 2005.90.2192.0 | 2,141,472 | 19-Sep-2006 | 13:52 | IA-64 | Sqlaccess.dll | 2005.90.2192.0 | 349,472 | 19-Sep-2006 | 13:51 | x86 | Sqlagent90.exe | 2005.90.2192.0 | 1,143,584 | 19-Sep-2006 | 13:52 | IA-64 | Sqlservr.exe | 2005.90.2192.0 | 72,233,760 | 19-Sep-2006 | 13:53 | IA-64 | Xpstar90.dll | 2005.90.2192.0 | 951,072 | 19-Sep-2006 | 13:51 | IA-64 | Xpstar90.rll | 2005.90.2192.0 | 152,352 | 19-Sep-2006 | 13:50 | IA-64 |
WORKAROUNDTo work around this problem, put the SELECT query that does not run in a BEGIN END block. For example, use code that resembles the following code example. SELECT * INTO TMP FROM SYS.SYSPROCESSES
GO
IF 1=1
BEGIN
SELECT * FROM TMP WHERE 1=1
END
LABEL:
GO
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 10/5/2006 |
---|
Keywords: | kbsql2005tsql kbQFE kbhotfixserver kbpubtypekc KB925335 kbAudDeveloper kbAudITPRO |
---|
|