Microsoft Server 2016 Standard: Update MSSQL 2017 Version 14 auf MSSQL 2019 Version 15 = funktioniert nicht: Fehlercode: 1706

Question

question

m2move-7048 asked Apr 22, '22 ErlandSommarskog answered Apr 28, '22

Microsoft Server 2016 Standard: Update MSSQL 2017 Version 14 auf MSSQL 2019 Version 15 = funktioniert nicht: Fehlercode: 1706

Guten Tag

Ich haben einen kleinen HP Proliant MicroServer Gen8 mit MSSQL 2017 Ver. 14 installiert und möchte die Datenbank upgraden auf MSSQL 2019 Ver. 15.

Leider geht das nicht und ich bekomme immer folgende Fehlermeldung:

Erforderliche Aktion:
Beheben Sie den Fehler mithilfe der folgenden Informationen, und versuchen Sie erneut, den Setupvorgang auszuführen.

Ursache für Funktionsfehler:
Da eine Abhängigkeit der Funktion einen Fehler verursacht hat, war der Setupvorgang für die Funktion nicht erfolgreich.

Fehlerdetails:
§ Fehler beim Installieren von Microsoft OLE DB-Treiber für SQL Server
Für das Produkt Microsoft OLE DB-Treiber für SQL Server wurde kein Installationspaket gefunden. Wiederholen Sie die Installation mit einer gültigen Kopie des Installationspakets 'msoledbsql_X64.msi'.
Fehlercode: 1706
Protokolldatei: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20220402_003205\msoledbsql_Cpu64_1.log
Besuchen Siehttps://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&Evtsrc=setup.rll&EvtID=50000&ProdVer=15.0.4013.40&EvtType=msoledbsql.msi%40InstallFiles%401706 um Hilfe bei der Problembehandlung zu erhalten.

Ebenfalls kann ich keine neue Installation machen, diese wird nicht angenommen.

Wo liegt das Problem? Ich bin kein Experte und kenne mich nicht gut aus.

Danke und Gruss
mc

sql-server-general

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AmeliaGu-msft · Apr 26 at 07:58 AM

Hi m2move-7048,

How are things going? Were the answers helpful?
Please feel free to let us know if you have any other question. If the post in the thread is helpful, you could kindly accept it as answer.

Best Regards,
Amelia

0 ·

Answer 1 · 2022-04-22T08:32:25.717Z

pituach answered Apr 22, '22 ErlandSommarskog commented Apr 23, '22

Welcome to the QnA forums @m2move-7048

The discussions here are conducted only in English (the interface not support non English language or in other world UNICODE). Therefore, If you want to continue the discussion then please translate the question into English.

I translated your question to English using Google translator so I am not 100% it was translated perfectly, but I will respond the translation I got.

The translation:

I have a small HP Proliant MicroServer Gen8 with MSSQL 2017 Ver. 14 installed and would like to upgrade the database to MSSQL 2019 Ver. 15

Unfortunately that doesn't work and I keep getting the following error message:

Required Action:
Use the information below to resolve the error and try the setup process again.

Cause of functional error:
Because a feature dependency caused an error, the feature setup process was unsuccessful.

Error details:
§ Failed to install Microsoft OLE DB Driver for SQL Server
No installation package was found for the product Microsoft OLE DB Driver for SQL Server. Retry the installation with a valid copy of the installation package 'msoledbsql_X64.msi'.
Error code: 1706
Log File: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20220402_003205\msoledbsql_Cpu64_1.log
Visit https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&Evtsrc=setup.rll&EvtID=50000&ProdVer=15.0.4013.40&EvtType=msoledbsql.msi%40InstallFiles%401706 for troubleshooting help.

Also I can not make a new installation, this is not accepted.

Where is the problem? I am not an expert and do not know my way around very well.

Thanks and regards
mc

Answer

(1) Make sure that you restart the machine before you try. Do everything as Administrator.

(2) To install the OLE DB Driver for SQL Server, you need the msoledbsql.msi installer. If it not installed then you should install it. Check the following document for more information:

https://docs.microsoft.com/sql/connect/oledb/applications/installing-oledb-driver-for-sql-server?view=sql-server-ver15&WT.mc_id=DP-MVP-5001699

I would recommend to check it is installed first since it might be corrupted as well. go to the control panel -> "uninstall program" and check if there is Microsoft OLE DB Driver for SQL Server. If it exists, then you might need to uninstall it -> restart your machine -> reinstall.

· 5

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

m2move-7048 · Apr 22 at 10:29 AM

Hi thanks for helo...

as I'm starting to learn not a pro on Windows Server Installation, I would like to know if I understand it correct.

Should I do an Image of the Installation and what is the best Image and Restore for Servers?

Download: msoledbsql.msi (German Vesion)

and install it by execute the command manually - see

195548-20220422-msoledbsqlmsi-03-upgrade-mssql-domain-feh.jpg

And then restart the SQL Upgrade Installation, is this correct!?

Then the installation Upgrade to Version 15 SQL 2019 should work fine!? Correct?

Or should I better install a new independent Installation?

See Pictures annex...

Thanks
mc

0 ·

20220422-msoledbsqlmsi-01-installation.jpg (84.0 KiB)

20220422-msoledbsqlmsi-02-upgrade-mssql.jpg (104.8 KiB)

20220422-msoledbsqlmsi-03-upgrade-mssql-domain-feh.jpg (84.1 KiB)

pituach m2move-7048 · Apr 22 at 12:16 PM

Hi,

Then the installation Upgrade to Version 15 SQL 2019 should work fine!? Correct?

I cannot be sure that I follow the information in the screenshot 100%, since I do not know German. In first glance and comparing to the English version , it sound like you understood correctly.

WITH THAT BEING SAID! I highly recommend you: NOT to upgrade version!

I always recommend NOT to upgrade versions (update a version yes but not upgrade to new version) and instead to use the opportunity in order to start a clean installation, which you can now configure in the best way, using your experience with your databases. There are multiple properties which you can configure for best performance which we do not know what will be best when start a new project/database/server.

This is my golden rule: DO NOT UPDATE VERSIONS :-)

Ronen Ariely
Personal Site | Blog | Facebook | Linkedin

0 ·

image.png (67.7 KiB)

ErlandSommarskog · Apr 22 at 09:41 PM

The discussions here are conducted only in English (the interface not support non English language or in other world UNICODE).

The interface apparently is able to cope with characters beyond ASCII. Every once in a while I see posts in Chinese here. And surely, you have managed to sneak in some Hebrew on a few occasions?

The forum appears to be restricted to the Unicode base plane, though, so posters wanting to use the Gothic script would be in trouble. I suspect that is more of a policy thing and a technical limitation.

0 ·

pituach ErlandSommarskog · Apr 23 at 01:42 PM

Yes, there is partially support for UNICODE but not fully. For example Emoji Unicode characters do not work here (unfortunately since I love using Emojis)

I did not check exactly what is the level of non-support for Unicode and it has no interests for me (in public), since it is officially not supported non-English discussion at this time according to the Microsoft team, but in anyway it is not supported (partially if you want to be more accurate, then I am OK with this).

0 ·

image.png (1.1 KiB)

ErlandSommarskog pituach · Apr 23 at 01:55 PM

Emoji characters are indeed beyond the Unicode base plane. When it comes to those characters, I'm inclined to see it as a feature that they are not permitted. :-)

0 ·

Answer 2 · 2022-04-22T08:51:17.407Z

AmeliaGu-msft answered Apr 22, '22 m2move-7048 commented Apr 28, '22

Hi m2move-7048,

Agree with pituach.
You also can go to installation media root folder \1033_ENU_LP ( the language you chose)\x64\Setup\x64, and double-click MSOLEDBSQL.MSI to install it manually.

Then re-upgrade SQL Server again.
If it still does not work, please share us the log in the C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20220402_003205\msoledbsql_Cpu64_1.log to analyze.

Best Regards,
Amelia

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

image.png (33.9 KiB)

· 2

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

m2move-7048 · Apr 22 at 10:33 AM

Hi thanks for helo...

as I'm starting to learn not a pro on Windows Server Installation, I would like to know if I understand it correct.

 Should I do an Image of the Installation and what is the best Image and Restore for Servers?

Download: msoledbsql.msi (German Vesion)

and install it by execute the command manually - see

195573-20220422-msoledbsqlmsi-03-upgrade-mssql-domain-feh.jpg

And then restart the SQL Upgrade Installation, is this correct!?

Then the installation Upgrade to Version 15 SQL 2019 should work fine!? Correct?

Or should I better install a new independent Installation?

195559-20220422-msoledbsqlmsi-04-upgrade-mssql-eigenstand.jpg

See Pictures annex...

Thanks
mc

0 ·

20220422-msoledbsqlmsi-01-installation.jpg (84.0 KiB)

20220422-msoledbsqlmsi-02-upgrade-mssql.jpg (104.8 KiB)

20220422-msoledbsqlmsi-03-upgrade-mssql-domain-feh.jpg (84.1 KiB)

20220422-msoledbsqlmsi-04-upgrade-mssql-eigenstand.jpg (102.4 KiB)

m2move-7048 · Apr 28 at 02:53 PM

hello... please find annex the asked file... thanks mc

check this download:

20220402_003205.zip / 20220422_122432.zip If it still does not work, please share us the log in the C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20220402_003205\msoledbsql_Cpu64_1.log to analyze.

Download-Link
https://wetransfer.com/downloads/e5d52d702d7f94603f70423c37e204f120220428144957/ca68d06d377ac9be812a75a0db450f9920220428145028/fd81f8

0 ·

Answer 3 · 2022-04-22T21:37:39.433Z

ErlandSommarskog answered Apr 22, '22 m2move-7048 commented Apr 23, '22

I don't know if that warning is related to the OLE DB provider, but it seems that your sever is a domain controller. Installing SQL Server on a domain controller is asking for trouble. That alone is reason for finding another machine and installing SQL Server on that machine and then copy the databases with BACKUP/RESTORE.

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

m2move-7048 · Apr 23 at 02:14 PM

hi... The machine was installed in 2017 from a pro in server. now we don't have any contact anymore as he moved away. I used this Windows Server 2016 Standard machine since then with the MSSQL 2017 Express Version SQL Server 14.0.2037 without any problems and it's still working well. I don't know what the problem is and why the update doesn't want to be done and asking the "msoledbsql_X64.msi" commant. what is that used for?
Sorry... I'm not a spezialist and at the moment no money for a new machine. what would be the best do be done...!? Is it possible to make a complet new installation of the system and ad the software afterwards? like on Windows 10 you can make a new installation without problems. thanks. mc

195788-20220423-sql-server-installation-01-windows-server.jpg 195756-20220423-sql-server-installation-02-sql-server-140.jpg

See informations on the machine

See informations on the SQL Server 14.0.2037 installation

0 ·

20220423-sql-server-installation-01-windows-server.jpg (81.0 KiB)

20220423-sql-server-installation-02-sql-server-140.jpg (24.9 KiB)

Answer 4 · 2022-04-23T15:41:26.917Z

ErlandSommarskog answered Apr 23, '22

I note that you have a quite an old build of SQL 2017. Obviously, if you are going to upgrade anyway, that does not really matter. Then again, I am not sure that you in current situation should upgrade to SQL 2019 at all. So it may be a good idea to download and install the most recent Cumulative Update for SQL Server 2017.

You don't have upgrade the current instance, but you can install a new instance. But then you need to change connection strings etc, and also copy logins etc. Well, you would have to do that with my suggestions as well, but you would still be on a domain controller, which is not a good idea.

Then again, if you install a new instance, that will in no way affect the existing instance. And you would still have the option to upgrade the current instance. However, you may get the same error, as I don't think this error is related to the upgrade as such. (MSOLEDBSQL is the OLE DB provider needed to set up linked servers to other SQL Server instances.)

I have a hinch that the issue you are running into is due to a mix of languages. What is the language of the current SQL 2017 installation, English or German? Which version did you download for SQL 2019? Do you have SQL Server Management Studio installed on this version? If so, which language?

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 5 · 2022-04-28T14:31:40.483Z

m2move-7048 answered Apr 28, '22

Hi... sorry really busy with other daily things... yes I think you are right. the installation seems to have a problem with to many APPS installed...

Microsoft Network in German should be OK (what can I delete?)
Microsoft Hel Viewer 2.2 or 2.3 in German should be OK (what can I delete?)
Microsoft ODBC Driver 13 / 17 and DB-Driver (are they correct or to many?)
Microsoft SQL Server 2012 / 2017 / 2019 Englisch, German (64bit?) I don't see what is correct!?
Microsoft Visual C++ 2013 / 2017 / !? why so many...
Microsoft Visual Studio?

I don't understand, why there are so many installations!? And I'm not sure what I can deinstall and what is needed for the Proffix Programm installed.

I think I would need somebody with more knowledge then I have. At the moment the server is running....

seepictures of installed software in the system:

thanks for your help!
mc

20220428-installierte-programme-01.jpg (61.7 KiB)

20220428-installierte-programme-02.jpg (61.2 KiB)

20220428-installierte-programme-03.jpg (90.1 KiB)

20220428-installierte-programme-04.jpg (108.3 KiB)

20220428-installierte-programme-05.jpg (54.3 KiB)

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 6 · 2022-04-28T21:21:42.803Z

ErlandSommarskog answered Apr 28, '22

You seem to have a mix of English and German software. This can lead to problems, at least if you mix English and German of the same thing.

I cannot comment on all those items you have listed, but the ODBC drivers of different versions are no problem, but it is perfectly possible to have them side by side.

Also, many of the items are sneaked in under the covers when you install other things.

I would try uninstalling Microsoft OLE DB-Treiber for SQL Server, and then see what happens.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

question