May 19, 2003 at 1:34 pm
Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:1447
Expression: m_SizeRec>0 && mSizeRec<=MAXDATAROW
SPID: 56
Process ID: 576
I recently began sporadically receiving this error message box from some SQL Tasks in a DTS package that I have been using without problems for months. (I have no such drive/path called q:\SPHINX ...). Anybody else ever run across this one or how to fix it?
Thanks.
Bill
Bill.
OCP
May 19, 2003 at 1:47 pm
More info:
Running the SQL in Query Analyzer generates the following:
SQL Server Execution Times:
CPU time = 0 ms, elapsed time = 0 ms.
SQL Server Execution Times:
CPU time = 0 ms, elapsed time = 0 ms.
Server: Msg 3624, Level 20, State 1, Line 1
SQL Server parse and compile time:
CPU time = 20 ms, elapsed time = 27 ms.
Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 53
Process ID: 576
ODBC: Msg 0, Level 16, State 1
Communication link failure
Connection Broken
I don't see how this can refer to a broken connection - it is an insert from one table to another in the same database.
Bill.
OCP
May 19, 2003 at 2:23 pm
Think that's an MS internal directorys, sounds awfully familiar. Check this out http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_20307973=.html
John Zacharkan
John Zacharkan
May 19, 2003 at 2:59 pm
Take a look here and specifically try DBCC CHECKDB to see what it reports http://dbforums.com/arch/68/2003/2/662838 but it commonly boils down to replication but may require a ticket with MS to specifically resolve the issue.
May 19, 2003 at 3:09 pm
Thanks.
At least I know I'm not the only one to have run into this. However, while the error message was the same, I have not re-attached a db, other than restoring from an MSDB backup when none of my dts packages would open one day last week, and I think that was after I started getting the error messages.
I tried following the sugestion to re-index in the post you referred me to. Unfortunately, when I attempted to re-index one of the tables I got the same (exact) error message from Query Analyzer as above.
Bill
May 19, 2003 at 4:47 pm
Thanks, Antares686.
Still no luck (I'm almost disappointed that there were no errors: CHECKDB found 0 allocation errors and 0 consistency errors). At least then I would have had an indication of the problem.
I checked the system event logs and didn't see any i/o related errors.
Also, you mentioned replication, but I'm not using replication.
Just for the heck of it (when in doubt, re-boot) I just shut down the SQL Server using Service Manager, then re-started it and the dts package ran fine. I was also able to re-index the table.
I'm not confident that the problem is solved, though.
Bill.
OCP
May 19, 2003 at 5:11 pm
If occurrs again I would definently check the MS KB site again at that time and if nothing related give them a call or email depedning on the urgency. Let them know a reboot seemed to work previously but issue returned if does.
However, based on the reboot and the fact your are hitting internal code errors here it seems to be a fault in the SQL Server executables and may occurr again.
Edited by - antares686 on 05/19/2003 5:12:05 PM
May 27, 2003 at 1:56 pm
Well, it now appears the problems have been caused by a corrupted hard disk. Today I received the following msg "The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:.". Chkdsk confirmed that there were errors, but the /f (fix) option does not seem to correct the problem. So, it apears that I will have to reformat/re-install.
Bill
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply