Re: Strange Error?

From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 10/26/05

  • Next message: Omran Abdurrahman: "users" 
    Date: Wed, 26 Oct 2005 13:46:27 -0600

    Is the application using the JDBC driver? I would guess so
    as that's typically when this error comes up.
    Are you using the latest version, service pack version of
    the driver JDBC Service Pack 3?

    -Sue

    On Tue, 25 Oct 2005 13:08:29 +0200, "Miha"
    <miha.bernik@email.si> wrote:

    >Hi
    >
    >After installing SP4 on our company SQL200 Standard Server, we get the
    >following error on all client computers (WinXP,Win2000) that are using our
    >local apllication that is accessing sql database
    >What could be the problem? No settings were changed, only SP4 was installed.
    >Any help will be appreciated
    >Regards
    >Miha
    >
    >Socket Error # 10054
    >Socket error (#10054): Connection reset by peer.
    >
    >Analyse & Solutions: An existing connection was forcibly closed by the
    >remote host. This normally results if the peer application on the remote
    >host is suddenly stopped, the host is rebooted, the host or remote network
    >interface is disabled, or the remote host uses a hard close (see setsockopt
    >for more information on the SO_LINGER option on the remote socket). This
    >error may also result if a connection was broken due to keep-alive activity
    >detecting a failure while one or more operations are in progress. Operations
    >that were in progress fail with WSAENETRESET. Subsequent operations fail
    >with WSAECONNRESET.
    >

  • Next message: Omran Abdurrahman: "users"

    Relevant Pages