mindsdb
[Bug]: SQL Server - "Save and Continue" for SQL Server Results in Status Code 500
Short description of current behavior
When attempting to save a new SQL Server connection, I am getting the error "Uh oh! Something went wrong: Request failed with status code 500".
After entering my connection information in the Connect form, I am able to successfully test my connection - but when I attempt to save, I am merely greeted with the above information, which includes no actionable information.
I then enabled showing extensions containers in Docker Desktop, at which time I could see the actual informative error:
2025-10-01 09:21:18,422 http ERROR mindsdb.api.http.namespaces.config: An error occurred during the creation of the integration:
Traceback (most recent call last):
File "/mindsdb/./mindsdb/api/http/namespaces/config.py", line 177, in put
ca.integration_controller.add(name, engine, params)
File "/mindsdb/./mindsdb/interfaces/database/integrations.py", line 187, in add
raise ValueError(f"The name must be in lower case: {name}")
ValueError: The name must be in lower case: MyDatabaseConnection
2025-10-01 09:21:18,422 http INFO uvicorn.access: 172.19.0.1:49438 - "PUT /api/config/integrations/MyDatabaseConnection HTTP/1.1" 500
I then noticed the error is also returned as the response when viewing from the web client, though the helpful error message is not displayed:
{
"title": "Error",
"detail": "Error during config update: The name must be in lower case:MyDatabaseConnection",
"timestamp": "2025-10-01 09:18:04.357164"
}
Video or screenshots
No response
Expected behavior
For the connection to save, or for an actionable error message to be displayed - ideally, with official documentation indicating "Connection names must be lower case", if this is, indeed, a requirement.
How to reproduce the error
Initially, I attempted to save this SQL Server connection via the Docker Desktop Extension.
I then began to troubleshoot view the local web portal, where my attempt to save the valid SQL Server conneciton again failed.
Anything else?
No response
