Closed dimesv closed 2 years ago
@dimesv can you please make sure the product id for the Microsoft_ODBC_Driver_17_SQL_Server_64bit_180251.exe matches "72AFAF21-33FB-45A5-9468-A9EC07427F82"?
Hello @dimesv,
The correct product id for Microsoft_ODBC_Driver_17_SQL_Server_64bit_180251.exe is 7453C0F5-03D5-4412-BB8F-360574BE29AF
.
PS C:\Windows\System32> get-wmiobject Win32_Product | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize
IdentifyingNumber Name LocalPackage
----------------- ---- ------------
{7453C0F5-03D5-4412-BB8F-360574BE29AF} Microsoft ODBC Driver 17 for SQL Server C:\windows\Installer\56d09309.msi
Thanks, Cameron K.
Hi @cameronkroeker ,
Thanks heaps for helping out. Super useful and worked perfectly.
Cheers, Jose
Hi @cameronkroeker ,
Thanks heaps for helping out. Super useful and worked perfectly.
Cheers, Jose
Glad to hear the installed worked.
Thanks, Cameron K.
Hi guys,
I have used the changes you have introduced with v3.3.0 and have few issues installing SQLServerClient. My settings are as follows:
"SQLServerClient": [ { "Name": "Microsoft ODBC Driver 17 for SQL Server", "InstallerPath": "C:\Temp\Microsoft_ODBC_Driver_17_SQL_Server_64bit_180251.exe", "ProductId": "72AFAF21-33FB-45A5-9468-A9EC07427F82", "Arguments": " /quiet /qn IACCEPTMSODBCSQLLICENSETERMS=YES ADDLOCAL=ALL" } ]
The software is installed, then the DSC moves on as follows:
Do you guys have any idea what the issue might be? The sql client was downloaded from the myesri web site in the 10.9.1 downloads section.
Cheers, Jose
Community Note
Module Version
Affected Resource(s)
Configuration Files
Expected Behavior
Actual Behavior
Steps to Reproduce
Important Factoids
References