SPR-hotfix release on support.symbol.com

// Expert user has replied.
E Efkan YILMAZ 3 years 5 months ago
1 2 0

is there somebody who is coordinating the release of SPR-hotfixes on support.symbol.com partner is asking if he should install hotfix-SPR17445 which corrects a problem when installing hotfix-SPR17289 - he has not installed SPR17289 - but the release notes of MC55-UpdateLoaderImage 02.35.00 stating an SPR16050/SPR17289-fix !!!!???? Is the issue of SPR17289 present in this image ? Is there no Test&Validation before releasing hotfixes to the public ?

Please Register or Login to post a reply

2 Replies

N Nagaraj L

SPR 17445 in your above post is related to "WS 2000 Wireless Switch". I guess you are referring to SPR 17745 which was recently posted to HotFixes site. Regarding SPR17289, we had it removed from HotFixes site (As per SPR 17745 release notes, SPR17289 fix is included in SPR 17745). Since SPR16050 and SPR17289 is included in release notes, Customer is NOT required to install SPR17289 again. SPR17289 fix comes with OEM Version 02.35.00. And, customers using OEM Version 02.35.00 are NOT required to install SPR 17745 which was released two days ago. SPR 17745 was released for OEM Version 01.27.0006 only (It is mentioned in the release notes).

T Thomas Cassar

If you look at the SPR database for SPR17445, you can see that the rootcause of the failure of the original patch was because the dll was not signed.  The new patch was just a re-release of the SPR17289 .dll fix, but of course properly signed.  This would not be an issue for the full OS release.  So therefore, from a BSP35 perspective it is not applicable. Also please be sure to fully understand the HotFix policy that is posted in the HotFix section of Support Central.  It outlines that HotFixes do not go through formal Test & Validation.  Most of the time issues like this would be caught by engineering level testing or the testing that the customer who opened the original SPR performs before we close an SPR.  Unfortunately, in this case it appears the unsigned .dll was not caught.

CONTACT
Can’t find what you’re looking for?