Results 1 to 7 of 7
  1. #1
    Join Date
    Mar 2004
    Posts
    4

    Unanswered: Problem starting SQL 2000

    My SQL2K was running fine. Yesterday, I decided to install SP3a. During the installation, it failed when apply sp3_serv_repl.sql. And I can't start SQL server anymore. The error is :

    FRunCM : Process <> generated Fatal Exception C0000005
    Exception Access Violation - SQLServer is terminating this process.

    No matter what I did, I couldn't start the service again.
    SO I decided to uninstall SQL2K and install again. Installation is ok, no problem. But, again the SQLServer service cannot start up. The same error appeared. Besides, there is also the error about :

    Supersocket Error 1355.

    I have tried all the suggestions that I can find in the net but nothing seems to work.

    Please advise what should I do. Thank you very much.

    Philip

  2. #2
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Those super socket errors are informational and no threat to the server.

    As defined in this KBA http://support.microsoft.com/?kbid=814572 you should get SP3a and re=apply.
    Try to look into the scripts involved in that sp3_serv_repl.sql file.

    BTW what are privileges of the account used to start SQL services?
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  3. #3
    Join Date
    Mar 2004
    Posts
    4
    Originally posted by Satya
    Those super socket errors are informational and no threat to the server.

    As defined in this KBA http://support.microsoft.com/?kbid=814572 you should get SP3a and re=apply.
    Try to look into the scripts involved in that sp3_serv_repl.sql file.

    BTW what are privileges of the account used to start SQL services?

    Yes, I read that Microsoft said the errors are informational. But it's strange as I am using LocalSystem and even tried local Administrator account to start the SQL services.

    I have read the KBA and actually I am already using SP3a when I got the errors. I have tried restarting the server and reapplying SP3a but it didn't help.

    I can start the SQL server manually using -c and -f options. But as soon as I tried to do a client connect, it will crash with the reported errors.

  4. #4
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    What is the level of service pack on OS?
    I suspect something to do with OS files mismatch, may try applying latest service pack on OS.

    Review event viewer log for any information that can help.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  5. #5
    Join Date
    Mar 2004
    Posts
    4
    Originally posted by Satya
    What is the level of service pack on OS?
    I suspect something to do with OS files mismatch, may try applying latest service pack on OS.

    Review event viewer log for any information that can help.
    It's already on SP4 but I will reapply.
    BTW, do you think it has something to do with MDAC?

    Thank you.

  6. #6
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    COuld be one of the reason.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  7. #7
    Join Date
    Mar 2004
    Posts
    4
    Originally posted by Satya
    COuld be one of the reason.
    I reapply SP4 but problem still exist. When I look the SQL log, everything seems to be starting ok. Databases were started and the last sentence said "Waiting for client connection" and then suddenly it crashed. May I know what is the SQLServer does after the "waiting for client connection"? I am trying to pinpoint where is the problem. The dump file shows the stack but doesn't record which module causes the problem.

    Thank you.

Posting Permissions

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