Article ID: 191333
Article Last Modified on 3/2/2005
APPLIES TO
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q191333
SYMPTOMS
If you apply a service pack on SQL Server 6.5 where QUOTED_IDENTIFIER is
turned on system-wide in the server configuration setting "user options",
the service pack installation scripts will fail and you will see the
following message:
Setup initialization could not be successfully completed.
ISQL.EXE could not be executed. Please check the relevant .OUT file
The Sqlole65.out file in the MSSQL\Install directory will show the
following message:
Msg 103, Level 15, State 2, Server SERVERNAME, Procedure sp_MStablekeys
The identifier that starts with 'Asser' is too long. Maximum length is 30.
Msg 170, Level 15, State 1, Server SERVERNAME, Procedure sp_MStablekeys
Line 122: Incorrect syntax near 'Assert failed: @indid is null in
sp_MStablekeys (pk/uq)'.
The server will be running, but you will not be able to establish a
connection to it in SQL Enterprise Manager. If you attempt to connect to
the server, you will get the following message:
A connection could not be established to SERVERNAME. This server has not
installed version 6.5 or later of the Microsoft SQL-DMO (SQLOLE) stored
procedures for its SQL Server version. The connection is denied.
CAUSE
Service pack installation scripts expect that the QUOTED_IDENTIFER option
is not turned on globally.
WORKAROUND
To work around this problem, try either of the following:
- Connect to the server using ISQL/W and use the sp_configure stored
procedure to record the current value for the "user options" parameter
and then change the setting to 0. Run the service pack setup and then
restore the configuration setting to its original value after the
service pack installation has completed. (See the SQL Server
documentation for information on how to change global configuration
settings.)
-or-
- Edit the Sqlole65.sql and Instrepl.sql files, inserting the line SET
QUOTED_IDENTIFIER OFF at the beginning of each script.
STATUS
Microsoft has confirmed this to be a problem in SQL Server version 6.5.
We are researching this problem and will post new information here in the
Microsoft Knowledge Base as it becomes available.
Additional query words: down upgrade failed backout enabled
Keywords: kbbug KB191333