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 |
|
Kurt Henderson
Starting Member
1 Post |
 Posted - 2008-04-21 : 22:53:52
|
| I have something very strange going on and any input would be appreciated.I have a Win2003 SBS server which I have had SQL 2000 Standard Edition installed on for a while. We use this server mainly for our own internal use but I have one client who I host their database on this same server. Last weekend, I installed Microsoft SQL Server Express Edition with Advanced Services along side the SQL 2000 installation. This was a side-by-side install and the MSDE2005 was installed as a different instance. The installation went fine and everything was working as expected and everything was fine Monday and Tuesday but then by Wednesday, my client started having problems locking up in our software. After doing a lot of searching and testing, I figured out that what it was hanging on was a simple SQL query. The query was "Select * from County". Once I figured this out, I was able to duplicate the lockup by doing this query in SQL Query Analyzer. The results I would get are as follows:[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).Server: Msg 11, Level 16, State 1, Line 0General network error. Check your network documentation.Connection BrokenI did a lot of research on this error and came up with nothing that would fix the problem. This is where it gets strange. To best understand the issue, I have bullet-pointed what I’ve tried and what works and what doesn’t. • This is not an issue of to many records because this table only has 105 records in it.• I can run the query just fine locally from the Win2003 server. I only have a problem running the query remotely.• I can run the same query remotely on several other tables in the same database without any problems.• I can run the same query using a different database on the same server and get records from the County table just fine both locally and remotely.• I hooked up a second computer on the same network (inside the firewall) running SQL 2000 (No MSDE Installed) and was able to run the query just fine locally.• I moved the database to the second computer and changed my router to point to the second computer and I had the exact same problem of not being able to run the query remotely.• I deleted the table completely and recreated it but still was unable to run the query remotely.• I created and new copy of the database (we have a base database we start from for new clients) and imported all of the data from the client database (with the exception that I did not import the county table, I entered it manually) and I had the exact same problem of not being able to run the query remotely.• I took the second computer back to my house with the same setup changed the firewall at my house to point to this second computer and I was able to run the query both locally and remotely.• The most logical conclusion is that there is a problem with the firewall. We are using a Sonicwall SoHo Tzw. I’ve checked and rechecked the firewall settings and did a lot of research on this but did not find any reason it would be blocking just one table in one database.By this point I’m getting pretty desperate and am trying anything. • I found out that if I did a “Select Top 8 From County”, it would work remotely but no more records than that.• I found out that if I selected all columns but the last column (which is a VarChar(80)), the query worked remotely.• I found out that if I changed the last columns values from <NULL> to “”, then the query would work remotely.• I found out if I left the last column as <NULL> but changed the “State_ID” column (which is an Int) value from 16 to say 20, then the query would run remotely.Needless to say, this is a strange one. Remember in all of this testing, I rebuilt the table several times and re-entered the data several times. None of this makes sense to me. Any suggestions would be appreciated. |
|
|
|
|
|
|
|
Absolute Perplexing Issue with a Simple Query