When Named Pipes was disabled? | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

When Named Pipes was disabled?

I had an issue in my production. The following information is from SQL Server logs: 2005-03-20 14:32:22.37 serverSQL server listening on TCP, Shared Memory, Named Pipes.
2005-03-20 15:02:36.32 serverSQL server listening on TCP, Shared Memory, Named Pipes.
2005-03-20 15:04:33.38 serverSQL server listening on TCP, Shared Memory, Named Pipes.
2005-03-21 02:02:19.71 serverSQL server listening on TCP, Shared Memory, Named Pipes.
2005-03-22 02:02:09.70 serverSQL server listening on TCP, Shared Memory.
2005-03-23 02:02:10.73 serverSQL server listening on TCP, Shared Memory.
2005-03-24 02:02:09.00 serverSQL server listening on TCP, Shared Memory. How can I find when exactly the Named Pipes was disabled? And who did it? CanadaDBA
As it refers the named pipes were disable on 22/03/05 at 02:02 and SQL do not keep such information in hand, so in order to avoid this issue in future you may use PROFILER or avoid having too many sys admins (SA) on SQL Server. Re-enable named pipes from server network utility on the server. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
1. Profiler? How can I use it to prevent this problem in future?
2. Regarding disabling named pipes; is it only possible from within SQL Server EM’s properties or it is possible to do it from within Windows? I want to know that someone has done it from within the Windows or SQL-Server.
3. There is a SQLAdmin domain id which can log in to the SQL Server as well. Almost everybody knows this id and the password. How can I control people to prevent these kind of issues?
quote:Originally posted by satya As it refers the named pipes were disable on 22/03/05 at 02:02 and SQL do not keep such information in hand, so in order to avoid this issue in future you may use PROFILER or avoid having too many sys admins (SA) on SQL Server. Re-enable named pipes from server network utility on the server. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided ?AS IS? with no rights for the sake of knowledge sharing.

CanadaDBA
You can disable named pipes or other net-libraries by: 1. Using SQL Server Network Utility
2. Editing registry Regarding Profiler, I guess Satya means to use it to trace who changes the setting thru SQL Server Network Utility. HTH
3. There is a SQLAdmin domain id which can log in to the SQL Server as well. Almost everybody knows this id and the password. How can I control people to prevent these kind of issues?
Ensure to maintain strict password measures and only know to you and department authority, if everybody know then its hard to find the culprit. As explained by PCSql avoid having too many administrators on the box or use third party tools to Audit the SQL server activity. May be PROFILER will help upto some extent but its not complete solution to monitor the under carpet transactions. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
But I am worry about impact on production’s performance if I run the PROFILER for let’s say 1 week or more. We have just upgraded our server and our Network Admin was working on the server as well. But no one knows who has disabled the Named Pipe. Is it possible that it was disabled by itself? CanadaDBA
NO chance of disabiling the network protocol by SQL engine itself, it must have occured by a user process or some kind of program that may disable the required protocol. It is a worrying factor to run the PROFILER on a production system for a longer period of time, instead you need to filter the causes by analysing the usage of database by all the users with admin privileges on that server. Instead you can run server side trace using extended stored procedures. No use now to know who did it, so beter late than ever… prevention is better than cure. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
…some kind of program that may disable the required protocol.
This might be the answer. I know that the NetAdmin was working on the server. My manager is looking for an answer to find out why this had happened and how we can prevent it occur again. Do you know such programs that might disable the protocol? Or are you sure the above italic phrase is correct? CanadaDBA
Best point of investigation is to refer to the event viewer on the server and check Security log to see who used the system during that time. You have to answer that question by reviewing usage of any third party tools across your enterprise or usage of any third party tools by the admin users. I don’t have any sure shot list of programs that might disable the important protocol on SQL Server. I’m also inclined towards a spyware program on the network, your Network Admin may answer about this. It looks like this was performed deliberately by an user.
May be other members in the forum might have faced similar situation, so wait for other opinions.
Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
You may want to check whether you have just applied SP3/SP3a or some security patches. I think Named Pipes is disabled for instance of SQL Server after applying SP3/SP3a or some security patches.<br /><br />But I believe it is very hard to find out how a network protocol is disabled.<br /><br />I’m not sure whether SQL Server logs obtains its information from the registry or really checking whether the network protocol is enabled. You may want to check the registry to see whether Named Pipes is still listed. If it is, it may be disabled because it is blocked somehow. <br /><br />What is the OS? Like XP SP2, TCP/IP is disabled since it is blocked by the default firewall setting.<br /><br />I hope someone can confirm my understanding too.[<img src=’/community/emoticons/emotion-2.gif’ alt=’:D‘ />]
The OS is Windows 2k3. CanadaDBA
Only this KBAhttp://support.microsoft.com/?scid=kb;en-us;821280&spid=2852&sid=global refers to disabling few features of named pipes which refers to the SQL Server 64 bit version and is not affective or referred for SQL Server standard or enterprise editions. I’m sure named pipes is the default and preferred protocol to communicate SQL Server and if you disable there must be other means of communication by using TCP/IP or multi-protocol. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
I just reread how XP SP2 affect SQL Server. Named Pipes seems to require Port 445. Since we’re talking about Windows 2003, did someone try to implement any beta version of Windows 2003 SP1 which I believe is similar to XP SP2. Just a wild guess.[<img src=’/community/emoticons/emotion-2.gif’ alt=’:D‘ />]<br /><br />
The following entry is in the SQL Server event log on Monday. Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 3/21/2005
Time: 1:59:49 PM
User: N/A
Computer: xxxxxxx
Description:
Error: 15457, Severity: 0, State: 1
Configuration option ‘show advanced options’ changed from 1 to 1. Run the RECONFIGURE statement to install. Is it related to the disabled Named pipes problem? CanadaDBA
I don’t think so. That is Severity 0 error. You will get it the 1st time you review server properties after a sql server starts. Which SQL Server service pack is applied and when?
True and nothing needs to be done. This error event will happen when viewing options from within Enterprise Manager. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
SQL Server Enterprise Edition 8.00.818 (SP3)
quote:Originally posted by pcsql …Which SQL Server service pack is applied and when?

CanadaDBA
Still the Named Pipe in production is disabled. Can I enable it without any issue? Should I do it after work hours? CanadaDBA
]]>