(sorry this has turned into a bit of an epic...thought I'd as the
experts!)
SQL 2k, sp3a. Dual xeon 2.4. 2 gig ram. everything on a 3 disk raid 5.
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Enterprise Edition on Windows NT 5.0 (Build 2195: )
Problem seems to be some extended procs that seemed to be running fine
on a 'vanilla' install on a different server now seem to be failing.
Failures occuring c 6 - 10 hours.
Sometimes the failure logs as the xp failure with severity 20 that I
kindof expect :s. other times absolutely nothing is logged.
There are a variety of error messages - or sometimes nothing at all.
http://www.mapinfo.com/common/docs/s...SWMSS48_RN.pdf
describes one of our issues, which seems to come out on the restart
after a failure:
Error event id is 19011, Message "SuperSocke t info:
ConnectionListe n(Shared-Memory (LPC)) : Error 5."
That site suggests:
Workaround
Suggested solutions include:
• Obtain a hotfix from Microsoft (http://www.microsoft.com). You will need to >cite the 94302reference number.
• Turn off shared memory in the client network configuration utility to >disable sharedmemory.
• Replace the SQL Server SSMSLPCN.DLL with the SSMSLPCN.DLL (8.00.540) from >SQLServer 2000 Service Pack 2.
- but I cant find any sensible information which describes this to
correlate! Searching MS for that number (94302) came up with zip.
The dll version we are running is 2000.80.760.0, although earlier
versions are elsewhere on the server (disk images).
Interesting to note that we seem to be able to replicate the 'leakage'
of improperly closed handles on this version, but not on the old
server running
that dll version 2000.80.194.0. This I understood to have been fixed
in sp3.
On one failure we caught the following (involving our extended procs):
2004-02-15 15:03:31.40 spid58 Error: 0, Severity: 20, State: 0
2004-02-15 15:03:31.40 spid58 Stored function
'xp_Contest_Cal culateScores' in the library 'e:\sql\xp\ga_p rocs.dll'
generated an access violation. SQL Server is terminating process 58..
2004-02-15 15:04:32.14 spid64 Error: 0, Severity: 20, State: 0
2004-02-15 15:04:32.14 spid64 Stored function 'xp_XML_GetSubT ree'
in the library 'e:\sql\xp\ga_p rocs.dll' generated an access violation.
SQL Server is terminating process 64..
2004-02-15 15:04:48.48 spid53 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 53, PSS = 0x472d7200, EC = 0x725fc098
*Stack Dump being sent to e:\sql\MSSQL\lo g\SQLDump0001.t xt
* *************** *************** *************** *************** *************** ****
*
* BEGIN STACK DUMP:
* 02/15/04 15:04:48 spid 53
This was followed about a minute later by:
2004-02-15 15:04:55.75 spid53 Stack Signature for the dump is
0x1CC03265
2004-02-15 15:04:55.75 spid53 SQL Server Assertion: File:
<recbase.cpp> , line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
2004-02-15 15:04:55.89 spid53 Using 'dbghelp.dll' version '4.0.5'
*Stack Dump being sent to e:\sql\MSSQL\lo g\SQLDump0002.t xt
2004-02-15 15:04:56.01 spid53 SqlDumpExceptio nHandler: Process 2292
generated fatal exception c0000005 EXCEPTION_ACCES S_VIOLATION. SQL
Server is terminating this process.
* *************** *************** *************** *************** *************** ****
*
* BEGIN STACK DUMP:
* 02/15/04 15:04:55 spid 53
As a side issue we have a number of 'initialisation of notify failed'
notes.
Any one have any clue about this?
Might the DLL need rolling back?
Is sp3a knacked for extended procs?
Is there some daft setting I've missed :/
Any good events to track in particular?
Cheers all!
