-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQL 2012 native client has moved #76
Comments
Thanks for raising this. Let me bring it up internally and see what the official guidance is. Stay tuned! Brian |
I wonder what the prerequisiteinstaller.exe would use for SP2016 in this case, if we let it run in online mode? If one of us gets the chance we should run it and then check the log for the permalink... |
That's how I found it. It fails with 1620 exit code. I have attached an issue from SharePointDsc above also. |
Have reached out to the product group internally, stay tuned. |
So per Yorick's comments and PR over at SharePointDSC, I have updated the URL for the SQL Server 2012 Native Client. Hopefully they update the permalink soon too, so manual installs work. |
Permalink/FWLINK has been updated by the PG! New destination URL is the same as the one for SP2019: https://download.microsoft.com/download/F/3/C/F3C64941-22A0-47E9-BC9B-1A19B4CA3E88/ENU/x64/sqlncli.msi |
http://download.microsoft.com/download/4/B/1/4B1E9B0E-A4F3-4715-B417-31C82302A70A/ENU/x64/sqlncli.msi URL is no longer available. Should we use SQL 2012 SP4 Native Client as a prerequisite for SP 2016 (similarly to how SP 2019 is using it)? I have tried it and it worked perfectly but I'm not sure it is fully supported by MS. The alternative might be installing "SQL Server® 2012 Native Client - QFE". I haven't really tried it.
Either way, should we update the AutoSPSourceBuilder?
The text was updated successfully, but these errors were encountered: