I should have added that not everyone will be affected by the issues found but we had stability problems with it.
We're not using EEM either but had 3 crashes on our dev server in the space of 4-5 days. My colleague testing it found other issues too (which I can't recall many of right now) but for CA to pull it from release means there must have been some major issues with it for various other people as well. I'm holding off H04 on our main production systems until we get a stable release. From: Pfleger, Jim [mailto:[email protected]] Sent: 26 May 2011 17:55 To: David Game Cc: Spectrum users Subject: Re: [spectrum] H04 experiences (WAS: Problems with Spectrum 9.2 H03) My understanding from CA is that it was pulled because it caused a problem in the Spectrum<->EEM integration, which we're not using. Regardless, we're stuck on H04 since hotfixes do not contain a rollback mechanism like patches do. We're putting in an ER for this. On 5/26/11 9:49 AM, "David Game" <[email protected]> wrote: Jim - HF04 has been pulled due to an inordinate number of bugs! If you can roll back to H03 until HF04 is "fixed" I'd strongly advise it. From: Pfleger, Jim [mailto:[email protected]] Sent: 26 May 2011 16:09 To: spectrum Subject: [spectrum] H04 experiences (WAS: Problems with Spectrum 9.2 H03) As promised, here's an update on the issues from my previous email - all four were addressed in H04. I'm awaiting final confirmation from our reporting guru on the SRM issue, but I believe it's been resolved. Also, we're occasionally getting duplicate notifications again, but the debug looks different from the last time this happened, so we're treating it as a separate issue. Because of these fixes (and others) we installed H04 as soon as it was available, so I can provide some early feedback. * We've found two events (so far) that are no longer logged to the events database (0x1010a and 0x1010d, for model attr changes). We're going to now conduct a full audit of what other undocumented event changes came with H04. * It seems that our failover servers are sometimes being started as root instead of ssadmin, which is mangling file permissions. The problem started after H04, but it's not clear why yet, partly because it's only happening on some of our failover servers. * The negative alarm counts issue citied in the release notes is not (completely) fixed, and we already have a new ticket open on it. That's all I have so far on H04. When I have anything else of note, I'll definitely share it with the group. HTH, Jim ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
smime.p7s
Description: S/MIME cryptographic signature
