Hi All
Ignore the error below, It's got to do with isolation levels (nolock in this case): refer http://support.microsoft.com/?kbid=834290 for details.
Error: 644, Severity: 21, State: 6
Could not find the index entry for RID '1631393920202020202020202020202033392020202020202 020202020202019bcd3113230303037333120202020202020' in index page (1:420134), index ID 0, database 'DBName'..
What I'd like to know is how to get the table name that was affected out of this error message. Do I query sysindexes, sysobjects, use a function or something else?
Thanks in advance.
GrahamNo need to answer the question:
dbcc traceon(3604)
dbcc page ('DBName', 1, 420134, 0)
select name from sysobjects where id =1141579105--m_objId from page header
dbcc traceon(3604)
dbcc page ('DBName', 1, 305272,0)
select name from sysobjects where id =1141579105--m_objId from page header
dbcc traceon(3604)
dbcc page ('DBName', 1, 369029, 0)
select name from sysobjects where id =2021582240--m_objId from page header
/*
TABLE A: DBCC PAGE Parameters
Parameter Description
dbid ID of the database containing the page
dbname Name of the database containing the page
filenum File number containing the page
pagenum Page number within the file
printopt Optional print option; takes one of these values:
0 Default; print the buffer header and page header
1 Print the buffer header, page header, each row separately, and the row offset table
2 Print the buffer and page headers, page as a whole, and the offset table
*/
Showing posts with label below. Show all posts
Showing posts with label below. Show all posts
Monday, March 26, 2012
Error: 605, Severity: 21, State: 1
Below message is frequently appearing in error log file. Before posting this
issue I searched net but I am not sure how to overcome this issue as it is
Production System and I am not much aware of SQL Server 2000. I can count on
table 'ComputerVulnerability' but cannot export the data. Your guidance will
be highly appreciated in helping and solving the issue before it become
critical.
(1:182850)/(1:182850)0/612197231
... IAM indicates that page is allocated to this object
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:182850)
in database 'Prod' belongs to object '0', not to object
'ComputerVulnerability'..
Hello,
As a first step execute a DBCC CHECKDB and get mofre information on the
error. To solve this you may need to try executing the DBCC with
REPAIR_REBUILD and if the issue is not solved you may need to take a backup
of database execute DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS .
If nothing works out you may need to restore from a last good backup. In
parallel you could create a Microsoft case and get the help of microsoft
product support.
Thanks
Hari
"Bini" <Bini@.discussions.microsoft.com> wrote in message
news:9EAD09C3-23F9-4F85-AC26-A9E247D3502E@.microsoft.com...
> Below message is frequently appearing in error log file. Before posting
> this
> issue I searched net but I am not sure how to overcome this issue as it is
> Production System and I am not much aware of SQL Server 2000. I can count
> on
> table 'ComputerVulnerability' but cannot export the data. Your guidance
> will
> be highly appreciated in helping and solving the issue before it become
> critical.
> (1:182850)/(1:182850) 0/612197231
> ... IAM indicates that page is allocated to this object
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:182850)
> in database 'Prod' belongs to object '0', not to object
> 'ComputerVulnerability'..
issue I searched net but I am not sure how to overcome this issue as it is
Production System and I am not much aware of SQL Server 2000. I can count on
table 'ComputerVulnerability' but cannot export the data. Your guidance will
be highly appreciated in helping and solving the issue before it become
critical.
(1:182850)/(1:182850)0/612197231
... IAM indicates that page is allocated to this object
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:182850)
in database 'Prod' belongs to object '0', not to object
'ComputerVulnerability'..
Hello,
As a first step execute a DBCC CHECKDB and get mofre information on the
error. To solve this you may need to try executing the DBCC with
REPAIR_REBUILD and if the issue is not solved you may need to take a backup
of database execute DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS .
If nothing works out you may need to restore from a last good backup. In
parallel you could create a Microsoft case and get the help of microsoft
product support.
Thanks
Hari
"Bini" <Bini@.discussions.microsoft.com> wrote in message
news:9EAD09C3-23F9-4F85-AC26-A9E247D3502E@.microsoft.com...
> Below message is frequently appearing in error log file. Before posting
> this
> issue I searched net but I am not sure how to overcome this issue as it is
> Production System and I am not much aware of SQL Server 2000. I can count
> on
> table 'ComputerVulnerability' but cannot export the data. Your guidance
> will
> be highly appreciated in helping and solving the issue before it become
> critical.
> (1:182850)/(1:182850) 0/612197231
> ... IAM indicates that page is allocated to this object
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:182850)
> in database 'Prod' belongs to object '0', not to object
> 'ComputerVulnerability'..
Error: 605, Severity: 21, State: 1
Below message is frequently appearing in error log file. Before posting this
issue I searched net but I am not sure how to overcome this issue as it is
Production System and I am not much aware of SQL Server 2000. I can count on
table 'ComputerVulnerability' but cannot export the data. Your guidance will
be highly appreciated in helping and solving the issue before it become
critical.
(1:182850)/(1:182850) 0/612197231
... IAM indicates that page is allocated to this object
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:182850)
in database 'Prod' belongs to object '0', not to object
'ComputerVulnerability'..Hello,
As a first step execute a DBCC CHECKDB and get mofre information on the
error. To solve this you may need to try executing the DBCC with
REPAIR_REBUILD and if the issue is not solved you may need to take a backup
of database execute DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS .
If nothing works out you may need to restore from a last good backup. In
parallel you could create a Microsoft case and get the help of microsoft
product support.
Thanks
Hari
"Bini" <Bini@.discussions.microsoft.com> wrote in message
news:9EAD09C3-23F9-4F85-AC26-A9E247D3502E@.microsoft.com...
> Below message is frequently appearing in error log file. Before posting
> this
> issue I searched net but I am not sure how to overcome this issue as it is
> Production System and I am not much aware of SQL Server 2000. I can count
> on
> table 'ComputerVulnerability' but cannot export the data. Your guidance
> will
> be highly appreciated in helping and solving the issue before it become
> critical.
> (1:182850)/(1:182850) 0/612197231
> ... IAM indicates that page is allocated to this object
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:182850)
> in database 'Prod' belongs to object '0', not to object
> 'ComputerVulnerability'..
issue I searched net but I am not sure how to overcome this issue as it is
Production System and I am not much aware of SQL Server 2000. I can count on
table 'ComputerVulnerability' but cannot export the data. Your guidance will
be highly appreciated in helping and solving the issue before it become
critical.
(1:182850)/(1:182850) 0/612197231
... IAM indicates that page is allocated to this object
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:182850)
in database 'Prod' belongs to object '0', not to object
'ComputerVulnerability'..Hello,
As a first step execute a DBCC CHECKDB and get mofre information on the
error. To solve this you may need to try executing the DBCC with
REPAIR_REBUILD and if the issue is not solved you may need to take a backup
of database execute DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS .
If nothing works out you may need to restore from a last good backup. In
parallel you could create a Microsoft case and get the help of microsoft
product support.
Thanks
Hari
"Bini" <Bini@.discussions.microsoft.com> wrote in message
news:9EAD09C3-23F9-4F85-AC26-A9E247D3502E@.microsoft.com...
> Below message is frequently appearing in error log file. Before posting
> this
> issue I searched net but I am not sure how to overcome this issue as it is
> Production System and I am not much aware of SQL Server 2000. I can count
> on
> table 'ComputerVulnerability' but cannot export the data. Your guidance
> will
> be highly appreciated in helping and solving the issue before it become
> critical.
> (1:182850)/(1:182850) 0/612197231
> ... IAM indicates that page is allocated to this object
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:182850)
> in database 'Prod' belongs to object '0', not to object
> 'ComputerVulnerability'..
Error: 605, Severity: 21, State: 1
Below message is frequently appearing in error log file. Before posting thi
s
issue I searched net but I am not sure how to overcome this issue as it is
Production System and I am not much aware of SQL Server 2000. I can count on
table 'ComputerVulnerability' but cannot export the data. Your guidance will
be highly appreciated in helping and solving the issue before it become
critical.
(1:182850)/(1:182850) 0/612197231
... IAM indicates that page is allocated to this object
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:182850)
in database 'Prod' belongs to object '0', not to object
'ComputerVulnerability'..Hello,
As a first step execute a DBCC CHECKDB and get mofre information on the
error. To solve this you may need to try executing the DBCC with
REPAIR_REBUILD and if the issue is not solved you may need to take a backup
of database execute DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS .
If nothing works out you may need to restore from a last good backup. In
parallel you could create a Microsoft case and get the help of microsoft
product support.
Thanks
Hari
"Bini" <Bini@.discussions.microsoft.com> wrote in message
news:9EAD09C3-23F9-4F85-AC26-A9E247D3502E@.microsoft.com...
> Below message is frequently appearing in error log file. Before posting
> this
> issue I searched net but I am not sure how to overcome this issue as it is
> Production System and I am not much aware of SQL Server 2000. I can count
> on
> table 'ComputerVulnerability' but cannot export the data. Your guidance
> will
> be highly appreciated in helping and solving the issue before it become
> critical.
> (1:182850)/(1:182850) 0/612197231
> ... IAM indicates that page is allocated to this object
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:182850)
> in database 'Prod' belongs to object '0', not to object
> 'ComputerVulnerability'..
s
issue I searched net but I am not sure how to overcome this issue as it is
Production System and I am not much aware of SQL Server 2000. I can count on
table 'ComputerVulnerability' but cannot export the data. Your guidance will
be highly appreciated in helping and solving the issue before it become
critical.
(1:182850)/(1:182850) 0/612197231
... IAM indicates that page is allocated to this object
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:182850)
in database 'Prod' belongs to object '0', not to object
'ComputerVulnerability'..Hello,
As a first step execute a DBCC CHECKDB and get mofre information on the
error. To solve this you may need to try executing the DBCC with
REPAIR_REBUILD and if the issue is not solved you may need to take a backup
of database execute DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS .
If nothing works out you may need to restore from a last good backup. In
parallel you could create a Microsoft case and get the help of microsoft
product support.
Thanks
Hari
"Bini" <Bini@.discussions.microsoft.com> wrote in message
news:9EAD09C3-23F9-4F85-AC26-A9E247D3502E@.microsoft.com...
> Below message is frequently appearing in error log file. Before posting
> this
> issue I searched net but I am not sure how to overcome this issue as it is
> Production System and I am not much aware of SQL Server 2000. I can count
> on
> table 'ComputerVulnerability' but cannot export the data. Your guidance
> will
> be highly appreciated in helping and solving the issue before it become
> critical.
> (1:182850)/(1:182850) 0/612197231
> ... IAM indicates that page is allocated to this object
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:182850)
> in database 'Prod' belongs to object '0', not to object
> 'ComputerVulnerability'..
Wednesday, March 21, 2012
Error: 17883, Severity: 1, State: 0
Hi ,
We are getting 17833 error with below message .
Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
Scheduler 3.
We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
but I still see this in SQL log at least once a week .
Can you pl. suggest the solution .
Thanks,
PrabhuTry to open a case with MS, when we did, they asked us to forward the
minidump file that gets created when that error is recorded in the SQL server
logs. Once MS took a look at the dump file, they determined that the errors
indicate possible underlying hardware issues on writes and reads, that effect
performance and hangs the scheduler. They recommended a thorough test of the
EMC hardware portion. So open a case and send them the minidump files you
should have on your harddrive and they can try to detect what may ba causing
SQL Server to throw error 17883. My understanding is that error 17883 can be
caused by many reasons, could be SQL server related and could be other
resource related.
"Prabhu" wrote:
> Hi ,
> We are getting 17833 error with below message .
> Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
> Scheduler 3.
> We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
> but I still see this in SQL log at least once a week .
> Can you pl. suggest the solution .
> Thanks,
> Prabhu
We are getting 17833 error with below message .
Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
Scheduler 3.
We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
but I still see this in SQL log at least once a week .
Can you pl. suggest the solution .
Thanks,
PrabhuTry to open a case with MS, when we did, they asked us to forward the
minidump file that gets created when that error is recorded in the SQL server
logs. Once MS took a look at the dump file, they determined that the errors
indicate possible underlying hardware issues on writes and reads, that effect
performance and hangs the scheduler. They recommended a thorough test of the
EMC hardware portion. So open a case and send them the minidump files you
should have on your harddrive and they can try to detect what may ba causing
SQL Server to throw error 17883. My understanding is that error 17883 can be
caused by many reasons, could be SQL server related and could be other
resource related.
"Prabhu" wrote:
> Hi ,
> We are getting 17833 error with below message .
> Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
> Scheduler 3.
> We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
> but I still see this in SQL log at least once a week .
> Can you pl. suggest the solution .
> Thanks,
> Prabhu
Error: 17883, Severity: 1, State: 0
Hi ,
We are getting 17833 error with below message .
Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
Scheduler 3.
We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
but I still see this in SQL log at least once a week .
Can you pl. suggest the solution .
Thanks,
PrabhuTry to open a case with MS, when we did, they asked us to forward the
minidump file that gets created when that error is recorded in the SQL serve
r
logs. Once MS took a look at the dump file, they determined that the errors
indicate possible underlying hardware issues on writes and reads, that effec
t
performance and hangs the scheduler. They recommended a thorough test of the
EMC hardware portion. So open a case and send them the minidump files you
should have on your harddrive and they can try to detect what may ba causing
SQL Server to throw error 17883. My understanding is that error 17883 can be
caused by many reasons, could be SQL server related and could be other
resource related.
"Prabhu" wrote:
> Hi ,
> We are getting 17833 error with below message .
> Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
> Scheduler 3.
> We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
> but I still see this in SQL log at least once a week .
> Can you pl. suggest the solution .
> Thanks,
> Prabhu
We are getting 17833 error with below message .
Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
Scheduler 3.
We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
but I still see this in SQL log at least once a week .
Can you pl. suggest the solution .
Thanks,
PrabhuTry to open a case with MS, when we did, they asked us to forward the
minidump file that gets created when that error is recorded in the SQL serve
r
logs. Once MS took a look at the dump file, they determined that the errors
indicate possible underlying hardware issues on writes and reads, that effec
t
performance and hangs the scheduler. They recommended a thorough test of the
EMC hardware portion. So open a case and send them the minidump files you
should have on your harddrive and they can try to detect what may ba causing
SQL Server to throw error 17883. My understanding is that error 17883 can be
caused by many reasons, could be SQL server related and could be other
resource related.
"Prabhu" wrote:
> Hi ,
> We are getting 17833 error with below message .
> Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
> Scheduler 3.
> We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
> but I still see this in SQL log at least once a week .
> Can you pl. suggest the solution .
> Thanks,
> Prabhu
Error: 17883, Severity: 1, State: 0
Hi ,
We are getting 17833 error with below message .
Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
Scheduler 3.
We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
but I still see this in SQL log at least once a week .
Can you pl. suggest the solution .
Thanks,
Prabhu
Try to open a case with MS, when we did, they asked us to forward the
minidump file that gets created when that error is recorded in the SQL server
logs. Once MS took a look at the dump file, they determined that the errors
indicate possible underlying hardware issues on writes and reads, that effect
performance and hangs the scheduler. They recommended a thorough test of the
EMC hardware portion. So open a case and send them the minidump files you
should have on your harddrive and they can try to detect what may ba causing
SQL Server to throw error 17883. My understanding is that error 17883 can be
caused by many reasons, could be SQL server related and could be other
resource related.
"Prabhu" wrote:
> Hi ,
> We are getting 17833 error with below message .
> Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
> Scheduler 3.
> We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
> but I still see this in SQL log at least once a week .
> Can you pl. suggest the solution .
> Thanks,
> Prabhu
sql
We are getting 17833 error with below message .
Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
Scheduler 3.
We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
but I still see this in SQL log at least once a week .
Can you pl. suggest the solution .
Thanks,
Prabhu
Try to open a case with MS, when we did, they asked us to forward the
minidump file that gets created when that error is recorded in the SQL server
logs. Once MS took a look at the dump file, they determined that the errors
indicate possible underlying hardware issues on writes and reads, that effect
performance and hangs the scheduler. They recommended a thorough test of the
EMC hardware portion. So open a case and send them the minidump files you
should have on your harddrive and they can try to detect what may ba causing
SQL Server to throw error 17883. My understanding is that error 17883 can be
caused by many reasons, could be SQL server related and could be other
resource related.
"Prabhu" wrote:
> Hi ,
> We are getting 17833 error with below message .
> Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
> Scheduler 3.
> We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
> but I still see this in SQL log at least once a week .
> Can you pl. suggest the solution .
> Thanks,
> Prabhu
sql
Monday, March 19, 2012
Error: 17883
Dear All,
My sql server 2000 RAID 5, clustered, window 2003 enterprise server keep
encountered the below errors continueously (30+ times a day), a week already.
And the performance is seriously degraded and most of the time, can't be
connected becasuse of timeout. Do any had applied the security pack MS03-031,
and is that really can solved the problem? Any concern before I apply it to
the cluster environment? Please advise!
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context 0x0AB86BB8.Henry wrote:
> Dear All,
> My sql server 2000 RAID 5, clustered, window 2003 enterprise server
> keep encountered the below errors continueously (30+ times a day), a
> week already. And the performance is seriously degraded and most of
> the time, can't be connected becasuse of timeout. Do any had applied
> the security pack MS03-031, and is that really can solved the
> problem? Any concern before I apply it to the cluster environment?
> Please advise!
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context
> 0x0AB86BB8.
See if this helps:
http://support.microsoft.com/?kbid=816840
--
David Gugick
Imceda Software
www.imceda.com
My sql server 2000 RAID 5, clustered, window 2003 enterprise server keep
encountered the below errors continueously (30+ times a day), a week already.
And the performance is seriously degraded and most of the time, can't be
connected becasuse of timeout. Do any had applied the security pack MS03-031,
and is that really can solved the problem? Any concern before I apply it to
the cluster environment? Please advise!
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context 0x0AB86BB8.Henry wrote:
> Dear All,
> My sql server 2000 RAID 5, clustered, window 2003 enterprise server
> keep encountered the below errors continueously (30+ times a day), a
> week already. And the performance is seriously degraded and most of
> the time, can't be connected becasuse of timeout. Do any had applied
> the security pack MS03-031, and is that really can solved the
> problem? Any concern before I apply it to the cluster environment?
> Please advise!
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context
> 0x0AB86BB8.
See if this helps:
http://support.microsoft.com/?kbid=816840
--
David Gugick
Imceda Software
www.imceda.com
Error: 17883
Dear All,
My sql server 2000 RAID 5, clustered, window 2003 enterprise server keep
encountered the below errors continueously (30+ times a day), a week already
.
And the performance is seriously degraded and most of the time, can't be
connected becasuse of timeout. Do any had applied the security pack MS03-031
,
and is that really can solved the problem? Any concern before I apply it to
the cluster environment? Please advise!
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context 0x0AB86BB8
.Henry wrote:
> Dear All,
> My sql server 2000 RAID 5, clustered, window 2003 enterprise server
> keep encountered the below errors continueously (30+ times a day), a
> week already. And the performance is seriously degraded and most of
> the time, can't be connected becasuse of timeout. Do any had applied
> the security pack MS03-031, and is that really can solved the
> problem? Any concern before I apply it to the cluster environment?
> Please advise!
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context
> 0x0AB86BB8.
See if this helps:
http://support.microsoft.com/?kbid=816840
David Gugick
Imceda Software
www.imceda.com
My sql server 2000 RAID 5, clustered, window 2003 enterprise server keep
encountered the below errors continueously (30+ times a day), a week already
.
And the performance is seriously degraded and most of the time, can't be
connected becasuse of timeout. Do any had applied the security pack MS03-031
,
and is that really can solved the problem? Any concern before I apply it to
the cluster environment? Please advise!
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context 0x0AB86BB8
.Henry wrote:
> Dear All,
> My sql server 2000 RAID 5, clustered, window 2003 enterprise server
> keep encountered the below errors continueously (30+ times a day), a
> week already. And the performance is seriously degraded and most of
> the time, can't be connected becasuse of timeout. Do any had applied
> the security pack MS03-031, and is that really can solved the
> problem? Any concern before I apply it to the cluster environment?
> Please advise!
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context
> 0x0AB86BB8.
See if this helps:
http://support.microsoft.com/?kbid=816840
David Gugick
Imceda Software
www.imceda.com
Error: 17883
Dear All,
My sql server 2000 RAID 5, clustered, window 2003 enterprise server keep
encountered the below errors continueously (30+ times a day), a week already.
And the performance is seriously degraded and most of the time, can't be
connected becasuse of timeout. Do any had applied the security pack MS03-031,
and is that really can solved the problem? Any concern before I apply it to
the cluster environment? Please advise!
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context 0x0AB86BB8.
Henry wrote:
> Dear All,
> My sql server 2000 RAID 5, clustered, window 2003 enterprise server
> keep encountered the below errors continueously (30+ times a day), a
> week already. And the performance is seriously degraded and most of
> the time, can't be connected becasuse of timeout. Do any had applied
> the security pack MS03-031, and is that really can solved the
> problem? Any concern before I apply it to the cluster environment?
> Please advise!
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context
> 0x0AB86BB8.
See if this helps:
http://support.microsoft.com/?kbid=816840
David Gugick
Imceda Software
www.imceda.com
My sql server 2000 RAID 5, clustered, window 2003 enterprise server keep
encountered the below errors continueously (30+ times a day), a week already.
And the performance is seriously degraded and most of the time, can't be
connected becasuse of timeout. Do any had applied the security pack MS03-031,
and is that really can solved the problem? Any concern before I apply it to
the cluster environment? Please advise!
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context 0x0AB86BB8.
Henry wrote:
> Dear All,
> My sql server 2000 RAID 5, clustered, window 2003 enterprise server
> keep encountered the below errors continueously (30+ times a day), a
> week already. And the performance is seriously degraded and most of
> the time, can't be connected becasuse of timeout. Do any had applied
> the security pack MS03-031, and is that really can solved the
> problem? Any concern before I apply it to the cluster environment?
> Please advise!
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context
> 0x0AB86BB8.
See if this helps:
http://support.microsoft.com/?kbid=816840
David Gugick
Imceda Software
www.imceda.com
Error: 17805, Severity: 20, State: 3
Hello,
I am getting the error(s) below.
Error: 17805, Severity: 20, State: 3
=======================
I/O error 1117(The request could not be performed because of an I/O device error.) detected during read at offset 0x000010aedde000 in file 'E:\Data\ABCD.MDF'.
Error: 823, Severity: 24, State: 2
=====================
I/O error 1117(The request could not be performed because of an I/O device error.) detected during read at offset 0x000010aede0000 in file ''E:\Data\ABCD.MDF'.
Any clue what could be the error related to. Is the a disk/SAN issue.
Thanks.
Hi Arzan,
It might be a hardware issue. You can check the following Microsoft
article on the very same issue:
http://support.microsoft.com/default...b;en-us;828339
Thanks,
Chandan Dutta
"Arzan" wrote:
> Hello,
> I am getting the error(s) below.
> Error: 17805, Severity: 20, State: 3
> =======================
> I/O error 1117(The request could not be performed because of an I/O device error.) detected during read at offset 0x000010aedde000 in file 'E:\Data\ABCD.MDF'.
> Error: 823, Severity: 24, State: 2
> =====================
> I/O error 1117(The request could not be performed because of an I/O device error.) detected during read at offset 0x000010aede0000 in file ''E:\Data\ABCD.MDF'.
> Any clue what could be the error related to. Is the a disk/SAN issue.
> Thanks.
I am getting the error(s) below.
Error: 17805, Severity: 20, State: 3
=======================
I/O error 1117(The request could not be performed because of an I/O device error.) detected during read at offset 0x000010aedde000 in file 'E:\Data\ABCD.MDF'.
Error: 823, Severity: 24, State: 2
=====================
I/O error 1117(The request could not be performed because of an I/O device error.) detected during read at offset 0x000010aede0000 in file ''E:\Data\ABCD.MDF'.
Any clue what could be the error related to. Is the a disk/SAN issue.
Thanks.
Hi Arzan,
It might be a hardware issue. You can check the following Microsoft
article on the very same issue:
http://support.microsoft.com/default...b;en-us;828339
Thanks,
Chandan Dutta
"Arzan" wrote:
> Hello,
> I am getting the error(s) below.
> Error: 17805, Severity: 20, State: 3
> =======================
> I/O error 1117(The request could not be performed because of an I/O device error.) detected during read at offset 0x000010aedde000 in file 'E:\Data\ABCD.MDF'.
> Error: 823, Severity: 24, State: 2
> =====================
> I/O error 1117(The request could not be performed because of an I/O device error.) detected during read at offset 0x000010aede0000 in file ''E:\Data\ABCD.MDF'.
> Any clue what could be the error related to. Is the a disk/SAN issue.
> Thanks.
Error: 17805, Severity: 20, State: 3
Hello,
I am getting the error(s) below.
Error: 17805, Severity: 20, State: 3
=======================
I/O error 1117(The request could not be performed because of an I/O device e
rror.) detected during read at offset 0x000010aedde000 in file 'E:\Data\ABCD
.MDF'.
Error: 823, Severity: 24, State: 2
=====================
I/O error 1117(The request could not be performed because of an I/O device e
rror.) detected during read at offset 0x000010aede0000 in file ''E:\Data\ABC
D.MDF'.
Any clue what could be the error related to. Is the a disk/SAN issue.
Thanks.Hi Arzan,
It might be a hardware issue. You can check the following Microsoft
article on the very same issue:
http://support.microsoft.com/defaul...kb;en-us;828339
Thanks,
Chandan Dutta
"Arzan" wrote:
> Hello,
> I am getting the error(s) below.
> Error: 17805, Severity: 20, State: 3
> =======================
> I/O error 1117(The request could not be performed because of an I/O device
error.) detected during read at offset 0x000010aedde000 in file 'E:\Data\AB
CD.MDF'.
> Error: 823, Severity: 24, State: 2
> =====================
> I/O error 1117(The request could not be performed because of an I/O device
error.) detected during read at offset 0x000010aede0000 in file ''E:\Data\A
BCD.MDF'.
> Any clue what could be the error related to. Is the a disk/SAN issue.
> Thanks.
I am getting the error(s) below.
Error: 17805, Severity: 20, State: 3
=======================
I/O error 1117(The request could not be performed because of an I/O device e
rror.) detected during read at offset 0x000010aedde000 in file 'E:\Data\ABCD
.MDF'.
Error: 823, Severity: 24, State: 2
=====================
I/O error 1117(The request could not be performed because of an I/O device e
rror.) detected during read at offset 0x000010aede0000 in file ''E:\Data\ABC
D.MDF'.
Any clue what could be the error related to. Is the a disk/SAN issue.
Thanks.Hi Arzan,
It might be a hardware issue. You can check the following Microsoft
article on the very same issue:
http://support.microsoft.com/defaul...kb;en-us;828339
Thanks,
Chandan Dutta
"Arzan" wrote:
> Hello,
> I am getting the error(s) below.
> Error: 17805, Severity: 20, State: 3
> =======================
> I/O error 1117(The request could not be performed because of an I/O device
error.) detected during read at offset 0x000010aedde000 in file 'E:\Data\AB
CD.MDF'.
> Error: 823, Severity: 24, State: 2
> =====================
> I/O error 1117(The request could not be performed because of an I/O device
error.) detected during read at offset 0x000010aede0000 in file ''E:\Data\A
BCD.MDF'.
> Any clue what could be the error related to. Is the a disk/SAN issue.
> Thanks.
Sunday, March 11, 2012
Error: 0, Severity: 19, State: 0
While my production sql server was running, suddenly i got the error below and the connection was lost. Can anyone pls guide what is this error for, why this occured and how to resolve it. I got this error 2 times in two months.
Error: 0, Severity: 19, State: 0
SqlDumpExceptionHandler: Process 232 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
I run SQL Server 2000 with SP4 with OS Win 2003. I found this error in event viewer. I am assuming that some procedure was running at this time.
Pls help me in troubleshooting this issue.
Help appreciated.
You've hit a bug of some kind - an access violation is an unexpected condition. You need to contact Product Support (http://support.microsoft.com/sql) to help figure out what happened and whether there's a fix available.
Thanks
Friday, March 9, 2012
error.log invalid protocol specified
I get the entries shown below in my error.log of
an msde on WinXP home.
Where does this Invalid Protocol specified for a ?
come from ?
Should i run svrnetcn.exe to configure protocols ?
Is it true, that I have to install MSDE with
DISABLENETWORKPROTOCOL=0 set to access it from
a remote site ?
2004-04-29 11:54:05.34 server Using 'SSNETLIB.DLL'
version '8.0.760'.
2004-04-29 11:54:05.34 server Invalid Protocol
specified for a
??4? instance: ?.
2004-04-29 11:54:05.34 server Invalid Protocol
specified for a
??t? instance: ?c??t?.
2004-04-29 11:54:05.34 server Invalid Protocol
specified for a
??t?y, Winsock Proxy instance: ?.
2004-04-29 11:54:05.34 spid5 Starting up
database 'model'.
2004-04-29 11:54:05.63 server SQL server listening on
192.168.1.34:
1433.
2004-04-29 11:54:05.63 server SQL server listening on
127.0.0.1:
1433.
2004-04-29 11:54:05.63 server SuperSocket Info: Bind
failed on TCP
port 1433.
2004-04-29 11:54:05.64 server SQL server listening on
192.168.1.34:
1433.
2004-04-29 11:54:05.64 server SQL server listening on
127.0.0.1:
1433.
..
hi Dominique,
"Dominique" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:a26601c434eb$a425b4f0$a601280a@.phx.gbl...
> I get the entries shown below in my error.log of
> an msde on WinXP home.
> Where does this Invalid Protocol specified for a ?
> come from ?
> Should i run svrnetcn.exe to configure protocols ?
> Is it true, that I have to install MSDE with
> DISABLENETWORKPROTOCOL=0 set to access it from
> a remote site ?
MSDE sp3a and MSDE release A install by default disabling all network
protocols in order to protect the installed instance from malicious external
attacks..
if you want your instance to be accessible from remote client you have to
enable network protocols at install time, via the DISABLENETWORKPROTOCOL=0
command line parameter or anabling them after install via Server Network
Utility (svrnetcn.exe)...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
an msde on WinXP home.
Where does this Invalid Protocol specified for a ?
come from ?
Should i run svrnetcn.exe to configure protocols ?
Is it true, that I have to install MSDE with
DISABLENETWORKPROTOCOL=0 set to access it from
a remote site ?
2004-04-29 11:54:05.34 server Using 'SSNETLIB.DLL'
version '8.0.760'.
2004-04-29 11:54:05.34 server Invalid Protocol
specified for a
??4? instance: ?.
2004-04-29 11:54:05.34 server Invalid Protocol
specified for a
??t? instance: ?c??t?.
2004-04-29 11:54:05.34 server Invalid Protocol
specified for a
??t?y, Winsock Proxy instance: ?.
2004-04-29 11:54:05.34 spid5 Starting up
database 'model'.
2004-04-29 11:54:05.63 server SQL server listening on
192.168.1.34:
1433.
2004-04-29 11:54:05.63 server SQL server listening on
127.0.0.1:
1433.
2004-04-29 11:54:05.63 server SuperSocket Info: Bind
failed on TCP
port 1433.
2004-04-29 11:54:05.64 server SQL server listening on
192.168.1.34:
1433.
2004-04-29 11:54:05.64 server SQL server listening on
127.0.0.1:
1433.
..
hi Dominique,
"Dominique" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:a26601c434eb$a425b4f0$a601280a@.phx.gbl...
> I get the entries shown below in my error.log of
> an msde on WinXP home.
> Where does this Invalid Protocol specified for a ?
> come from ?
> Should i run svrnetcn.exe to configure protocols ?
> Is it true, that I have to install MSDE with
> DISABLENETWORKPROTOCOL=0 set to access it from
> a remote site ?
MSDE sp3a and MSDE release A install by default disabling all network
protocols in order to protect the installed instance from malicious external
attacks..
if you want your instance to be accessible from remote client you have to
enable network protocols at install time, via the DISABLENETWORKPROTOCOL=0
command line parameter or anabling them after install via Server Network
Utility (svrnetcn.exe)...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Wednesday, March 7, 2012
error with SQL statement
hi, i try the below sql code, however when i try to execute the command, it always give me the error 'Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause.'
If i remove the "(SELECT [description] = CASE WHEN ([description]) <> '' THEN [description] ELSE [tbl_batch_completed].[status] END)" under the group by clause, it will work
do I need to change something in the sql statement?
Thanks in advance
You are going to have to remove the select staement from the group by. Also in that SQl Staement there is no from clause... It does not know where to get the batch completed information.SELECT TAG_FACE_CON.REQUEST_ID,
(SELECT [description] = CASE WHEN ([description]) <> '' THEN [description] ELSE [tbl_batch_completed].[status] END)AS statusFROM (TAG_FACE_CON RIGHT JOIN tbl_batch_completed ON TAG_FACE_CON.GROUP_ID = tbl_batch_completed.ID)
GROUP BY TAG_FACE_CON.REQUEST_ID,(SELECT [description] = CASE WHEN ([description]) <> '' THEN [description] ELSE [tbl_batch_completed].[status] END)
I would look into create a temp table to create the first section as raw data, then when you need to do the group by run it as a query from the temp table.|||I think restructuring your query like this will solve your problem:
SELECT
TAG_FACE_CON.REQUEST_ID,
CASE
WHEN [description] <> '' THEN [description]
ELSE [tbl_batch_completed].[status]
END AS status
FROM
TAG_FACE_CON
RIGHT JOIN
tbl_batch_completed ON TAG_FACE_CON.GROUP_ID = tbl_batch_completed.ID
GROUP BY
TAG_FACE_CON.REQUEST_ID,
CASE
WHEN [description] <> '' THEN [description]
ELSE [tbl_batch_completed].[status]
END
Terri
Error with Openrowset
I have a text file, that I need to import to SQL. I am trying to do this using OPENROWSET. This is the qry i use below.
select * from OpenRowset('MSDASQL',
'Driver={Microsoft Text Driver
(*.txt; *.csv)};
DefaultDir=c:\edge;',
'select * from
vwConstrLendingLoanDefiDetailReady.txt')
I have created a System DSN, For the microsoft text driver. Anyhow it throws this error:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize returned 0x80004005: ].
Any idea why?
If this is in SQL 2005Go to Surface Area Configuration->Surface Area Configuration for Features
Database Engine->Ad Hoc Remote Queries
Make sure 'Enable OPENROWSET and OPENDATASOURCE Support' is checked.|||It is SQL SERVER 2000. I have used Openrowset while connecting to other dbs like SQL Server etc...|||i FOUND THE Fix. I had an extra space, in mjy qry. Fixed that and it was able to execute the qry, and return the data.
Sunday, February 26, 2012
Error with linked server after failover
Hi all,
The following query that uses a linked server is giving me the error message below after I initiate a failover (ALTER DATABASE Northwind SET PARTNER FAILOVER).I have SQL Server 2005 SP2.I think that without the service pack there is another error too.
The query is run from a database other than northwind of course.
select * from DualLink.northwind.dbo.Test1
Please note that:
without a failover itworks perfectly
it always work if I try to run it a second time - only the first time it fails.
it fails the first time for each of the open connections. A new connection that was open after the failover will work fine.
A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
The linked server is defined as
EXEC master.
dbo.sp_addlinkedserver
@.server = N'DualLink',
@.srvproduct=N'',
@.provider=N'SQLOLEDB',
@.catalog=N'northwind',
@.provstr=N'Server=(local);FailoverPartner=MyIPAddr;'
EXEC master.dbo.sp_addlinkedsrvlogin
@.rmtsrvname = 'DualLink',
@.useself = false,
@.locallogin = 'sa',
@.rmtuser = 'sa',
@.rmtpassword = 'MyPwd'
Thanks,
Avi
I am having the same problem except I don't have a linked server.
I am running SQL Server 2005 sp1 and Windows 2003 using clustering.
In addition to your symptoms I have noticed the following:
1. The error occurs when I make a query through Server Manager and when using a java app that queries a database using an ASP page. However, if I bring up our website as the first request after failover it works fine.
2. If I failover from Server1 to Server2 and don't make any requests while it is on Server2 and then failover back to Server1 I do not get the error. If I make any requests while it is on Server2 then the first request I make on Server1 after failing over will cause the error.
If you have solved the problem I would like to know how. If I find a solution I will post it here.
Blake
error with connection with SQL SERVER
Hi
I am developing web application.
I have connected my app. with sql server using web.config as code given below using Named pipe connection
<appSettings>
<add key="constring" value="Server=ebserver;UID=sa;database=Airport-Clearance;Integrated Security=SSPI;network library=dbnmpntw;" />
</appSettings
After than i have added a new CLASS in my app.
in that, I have written as given below code.
public SqlConnection GetConnection()
{
System.Configuration.AppSettingsReader objApp = new System.Configuration.AppSettingsReader ();
SqlConnection sqlconn = new SqlConnection ();
sqlconn.ConnectionString = Convert.ToString(objApp.GetValue("constring", typeof(string)));
return sqlconn ;
}
Finally, In load event of form, I have written as below code.
Class1 objcs = new Class1() ;
SqlConnection sqlconn = objcs.GetConnection ();
SqlDataAdapter filling = new SqlDataAdapter("select * from Airport",sqlconn);
DataSet ds = new DataSet();
sqlconn.Open();
//filling.Fill(ds,"Airport");
//DataGrid dg = new DataGrid();
dg.DataSource = ds.Tables["Airport"];
dg.DataBind();
//Do what ever
sqlconn.Close ();
When i run this application
It gives error like
provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
If i use try catch then it doesnt display any error.but Even it doesnt display datagrid on form.
Please give me solution.
Even how to run app. line by line as we run in VB using F8.
Reply please,
Regards,
ASIFTry this instead (assuming you're not using beta version):
public SqlConnection GetConnection()
{
SqlConnection sqlconn = new SqlConnection ();
sqlconn.ConnectionString = System.Configuration.ConfigurationManager.ConnectionStrings["constring"].ConnectionString;
return sqlconn ;
}
Sunday, February 19, 2012
Error while running the "Execute SQL task"
hi frnds,
Till last week my SSIS package was running fine.
now it is throwing the below mentioned error:
SSIS package "DNB_GMS_PO_Transition.dtsx" starting.
Error: 0xC0202009 at DNB_GMS_PO_Transition, Connection manager "CTSINNVLSDNB1\SQLEXPRESS.cedprod.cedprod": An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80040E4DDescription: "Login failed for user 'cedprod'.".
Error: 0xC00291EC at Takingbackup of the affected tables, Execute SQL Task: Failed to acquire connection "CTSINNVLSDNB1\SQLEXPRESS.cedprod.cedprod". Connection may not be configured correctly or you may not have the right permissions on this connection.
Task failed: Takingbackup of the affected tables
Warning: 0x80019002 at DNB_GMS_PO_Transition: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "DNB_GMS_PO_Transition.dtsx" finished: Failure.
i was unable to figure it out.but i had connected correctly to Database.
if i run those queries in the Query analyser with the same DB connection its running fine.
its urgent.
please tell me the soultion.
And in that Query Analyzer session you were logging in a "CEDPROD"?|||ya i was able to log in the CEDPROD and l logged in the Query Analyser too|||Did you choose to "save the password" in the connection manager when setting it up? Have you promoted this package to SQL Server and are trying to run it there?|||ya i selected the " save my password " and its running fine in SQL Server 2000Error while running Query
Hi,
SQL Server 7
When i ran a query in query analyzer i am getting the below error.
once i closed and opened the query analyzer and ran the same query it worked fine.
pls the error which i got in first time.
Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
Pls help me in this
TIA
AdilSo, after you reopened QA the same query ran with no errors? Are you suspecting you're going to get it again?|||hi
thanks for the reply
yes, i'm worried if it comes again whats the solution for it.
pls help me out.
TIA|||The problem seems to be that you've got some bits stuck in your network cable. Remove the cable, shake it vigorously in all four cardinal compass points (north, east, south, and west), and plug it back in. Things should work just fine then!
On a slightly more serious note, removing the network cable will actually fix the problem in most cases. There was some kind of communication error, possibly lost data/framing error/digi-voodoo/etc. When you remove the network cable for any significant amount of time (over a few seconds), the NIC resets. When the cable is reattached, the NIC reconnects, and whatever problem there was is magically gone.
If nothing else, the attention that you get when everybody thinks that you've clearly lost what little mind you might have once had, then your bizzare behavior appears to fix the problem will get you lots of digi-voodoo status.
-PatP|||that's an interesting solution, but considering the real reason for the above error actually very precise. now, here's your reference material (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q176/2/56.asp&NoWebContent=1) in this regard.|||Pat Phelan, you need to be more carefull about your advice. I followed your intructions and got bits all over my carpet. They are extremely hard to get out, and since the dang things carry a static charge they stick to my cat and he has tracked them all over the house. On a positive note, they seemed to pass through his digestive tract pretty quickly.
SQL Server 7
When i ran a query in query analyzer i am getting the below error.
once i closed and opened the query analyzer and ran the same query it worked fine.
pls the error which i got in first time.
Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
Pls help me in this
TIA
AdilSo, after you reopened QA the same query ran with no errors? Are you suspecting you're going to get it again?|||hi
thanks for the reply
yes, i'm worried if it comes again whats the solution for it.
pls help me out.
TIA|||The problem seems to be that you've got some bits stuck in your network cable. Remove the cable, shake it vigorously in all four cardinal compass points (north, east, south, and west), and plug it back in. Things should work just fine then!
On a slightly more serious note, removing the network cable will actually fix the problem in most cases. There was some kind of communication error, possibly lost data/framing error/digi-voodoo/etc. When you remove the network cable for any significant amount of time (over a few seconds), the NIC resets. When the cable is reattached, the NIC reconnects, and whatever problem there was is magically gone.
If nothing else, the attention that you get when everybody thinks that you've clearly lost what little mind you might have once had, then your bizzare behavior appears to fix the problem will get you lots of digi-voodoo status.
-PatP|||that's an interesting solution, but considering the real reason for the above error actually very precise. now, here's your reference material (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q176/2/56.asp&NoWebContent=1) in this regard.|||Pat Phelan, you need to be more carefull about your advice. I followed your intructions and got bits all over my carpet. They are extremely hard to get out, and since the dang things carry a static charge they stick to my cat and he has tracked them all over the house. On a positive note, they seemed to pass through his digestive tract pretty quickly.
Subscribe to:
Posts (Atom)