# Virtualmin cannot update msodbcsql17

**URL:** <https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248>\
**Category:** Virtualmin\
**Created:** [August 27, 2020, 11:18am UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248 "2020-08-27T11:18:51Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rory\_Bremner1](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/a3d4f5/32.png) [@Rory\_Bremner1](https://forum.virtualmin.com/u/Rory_Bremner1)\
**Post date:** [August 27, 2020, 11:18am UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/1 "2020-08-27T11:18:52Z")

</div>

After hundreds of updates I have encountered an update which cannot be performed:  
‘ERROR: The EULA was not accepted. Installation aborted.’

My system is fully updated otherwise.  
Maybe you can help?

| Package name | msodbcsql17 |
| --- | --- |
| Update system | APT |
| Package description | amd64 ODBC Driver for Microsoft® SQL Server® |
| Current state | New version 17.6.1.1-1 |
| Installed version | 17.5.2.1-1 |
| Available version | 17.6.1.1-1 |
| Installation source | Bionic |

This is what I get when I click the update button in Virtualmin:

Now updating msodbcsql17 …  
Installing package(s) with command apt-get -y install msodbcsql17 …  
Reading package lists…  
Building dependency tree…  
Reading state information…  
The following packages will be upgraded:  
msodbcsql17  
Preconfiguring packages …  
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.  
Need to get 0 B/743 kB of archives.  
After this operation, 0 B of additional disk space will be used.  
(Reading database …  
(Reading database … 5%  
(Reading database … 10%  
(Reading database … 15%  
(Reading database … 20%  
(Reading database … 25%  
(Reading database … 30%  
(Reading database … 35%  
(Reading database … 40%  
(Reading database … 45%  
(Reading database … 50%  
(Reading database … 55%  
(Reading database … 60%  
(Reading database … 65%  
(Reading database … 70%  
(Reading database … 75%  
(Reading database … 80%  
(Reading database … 85%  
(Reading database … 90%  
(Reading database … 95%  
(Reading database … 100%  
(Reading database … 228165 files and directories currently installed.)  
Preparing to unpack …/msodbcsql17\_17.6.1.1-1\_amd64.deb …  
ERROR: The EULA was not accepted. Installation aborted.  
dpkg: error processing archive /var/cache/apt/archives/msodbcsql17\_17.6.1.1-1\_amd64.deb (–unpack):  
new msodbcsql17 package pre-installation script subprocess returned error exit status 1  
Errors were encountered while processing:  
/var/cache/apt/archives/msodbcsql17\_17.6.1.1-1\_amd64.deb  
[Rootkit Hunter version 1.4.6]  
File updated: searched for 181 files, found 149  
E: Sub-process /usr/bin/dpkg returned an error code (1)  
… install failed!

---

<div class="post-metadata">

**Author:** ![DrCarsonBeckett](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/drcarsonbeckett/32/650_2.png) [@DrCarsonBeckett](https://forum.virtualmin.com/u/DrCarsonBeckett)\
**Post date:** [August 27, 2020, 6:37pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/2 "2020-08-27T18:37:08Z")

</div>

> [@Rory\_Bremner1](#):
>
> ERROR: The EULA was not accepted. Installation aborted.

I guess thats your problem. After that line, you see the notice about pre-installation. And the EULA is a part of the pre-installation.  
Try to update it through direct SSH.

---

<div class="post-metadata">

**Author:** ![Rory\_Bremner1](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/a3d4f5/32.png) [@Rory\_Bremner1](https://forum.virtualmin.com/u/Rory_Bremner1)\
**Post date:** [August 27, 2020, 8:17pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/3 "2020-08-27T20:17:37Z")

</div>

Is there some setting in Virtualmin that I can change to accept EULA automatically?

---

<div class="post-metadata">

**Author:** ![DrCarsonBeckett](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/drcarsonbeckett/32/650_2.png) [@DrCarsonBeckett](https://forum.virtualmin.com/u/DrCarsonBeckett)\
**Post date:** [August 27, 2020, 8:26pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/4 "2020-08-27T20:26:24Z")

</div>

I am not sure, but maybe @Ilia or @Joe might know that.  
You can always simply SSH in and do it manually.

---

<div class="post-metadata">

**Author:** ![Rory\_Bremner1](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/a3d4f5/32.png) [@Rory\_Bremner1](https://forum.virtualmin.com/u/Rory_Bremner1)\
**Post date:** [August 27, 2020, 8:40pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/5 "2020-08-27T20:40:44Z")

</div>

Yes of course, that’s how I installed it to begin with.  
Just wondering if Virtualmin can do it automatically for me every time a new update comes out.

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [August 27, 2020, 8:59pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/6 "2020-08-27T20:59:49Z")

</div>

WTF?!? They put a EULA prompt in a deb package? The monsters. The absolute bastards.

That’s a packaging bug. A packaging disaster. An offense against the gods of computing.

---

<div class="post-metadata">

**Author:** ![Ilia](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/ilia/32/10185_2.png) [@Ilia](https://forum.virtualmin.com/u/Ilia)\
**Post date:** [August 27, 2020, 8:59pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/7 "2020-08-27T20:59:58Z")

</div>

Hi,

What distro and version is this?

Virtualmin doesn’t update anything but package manager does. What Webmin and Virtualmin versions do you have installed? How Virtualmin was installed on the system?

There is no package I can find called `msodbcsql17` in Debian/Ubuntu systems.

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [August 27, 2020, 9:01pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/8 "2020-08-27T21:01:18Z")

</div>

> [@Ilia](#):
>
> What distro and version is this?

He already said it’s Bionic. (Ubuntu.)

> [@Ilia](#):
>
> What Webmin and Virtualmin versions do you have installed? How Virtualmin was installed on the system?

Doesn’t matter. This is a broken third party package. We’re not gonna try to accommodate bad (really bad) packages.

---

<div class="post-metadata">

**Author:** ![Ilia](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/ilia/32/10185_2.png) [@Ilia](https://forum.virtualmin.com/u/Ilia)\
**Post date:** [August 27, 2020, 9:01pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/9 "2020-08-27T21:01:40Z")

</div>

> [@Joe](#):
>
> Doesn’t matter. This is a broken third party package. We’re not gonna try to accommodate bad (really bad) packages.

Yeah, as there is no such package for me in default repos.

---

<div class="post-metadata">

**Author:** ![Ilia](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/ilia/32/10185_2.png) [@Ilia](https://forum.virtualmin.com/u/Ilia)\
**Post date:** [August 27, 2020, 9:02pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/10 "2020-08-27T21:02:46Z")

</div>

I wonder, should we run and update with a param (if there is one) passed to package manager to automatically accept that?

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [August 27, 2020, 9:08pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/11 "2020-08-27T21:08:47Z")

</div>

No. We can’t safely accommodate every random bit of nonsense packagers put in the pre/post scripts. It’s an upstream packaging bug.

---

<div class="post-metadata">

**Author:** ![Rory\_Bremner1](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/a3d4f5/32.png) [@Rory\_Bremner1](https://forum.virtualmin.com/u/Rory_Bremner1)\
**Post date:** [August 27, 2020, 9:12pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/12 "2020-08-27T21:12:47Z")

</div>

> **[Install the Microsoft ODBC driver for SQL Server (Linux) - SQL Server](https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server?view=sql-server-ver15)**
>
> Learn how to install the Microsoft ODBC Driver for SQL Server on Linux clients to enable database connectivity.

This is on a Ubuntu 18.04

---

<div class="post-metadata">

**Author:** ![Rory\_Bremner1](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/a3d4f5/32.png) [@Rory\_Bremner1](https://forum.virtualmin.com/u/Rory_Bremner1)\
**Post date:** [August 27, 2020, 9:50pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/13 "2020-08-27T21:50:47Z")

</div>

They mention this in the above link:  
Note

You can substitute setting the environment variable ‘ACCEPT\_EULA’ with setting the debconf variable ‘msodbcsql/ACCEPT\_EULA’ instead: `echo msodbcsql17 msodbcsql/ACCEPT_EULA boolean true | sudo debconf-set-selections`

---

<div class="post-metadata">

**Author:** ![Rory\_Bremner1](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/a3d4f5/32.png) [@Rory\_Bremner1](https://forum.virtualmin.com/u/Rory_Bremner1)\
**Post date:** [August 27, 2020, 9:52pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/14 "2020-08-27T21:52:08Z")

</div>

This is the guide I followed to install on multiple php versions:

> <https://github.com/microsoft/msphpsql/issues/1145>
>
> Hi,
> I wanted to be able to access SQL Server from Ubuntu 18.04, so I followed this procedure:
> sudo su
> curl https://packages.microsoft.com/keys/microsoft.asc | apt-key...

---

<div class="post-metadata">

**Author:** ![system](https://cdn.forum.virtualmin.com/uploads/default/original/2X/c/cd96d761e326db4b2bef94886a639109bd7a8e76.svg) [@system](https://forum.virtualmin.com/u/system)\
**Post date:** [August 31, 2020, 9:52pm UTC](https://forum.virtualmin.com/t/virtualmin-cannot-update-msodbcsql17/107248/15 "2020-08-31T21:52:10Z")

</div>

Closed on August 31, 2020, 9:52pm UTC

This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.
