While in Raiser's Edge Entprise SQL Server 2000 edition 7.80.1122.34, users receives "Communication link failure" at least once a day but are able to log in again immediately. No specific function or task encounters this condition. Specific errors are:"General ODBC Error: [Microsoft][ODBC SQL Server Driver]Communication link failure Native error:D" and "requery7 Run-time error'-2147211486 (B0042722)': General ODBC Error: [Microsoft][ODBC SQL Server Driver]Communication link failure Native error:0". Cases have been opened with Support with Microsoft Windows 2000 Performance Monitoring logs; also logs from XP workstation but cause of errors not found. Three users from one location have reported this problem. We have about 50 users in five different buildings. Our plans are to upgrade production to RE 7.82.1514 and FE 7.70.638 about Oct 15, 2007 but these momentary disconnects greatly disrupt production, especially when posting gifts and creating batches. I suspect SQL Server 2000. Will SQL Server 2005 solve this problem? Tips/solutions shall be appreciated. [i]--- Edited at 9/25/2007 5:09:44 PM by Fred Gaines[/i] [i]--- Edited at 9/25/2007 5:11:15 PM by Fred Gaines[/i]

Here is a suggestion: "I would imagine that it is a network connectivity issue and not connected to SQL server. It more than likely is a network congestion issue in which they are overloading a switch which would cause the SQL server to "disappear" long enough for the error to occur."

We've experienced this same problem at RCS and are fairly confident it is not a network issue. Exact same behavior as described below, so we tested this on a client connected directly to the core. Ran a ping test simultaneously. Every ping was returned in under 1ms, but received the error after a bit of inactivity in RE7. Not a perfect test, but did show a very solid network connection during the time the error occurred. We've seen the same error in EE7, by the way. Worked with Blackbaud on this for a while, and the only suggestion they had was a complete reinstall on the clients. Did this. The error seems to have largely gone away, though we do see occasional relapses. We're on SQL 2005 Standard. -Sean Dagony-Clark Riverdale Country School Bronx, NY [i]--- Edited at 9/26/2007 8:34:49 AM by Sean Dagony-Clark[/i]

I have been meaning to come in here and reply to this - and I am just getting around to doing it. I get this error constantly and I am a Patron Edge user not an RE user, RE is in my organization and connected to the same server... We have not been able to pinpoint the cause either, but it is becoming very annoying and time consuming because everytime the application disconnects from the server I have to force it to close then try to logon again... It's a great time!

We've been living with this for a while. Once we get new switches next year I'll know for sure whether that's the issue or not. RE is the worst offender for us = don't see it much with FE or PE and none of my other SQL apps here have the problem. My best guess is that certain RE objects have not been correctly closed by the programmers so the instance remains in memory.