BUG: Client Terminated on Repeated Unsuccessful Obj ResolutionID: Q150955
|
During object resolution, the server terminates the client process if the
object resolution is not successful for five consecutive attempts.
This applies only to version 6.0 Service Pack 2. The problem
characteristics are completely different on SQL Server version 6.0 without
any Service Packs installed. Please see the following Knowledge Base
article for details:
Q134659 : FIX: Unexpected Behavior During Object Resolution
Ensure that all the views have proper base tables. Alternately, drop and recreate the views whenever the base tables are dropped.
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 6.0. We are researching this problem and will post new information
here in the Microsoft Knowledge Base as it becomes available.
This problem does not occur in Microsoft SQL Server Version 6.5.
On a select from a view where the base table has been changed, the client
process is terminated with error 603 on every fifth attempt.
The sequence of events is the following:
create table table1 (col1 int,col2 int)
create view view1 as select col2 from table1
drop table table1
create table table1 (col1 int)
select from view1
Msg 207, Level 16, State 2
Invalid column name 'col2'.
Msg 603, Level 19, State 1
The SQL Server is terminating this process.
1> select * from table1 /* any statement */
2> go
DB-Library: Possible network error: Write to SQL Server Failed.
Net-Library error 232: ConnectionWrite (WriteFile()).
DB-Library: DBPROCESS is dead or not enabled.
DB-Library: DBPROCESS is dead or not enabled.
DB-Library: DBPROCESS is dead or not enabled.
DB-Library: DBPROCESS is dead or not enabled.
DB-Library: DBPROCESS is dead or not enabled.
Additional query words: hang object resolution servpack
Keywords : kbprg SSrvProg kbbug6.00.sp2
Version : 6.0
Platform : WINDOWS
Issue type :
Last Reviewed: March 25, 1999