SQL2000问题汇总

SQLServer2000常见系统错误第一章启动与配置2、SQL Server服务器一一错误日志错误日志是SQL Server2000服务器中记录服务器级信息的文件。

当SQL Server启动、关闭和发生系统级错误时，SQL Server会自动记录有关信息。

查看错误日志：C:\Program Files'Microsoft SQL Server\MSSQL\LOGB la2EOJ-O9-01 16151^ 93server将SQL Eerirer 俏■&记录在立件,S C： -Prograii FilesVNicrcsof t SQL SErwiAllSSQLMo日■ESWKUOG* 中1 2(07-09-01 L6:IS:1^ 90服芻器匡程ID呈4022.2CO7-D&-01 (6:15:19 M Eflnzir健菩撕右利til.2COT-ra-Ol LG: 15:1^.93Eflrwir Ccippr-i gKt (O LCSB—2002 W L cyotoft Corpor-iti m.2CO1-M-H1 LG: I5:1<1 90Etirizir IN i ere toft SQL Ekiz.ir 2QJ0 —fi. 00. 2139 (Tint il 1SEJ ...2CET-M-01 LG: IE:1<1 92£卩号*™■-kigK s（已检側剣1僚n启动.2001-09-01 LE-: 15:20. 12已^ 曲沁［糧式坯淮rfl配置了泌皿心.SDDT-09-01 LG: 15:20. 12zarv^r便期＜1产5"迹分肚KG30］111块，K0CO］领騎有音块.0DDT-O9-O1 LE-: 15:20. 14尝减初皓化甘杓式李憨药调軌server3007-03-01 te： 15:20. IS server Puled. tc> >lit-a.Lii rrans4c-lL cnDi =p*iL=:erIxL-ttrfixce： XAET_^K^IMBDTAyjJIL.^ELZ2OO7-OB-01 te；lE:30.21印i期启动数据库"maZ严“2CO7-O9-01 te；lE：20. <2邛id3服务密名前昱'*EiriM 41)3200X4341:1“£007-08-01 L6:lE:20. *25«nrifcr正在便臣•嗚HETLZm-DLJ/1版試*-B. 0.233^** .2C07-09-01 te：IS:S0. 42i JI i^5启动数施库t（™iJ.55P2007-09-01 [6; 15:30. 43启动数据库“n^d屮・3007-09-01 te； 15:30. 45server£事疋在曲听]2TQ.QU 1133^2007-09-01 [6； 15:30, 45server SQL f er ver FE1E 听 E 侔.1 KL 岀.E吨：1<3亦£001-09-01 IX;巧；2)暫server3qL ^trvs-疋在區昕192.1&0.1.6： 1433-EOIT-Q9-Q1 L6;15；aO s32科id?启动数据库m讪評・S00T-09-Q1 16:15:20.513qL s岂已堆备軒进可容户端找EC0T-09-Q1 L6；l5；30.51server胡匚Serrer 疋在還昕TCf^ Stared nemery, Vanel ripes・ZCOT-O9-01 L6；l5；30.53spidlO启励数据库“恥）■讪:1）旷n2C0T-Q9-Q1 Le-；I5；3O.T1jjpidS躺数培库・2COT-09-Q1 L& I5 ZL12zpi羽启励数据库“疑吓dtT -ZCOT-D301 [6；I5；ZL.1S刃i胡SQL slabsl counter coll ecl ion task is creatiid.ZOIT-ra-Ol [&；I5；ZL. IS刊⑷ZOJT-D9-01 [6； 15： 36.9&护用■"Etu\dlT 価本'ZOCC W. ：036J来如"护祈？诂过寿ST^re^v*rsi^ □总结SQL Server启动的过程SQL Server数据库系统数据故障Master系统数据库对于SQL Server实例至关重要，是管理实例和所有数据库的数据库；Model系统数据库是系统创建所有数据库的模板。

SQL Server2000安装错误解决方法一、出现“配置服务器失败，请参考系统日志说明”和安装过程进度条退回如果是windows xp的系统，可以在C:\WINDOWS目录下查看sqlstp.log文件，里面有错误信息，敝人曾碰到过几种情况，参考了部分网络资料，现整理如下：失败情况一：sqlstp.log文件中的错误信息：正在与服务?driver={sql server};server=ZHL;UID=sa;PWD=;database=master[Microsoft][ODBC 驱动程序管理器] 驱动程序的SQLAllocHandle on SQL_Hdriver={sql server};server=ZHL;UID=sa;PWD=;database=master[Microsoft][ODBC 驱动程序管理器] 驱动程序的SQLAllocHandle on SQL_Hdriver={sql server};server=ZHL;UID=sa;PWD=;database=master[Microsoft][ODBC 驱动程序管理器] 驱动程序的SQLAllocHandle on SQL_HSQL Server 配置?################################################################## #############13:40:06 Process Exit Code: (-1)13:40:09 安装程序配置服务器失败。

参考服务器错误日志和C:\WINNT\sqlstp.log 了解更多信息。

13:40:09 Action CleanUpInstall:解决方法：当出现这个错误时，试一下重装系统文件：修复系统而不是全新安装。

修复系统文件之后，再装sql server，则不会出现此错误消息失败情况三：sqlstp.log文件中的错误信息：在与服务?driver={sql server};server=ZHL;UID=sa;PWD=;database=master[Microsoft][ODBC SQL Server Driver][Named Pipes]连接?[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead (ReadFile()).driver={sql server};server=ZHL;UID=sa;PWD=;database=master[Microsoft][ODBC SQL Server Driver][Named Pipes]连接?[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead (GetOverLappedResult()).driver={sql server};server=ZHL;UID=sa;PWD=;database=master[Microsoft][ODBC SQL Server Driver][Named Pipes]连接?[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead (GetOverLappedResult()).SQL Server 配置?############################################################ ###################17:17:41 Process Exit Code: (-1)17:17:45 安装程序配置服务器失败。

sql server 2000 错误信息解释（SQL Server 2000错误信息解释）Description of error severity (message text)110 last upgrade version date: 10/11/90.2110 warning: serious error%1! Occurred in%2!. Please note the error and time, and then contact the system administrator.10215 syntax errors near''%1!!'.10315%1 with''%2 Too long. The maximum length is%4!.10415 if the statement contains the UNION operator, then the items in the ORDER BY clause must appear in the selection list.10515 string''%1!! 'before there is an unclosed quotation mark.10616 there are too many table names in the query. The maximum allowable number is%1!.The 10715 column prefix''%1 '' does not match the table name or alias used in the query.The position of%1 10815 ORDER in the BY clause exceeds the number of items in the select list.The number of columns in the 10915 INSERT statement is greater than the number specified in the VALUES clause. The number of VALUES clauses must be matched to the number of columns specified in the INSERT statement.The number of columns in the 11015 INSERT statement is less than the number specified in the VALUES clause. The number of VALUES clauses must be matched to the number of columns specified in the INSERT statement.11115''%1! 'must be the first statement in the batch query.11215%1! No variables are allowed in the statement.11315 short notes at the end of'*/'mark.11415 invalid access mode for statements that assign values to variables.11615 when you do not introduce a subquery with EXISTS, you can only specify an expression in the selection list.11715%1! Name''%2! 'contains the number of prefixes greater than the maximum value. The maximum value is%4!.11815 only the members of the sysadmin role can specify the%1!%2 option of the statement.11915, you must pass the number of parameters%1, and pass the following parameters in the form of'@name = value'. Oncethe'@name = value'form is used, all subsequent parameters must be passed in the form of'@name = value'.The selection list of the 12015 INSERT statement contains less entries than that in the insert list. The number of SELECT statements must match the number of columns in the INSERTstatement.The selection list of the 12115 INSERT statement contains more entries than that in the insert list. The number of SELECT statements must match the number of columns in the INSERT statement.12215%1! Options are allowed only for%2! Syntax.The 12315 batch / process exceeds the maximum length of%1 characters.12415 CREATE PROCEDURE does not contain any statements.The 12515 Case expression can only be nested into the%1! Layer.12815 the name''%1! 'is not allowed in this context. Only constants, expressions, or variables are allowed here. Column names are not allowed.12915 fill factor%1! Is an invalid percentage; fill factor must be between 1 and 100.13016 cannot aggregate functions with expressions that contain aggregations or sub queries.13115 gives the size of "%2!''%3!!". (%1!) exceeds the maximum allowed value of any data type (%5!).13215 tag''%1!! 'has been declared. Tag names must be unique within batch queries or stored procedures.The 13315 GOTO statement points to the label''%1 '', but the tag has not yet been declared.The 13415 variable name''%1!! 'has been declared. Variable names must be unique within a batch query or stored procedure.13515 cannot use the BREAK statement outside the scope of the WHILE statement.13615 cannot use the CONTINUE statement outside the scope of the WHILE statement.13715 must declare variable''%1! ''.13815 do not allow relative clauses to be used in subquery.13915 cannot assign default values to local variables.140 15 只能在 create trigger 语句内部使用 if update.141 15 向变量赋值的 select 语句不能与数据检索操作结合使用.142 15 约束 ''% 1! " 的定义中有错误语法.143 15 在排序依据列表中没有找到 compute by 子句中的某一项.计算依据列表中的所有表达式也必须同时出现在排序依据列表中.144 15 在用于 group by 子句分组依据列表的表达式中, 不能使用聚合或子查询.145 15 如果指定了 select distinct, 那么 by order of 子句中的项就必须出现在选择列表中.146 15 未能为子查询分配辅助表.超出了查询中表数目的最大值 (% 1! ).147 15 聚合不应出现在 where 子句中, 除非该聚合位于 having 子句或选择列表所包含的子查询中, 并且要对其进行聚合的列是外部引用.148 15 waitfor 所用的时间字符串 ''% 1! " 中时间语法有误.149 15 waitfor 所用的时间值 ''% 1! " 是无效值.请检查日期 / 时间语法.150 15 外联接的两项都必须包含列.151 to 15 ''% 1! " 是无效 money 值.153 15 在% 3! 语句中有% 1! 选项的无效使用.154 of 15 在% 2! 中不允许使用% 1! .155 15 ''% 1! " 不是可以识别的% 3! 选项.156 15 在关键字 ''% 1! " 附近有语法错误.157 15 聚合不应出现在 update 语句的集合列表中.159 15 对于 drop index, 必须以 tablename.indexname 的形式同时给出表名和索引名.160 15 规则不包含变量.161 15 规则包含多个变量.163 15 计算依据列表与排序依据列表不匹配.164 15 group by 表达式必须引用出现在选择列表中的列名.165 16 不能授予或废除特权% 1! .166 15 ''% 1! " 不允许将数据库名称指定为对象名前缀.167 16 不能在临时对象上创建触发器.168 of 15% 1! " % 2! " 超出了计算机表示范围 (% 4! 字节).169 15 在排序依据列表中多次指定了某一列.排序依据列表中的列必须是唯一的.170 15 第% 1! 行: 在 ''% 1! " 附近有语法错误.171 15 不能在浏览模式中使用 select into.172 15 不能在浏览模式中使用 holdlock.173 15 列 ''% 1! " 的定义中必须包括数据类型.174 15% 1! 函数要求有% 2! 个参数.177 15 仅当 select 语句中有 into 子句时, 才能使用 identity函数.178 15 在此上下文中不能使用带有返回值的 return 语句.179 15 向存储过程传递常量时不能使用 output 选项.180 15 此% 1! 语句中参数太多.参数最大数目为% 2! .181 15 不能在 declare 语句中使用 output 选项.182 15 必须为 readtext 或 writetext 实用工具提供表名和列名.183 15 列 ''% 2! " 的小数位数 (% 1! ) 必须介于% 4! 到% 5. 之间.185, 15 数据流在大容量形式下的 writetext 语句中无效.186 15 writetext 语句中缺少数据流.188 15 在 create database 语句中, 如果不同时指定至少一个非日志设备, 就不能指定日志设备.189 15% 1! 函数要求有% 2! 到% 3! 个参数.191 15 sql 语句的某些部分嵌套过深.Please rewrite the query or decompose it into several smaller queries.19216 decimal digits must be less than or equal to accuracy.19315 the object name or column name at the beginning of''%1! 'is too long. The maximum length is%3! A character.The 19415 SELECT INTO statement cannot contain the SELECT statement assigned to the variable.19515''%1!! 'is not an%3 that can be identified!.The 19615 SELECT INTO must be the first query in the SQL statement containing the UNION operator.19715 cannot use EXECUTE as a source when inserting variables into a table.The 19815 browse mode is invalid for statements containing the UNION operator.The 19915 INSERT statement cannot contain the SELECT statement assigned to the variable.The 20116 procedure''%1! 'requires parameter''%3'! ', but this parameter is not provided.20216 WAITFOR type''%1! 'invalid. The supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR and DATETIME. WAITFOR DELAY also supports INT and SMALLINT data types.The 20316 name''%1!! 'is not a valid identifier.20420 a normalization error occurred in node%1.20516 all queries in the SQL statement containing the UNION operator must have the same number of expressions in the target list.20616 operand type conflict:%1! Incompatible with%2!20716 column''%1!! invalid.20816 object name''%1 '' invalid.20916 column names''%1! 'unclear.21016 syntax error when converting from binary/varbinary string to datetime.21216 the length of the expression result exceeds the maximum limit. The maximum value is%1, but the current length is%2!.21316 insert error: the column name or the number of supplied values does not match the table definition.The 21416 procedure requires the parameter''%1! ''''%2 '' type.21716 exceeds the maximum number of layers of stored procedures, functions, triggers, or views (maximum number of layers is%1!).22016 arithmetic overflow error occurred in data type%1 = value =%2!.22110 FIPS warning: implicit transformation from%1 to%2.The 22311 object ID%1! Is specified as the default value of column ID%3 in table ID%2!, but the object is missing or not the default value type.The 22411 object ID%1! Is specified as the rule of column ID%3 in table ID%2!, but the object is missing or not the default value type.22616%1 statement is not allowed in multi statement transactions.22914 rejected the%1 permissions for object''%2! \ "(database''%4! ', owner''%6!' ').23014 rejected the%1! Permissions of column''%2! \ "(database''%6! ', owner''%8!') for object''%4!!'.23111 there is no such default value. ID =%1! Database ID =%2!.23216 arithmetic overflow error of type%1! = value =%2!.The column''%1!! 'in table 23316'!''%3!! 'cannot be empty.23416, the result space is insufficient, can not convert money value to%1!.23516 cannot convert char value to money. The syntax of the char value is incorrect.23616 money overflow error caused by the conversion from char data type to money data type.23716, the result space is insufficient, can not convert money value to%1!.23816 the result space is insufficient, can't convert the%1 value (=%2!) to the money data type.24116 syntax errors from string to datetime.24216 conversion from char data type to datetime data type leads to datetime value cross boundary.24316 type%1! Is not a defined system type."24416%1! Value''%2!!" conversion overflowed the%4! Column.Please use a larger integer column.24516 syntax error when converting%1! Value''%2!! 'to a column with data type%4!."24816%1! Value''%2!!" conversion overflowed the int column. Exceeded the maximum integer value.25116 failed to allocate auxiliary tables for query optimization. Exceeded the maximum number of tables in the query (%1!).25616 data type%1! Invalid for function%2. The allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary.25716 implicit conversion from data type%1 to%2 is not allowed. Use the CONVERT function to run this query.25916 a special update to the system directory is not enabled. The system administrator must reconfigure the SQL Server to allow this operation.26016 the implicit conversion from data type%1 to data type%2 is not allowed (table''%3 ', column''%5' '). Use the CONVERT function to run this query.26116''%1!! 'is not a recognized function.26216 deny%1! Permissions in database''%2!'.26316 must specify the table to choose from.26416 column name''%1 \ "\" appears many times in the list of result columns.The transaction count after 26616 EXECUTE indicates that the COMMIT or ROLLBACK TRANSACTION statement is missing. Original count =%1! Current count =%2!.26716 cannot find object''%1! ''.26816 cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option.27016 cannot modify object''%1 ''.27116 cannot modify column''%1 '' because the column is a computed column.27216 cannot update the timestamp column.27316 cannot insert non null values in the timestamp column. Use INSERT statements with columns or timestamp columns with default values of NULL.27816 the text, ntext, and image data types cannot be used in the GROUP BY clause.27916 in this subquery or aggregation expression, text, ntext, and image data types are invalid.28016 for TEXTPTR functions, only text, ntext, and image columns are valid.28116 when%2 is converted to a string,%1 is an invalid style number.The 28210 process''%1 '' tries to return to the state value NULL, but this is not allowed. Will be returned to the state value 0.28316 within INSTEAD OF triggers, READTEXT cannot be used for inserted or deleted tables.28416 cannot bind rules to text, ntext, or image data types.28516 READTEXT, WRITETEXT, and UPDATETEXT statements cannot beused for views or functions.28616 cannot update logical tables INSERTED and DELETED.28716 triggers are not allowed to use%1.The 28816 PATINDEX function can only manipulate data types of char, nchar, varchar, nvarchar, text and ntext.Invalid property specified for 29116 CAST or CONVERT: for type''%1!! '29216, the result space is insufficient, can not convert smallmoney value to%1!.29316 cannot convert char value to smallmoney. The syntax of the char value is incorrect.29416 smallmoney overflow error caused by the conversion from char data type to smallmoney data type.29516 syntax errors from string to smalldatetime data type.29616 conversion from char data type to smalldatetime data type leads to smalldatetime value cross boundary.29816 smalldatetime overflow error caused by the conversion from datetime data type to smalldatetime data type.29916 call the function DATEADD with the wrong type%1.The 30116 query contains an outer join request that is not allowed.30316 table''%1!! 'is the internal member of the external join clause. This is not allowed if the table is also included in the normal join clause.30616 cannot compare or sort text, ntext, and image data types unless IS NULL or LIKE operators are used.The index ID%1 on the table''%2!! 'specified in the 30716 FROM clause does not exist.The index''%1!! 'on the table''%3!!' specified in the 30816 FROM clause does not exist.31116 cannot use text, ntext or image columns in the inserted table and the deleted table.31216 cannot refer to text, ntext, or image columns in the filter stored procedure.31316 the number of parameters provided for the process or function%1! Is not enough.40116 statement or expression%1! Not yet implemented.40316 for data types, operators are invalid. The operator is%1! The type is%2!.40916%1! Operation cannot use%2! Data type as parameter.41020 sorting according to the list does not exist in the first%1! Section COMPUTE clause%2!''BY''expression.41120 select the aggregate expression COMPUTE%2 without the existence of the%1 clause in the list.The 42016 text, ntext, and image data types cannot be used in the ORDER BY clause.42516 the data type%1 of the received variable is not equal to the data type%2 of column''%3'!.42616 the length of the receive variable%1! Less than the length of column''%3!! '%2!.42720 failed to load sysprocedures entries in database ID%2! Constraint ID%1.42820 failed to find the row corresponding to the constraint ID%1 in the database ID%2! In sysconstraints.42920 compile failed to find new constraint ID%1 in the database ID%2! Sysconstraints!.43020 cannot parse the table name of object ID%1 in database ID%2 when compiling foreign key.43119 failed to bind foreign key constraints. There are too many tables involved in the query.43320 failed to find the CHECK constraint of''%1 '', although the table is marked as having CHECK constraints.43620 failed to open the referenced table ID%1 in database ID%2!.43720 failed to parse referenced column names in table ID%1.43820 failed to parse reference column names in table ID%1.43920 failed to find the FOREIGN KEY constraint of table''%1 KEY 'in table ID%3!', although the table is marked as having FOREIGN constraints.44116 cannot use the''%1! 'function on the remote data source.44316 incorrect use of''%1!! 'in the function.44416 the SELECT statement contained in the function cannot return data to the client.44516 cannot use the COLLATE clause for an expression containing a COLLATE clause.44616 can't solve the collation conflict of%1! Operation.44716 expression type%1! Invalid for the COLLATE clause.44816 rule''%1 '' invalid.The 44916 collation conflicts because the sorting clause usesdifferent sorting rules''%1!! 'and'''%3! ''.45016 does not support code page conversion for text data types. From:%d to:%1!.45116 cannot resolve the collation conflict of column%1... (in%2! Statement).The 45216 COLLATE clause cannot be used to define user data types.45316 supports sorting rule''%1 '' for Unicode data types, and cannot set the collation at the database or server level.The last statement in the 45516 function must be a return statement.45616 cannot execute value from%1!The implicit transformation to%2, because the result ordering rule is not resolved because of the conflict of collation.45716 cannot perform the implicit conversion from%1 to%2 because the collation of the value cannot be resolved because of the conflict of collation.The 50216 SQL debug interface (SDI) requires that SQL Server cannot log in with system accounts when it is started as a service. Please reset the control panel to login with user account.50316 unable to connect%2! Send symbolic information to the debugger on%1. Debugging disabled.50416 unable to connect to the debugger on%1! (error = 0x%2!). Make sure that the client components have been installed and registered on%3! (such as SQLDBREG.EXE). Debugging of connection%5! Has been disabled.50516 the current user account is invoked with SETUSER. Database is not allowed.An invalid escape symbol''%1!! 'is specified in the 50616 LIKE predicate.Invalid parameter for 50716 SET ROWCOUNT. Must be nonempty and nonnegative integers.50816 unable to connect to the debugger on%1! (error = 0x%2!). Make sure that the client components have been installed and registered on%3! (such as SQLLE.DLL). Debugging of connection%5! Has been disabled.50911 not found username''%1! ''.51016 cannot create a worksheet row that is larger than the allowed maximum. Please resubmit queries with ROBUST PLAN prompt.51116 cannot create a row of size%1. This value is greater than the allowed maximum%2!.The 51216 subquery returns more than one value. When the query, followed by = =,! < < = > > =,,,, or as a sub query expression, this is not allowed.The insertion or update of the 51316 column conflicts with the rules enforced by the previous CREATE RULE statement. The statement has been terminated. The conflict occurred in the database''%1!! ', table''%3!', column''%5! ''.51416 cannot connect with debugger on%1! (error = 0x%2!). Debugging of connection%3! Has been disabled.51516 cannot insert NULL value into column''%1!! ', table''%3!'; this column does not allow null values. %ls failure.51616 attempts to initialize the OLE library failed. Please check the correct version of OLE DLL on this computer.Overflow occurs when adding value to 51716 column''%1 '.51816 cannot convert data type%1 to%2!.52016 SQL Server no longer supports SQL debug interface (SDI)%1! Version.52820 detects system errors when attempting to use the upsleep system function.52916 explicit conversions from data type%1 to%2 are not allowed.53216 timestamp (changed to%1!) indicates that other users have updated the line.53516 the difference between the two datetime columns results in a runtime overflow.53616 passed the invalid length parameter to the substring function.53816 couldn't find''%1!'. The language may have been removed. Please contact the system administrator.54216 encountered an invalid datetime value. It's worth more than 9999 years.54416 when IDENTITY_INSERT is set to OFF, explicit values cannot be inserted into the identity column in table''%1 ''.54516 when IDENTITY_INSERT is set to ON, you must specify the explicit value of the table''%1.54716%1! Statement and%2!%3! Constraint''%4!! 'conflict. The conflict occurred in the database''%6!! ',table''%8!''%10!%11!%13!.54816 the replication management scope is full and must be updated by replication agents. %1! Conflict occurs in database''%2!! ', table''%4!''%6!%7!%9!. You can callSp_adjustpublisheridentityrange to get a new identity range.55016 attempts to insert or update failed,The reason is that a view spanned by the target view or the target view specifies the WITH CHECK OPTION, and that one or more result lines of the operation do not conform to the constraints of the CHECK OPTION constraint.The 55116 checksum has been changed to%1!. This indicates that other users have updated the line.The 55215 CryptoAPI function''%1! 'failed. Wrong 0x%2!:%3!55516 user defined functions are not yet enabled.55616 because the stored procedure changes the architecture of the target table, INSERT EXEC fails.55716 only functions and extended stored procedures can execute from within the function.55816 within FUNCTION, remote function calls are not allowed.56116 access file''%1!! 'failed56216 access file''%1!! 'failed. You can only access files by sharing.The transaction of the 56314 INSERT EXEC statement has been rolled back. The INSERT EXEC operation will terminate.56416 attempts to create records with fixed length''%1 ''. The maximum allowable length is''%2!! ".56518 server encountered stack overflow during compilation.56621 write audit tracking error. SQL Server is about to close.56716 file%1! There is no or not identifiable trace file. Or error opening the file.56816 server encountered error''%1!!'.60112 cannot continue scanning in NOLOCK mode due to data movement.60221 failed to find the row corresponding to the index ID%3 in the database ID%1! Object ID%2! In sysindexes. Please run DBCC CHECKTABLE on sysindexes.60421 failed to find the row corresponding to the object ID%1 in database''%2 '' in sysobjects. Please run DBCC CHECKTABLE on sysobjects.60521 a logical page%1 trying to extract from database''%2 '! \ "belongs to object''%4!', not object''%6!! ''.60721 in the session descriptor of object''%1 \ "\", the space allocated for search parameters is insufficient. Space with only%3! Search parameters.61521 failed to find the database table of ID is%1! Name''%2!!'. 61720 trying to hash the descriptor of the object ID%1! In thedatabase ID%2!, the descriptor is not found in the hash table.61821, the VARNO parameter passed to the OpenTable system function is%1!. The maximum effective value is%2!.62216 does not assign files for file group''%1 ''. Only when you add a file, can you fill the table, index, and text, ntext, and image columns on this file group.62321 failed to retrieve rows from the page by RID, because the logical page%1 is not a data page. %2!. %4!.62421 failed to retrieve rows from the page by RID, because the requested RID is higher than the last RID value in the page. %1!. %2!, DBID%3!.62521 cannot retrieve the row by page RID from page%1, because slotid (%2!) is invalid.62616 cannot use ROLLBACK with a save point inside a distributed transaction.62716 cannot use SAVE TRANSACTION within a distributed transaction.62813 cannot send SAVE TRANSACTION when there is no active transaction.63520 process%1! Trying to delete the DES resource lock%2, but the lock is not controlled by the process.63720 index shrink program returns invalid state value 0.63921 failed to extract the logical page%1 of the database ID%2!. The page is not currently allocated."64421 failed to find the index entries of index RID''%1!" in the index page%3! (index ID%4, database''%5! '').64921 failed to find the clustered index entry (object ID%2, status 0x%3!) of page%1. The index page used to search for this entry is%4 in database''%5!'!。

SQL2000安装失败原因大全2008-12-03 13:455645人阅读评论(1)收藏举报一、安装程序配置服务器失败首先把安装目录和C:/Program Files下的Microsoft SQL Server文件夹删了,删除在current_user和local_machine/software/microsoft/ 下有关Microsoft sql server 全部信息，然后1 打开注册表在'开始'--'运行'键入'regedit'2 按下列顺序点击打开+ HKEY_LOCAL_MACHINE+ SOFTWART+ Microsoft+ Windows+ CurrentVersion+ Setup+ ExceptionComponents3 将ExceptionComponents 下面的文件夹全部删除!如{60BFF50D-FB2C-4498-A577-C9548C390BB9}{60BFF50D-FB2C-4498-A577-C9548C390BB9}{60BFF50D-FB2C-4498-A577-C9548C390BB9}{60BFF50D-FB2C-4498-A577-C9548C390BB9}.......4 重新启动:5 重新安装SQL Server 2000安装仍然失败，解决方法删除注册表与相关的SQL目录，然后重起，问题仍然不能解决，郁闷了好长一段时间，就算系统是刚装的，也会出现提示。

问题很有可能是计算机名的大小写引起来，计算机名小写，而SQL2000要区分大小写，导致找不到相应的主机服务，因此总是报错。

解决办法：我的电脑－－属性－－计算机名——更改——重新启动全部修改为大写后安装问题解决！二、sql 2000安装挂起问题解决安装SQL Server2000的时候，安装程序提示安装程序被挂起，让重新启动电脑，但即便是重新启动了再次安装，SQL Server2000的安装程序依旧提示这个错误。