Failed Assertion

Could you please help me out if you know how to resolve this error:
SQL Server Assertion: File: <diskio.c>, line=670
Failed Assertion = 'filepos + cBytes <= (DWORDLONG) m_size << PAGESIZEBITS'.
On Fri, 1 Jun 2007 13:11:01 -0700, sam wrote:

>Could you please help me out if you know how to resolve this error:
>SQL Server Assertion: File: <diskio.c>, line=670
>Failed Assertion = 'filepos + cBytes <= (DWORDLONG) m_size << PAGESIZEBITS'.
Hi Sam,
A failed assertion is on most cases an indication of a bug. It could
also be related to some inconsistency on your DB.
Steps to take:
1. Run CHECKDB on your databases.
2. Upgrade to latest service pack.
3. If problem persists, open a support case with Microsoft.
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
|||Hi Hugo,
Thanks a lot for your quick respond on this matter. Yes, Planning to run
dbcc checkdb on affected database. Also, suggested team to upgrade SQL Server
2000 to SP4, currently it is SP3 with Hotfix 818.
Thanks,
Sam
"Hugo Kornelis" wrote:

> On Fri, 1 Jun 2007 13:11:01 -0700, sam wrote:
>
> Hi Sam,
> A failed assertion is on most cases an indication of a bug. It could
> also be related to some inconsistency on your DB.
> Steps to take:
> 1. Run CHECKDB on your databases.
> 2. Upgrade to latest service pack.
> 3. If problem persists, open a support case with Microsoft.
> --
> Hugo Kornelis, SQL Server MVP
> My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
>

Failed Assertion

We're getting the following on a Windows 2003 Server, running SQL 2000 SP3a.
17066:
SQL Server Assertion: File: <diskio.c>, line=670
Failed Assertion = 'filepos + CBytes <= (DWORDLONG) m_size << PAGESIZEBITS'.
Any ideas?
Jeremy
Well I think by Failed Assertion means it failed some runtime check. Theres
no way to really know whats causing this error in your specific instance but
its probably some kind of database information inconsistency. Type DBCC
CHECKDB and see what it says. Your database probably isnt normalized well
enough.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200601/1

Failed Assertion

We're getting the following on a Windows 2003 Server, running SQL 2000 SP3a.
17066:
SQL Server Assertion: File: <diskio.c>, line=670
Failed Assertion = 'filepos + CBytes <= (DWORDLONG) m_size << PAGESIZEBITS'.
Any ideas?
JeremyWell I think by Failed Assertion means it failed some runtime check. Theres
no way to really know whats causing this error in your specific instance but
its probably some kind of database information inconsistency. Type DBCC
CHECKDB and see what it says. Your database probably isnt normalized well
enough.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200601/1

Failed Assertion

Could you please help me out if you know how to resolve this error:
SQL Server Assertion: File: <diskio.c>, line=670
Failed Assertion = 'filepos + cBytes <= (DWORDLONG) m_size << PAGESIZEBITS'.On Fri, 1 Jun 2007 13:11:01 -0700, sam wrote:
[vbcol=seagreen]
>Could you please help me out if you know how to resolve this error:
>SQL Server Assertion: File: <diskio.c>, line=670
>Failed Assertion = 'filepos + cBytes <= (DWORDLONG) m_size << PAGESIZEBITS'.[/vbcol
]
Hi Sam,
A failed assertion is on most cases an indication of a bug. It could
also be related to some inconsistency on your DB.
Steps to take:
1. Run CHECKDB on your databases.
2. Upgrade to latest service pack.
3. If problem persists, open a support case with Microsoft.
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis|||Hi Hugo,
Thanks a lot for your quick respond on this matter. Yes, Planning to run
dbcc checkdb on affected database. Also, suggested team to upgrade SQL Serve
r
2000 to SP4, currently it is SP3 with Hotfix 818.
Thanks,
Sam
"Hugo Kornelis" wrote:

> On Fri, 1 Jun 2007 13:11:01 -0700, sam wrote:
>
> Hi Sam,
> A failed assertion is on most cases an indication of a bug. It could
> also be related to some inconsistency on your DB.
> Steps to take:
> 1. Run CHECKDB on your databases.
> 2. Upgrade to latest service pack.
> 3. If problem persists, open a support case with Microsoft.
> --
> Hugo Kornelis, SQL Server MVP
> My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
>