1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

SQLOLEDB crash in SQL 2000 - help!

Discussion in 'Software' started by Mikeyboy, Oct 23, 2011.

  1. Mikeyboy

    Mikeyboy Kilobyte Poster

    Hi All,

    Had an issue suddenly rear its ugly head in work, we have a 2003 server running SQL 2000 which has been rock solid for years, and all of a sudden has started crashing constantly (which is causing issues across the business), and we are all stumped, none of us have an idea how to fix it.

    The error we are getting is

    Faulting application sqlservr.exe, version 2000.80.2039.0, faulting module sqloledb.dll, version 2000.86.3959.0, fault address 0x0004d264.

    Cant seem to find much on this, we tried replacing the sqloledb.dll with one from a SQL 2005 server which works OK, but this did nothing. Can't do a repair install, as it is not an option in add/remove programs, and putting the disk in doesn't give us the option either. Updated to the latest service pack, nothing seems to have sorted it.

    Nothing has changed recently, some changes were made on the 2005 server recently to improve performance, and seems whenever a large query between these two linked servers is run, it falls over with the above error.

    Anyone any ideas on where we can go next?
    Certifications: VCP,MCSA, MCP, MCDST, MCITP, MCTS, A+, N+
  2. dmarsh

    dmarsh Terabyte Poster

    Anything else in the event logs ? Whats changed on the machine ? Is this likely a bad install or file corruption or a real bug thats jut been discovered ? Maybe an abnormal load or routine has caused a different execution path ?

    Send a crashdump or minidump to MS ?

    Set up a post mortem debugger ?
    Enabling Postmortem Debugging

    Failing that use Visual Studio express as a user mode debugger and attach to process before crash.

    Not all dll's are the same despite their name, is the replaced dll also the same size and version ? If its a COM DLL did you re-register it ? MS are good at backward compatibility but its not a safe practice to take a SQL 2005 DB dll and apply to a SQL 2000 DB.

    Try enabling Gflag to allow you to detect heap violations ?

    You say constantly ? How often ? What circumstances ? What users are on the DB during crash ? What execution plans are running ? Is the machine low on resources ? etc

    Failing all that, why not rebuild the server on new kit with a newer version of SQL Server.
    Last edited: Oct 24, 2011
    Certifications: CITP, BSc, HND, SCJP, SCJD, SCWCD, SCBCD, SCEA, N+, Sec+, Proj+, Server+, Linux+, MCTS, MCPD, MCSA, MCITP, CCDH
  3. Mikeyboy

    Mikeyboy Kilobyte Poster

    Just wanted to follow up on this. Thanks for the reply :)

    As mentioned there were some changes on the other 2005 server, although some of these changes were reverted, some new indexes were created by some 3rd party software (dont know what it was) but these were the key, we deleted these and everything back to normal! One stressful week come to an end.

    We were going to try a reinstall of SQL but installed it on a separate machine first, simulated the same reports and received the same errors, took these indexes out and hey presto... a weight off all our shoulders!!
    Certifications: VCP,MCSA, MCP, MCDST, MCITP, MCTS, A+, N+

Share This Page