• API Overview
  • EBICS API
  • FinTS API
  • XS2A API
  • SEPA API
Search Results for

    Enum FinCommServiceExceptionCode

    Enumerates the possible types of failure that caused the FinCommServiceException to be thrown.

    Namespace: Subsembly.FinTS
    Assembly: Subsembly.FinTS.Core.dll
    Syntax
    public enum FinCommServiceExceptionCode

    Fields

    Name Description
    BadCommAddress

    The communication address that was passed to Connect(String, String, IFinFilter) was syntactically wrong. This exception was thrown by simply looking at the provided communication address. No attempt was made to actually establish a connection.

    BadCommAddressSuffix

    The communication address suffix that was passed to Connect(String, String, IFinFilter) was syntactically wrong. This exception was thrown by simply looking at the provided communication address. No attempt was made to actually establish a connection.

    ConnectFailure

    A connection could not be established by Connect(String, String, IFinFilter). Maybe the given communication address is wrong or the server is down. Another very common reason is that the connection is prevented by some firewall, a missing proxy configuration or required authorisation.

    ConnectionClosed

    The connection was unexpectedly closed by the server.

    ProtocolError

    Some protocol error on the transport layer (or below) occured. This is not a FinTS protocol error!

    ProxyError

    Some (protocol/communication) error while talking to a (SOCKS5) proxy server.

    Timeout

    No response was received within the given response timeout limit.

    In This Article
    Back to top Copyright 2009-2025 Subsembly GmbH