msodbcsql.msi and MsSqlCmdLnUtils.msi Install woes

[GreyFox]

Hi all,

 

I'm not sure if this is the correct part of the forum for this, so apologies in advance if it's not. We have a third party trying to install a piece of software on one of our user's PCs. It's Windows 10 Education Edition, v1803, with the latest Windows Updates etc. Before they can install the software, they need to install two other bits of software - file names in the title.

 

'Microsoft ODBC Driver 11 for SQL Server' (msodbcsql.msi) and 'Microsoft Command Line Utilities 11 for SQL Server' (MsSqlCmdLnUtils.ms)

 

'Microsoft ODBC Driver 11 for SQL Server' seems to install ok, ensuring you change it so the 'ODBC Driver for SQL Server SDK' feature installs as well. However, when trying to install the 'Microsoft Command Line Utilities 11 for SQL Server', we get the following message.

 

 

The driver is installed!

I've seen this elsewhere, but can't remember how I got around the issue. Any ideas please? This occurs on my user's PC, my PC and a VM I've tested it on, so it's not a one off. The VM and other user's PCs are both freshly reimaged.

 

After some more playing it now seems to install on my VM (with an SQL Server 2014) popup appearing asking if I want to make the change to my PC. To do this, I had to install the first file, run it again and choose 'Modify', keeping the settings the same. I've managed to get it to install on my PC previously, by running the second file as a different user. This doesn't work on my user's PC though, with the same 'other user' account. All the account I've used when trying to install these files have local and network admin rights.

 

Any help would be greatly appreciated.

 

Thank you

 

GreyFox

 

Edit - I forgot to mention. These are specific versions we're trying to install. The third party company has had no issues installing them on other PCs elsewhere, earlier in the day.

Edited August 23, 2018 by GreyFox

[johnpd]

Is this for lucid exact? I’m trying to get the same installs on the same os build also but not getting that error. However I didn’t select the sdk part. I guess I can try and see what I get too?

[johnpd]

Solved mine - it was a shortcut issue

[GreyFox]

Hi johnpd,

 

I think this was a piece of finance software. A colleague of mine managed to get this working. I can't remember exactly what he did, but he was able to install the software via Powershell.

 

Thanks

 

GreyFox