Welcome to Forums Sign in | Join | Help | Forums
in Search


Communication Link Failures in GrantedGE, Raiser's Edge and Financial Edge

Last post 07-16-2009 8:28 AM by Sean Finn. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 07-14-2009 2:15 PM

    • Rachel Adkins
    • Top 500 Contributor
    • User Since: 2006
    • Posts 24
    • Organization: The Community Foundation of Louisville
    • Products:  Blackbaud NetCommunity, The Financial Edge, The Raiser's Edge

    Communication Link Failures in GrantedGE, Raiser's Edge and Financial Edge

    We have recently started receiving the following error message in GrantedGE, Raiser's Edge and Financial Edge:

    General ODBC Error: [Microsoft][ODBC SQL Server Driver]Communication link failure

    Native error: 0

     We did not notice these errors until after installing Kaskpersky Anti-Virus. After we shut down and restart the program it is okay for a while, but locks up again. Also, when one person in the office locks up, everyone then does.

     Has anyone else experienced this issue? Any suggestions?

     Thanks!

    We /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;}

  • 07-16-2009 8:28 AM In reply to

    Re: Communication Link Failures in GrantedGE, Raiser's Edge and Financial Edge

     Hi Rachel,

    Unfortunately, the error you reference is a bit generic in nature.  It typically means that something caused the program to stop talking with the database server or that the database server stopped working momentarily.  The causes can range from bad network hardware to software (such as Kaskpersky blocking/halting connections).  Since this is happening with all users take a close look at your SQL server and attempt relaxing some anti-virus settings.  If it's a 2003 server, please also see:

    http://support.microsoft.com/kb/945977 (disable the TCP Chimney on the SQL Server)

    However, there may be other issues between the server and workstations.  Some other steps to try can be found in our Knowledgebase (especially if this seems to happen after users come back from lunch and left the software open and connected):

    http://www.blackbaud.com/esupport/esupport.asp?resource=&number=0&id=BB113617


    Hope this helps,

    -Sean

     

Page 1 of 1 (2 items)