MS SQL server loosing conectivity

Hi,

I have a strange problem at one of my clients.
This client has one Hell of the SBS 2008, pimped-up to the nonsense. At first, they bought SBS 2008 from me, explicitelly said they do not need anything else, just a plain File server + domain controller. They requested me to set it up, then refused to pay for monthly SLA.

Ok, it has been 3 years since, and they called me to take a look at their SBS 2008, saying they have problems with SQL.
What SQL?

Woooohooo...I have never seen such a pimped up SBS :)
It has, beside SBS functionality:
- 1 MySQL database
- 1 Firebird SQL
- 1 MS SQL 2000 instance
- 2 MS SQL 2005 instances
- 5 MS SQL 2008 instances
- 1 Oracle VirtualBox virtual PC inside
- all volumes and shares have "Everyone" with Full Permissions granted
lol :))

Now, let's skip debate whether we should laugh or cry, and also must avoid any EXPENSIVE tasks. They do not have money, so 500 EUR is top they can pay for repair. Othervise they'll just switch back to work on each workstation separately.

Now, THE PROBLEM
All SQL databases were working fine for 3 years, until 2 weeks ago. Then SBSMonitoring DB got filled up to 4GB, which is top, and it begun drawing red circles in Event Logs.
At that moment most probably SOMEBODY did something nasty to SQL server, but there are 5 admins from 5 different applications, and it is impossible to know who did what.
The fact is, that from there on SQL instances begun refusing connections. Some applications worked for up to 5 minutes, then threw SQL Connection Error and froze.

Now, they called me.
First I sanitized blown up SBSMonitoring database, which I simply copied over from healthy source, put it into proper folder and started up SQL instance. All went fine (ok, SBS Console is unaware of server status, but doesn't matter).
But this did not solve SQL Connectivity Error.

I did some more insight excursion into SQL Management and found out, that most of SQL Admin roles simply vanished from SQL --> Security --> Logins!!!??? Simpy they were not there.
I called tech guy from one of application, and we re-created Admin role for their app in SQL...and Voila...this application raised up from dead. Working fine.

I thought kewl, we've got it...and recreated all other missing Admin roles...
...but this only repaired 3 out of 5 applications, which are using some SQL instance.

Now, the situation is:
- if run FROM SERVER directly, the application works fine
- but if run FROM CLIENT computer, some SQL error pops-up. Meaningless SQL error, different for each application.

Any idea what was going on with that server?
LVL 18
Andrej PirmanAsked:
Who is Participating?
 
Andrej PirmanConnect With a Mentor Author Commented:
So far no problems!
Seems like the last modification solved the problem:
- on server I added SynAttackProtect parameter for this network card, following this guide: http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
0
 
Matt BowlerDB team leadCommented:
I would need to see the connection strings and the error (MEANINGLESS OR NOT :))
0
 
PortletPaulfreelancerCommented:
pleased somebody said it:

Meaningless SQL error, different for each application.
suggest you supply these - they may not be so meaningless

that said: that client needs quite a deal of education, I sympathize.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
Andrej PirmanAuthor Commented:
Hi,

I know that "meaningless error" might also be of some help, but it all depends upon where the client is at the moment inside the application, what he/she is doing, but the culpit of all of them is that all errors are somehow SQL connection related.

I'll get back with some of those errors later today, when I will be back on site.
0
 
Matt BowlerDB team leadCommented:
My apologies - I must have accidently hit the caps lock - I didn't intend for "meaningless error" to be in upper case. But yes please - post errors with details of where they are occurring and we'll see what we can work out...
0
 
Andrej PirmanAuthor Commented:
Hi,
sorry for not getting back - vacation.

Well, 3 weeks it was all fine after some general sanitazing work in server (replaces SBSMonitirng db, scandisk, cleaned temp files, defrag, installed updates etc.), but now again, the same problem. SQL application works for 1-15 minutes, enables entering some dozen SQL queries...then refuses to connect. Quite random.

Error:

Microsoft OLE DB Provider for SQL Server (0x80004005)
[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.

I've already tried the following:
- PING is constant, no errors, no lost packages, under 1ms
- absolutelly NO errors on server-side SQL log. Only on client-side.
- no errors on server-side event logs
- the same application works if run on SERVER, meaning there is nothing wrong with SQL database itself
- on server I added SynAttackProtect parameter for this network card, following this guide: http://support.microsoft.com/default.aspx?scid=kb;en-us;899599

Any other idea?
0
 
Andrej PirmanAuthor Commented:
No other relevant suggestions were provided.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.