Results 1 to 6 of 6
  1. #1
    Join Date
    Apr 2003
    Posts
    3

    Unanswered: SQL 2000 crash after SP3: EXCEPTION_ACCESS_VIOLATION

    We attempted to upgrade two machines from 7.0 to 2000/SP3. The 2000 instances will crash if:

    you connect to the database using enterprise manager
    you perform a "DBCC CHECKDB"

    the latter gets you this:
    [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionCheckForData (CheckforData()).
    Server: Msg 11, Level 16, State 1, Line 0
    General network error. Check your network documentation.

    Connection Broken

    as does sp3_serv_uni.sql during SP3 install.

    Again, this is on two different machines. Both were wiped clean (SQL uninstalled, all files removed, registry cleaned) and neither will run SQL 2000.

    The SQLDump file is attached.
    Attached Files Attached Files

  2. #2
    Join Date
    Dec 2002
    Location
    Czech Republic
    Posts
    249
    Well, you upgraded MSSQL7 by a MSSQL2K service pack 3, TWICE

    I wonder it can be done. Can you attach your databases (MDF) to a working MSSQL7 server?

  3. #3
    Join Date
    Apr 2003
    Posts
    3

    SP3 deux

    Yes, SP3 was installed twice. (How did you know that?) It was inadvertent, but only on one machine. Both machines have 7.0 running, now with 2000 client tools. I can't believe a SP3 is that unstable, or that dangerous.. SQL 2000 will not run after:

    uninstalling SQL Server
    cleaning registry
    deleting all directories and files
    resintalling

    The MDF's are off the CD, and they don't connect to 7.0

    Server: Msg 5172, Level 16, State 15, Line 1
    The header for file 'C:\Program Files\Microsoft SQL Server\MSSQL$ROC0WP2000\Data\pubs.mdf' is not a valid database file header. The PageAudit property is incorrect.

  4. #4
    Join Date
    Dec 2002
    Location
    Czech Republic
    Posts
    249
    You probably didn't install SP3, but MSDE 2000 SP3 Instance without upgrade option. Your files are in your old database folder, deleted or upgraded to MSSQL2K format. Find them first.
    Do not care about pubs, it in MSSQL2K format already. Where are your real databases?

  5. #5
    Join Date
    Apr 2003
    Posts
    3
    MSDE might have something to do with it. This is a new machine. The install order was

    .NET installed
    MSDE installed
    Upgraded to full server
    SP 3 installed (from MS website, right after slammer)

    (everything happy)

    SP 3 installed again

    (oops)

    SQL uninstalled
    MSDE uninstalled
    SQL 7.0 installed


    The data is unimportant here, the real problem is that no matter what I do, I can't install SQL 2000 and get it working.
    My co-worker, who is much smarter than I, also has the same problem with his machine. No other machines in the office built at the same time have this problem, and both affected machines are happily functioning as 7.0 development servers.

  6. #6
    Join Date
    Dec 2002
    Location
    Czech Republic
    Posts
    249
    Try to install a new MSSQL2K instance (different name).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •