Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

bulkcopy PyCore login is closed by SQL Server 2019 while ODBC and Go clients succeed (1.14.0)

Geschlossen
  • Stimmt etwas nicht?
#750 4 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

@bewithgaurav arbeitet bereits daran.

Seit 10.9.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

area: bulk-copy bug triage done
Describe the bug

cursor.bulkcopy() fails while opening its separate native/PyCore connection, although the normal mssql_python.connect() connection succeeds with the same server, database, SQL login, encryption settings, and process.

The failure occurs before destination metadata is read or any rows are sent. It reproduces with both a base table and a view, and even with an empty iterator.

Exception message:
RuntimeError: Failed to connect to SQL Server: Protocol Error: Failed to receive token during login response parsing.

Relevant filtered native TDS trace:
ERROR mssql_tds::message::login: Failed to receive token during login response parsing. Error: ConnectionClosed("Connection closed by server while reading TDS packet header")
DEBUG mssql_tds::connection_provider::tds_connection_provider: Connection attempt failed: Protocol Error: Failed to receive token during login response parsing.
ERROR mssql_py_core::connection: Failed to connect to SQL Server: Protocol Error: Failed to receive token during login response parsing.

This resembles #600, but the trace is different from the DatabaseMirroringPartner UnimplementedFeature fixed by microsoft/mssql-rs#69. This server reports SERVERPROPERTY('IsHadrEnabled') = 0; sys.database_mirroring has no partner or mirroring state for either master or the target database.

To reproduce

The following is the complete minimal reproduction. It creates and cleans up a small table through the working ODBC connection. Substitute environment variables for a SQL Server 2019 instance and SQL-authenticated test account with DDL permissions.

import os

import mssql_python


def braced(value: str) -> str:
    return "{" + value.replace("}", "}}") + "}"


server = os.environ["MSSQL_TEST_SERVER"]
database = os.environ["MSSQL_TEST_DATABASE"]
username = os.environ["MSSQL_TEST_USERNAME"]
password = os.environ["MSSQL_TEST_PASSWORD"]

connection_string = ";".join(
    (
        f"SERVER={braced(server)}",
        f"DATABASE={braced(database)}",
        f"UID={braced(username)}",
        f"PWD={braced(password)}",
        "Encrypt=yes",
        "TrustServerCertificate=yes",
        "",
    )
)

connection = mssql_python.connect(connection_string, timeout=20)
cursor = connection.cursor()

try:
    cursor.execute("SELECT @@VERSION, DB_NAME(), ORIGINAL_LOGIN()")
    print(tuple(cursor.fetchone()))  # succeeds

    cursor.execute("DROP TABLE IF EXISTS dbo.mssql_python_bulkcopy_login_repro")
    cursor.execute(
        "CREATE TABLE dbo.mssql_python_bulkcopy_login_repro (id int NOT NULL)"
    )
    connection.commit()

    # Fails while PyCore opens its separate connection. The same failure occurs
    # with [(1,)] and with an existing view as destination.
    print(
        cursor.bulkcopy(
            "dbo.mssql_python_bulkcopy_login_repro",
            iter(()),
            timeout=10,
        )
    )
finally:
    cursor.execute("DROP TABLE IF EXISTS dbo.mssql_python_bulkcopy_login_repro")
    connection.commit()
    cursor.close()
    connection.close()

Also reproduced with these variations:

  • SERVER=host
  • SERVER=host,1433
  • SERVER=tcp:host,1433
  • connecting to the target database and using a two-part destination name
  • connecting to master and using a fully qualified three-part destination name
  • fire_triggers=False and fire_triggers=True
  • base table and view destinations

Independent controls using the same server and SQL account all succeed:

  • normal mssql_python.connect() plus SELECT
  • ODBC sqlcmd 18.6
  • Go sqlcmd 1.10.0
  • ODBC bcp 18.6 initialization against the same table and view (0 rows copied, exit code 0)

All clients connect to the same explicit TCP port 1433 with encryption enabled and the development certificate trusted.

Expected behavior

cursor.bulkcopy() should establish its native connection and bulk copy the rows when the normal driver connection and other TDS/BCP clients can connect using the same endpoint and credentials.

If the server closes the login connection, the driver should ideally preserve enough diagnostic context to identify the rejected login feature or packet.

Further technical details

Python version: 3.12.11
mssql-python version: 1.14.0
Bundled mssql-python-odbc version: 18.6.2.1
SQL Server version: SQL Server 2019 Standard, 15.0.4430.1
Operating system: macOS 26.5.2, arm64

Additional context

  • The target server is reachable and remains available throughout the tests.
  • There is no separate Bulk Copy port; all successful and failing clients use TCP 1433.
  • Encrypt=yes;TrustServerCertificate=yes is explicitly present, so this does not appear to be the already-fixed connection-parameter forwarding problem from #501.
  • No credentials, hostnames, or packet contents are included in this report.
Vorherrschende Sprache
Python
Sterne
478
Forks
62
Ø Merge
3 T. 19 Min.
Gemergte PRs (30 T.)
28

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/mssql-python

Alle Issues in microsoft/mssql-python

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.