|
Home > Archive > MS SQL Server > July 2005 > Is bug described in article 872843 really fixed?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Is bug described in article 872843 really fixed?
|
|
| Jonathan Levine 2005-07-29, 3:23 am |
| I'm running SQL Server 2000 SP4 with the AWE hotfix (build 2040?) on Windows
Server 2003 with replication.
This morning, my log reader agents failed. In the server log, I saw the
following messages:
SQL Server Assertion: File: <logscan.cpp>, line=1985
Failed Assertion = 'startLSN >= m_curLSN'.
....
SQL Server Assertion: File: <logscan.cpp>, line=2223
Failed Assertion = 'm_noOfScAlloc == 0'.
KB article 872843 says that this is supposed to be fixed in SP4... is it?
Or did it come back in the AWE hotfix?
Regards,
Jonathan
| |
| Sophie Guo [MSFT] 2005-07-29, 3:23 am |
| Hello,
KB872843 is included in SQL server 2000 SP4. It appears a new issue and is
not related to the AWE hotfix. Please reInitializing the replication and
then check if the issue still exists.
To find out the cause of this issue we may need to analyze memory dumps,
this work has to be done by contacting Microsoft Customer Service and
Support (CSS). Therefore, if the issue still exists, please contact CSS for
more immediate assistance. For more information on available CSS services,
please click here:
http://support.microsoft.com/defaul...e#faq
607
|
|
|
|
|