May 31, 2009 at 11:47 pm
Hi experts
when i tried to acess databases remotly from server
server is hanging(not able to open that application)
the following details are
OS : 2003 Enterprise Server SP2
Database : SQL server 2005
Application : sam
please let me Know when and at what situation server gets hanged and what are the solutuins to fix this issue permanently
PLs its urgent reply soon
Thanks in advance
June 1, 2009 at 12:08 am
Hi,
Good one. I can provide a handfull list for sever hung but I have some questions before that:
1) As you mentioned we are not able to connect to SQL Server,
are we connecting thru SSMS (installed on client machine)
or we are using OSQL/SQLCMD?
2) Are we able to connect to SQL or it fails? If failes does it gives some
errors?
3) After failure of login are we able to PING to the server using Name/
IP Address?
4) Are we facing any 17883/17884 scheduler hung problem?
5) How many instance of SQL are runing on this server and whether
problem occurs only when connect to specific instance only?
6) What we do in order to resolve this issue?
Scenarios when Server is Hung
========================
1) Insufficient Memory
2) HIGH CPU Utilisation
3) Faulty Network because of which we feel we are not able to
connect to server is appears HUNG.
4) Faulty NIC card.
5) Scheuler Hung (17883/17884).
6) Server freeze (OS).
Please let me know in case you have specific questions on this.
Regards
GURSETHI
June 1, 2009 at 5:25 am
sivark1 (5/31/2009)
Hi expertswhen i tried to acess databases remotly from server
server is hanging(not able to open that application)
the following details are
OS : 2003 Enterprise Server SP2
Database : SQL server 2005
Application : sam
please let me Know when and at what situation server gets hanged and what are the solutuins to fix this issue permanently
PLs its urgent reply soon
Thanks in advance
Do you have access to the error/application log? Any hints on that?
February 18, 2010 at 3:21 am
Typical woolly response. SQL Server is crap!
February 18, 2010 at 3:45 am
terry.payne (2/18/2010)
Typical woolly response. SQL Server is crap!
IMO a "woolly" response is needed when a question is asked with no "meat" in it.
Anyone with some knowledge of databases and or O/S's would also supply any errors in app/sys log, sql error log etc. On top of that would be stats from the O/S like mem info, cpu usage bla bla. At least the spec of the server, size of DB, concurrent connection...
Granted some people are beginners and need assistance, but sure if they work on computers/server they know the 1st place to look.
See....
February 18, 2010 at 3:57 am
Can you access remote folders on that server via windows Server? \\servername\foldername?
Is you app (sam) looking for an IP or hostname? Is the named pipes configured on the hosting sql server?
Please provide more info.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
February 18, 2010 at 4:16 am
All to often there are no messages at all and no specific entries to be found in the log files. The memory capacity of both the server and the client workstation should be more than adaquate to deal with the nature of the work I am involved with. The main interface to SSMS just regularly has a bizarre habit of freezing up for no apparent reason. On average this probably happens about 2-3 times a day. After rebooting my local workstation surprise, surprise everything works fine! Surely, the least that Microsoft could do is actually provide some meaningful messages.
February 18, 2010 at 4:24 am
terry.payne (2/18/2010)
All to often there are no messages at all and no specific entries to be found in the log files. The memory capacity of both the server and the client workstation should be more than adaquate to deal with the nature of the work I am involved with. The main interface to SSMS just regularly has a bizarre habit of freezing up for no apparent reason. On average this probably happens about 2-3 times a day. After rebooting my local workstation surprise, surprise everything works fine! Surely, the least that Microsoft could do is actually provide some meaningful messages.
Sounds more like you have worktation issues, and all your issues could be the result of other problems.
A bit on the negative side towards MS? 😀
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
February 18, 2010 at 4:29 am
If there are no errors, then stating that fact stops people who are offering Free assistance wasting time on asking "has anything changed?" or "what are in the error logs" or "has this occurred before" etc
Yes, granted there are issues with SQL Server/SSMS but no sw is bug free or reasonable error message captured 100% of the time! But in the event of varying issues, surely you must agree supplying "reasonable" (reasonable = "it depends") amount of background to the problem is going to help you get a quicker response?!?
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply