SQL client refusing connections until alias recreated

[clarkin]

Getting an unusual problem today between our app server and our db server - things will run fine until suddenly all connections to SQL server will be refused.

When this happens I can still see/access the SQL server machine from the app server, and can connect correctly (eg via QA) to SQL server from any other machines, but cannot connect from the app server.

When I remove + recreate the alias for the sql server instance in client network utility on the app server, things start working again for a while. Still haven't worked out what actions exactly cause it to start refusing again.

These 2 machines have been working fine for the last 14 months, and we haven't installed anything new on either in at least 2 months.

Anyone seen this kind of behavior before?

Thanks in advance

Posting code? Wrap it with code tags: [ignore]

[/ignore][code]CodeHere

[ignore][/code][/ignore].

 

[SQLBill]

How many connections are allowed in SQL Server?
In Enterprise Manager (EM), expand to the server group. Right click, select properties, go to Connections tab. Check connections.
How many connections are occuring?
In EM, expand to Management. Expand that to find Current Activity, expand that. Click on Process Info. That will show how many connections there are and how many are active.

We have an app that acts as a 'middle man' for our users. If the users don't close their console properly, the app leaves the connection open expecting the user to reopen/reuse the connection. This can create several unused connections. Stopping the app server (as you do) breaks these unclosed connections and everything works fine again.

If this is your issue, you need to get the users to properly close their connections.

-SQLBill


Posting advice: FAQ481-4875