After applying SP2-CU7 patches to my SQL 2012 machines, I receive an error:
“An Unhandled Exception occurred and the application will shut down immediately.”
“Error: Index was out of range…”
Anybody else have this problem?
This is currently a known issue with SQLadmintoolset’s Patch Analyzer with SQL Server 2012 SP2 with CU7 installed. Development has noted this is bug and plans to fix it in a future release of SQLadmintoolset.
Currently, the only workaround for the crashes is to remove the CU7 update from your SQL Server 2012.
If you would like I can create a Support Case and attach it to the open Development ticket, so you can be notified when a release of SQLadmintoolset which includes a fix for this issue is available.
Has this issue been fixed?
This issue has not been fixed at this time. Development is in the process of developing an out of cycle release to address this issue. However, there is no timeframe as to the availability of the release.
If you create a Support Case, we can attach it to the open Development ticket, so you can be notified when a release of SQLadmintoolset which includes a fix for this issue is available.
It’s 6 weeks. Any news?
Development is still working a new release to address this issue and have not provided at timeframe for availability at this time. Once, they have provided an update then you will be informed.
Development has not provided us with an update at time. They are still currently in the process of developing a new release which will address the issue.
This issue seems to have been resolved – but by Microsoft, not by Idera. I just applied SP3 to one of my SQL 2012 servers, and now Patch Analyzer can scan it without crashing. I hadn’t been able to scan this server since July.
Apparently procrastination is a viable business plan after all…
Update: The issue is not resolved; it just doesn’t express itself when there is no CU. So SP3 doesn’t cause an error, but SP3-CU1 will. Unless Idera can fix their products before then to handle the new output format of @@VERSION.