starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 17:26:03 +03:00

[GH-ISSUE #11824] MSSQL 2025 fails install on multiple nodes and version installs #2490

New issue

Closed

opened 2026-02-26 12:52:37 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 12:52:37 +03:00

Owner

Originally created by @connornz on GitHub (Feb 12, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11824

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

SQL Server 2025

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/sqlserver2025.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.04

📈 Which Proxmox version are you on?

Proxmox Virtual Environment 9.1.4

📝 Provide a clear and concise description of the issue.

Script completes, but LXC OS / Install fails. Tried on multiple nodes as I thought it was processor related. i5-1235U and dual Xeon 2697v4's
Tried both advanced and default settings
Tried running setup selecting Express, Enterprise developer and Standard developer - all fail.

🔄 Steps to reproduce the issue.

Step 1: Run Script
Step 2: Select Default Settings
Step 3: Press Y for MSSQL Setup Now
Step 4: Enter Administrator/SA password
Step 5: Select Version of MSSQL to install. 2,3 or 4
MSSQL Errors here.

❌ Paste the full error output (if available).

/ // __ \ / / / / ______ _____ _____ | \ / __ _ \ / /
_ / / / / / / _ / _ / / | / / _ / / __/ // / / // // \
/ / // / / / / / __/ / | |/ / __/ / / __// // / __// /
//__/___/ //___// |/_// //_/___/_____/

⚙️ Using Default Settings on node pve
💡 PVE Version 9.1.5 (Kernel: 6.17.4-2-pve)
🆔 Container ID: 120
🖥️ Operating System: ubuntu (24.04)
📦 Container Type: Privileged
💾 Disk Size: 10 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🚀 Creating a SQL Server 2025 LXC using the above default settings

✔️ Storage local (Free: 16.8GB Used: 72.5GB) [Template]
no such logical volume samsung-nvme/samsung-nvme
no such logical volume hynix-nvme/hynix-nvme
no such logical volume nvme/nvme
✔️ Storage sandisk-ssd (Free: 219.0GB Used: 0.0B) [Container]
✔️ Storage 'sandisk-ssd' (lvmthin) validated
✔️ Template storage 'local' validated
✔️ Cluster is quorate
✔️ Template search completed
✔️ Template ubuntu-24.04-standard_24.04-2_amd64.tar.zst [local]
✔️ LXC Container 120 was successfully created.
✔️ USB passthrough configured
✔️ Started LXC Container
✔️ Network in LXC is reachable (ping)
✔️ Customized LXC Container
✔️ Set up Container OS
✔️ Network Connected: 172.16.2.13
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
✔️ Updated Container OS
✔️ Installed Dependencies
✔️ Repository configured
✔️ Installed SQL Server 2025
✔️ Installed SQL Server Tools
Do you want to run the SQL Server setup now? (Later is also possible) <y/N>y
Choose an edition of SQL Server:

Evaluation (free, no production use rights, 180-day limit)
Enterprise Developer (free, no production use rights)
Standard Developer (free, no production use rights)
Express (free)
Standard (PAID)
Enterprise (PAID) - CPU core utilization restricted to 20 physical/40 hyperthreaded
Enterprise Core (PAID) - CPU core utilization up to Operating System Maximum
I bought a license through a retail sales channel and have a product key to enter.
Standard (Billed through Azure) - Use pay-as-you-go billing through Azure.
Enterprise Core (Billed through Azure) - Use pay-as-you-go billing through Azure.

Details about editions can be found at
https://go.microsoft.com/fwlink/?LinkId=2109348

Use of PAID editions of this software requires separate licensing through a
Microsoft Volume Licensing program.
By choosing a PAID edition, you are verifying that you have the appropriate
number of licenses in place to install and run this software.
By choosing an edition billed Pay-As-You-Go through Azure, you are verifying
that the server and SQL Server will be connected to Azure by installing the
management agent and Azure extension for SQL Server.

Enter your edition(1-10): 2
The license terms for this product can be found in
/usr/share/doc/mssql-server or downloaded from: https://aka.ms/useterms

The privacy statement can be viewed at:
https://go.microsoft.com/fwlink/?LinkId=853010

Enter the SQL Server system administrator password:
Confirm the SQL Server system administrator password:
Configuring SQL Server...

This program has encountered a fatal error and cannot continue running at Thu Feb 12 21:17:47 2026
The following diagnostic information is available:

     Reason: 0x00000004
    Message: ASSERT: Expression=(NT_SUCCESS(status)) File=LibOS\Windows\Kernel\DRtl\sqlpalstubs.cpp Line=886
Stack Trace:
             file://package6/windows/system32/sqlpal.dll+0x000000000000A5D2
             file://package6/windows/system32/sqlpal.dll+0x0000000000009905
             file://package6/windows/system32/sqlpal.dll+0x00000000000055A4
             file://package6/windows/system32/sqlpal.dll+0x0000000000005432
             file://package6/windows/system32/sqlpal.dll+0x00000000000E8744
             file://package6/windows/system32/sqlpal.dll+0x00000000000AA8F1
             file://package6/windows/system32/sqlpal.dll+0x00000000000AAFA4
             file://package6/windows/system32/sqlpal.dll+0x00000000000AA4EA
             file://package6/windows/system32/sqlpal.dll+0x00000000000AC910
             file://package6/windows/system32/sqlpal.dll+0x0000000000006FBC
             file://package6/windows/system32/sqlpal.dll+0x00000000000065AE
             file://package6/windows/system32/sqlpal.dll+0x0000000000006A49
             file://package6/windows/system32/sqlpal.dll+0x0000000000121AF1
    Process: 9949 - sqlservr
     Thread: 9954 (application thread 0x8)
Instance Id: 42c44932-3e96-4e4a-9315-aaea04505c68
   Crash Id: 5daaf78f-30ce-4dd2-8b0b-4ade7d50c81c
Build stamp: 846dddf78aedca3a066aae70e12be8f80ab4629a86b2cd7650d2fb8ff2b4adf6

Distribution: Ubuntu 24.04.4 LTS
Processors: 2
Total Memory: 270301515776 bytes
Timestamp: Thu Feb 12 21:17:47 2026
Last errno: 22
Last errno text: Invalid argument
Capturing a dump of 9949
FAILED to capture a dump. Details in paldumper log.
Executing: /opt/mssql/bin/handle-crash.sh with parameters
handle-crash.sh
/opt/mssql/bin/sqlservr
9949
/opt/mssql/bin
/var/opt/mssql/log/

 42c44932-3e96-4e4a-9315-aaea04505c68
 5daaf78f-30ce-4dd2-8b0b-4ade7d50c81c

Ubuntu 24.04.4 LTS
Capturing core dump and information to /var/opt/mssql/log...
Capture info: Kernel Version
Capture info: OS release
Capture info: System memory information
Capture info: Command line
Capture info: Start Time
Capture info: Process limits
Capture info: Thread list
Capture info: Processor topology
Capture info: Process mounts
Capture info: Process statistics
Capture info: Process status
Capture info: Process memory maps
Capture info: Process memory maps (detailed)
Capture info: Core Dump filter
Capture info: Process CGroup information
cat: /sys/fs/cgroup/user.slice/user-999.slice/session-970.scope/memory.reclaim: Permission denied
Capture info: Process scheduler information
Capture info: Process list
Capture info: Process handle information
Capture info: Process environment variables
Capture info: System package list (dpkg)
dmesg: read kernel buffer failed: Operation not permitted
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
No journal files were opened due to insufficient permissions.
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
No journal files were opened due to insufficient permissions.
tail: cannot open '/var/log/syslog' for reading: Permission denied
Capture info: Current application configuration
Thu Feb 12 21:17:48 AEDT 2026 Capturing program information
Thu Feb 12 21:17:48 AEDT 2026 Attempting to capture a dump with paldumper for pid 9949
WARNING: Capture attempt failure detected
Attempting to capture a filtered dump with paldumper for pid 9949
WARNING: Attempt to capture dump failed. Reference /var/opt/mssql/log/core.sqlservr.9949.temp/log/paldumper-debug.log for details
Thu Feb 12 21:17:48 AEDT 2026 Attempting to capture a dump with gdb
WARNING: Unable to capture crash dump with GDB. You may need to
allow ptrace debugging, enable the CAP_SYS_PTRACE capability, or
run as root. See log in: /var/opt/mssql/log/core.sqlservr.9949.temp/log/gdb.log
Thu Feb 12 21:17:48 AEDT 2026 Capturing program binaries
Thu Feb 12 21:17:48 AEDT 2026 Compressing the dump files
Core dump and information are being compressed (bzip2) in
the background. When complete, they can be found in the following location:
/var/opt/mssql/log/core.sqlservr.02_12_2026_21_17_47.9949.tbz2
Initial setup of Microsoft SQL Server failed. Please consult the ERRORLOG
in /var/opt/mssql/log for more information.
✖️ in line 51: exit code 1 (General error / Operation not permitted): while executing command /opt/mssql/bin/mssql-conf setup
--- Last 20 lines of silent log ---
Selecting previously unselected package mssql-tools18.
Preparing to unpack .../8-mssql-tools18_18.6.1.1-1_amd64.deb ...
Unpacking mssql-tools18 (18.6.1.1-1) ...
Selecting previously unselected package unixodbc-dev:amd64.
Preparing to unpack .../9-unixodbc-dev_2.3.12-1ubuntu0.24.04.1_amd64.deb ...
Unpacking unixodbc-dev:amd64 (2.3.12-1ubuntu0.24.04.1) ...
Setting up unixodbc-common (2.3.12-1ubuntu0.24.04.1) ...
Setting up libltdl7:amd64 (2.4.7-7build1) ...
Setting up libodbc2:amd64 (2.3.12-1ubuntu0.24.04.1) ...
Setting up libodbccr2:amd64 (2.3.12-1ubuntu0.24.04.1) ...
Setting up libodbcinst2:amd64 (2.3.12-1ubuntu0.24.04.1) ...
Setting up odbcinst (2.3.12-1ubuntu0.24.04.1) ...
Setting up unixodbc (2.3.12-1ubuntu0.24.04.1) ...
Setting up msodbcsql18 (18.6.1.1-1) ...
odbcinst: Driver installed. Usage count increased to 1.
Target directory is /etc
Setting up unixodbc-dev:amd64 (2.3.12-1ubuntu0.24.04.1) ...
Setting up mssql-tools18 (18.6.1.1-1) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.7) ...

📋 Log saved to: /root/.install-355c2766.log
✖️ Installation failed in container 120 (exit code: 1)

✔ Installation log: /tmp/install-lxc-120-355c2766.log

Remove broken container 120? (Y/n) [auto-remove in 60s]:
No response - auto-removing container
Removing container 120
✔️ Container 120 removed

info.log

🖼️ Additional context (optional).

No response

Originally created by @connornz on GitHub (Feb 12, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11824 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? SQL Server 2025 ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/sqlserver2025.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.04 ### 📈 Which Proxmox version are you on? Proxmox Virtual Environment 9.1.4 ### 📝 Provide a clear and concise description of the issue. Script completes, but LXC OS / Install fails. Tried on multiple nodes as I thought it was processor related. i5-1235U and dual Xeon 2697v4's Tried both advanced and default settings Tried running setup selecting Express, Enterprise developer and Standard developer - all fail. ### 🔄 Steps to reproduce the issue. Step 1: Run Script Step 2: Select Default Settings Step 3: Press Y for MSSQL Setup Now Step 4: Enter Administrator/SA password Step 5: Select Version of MSSQL to install. 2,3 or 4 MSSQL Errors here. ### ❌ Paste the full error output (if available). / ___// __ \ / / / ___/___ ______ _____ _____ |__ \ / __ \__ \ / ____/ \__ \/ / / / / / \__ \/ _ \/ ___/ | / / _ \/ ___/ __/ // / / /_/ //___ \ ___/ / /_/ / / /___ ___/ / __/ / | |/ / __/ / / __// /_/ / __/____/ / /____/\___\_\/_____/ /____/\___/_/ |___/\___/_/ /____/\____/____/_____/ ⚙️ Using Default Settings on node pve 💡 PVE Version 9.1.5 (Kernel: 6.17.4-2-pve) 🆔 Container ID: 120 🖥️ Operating System: ubuntu (24.04) 📦 Container Type: Privileged 💾 Disk Size: 10 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🚀 Creating a SQL Server 2025 LXC using the above default settings ✔️ Storage local (Free: 16.8GB Used: 72.5GB) [Template] no such logical volume samsung-nvme/samsung-nvme no such logical volume hynix-nvme/hynix-nvme no such logical volume nvme/nvme ✔️ Storage sandisk-ssd (Free: 219.0GB Used: 0.0B) [Container] ✔️ Storage 'sandisk-ssd' (lvmthin) validated ✔️ Template storage 'local' validated ✔️ Cluster is quorate ✔️ Template search completed ✔️ Template ubuntu-24.04-standard_24.04-2_amd64.tar.zst [local] ✔️ LXC Container 120 was successfully created. ✔️ USB passthrough configured ✔️ Started LXC Container ✔️ Network in LXC is reachable (ping) ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 172.16.2.13 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS ✔️ Installed Dependencies ✔️ Repository configured ✔️ Installed SQL Server 2025 ✔️ Installed SQL Server Tools Do you want to run the SQL Server setup now? (Later is also possible) <y/N>y Choose an edition of SQL Server: 1) Evaluation (free, no production use rights, 180-day limit) 2) Enterprise Developer (free, no production use rights) 3) Standard Developer (free, no production use rights) 4) Express (free) 5) Standard (PAID) 6) Enterprise (PAID) - CPU core utilization restricted to 20 physical/40 hyperthreaded 7) Enterprise Core (PAID) - CPU core utilization up to Operating System Maximum 8) I bought a license through a retail sales channel and have a product key to enter. 9) Standard (Billed through Azure) - Use pay-as-you-go billing through Azure. 10) Enterprise Core (Billed through Azure) - Use pay-as-you-go billing through Azure. Details about editions can be found at https://go.microsoft.com/fwlink/?LinkId=2109348 Use of PAID editions of this software requires separate licensing through a Microsoft Volume Licensing program. By choosing a PAID edition, you are verifying that you have the appropriate number of licenses in place to install and run this software. By choosing an edition billed Pay-As-You-Go through Azure, you are verifying that the server and SQL Server will be connected to Azure by installing the management agent and Azure extension for SQL Server. Enter your edition(1-10): 2 The license terms for this product can be found in /usr/share/doc/mssql-server or downloaded from: https://aka.ms/useterms The privacy statement can be viewed at: https://go.microsoft.com/fwlink/?LinkId=853010 Enter the SQL Server system administrator password: Confirm the SQL Server system administrator password: Configuring SQL Server... This program has encountered a fatal error and cannot continue running at Thu Feb 12 21:17:47 2026 The following diagnostic information is available: Reason: 0x00000004 Message: ASSERT: Expression=(NT_SUCCESS(status)) File=LibOS\Windows\Kernel\DRtl\sqlpalstubs.cpp Line=886 Stack Trace: file://package6/windows/system32/sqlpal.dll+0x000000000000A5D2 file://package6/windows/system32/sqlpal.dll+0x0000000000009905 file://package6/windows/system32/sqlpal.dll+0x00000000000055A4 file://package6/windows/system32/sqlpal.dll+0x0000000000005432 file://package6/windows/system32/sqlpal.dll+0x00000000000E8744 file://package6/windows/system32/sqlpal.dll+0x00000000000AA8F1 file://package6/windows/system32/sqlpal.dll+0x00000000000AAFA4 file://package6/windows/system32/sqlpal.dll+0x00000000000AA4EA file://package6/windows/system32/sqlpal.dll+0x00000000000AC910 file://package6/windows/system32/sqlpal.dll+0x0000000000006FBC file://package6/windows/system32/sqlpal.dll+0x00000000000065AE file://package6/windows/system32/sqlpal.dll+0x0000000000006A49 file://package6/windows/system32/sqlpal.dll+0x0000000000121AF1 Process: 9949 - sqlservr Thread: 9954 (application thread 0x8) Instance Id: 42c44932-3e96-4e4a-9315-aaea04505c68 Crash Id: 5daaf78f-30ce-4dd2-8b0b-4ade7d50c81c Build stamp: 846dddf78aedca3a066aae70e12be8f80ab4629a86b2cd7650d2fb8ff2b4adf6 Distribution: Ubuntu 24.04.4 LTS Processors: 2 Total Memory: 270301515776 bytes Timestamp: Thu Feb 12 21:17:47 2026 Last errno: 22 Last errno text: Invalid argument Capturing a dump of 9949 FAILED to capture a dump. Details in paldumper log. Executing: /opt/mssql/bin/handle-crash.sh with parameters handle-crash.sh /opt/mssql/bin/sqlservr 9949 /opt/mssql/bin /var/opt/mssql/log/ 42c44932-3e96-4e4a-9315-aaea04505c68 5daaf78f-30ce-4dd2-8b0b-4ade7d50c81c Ubuntu 24.04.4 LTS Capturing core dump and information to /var/opt/mssql/log... Capture info: Kernel Version Capture info: OS release Capture info: System memory information Capture info: Command line Capture info: Start Time Capture info: Process limits Capture info: Thread list Capture info: Processor topology Capture info: Process mounts Capture info: Process statistics Capture info: Process status Capture info: Process memory maps Capture info: Process memory maps (detailed) Capture info: Core Dump filter Capture info: Process CGroup information cat: /sys/fs/cgroup/user.slice/user-999.slice/session-970.scope/memory.reclaim: Permission denied Capture info: Process scheduler information Capture info: Process list Capture info: Process handle information Capture info: Process environment variables Capture info: System package list (dpkg) dmesg: read kernel buffer failed: Operation not permitted Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. tail: cannot open '/var/log/syslog' for reading: Permission denied Capture info: Current application configuration Thu Feb 12 21:17:48 AEDT 2026 Capturing program information Thu Feb 12 21:17:48 AEDT 2026 Attempting to capture a dump with paldumper for pid 9949 WARNING: Capture attempt failure detected Attempting to capture a filtered dump with paldumper for pid 9949 WARNING: Attempt to capture dump failed. Reference /var/opt/mssql/log/core.sqlservr.9949.temp/log/paldumper-debug.log for details Thu Feb 12 21:17:48 AEDT 2026 Attempting to capture a dump with gdb WARNING: Unable to capture crash dump with GDB. You may need to allow ptrace debugging, enable the CAP_SYS_PTRACE capability, or run as root. See log in: /var/opt/mssql/log/core.sqlservr.9949.temp/log/gdb.log Thu Feb 12 21:17:48 AEDT 2026 Capturing program binaries Thu Feb 12 21:17:48 AEDT 2026 Compressing the dump files Core dump and information are being compressed (bzip2) in the background. When complete, they can be found in the following location: /var/opt/mssql/log/core.sqlservr.02_12_2026_21_17_47.9949.tbz2 Initial setup of Microsoft SQL Server failed. Please consult the ERRORLOG in /var/opt/mssql/log for more information. ✖️ in line 51: exit code 1 (General error / Operation not permitted): while executing command /opt/mssql/bin/mssql-conf setup --- Last 20 lines of silent log --- Selecting previously unselected package mssql-tools18. Preparing to unpack .../8-mssql-tools18_18.6.1.1-1_amd64.deb ... Unpacking mssql-tools18 (18.6.1.1-1) ... Selecting previously unselected package unixodbc-dev:amd64. Preparing to unpack .../9-unixodbc-dev_2.3.12-1ubuntu0.24.04.1_amd64.deb ... Unpacking unixodbc-dev:amd64 (2.3.12-1ubuntu0.24.04.1) ... Setting up unixodbc-common (2.3.12-1ubuntu0.24.04.1) ... Setting up libltdl7:amd64 (2.4.7-7build1) ... Setting up libodbc2:amd64 (2.3.12-1ubuntu0.24.04.1) ... Setting up libodbccr2:amd64 (2.3.12-1ubuntu0.24.04.1) ... Setting up libodbcinst2:amd64 (2.3.12-1ubuntu0.24.04.1) ... Setting up odbcinst (2.3.12-1ubuntu0.24.04.1) ... Setting up unixodbc (2.3.12-1ubuntu0.24.04.1) ... Setting up msodbcsql18 (18.6.1.1-1) ... odbcinst: Driver installed. Usage count increased to 1. Target directory is /etc Setting up unixodbc-dev:amd64 (2.3.12-1ubuntu0.24.04.1) ... Setting up mssql-tools18 (18.6.1.1-1) ... Processing triggers for man-db (2.12.0-4build2) ... Processing triggers for libc-bin (2.39-0ubuntu8.7) ... ----------------------------------- 📋 Log saved to: /root/.install-355c2766.log ✖️ Installation failed in container 120 (exit code: 1) ✔ Installation log: /tmp/install-lxc-120-355c2766.log Remove broken container 120? (Y/n) [auto-remove in 60s]: No response - auto-removing container Removing container 120 ✔️ Container 120 removed [info.log](https://github.com/user-attachments/files/25258462/info.log) ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:52:37 +03:00

closed this issue
added the
external
label

kerem commented

2026-02-26 12:52:37 +03:00

Author

Owner

@MickLesk commented on GitHub (Feb 12, 2026):

This is a Linux Kernel 6.17 incompatibility with SQL Server's SQLPAL (Platform Abstraction Layer).

The crash occurs in sqlpalstubs.cpp:886 with errno 22 (Invalid argument) - this happens before any SQL Server code runs.

Microsoft sleep, like every day. This requires a fix from Microsoft. The script itself works correctly on supported kernel versions.

@MickLesk commented on GitHub (Feb 12, 2026): This is a Linux Kernel 6.17 incompatibility with SQL Server's SQLPAL (Platform Abstraction Layer). The crash occurs in sqlpalstubs.cpp:886 with errno 22 (Invalid argument) - this happens before any SQL Server code runs. Microsoft sleep, like every day. This requires a fix from Microsoft. The script itself works correctly on supported kernel versions.

kerem commented

2026-02-26 12:52:37 +03:00

Author

Owner

@MickLesk commented on GitHub (Feb 12, 2026):

This is a known Microsoft SQL Server SQLPAL incompatibility with Linux Kernel 6.x in LXC containers.

Affected: Proxmox VE 9 (all Kernel 6.17 versions)
Not affected: Proxmox VE 8 (Kernel 6.x+ - 6.11 ), VMs (any PVE version)

Workaround: Deploy SQL Server in a VM instead of LXC container.

We've added a warning to the JSON metadata. This is an upstream Microsoft issue - no fix possible on our side.

@MickLesk commented on GitHub (Feb 12, 2026): This is a **known** Microsoft SQL Server SQLPAL incompatibility with Linux Kernel 6.x in LXC containers. **Affected:** Proxmox VE 9 (all Kernel 6.17 versions) **Not affected:** Proxmox VE 8 (Kernel 6.x+ - 6.11 ), VMs (any PVE version) **Workaround:** Deploy SQL Server in a VM instead of LXC container. We've added a warning to the JSON metadata. This is an upstream Microsoft issue - no fix possible on our side. Related: [https://forum.proxmox.com/threads/proxmox-9-microsoft-sql-server-bug.162547/](vscode-file://vscode-app/c:/Users/LeskowitzMickey/AppData/Local/Programs/Microsoft%20VS%20Code/591199df40/resources/app/out/vs/code/electron-browser/workbench/workbench.html) https://github.com/community-scripts/ProxmoxVE/pull/11829

kerem referenced this issue

2026-02-26 13:34:39 +03:00

[PR #2494] [MERGED] Fix: Actual Budget, add missing .env when updating #3790

kerem referenced this issue

2026-02-26 13:34:40 +03:00

[PR #2496] [MERGED] Breaking: Actual Budget Script (HTTPS / DB Migration / New Structure) - Read Description #3792

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2490

No description provided.

Rows
Columns