Downloads:
34
Downloads of v 12.0.2000.8:
34
Last Update:
09 Dec 2020
Package Maintainer(s):
Software Author(s):
- Bjoern Strausmann
Tags:
microsoft-system-clr-types-for-sql-server-2014 admin- Software Specific:
- Software Docs
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Microsoft System CLR Types for SQL Server 2014 (Install)
- Software Specific:
- Software Docs
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
34
Downloads of v 12.0.2000.8:
34
Maintainer(s):
Software Author(s):
- Bjoern Strausmann
Microsoft System CLR Types for SQL Server 2014 (Install)
- 1
- 2
- 3
Some Checks Are Exempted or Are Not Yet Complete
Not All Tests Have Passed
This package was rejected on 07 May 2021. The reviewer chocolatey-ops has listed the following reason(s):
Microsoft-System-CLR-Types-for-SQL-Server-2014
Package Specific
Installer Properties
The following install arguments can be passed:
OPENREADME
SAPBINOTEPAD
PROMPTROLLBACKCOST
INSTALLLEVEL
ALLUSERS
ISENABLEDWUSFINISHDIALOG
CA_ERRORCOUNT
CA_WARNINGCOUNT
CA_SUCCESSCOUNT
UI_SHOWCOPYRIGHT
NEWERFOUND_32
OLDERFOUND_32
OLDERFOUND2_32
INSTALLSQLSHAREDDIR_32
MSSDKINSTALLDIR
To append install arguments to the current silent arguments passed to the installer, use --install-arguments="''"
or --install-arguments-sensitive="''"
. To completely override the silent arguments with your own, also pass --override-arguments
.
Example: choco install packageId [other options] --install-arguments="'PROPERTY=value PROPERTY2=value2'"
To have choco remember parameters on upgrade, be sure to set choco feature enable -n=useRememberedArgumentsForUpgrades
.
## NOTE: In 80-90% of the cases (95% with licensed versions due to Package Synchronizer and other enhancements),
## AutoUninstaller should be able to detect and handle registry uninstalls
## See https://chocolatey.org/docs/commands-uninstall
## and https://chocolatey.org/docs/helpers-uninstall-chocolatey-package
$ErrorActionPreference = 'Stop';
$packageArgs = @{
packageName = $env:ChocolateyPackageName
softwareName = 'Microsoft System CLR Types for SQL Server 2014*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
fileType = 'msi'
silentArgs = "/qn /norestart"
validExitCodes= @(0,1605,1614,1641,3010)
}
$uninstalled = $false
# Get-UninstallRegistryKey is new to 0.9.10, if supporting 0.9.9.x and below,
# take a dependency on "chocolatey-core.extension" in your nuspec file.
# This is only a fuzzy search if $softwareName includes '*'. Otherwise it is
# exact. In the case of versions in key names, we recommend removing the version
# and using '*'.
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
$key | % {
$packageArgs['file'] = "$($_.UninstallString)" #NOTE: You may need to split this if it contains spaces, see below
if ($packageArgs['fileType'] -eq 'MSI') {
$packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
$packageArgs['file'] = ''
} else {
# NOTES:
# - You probably will need to sanitize $packageArgs['file'] as it comes from the registry and could be in a variety of fun but unusable formats
# - Split args from exe in $packageArgs['file'] and pass those args through $packageArgs['silentArgs'] or ignore them
# - Ensure you don't pass double quotes in $file (aka $packageArgs['file']) - otherwise you will get "Illegal characters in path when you attempt to run this"
# - Review the code for auto-uninstaller for all of the fun things it does in sanitizing - https://github.com/chocolatey/choco/blob/bfe351b7d10c798014efe4bfbb100b171db25099/src/chocolatey/infrastructure.app/services/AutomaticUninstallerService.cs#L142-L192
}
Uninstall-ChocolateyPackage @packageArgs
}
} elseif ($key.Count -eq 0) {
Write-Warning "$env:ChocolateyPackageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$($key.Count) matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $($_.DisplayName)"}
}
## OTHER POWERSHELL FUNCTIONS
## https://chocolatey.org/docs/helpers-reference
#Uninstall-ChocolateyZipPackage @packageArgs # Only necessary if you did not unpack to package directory - see https://chocolatey.org/docs/helpers-uninstall-chocolatey-zip-package
#Uninstall-ChocolateyEnvironmentVariable # 0.9.10+ - https://chocolatey.org/docs/helpers-uninstall-chocolatey-environment-variable
#Uninstall-BinFile # Only needed if you used Install-BinFile - see https://chocolatey.org/docs/helpers-uninstall-bin-file
## Remove any shortcuts you added in the install script.
md5: C8B9170257C1D8A36732F6460FB2C491 | sha1: 873AC7290C059AF1389824167DC2177066304C29 | sha256: 1D9749BA3A067B5E4BA6C6A9ECE436640595632C1A9301CEEB6574BFFBBFABC0 | sha512: DDA74AD8D50ECC199CAFEFFBBCC50417DB0D0BED14A3ADD43569350CC558EE3B25C4E44FFAF08D475F3B60D91FD132609C4B8C6E0E33C2BAB139B95FA89A2B01
Log in or click on link to see number of positives.
- microsoft-system-clr-types-for-sql-server-2014.12.0.2000.8.nupkg (dc273f5bca50) - ## / 64
- SQLSysClrTypes.msi (1d9749ba3a06) - ## / 46
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Microsoft Corporation
This package has no dependencies.
Ground Rules:
- This discussion is only about Microsoft System CLR Types for SQL Server 2014 (Install) and the Microsoft System CLR Types for SQL Server 2014 (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Microsoft System CLR Types for SQL Server 2014 (Install), or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
strausmann (maintainer) on 09 Dec 2020 11:06:03 +00:00:
User 'strausmann' (maintainer) submitted package.
chocolatey-ops (reviewer) on 09 Dec 2020 11:39:05 +00:00:
microsoft-system-clr-types-for-sql-server-2014 has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 22 Apr 2021 09:49:46 +00:00:
We've found microsoft-system-clr-types-for-sql-server-2014 v12.0.2000.8 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
chocolatey-ops (reviewer) on 07 May 2021 09:51:28 +00:00:
Unfortunately there has not been progress to move microsoft-system-clr-types-for-sql-server-2014 v12.0.2000.8 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.
Status Change - Changed status of package from 'submitted' to 'rejected'.
strausmann (maintainer) on 28 Jun 2021 12:27:31 +00:00:
The problem is that there is no official download source for this Microsoft application anymore. Therefore I have attached it to the package.
Validation Status Change - Validation tests have been set to rerun.