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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-11-15 : 08:41:54
|
| Saleem writes "I am facing this error when ever i run some stored procedures. It seems that this error has nothing to do with the procedures. But if we run the query taken out of the procedure on qurey analyser the stored procedure starts to work. Strange!Following is the description of error as it is called from ASP page Error Type:Microsoft OLE DB Provider for SQL Server (0x80004005)[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation./writelance/Include/top.asp, line 408plzzzzzzzzzzzz helpsaleem" |
|
|
ValterBorges
Master Smack Fu Yak Hacker
1429 Posts |
|
|
redbrad0
Posting Yak Master
176 Posts |
Posted - 2005-02-11 : 09:29:55
|
| I am also having this problem and tried checking out the link posted and all it showed was someone who was asking for a answer to this. I have a web server and then a SQL Server and usually does not have any problems but have been seening lately this error coming up very random. If I refresh the page then it works fine.Any ideas?Quality Web Hosting & Designhttp://www.eznthosting.com |
 |
|
|
rcristel
Starting Member
1 Post |
Posted - 2005-07-07 : 12:48:08
|
| I'm having the same issues on win2003 standard edition server.Everything was working just fine until a day or two ago... nothing that I know of changed...It's a completely random error and it's happening for around 10 or so seconds every couple of hours.anyone else experiencing these issues? |
|
|
|
KRW
Starting Member
3 Posts |
Posted - 2005-07-19 : 12:33:30
|
| We are experiencing the same - Would like to know - SQL SErver 2000 on WIN 2003 -- when application is running on WIN 2000 server connecting via ODBC to this sql server database |
|
|
|
bhlaws
Starting Member
2 Posts |
Posted - 2006-08-16 : 10:02:44
|
| FYI, I came across a post at another site which referenced a KB article about BizTalk. I think it's the same problem. Check out http://support.microsoft.com/default.aspx?scid=kb;en-us;899599Basically, Server 2003 SP1 has a "feature" which is supposed to prevent a suspected denial of service attack. If the server is heavily used, it will mistakenly identify the valid processes as a threat and drop the packets. I'm getting this problem on one of my servers, so I'm going to implement the fix they give. I'll see if it helps. |
|
|
|
rmench
Starting Member
1 Post |
Posted - 2006-08-22 : 18:13:34
|
| How did this work our for you? What are the consequences of making this change? |
|
|
|
bhlaws
Starting Member
2 Posts |
Posted - 2006-08-25 : 15:50:45
|
| The servers have since been rebooted and I haven't had a problem yet. I also have not seen that error since then. However, since this job runs every 3 minutes, I've only got 2 days-worth of history to look at. Well, at least I can say I haven't gotten called about it yet. :> Then it again, there error happened pretty rarely anyway. To quote the renowned Kermit The Frog: "No gnus is good gnus!" |
|
|
|
|
|
|
Network Error