Solved

All pipe instances are busy

Posted on 2004-03-25
9
1,640 Views
Last Modified: 2008-03-04
the exporter - about once every two to three weeks - the exporter just dies and gives us this error message:

      Connecting to XXX*Master
      getConnection failed (\\.\pipe\mssql$gmrprod\sql\query (All pipe instances are busy))
      Connection to XXX*Master Failed

any idea what it's doing when it times out? and is there a way to increase the exporter time out?

Any suggestions to fix the above issue will be greatly appreciated.

Thanks.
0
Comment
Question by:crishna1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
9 Comments
 
LVL 30

Expert Comment

by:Rich Weissler
ID: 10681529
I'm not certain this is a timout issue, is it?  There is a small chance that this could be a DOS attack, or other malware... which actually could be running on that server.

This looks like MS SQL.  Have you applied all the patches?  You could be getting hit by the Slammer virus every few weeks.
Check here for more information: http://www.microsoft.com/security/slammer.asp

At a minimum, make certain you have this patch applied to the server:
http://www.microsoft.com/technet/security/bulletin/MS02-061.mspx

All slammer takes to clear out is a reboot... but it will be infected again a few days or weeks later if it isn't patched...
0
 

Author Comment

by:crishna1
ID: 10681587
You are right , this is MS Sql.

Also,FYI :we are using it for fail over and disaster recovery - Our product normally runs 100% on the same node.

my dumb question , is there anything like increasing the number of pipes?

please advice
Thanks.
0
 
LVL 30

Expert Comment

by:Rich Weissler
ID: 10683422
Ohhh.  I wish elsewhere right now so that I could test this, but it looks like the maximum number of named pipes are automatically determined by the operating system based on the resources available.  When the error occurs, take a look at "Computer Management", and I think it's sessions to see the pipes currently in use.  (I don't think that is IPC$ traffic, but I could be wrong.  I'll have to get back to my system tomorrow to check...)

(Anyone else want to jump on that one before tomorrow for an assist?)

In any event, I suspect if the system is working correctly for weeks at a time, without problems, and they SQL Server isn't patched, that you are getting infected every few weeks by the Slammer virus.  You can look here: http://isc.sans.org at the volume of port 1434 traffic to see that Slammer and it's ilk are still alive and well on the net.  :-(  )
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 30

Accepted Solution

by:
Rich Weissler earned 500 total points
ID: 10687331
Ok, two items:
  (1) Don't uses "Computer Management" to check on the number of sessions open.  You CAN use the old standby in SQL Server Enterprise Manager, Management, Current Info, Process Info -- and that will tell you what is currently running on the SQL server.
  (2) I still don't see any way of configuring the maximum number of named pipes.  Your server should continue to allow allow connections until it runs out of other resources.
0
 

Author Comment

by:crishna1
ID: 10783986
any further information on this??
0
 
LVL 30

Expert Comment

by:Rich Weissler
ID: 10784042
Have you been able to confirm whether you have the Slammer virus?  Is the SQL Server patched to at least SP3?

The number of pipes is fluid based on available resources.
0
 

Author Comment

by:crishna1
ID: 10784058

I am currently located in a different location from where the server is, i need to check with the folks there.
let me get back with you on those, is there anyother information  i need to ask for?

Appreciate your help!

Thanks.
0
 
LVL 30

Expert Comment

by:Rich Weissler
ID: 10784251
When the problem occurs, does the CPU utilization on the SQL server spike up to around 100%?

They can check the patch level by running Query Analyzer and entering "SELECT @@VERSION"
Which will return a line which starts with: "Microsoft SQL Server  2000 - 8.00.818 (Intel X86)   [...]"
Per http://www.tacktech.com/display.cfm?ttid=60

8.00.818 is the current version.  If they are running a version before 8.00.760, you have reason to be concerned.
0
 

Author Comment

by:crishna1
ID: 10805790
The following is the info i got from my folks, please advice!

Thanks.


Answers :

All SQL Servers have been updated with the SLAMMR virus fix.
SP3 has been installed for sometime now.
The problem has only happened twice this year and we weren't
monitoring the CPU.

We don't run SQL Servers here on port 1433. The SQL Servers are all named
instances clustered via Veritas software. Which is the reason we had to use
the Named Pipe name in the connection string of the exporter. The Net Bios
name or the ip address will not work connecting to this SQL database, at
least we haven't been able to get it to work since moving off MS Cluster to
Veritas.



0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Recommendation for open source Monitoring 7 99
ASA NAT rule change 3 85
Routing Issue 26 67
Need to cut my Verizon home cost 3 63
When you try to share a printer , you may receive one of the following error messages. Error message when you use the Add Printer Wizard to share a printer: Windows could not share your printer. Operation could not be completed (Error 0x000006…
I had an issue with InstallShield not being able to use Computer Browser service on Windows Server 2012. Here is the solution I found.
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question