Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4073] [FEAT]: MSSQLConnector Support additonal provider config for options.encrypt #2598

New Issue
Closed
opened 2026-02-22 18:30:23 -05:00 by yindo · 5 comments
yindo commented 2026-02-22 18:30:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @jstawski on GitHub (Jun 30, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4073

Originally assigned to: @shatfield4 on GitHub.

How are you running AnythingLLM?

Docker (remote machine)

What happened?

When the agent tries to execute any SQL statement agains the Azure SQL Server database it fails with the following log

[36m[backend] info: [AgentHandler] [debug]: @agent is attempting to call sql-get-table-schema tool
[backend] info: [AgentHandler] Using the sql-get-table-schema tool.
[backend] info: MSSQLConnector ConnectionError: Server requires encryption, set 'encrypt' config option to true.
at /app/server/node_modules/mssql/lib/tedious/connection-pool.js:85:17
at Connection.onConnect (/app/server/node_modules/tedious/lib/connection.js:838:9)
at Object.onceWrapper (node:events:632:26)
at Connection.emit (node:events:517:28)
at Connection.emit (/app/server/node_modules/tedious/lib/connection.js:959:18)
at /app/server/node_modules/tedious/lib/connection.js:2234:18
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[backend] info: [AgentHandler] sql-get-table-schema raised an error. Cannot read properties of null (reading 'close')

Are there known steps to reproduce?

  1. Turn on SQL Connector on Agent Skills
  2. Add a connection to a SQL Server hosted on Azure
  3. In the chat ask the agent to retrieve list of tables, or any prompt that will require reading from the database.
Originally created by @jstawski on GitHub (Jun 30, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4073 Originally assigned to: @shatfield4 on GitHub. ### How are you running AnythingLLM? Docker (remote machine) ### What happened? When the agent tries to execute any SQL statement agains the Azure SQL Server database it fails with the following log > [36m[backend] info: [AgentHandler] [debug]: @agent is attempting to call `sql-get-table-schema` tool [backend] info: [AgentHandler] Using the sql-get-table-schema tool. [backend] info: MSSQLConnector ConnectionError: Server requires encryption, set 'encrypt' config option to true. at /app/server/node_modules/mssql/lib/tedious/connection-pool.js:85:17 at Connection.onConnect (/app/server/node_modules/tedious/lib/connection.js:838:9) at Object.onceWrapper (node:events:632:26) at Connection.emit (node:events:517:28) at Connection.emit (/app/server/node_modules/tedious/lib/connection.js:959:18) at /app/server/node_modules/tedious/lib/connection.js:2234:18 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [backend] info: [AgentHandler] sql-get-table-schema raised an error. Cannot read properties of null (reading 'close') ### Are there known steps to reproduce? 1. Turn on SQL Connector on Agent Skills 2. Add a connection to a SQL Server hosted on Azure 3. In the chat ask the agent to retrieve list of tables, or any prompt that will require reading from the database.
yindo added the enhancementgood first issueIntegration Requestfeature request labels 2026-02-22 18:30:23 -05:00
yindo closed this issue 2026-02-22 18:30:23 -05:00
yindo commented 2026-02-22 18:30:24 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 30, 2025):

For https://github.com/Mintplex-Labs/anything-llm/blob/91e498229cc6893744ae718df3479cd742c0e2e3/server/utils/agents/aibitat/plugins/sql-agent/SQLConnectors/MSSQL.js#L19 - add a UI control to enable encrypted databases to be connected.

@timothycarambat commented on GitHub (Jun 30, 2025): For https://github.com/Mintplex-Labs/anything-llm/blob/91e498229cc6893744ae718df3479cd742c0e2e3/server/utils/agents/aibitat/plugins/sql-agent/SQLConnectors/MSSQL.js#L19 - add a UI control to enable encrypted databases to be connected.
yindo commented 2026-02-22 18:30:24 -05:00
Author
Owner
Copy Link
Copy Source

@jstawski commented on GitHub (Jul 8, 2025):

What is the process for feature requests? When do they become part of master to be released into prod? Also, what is the process of updating an existing production instance hosted in a container?

@jstawski commented on GitHub (Jul 8, 2025): What is the process for feature requests? When do they become part of master to be released into prod? Also, what is the process of updating an existing production instance hosted in a container?
yindo commented 2026-02-22 18:30:24 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 8, 2025):

What is the process for feature requests?

Typically, we do the most popular ones first. It is really at our core team discretion when it comes to that since some are higher lift than others. Some are easier and can be done with outside contributorship, like this one. Which is pretty low lift. I have @shatfield4 assigned to this, who is core team and he will get to it as he works through his backlog. He works on a lot of things and knocking out feature requests in this repo isnt his only job.

When do they become part of master to be released into prod?

When the issue is closed via an assoicated Pull Request

Also, what is the process of updating an existing production instance hosted in a container?

This is not what someone should do to make changes since on container reboot, your changes would vanish. You would need to create your own image on a fork. That is standard practice for getting changes in Docker outside of a main release. Otherwise, you could run the app in a non-containerized way (hard if not technical!) and you can then have your changes very quickly - still done on a fork

@timothycarambat commented on GitHub (Jul 8, 2025): > What is the process for feature requests? Typically, we do the most popular ones first. It is really at our core team discretion when it comes to that since some are higher lift than others. Some are easier and can be done with outside contributorship, like this one. Which is pretty low lift. I have @shatfield4 assigned to this, who is core team and he will get to it as he works through his backlog. He works on a lot of things and knocking out feature requests in this repo isnt his only job. > When do they become part of master to be released into prod? When the issue is closed via an assoicated Pull Request > Also, what is the process of updating an existing production instance hosted in a container? This is not what someone should do to make changes since on container reboot, your changes would vanish. You would need to create your own image on a fork. That is standard practice for getting changes in Docker outside of a main release. Otherwise, you could run the app in a non-containerized way (hard if not technical!) and you can then have your changes very quickly - still done on a fork
yindo commented 2026-02-22 18:30:24 -05:00
Author
Owner
Copy Link
Copy Source

@jstawski commented on GitHub (Jul 8, 2025):

For the last question, I meant... how do I update an instance of AnythingLLM once a new version is available. If the container is pointing to latest is that enough?

In other words, I want to know how I would upgrade my instance of AnythingLLM in order to get this feature once it makes it into the next version.

@jstawski commented on GitHub (Jul 8, 2025): For the last question, I meant... how do I update an instance of AnythingLLM once a new version is available. If the container is pointing to `latest` is that enough? In other words, I want to know how I would upgrade my instance of AnythingLLM in order to get this feature once it makes it into the next version.
yindo commented 2026-02-22 18:30:24 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 9, 2025):

Oh, then yes - provided you ran the official command then you have persistent storage. All you would do is just run docker pull mintplexlabs/anythingllm and then re run the above linked command and all data and such will carry over as updates roll out

@timothycarambat commented on GitHub (Jul 9, 2025): Oh, then yes - provided you [ran the official command](https://docs.anythingllm.com/installation-docker/quickstart) then you have persistent storage. All you would do is just run `docker pull mintplexlabs/anythingllm` and then re run the above linked command and all data and such will carry over as updates roll out
yindo changed title from [FEAT]: `MSSQLConnector` Support additonal provider config for `options.encrypt` to [GH-ISSUE #4073] [FEAT]: `MSSQLConnector` Support additonal provider config for `options.encrypt` 2026-06-05 14:47:28 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label Integration Request enhancement feature request good first issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2598
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?