Troubleshooting a SQL Server...

I’m having problems MS SQL server.  It is Windows 2003, IIS 6, with a copy of SQL Server 2000 sp3a and the BlueDragon application server installed.

I’ve noticed two times now that SQL Server agent in the taskbar is red and stopped.  So I restart SQL Server.  However, this only sort of fixes the problem.  While I can use Enterprise Manager from this specific server to get on SQL Server and run queries, etc, other things don’t work.  I can not use Enterprise Manager on a remote server to connect!?  Also, BlueDragon which is a ColdFusion application server, can’t run queries on the database either.

From what I can tell I can “telnet 000.000.000.000 1433” to the server, and that is responding – even from a remote computer.  (I don’t know how to log in doing this or anything else.  I just know I’m not seeing an error that says “Could not open connection to the host, on port 1433: Connect failed” as if I was to try doing this on say port 888 or 999.)

So my questions are twofold:


1.) Why might SQL Server only be working from Enterprise manager on this specific server, but not from other machines?  Why can’t I query the database from BlueDragon either which is running on the same machine?  This might be an easier question to answer because I see a bunch of application errors in the Event Viewer saying:

7/9/2005 – 1:52:11 PM – Category 2 – Event 17055
 “SuperSocket Info: Bind failed on TCP port 1433.”

7/9/2005 – 1:52:11 PM – Category 8 – Event 19011
 “SuperSocket info: Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013.”

I’m guessing because SQL server, after it crashed, did not free up port 1433, and thus when I start it again it can’t get exclusive use of this port.


2.) How can I track down the problem and find what is causing SQL server to shut down in the first place?  In the application event viewer I see:

7/9/2005 – 4:05:37 AM – Category 2 – Event 17055
 “17311 : SQL Server is aborting. Fatal exception c0000005 caught.”

7/9/2005 – 4:05:37 AM – Category 2 – Event 17055
 “17310 : SqlDumpExceptionHandler: Process 3220 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.”

Also, this happened yesterday, where I’m seeing the following application errors too:

7/8/2005 – 9:54:25 PM – Category 2 – Event 17055
“17310 : process_commands: Process 3888 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.”

7/8/2005 – 9:54:25 PM – Category 2 – Event 17055
 “17310 : process_commands: Process 3020 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.”

7/8/2005 – 9:54:25 PM – Category 2 – Event 17055
 “17310 : process_commands: Process 1392 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.”
LVL 1
rebiesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Anthony PerkinsCommented:
Please maintain these abandoned questions:
1 05/10/2005 500 1045 Error on MySQL 4.1.11 during Server...  Open Mysql
2 05/18/2005 500 Form method=post in JavaScript?  Open JavaScript
rebiesAuthor Commented:
acperkins:

I will do that at another time.  I have not gotten the answers I need on those two questions and those issues remain open for me.  I have been meaning to answer the questions, but realize it'll take me a couple hours to get back into those projects, work through the solutions and see who's answer best meets the question I asked.

Right now I care about Microsoft SQL Server and why it's crashing.  Can you offer any help on this?  I will be sure to close those other questions assuming I can find a solution to my current problem first!
k_murli_krishnaCommented:
While installing SQL Server, there are 2 options i.e. SQL Server 2000 Enterprise Edition server OR Microsoft SQL Server Desktop Engine(MSDE). Just choose the checkbox named default during an installation & do not choose radio button & supply an instance name.
Your Server service should be MS$MYINST & not MSSQLSRV. There is a 80 folder which is common in Program Files\MS SQL Server. If you install server as well as MSDE you will get 2 folders & both will work. MSDE will connect from local Enterprise Manager but not from that of a remote machine. To use isql or osql which are present in 80\bin:
1) MS SQL SERVER
isql -S KSGT0689 -d TEST -U sa -P sa
2) MSDE
isql -S \KSGT0689\MYINST -d TEST -U sa -P sa

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

rebiesAuthor Commented:
k_murli_krishna:

I think you misunderstood.  (or maybe I am misunderstanding.)  This is not the desktop version, but instead a 1 Processor license of Microsoft SQL Server 2000 Standard Edition.  It is not the desktop Engine.  Before SQL Server shuts itself down it does accept incoming Enterprise Manager connections.  It's Part 1 of my question that is asking why when I start it up again it is not binding itself to these ports.

More importantly to me, what could be causing it to shut down on it's own?  (MSSQL, not the server)  I think it has something to do with the “17311 : SQL Server is aborting. Fatal exception c0000005 caught.” error I pointed about above, but I don't know where to go from here.   Does that error indicate a specific problem, or query in the database?  Can I read into that error any further or the other application errors I pointed out?
Anthony PerkinsCommented:
>>I have not gotten the answers I need on those two questions and those issues remain open for me.<<
Than you should have said so at the time.

>> Can you offer any help on this?  <<
Sorry, I will also have to "do that at another time".
rebiesAuthor Commented:
Thanks acperkins - your help is no longer needed here.  I'm hoping others can offer a helping hand in this matter.  Please stop making this topic about something else!
Anthony PerkinsCommented:
Fair enough.  But it is just only fair to let you know that experts will be more responsive if you take the time to maintain your abandoned questions as per the EE Guidelines that you agree to every time you sign on to this site.

In any case, it is your choice, I wish you the best of luck (I suspect you care going to need it)

<unsubscribe>
Racim BOUDJAKDJIDatabase Architect - Dba - Data ScientistCommented:
rebies,

Agreed with acperkins, please maintain your questions.  Just check out EE's guidelines if you may ask yourself some question about how to deal with questions on which you are not satisfied with the answers but dont leave them open too long...Good luck with the rest of the question...
Guy Hengel [angelIII / a3]Billing EngineerCommented:
I experienced quite the same problem on my laptop, and I had found out that it was due to some trojan/worm that hacked my windows installation... I had to reinstall the SQL Server and it worked again for 3 weeks :-(
Hope your server is not affected, but it might be worth a look.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.