Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Jon G
Starting Member
31 Posts |
 Posted - 2012-04-06 : 07:22:28
|
My client has a virtual(vmware) SBS 2011 server running SQL server 2008R2 Express. My application connects from an XP client pc to the database and performs queries. Before yesterday everything was running fine without problems. However, suddenly yesterday morning the client pc's (some of them, not all) were throwing up an MDAC error "Catastrophic Failure" when performing a search. I have reorganised the database indexes and checked the database and all is fine with no errors reported and autoshrink is turned off. The database is only 170mb (mdf) and the ldf is 1.5mb, this is normal for this database. A full sql backup is performed every night.I installed my client software on the server as a test and all worked fine as it should without problems. The only thing that has changed on the server since before the errors started from the remote xp clients is SBS2011 update rollup 2 2660819Any ideas would be greatfully received as I am tearing out the very few strands of hair that I have left.thanks in advanceJon |
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2012-04-06 : 09:32:20
|
do you have any more information other than "Catastrophic Failure" like an error code, callstack, etc?if you can connect from some clients but not others, then the problem is most likely not with the database. It's with the clients.
elsasoft.org |
 |
|
|
Jon G
Starting Member
31 Posts |
Posted - 2012-04-06 : 11:06:49
|
quote:
Originally posted by jezemine
do you have any more information other than "Catastrophic Failure" like an error code, callstack, etc?if you can connect from some clients but not others, then the problem is most likely not with the database. It's with the clients.
elsasoft.org
The only error is "Catastrophic Failure" and there are no error codes. I can connect from all clients, it is only when performing the query that the error is raised, but by that point the connection to the database is already open. I don't think it can suddenly be all the client pc's. There are 20 client pc's and some of them have the problem and some of them don't and none of the client pc's have been updated. All of this was working perfectly 2 days ago and then suddenly the error started popping up. My gut feel is that it is the server, not necessarily the database of course, might be something else on the server. All very annoying  |
|
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2012-04-07 : 18:31:05
|
anything in the NT eventlog on the client machines?
elsasoft.org |
|
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2012-04-09 : 09:29:23
|
| Could you supply the driver version number?Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
Jon G
Starting Member
31 Posts |
Posted - 2012-04-09 : 17:40:31
|
quote:
Originally posted by jackv
Could you supply the driver version number?Jack Vamvas--------------------http://www.sqlserver-dba.com
The driver version of what ?thanks |
|
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2012-04-10 : 04:03:29
|
| Is an ODBC driver being used?Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
Jon G
Starting Member
31 Posts |
Posted - 2012-04-10 : 16:47:02
|
| Rather strangely, the problem just went away on it's own today, so I'm wondering if it was something else at the server slowing everything down? On the other hand, it could of course be that the customer had done something to cause this error and then rectified his own mistake without telling me of course ;-)thanks for your replies and I will report back if it happens again |
|
|
|
|
|
|
|
|
Catastrophic Failure