Quickr hotfix adventures
July 28, 2010 1 Comment
A colleague of mine, Ben Williams, has been working extensively over the last few weeks with IBM to resolve a Quickr 8.2 instability issue for a customer. The initial fix was upgrading from fix pack 11 (8.2.0.11) to fix pack 12 (8.2.0.12), this didn’t resolve the issue and actually created a new one; creating a Quickr Place from a Lotus Connections Community failed and produced the following error – “Failed to create or update an associated application.” (fig. 1)
fig. 1
IBM provided a Quickr hotfix – 14-003a – which resolved the new issue (not the original issue though) but during the testing of it two new issues where discovered.
1. The Quickr Place widget in Lotus Connections Communities stopped working.
2. Disconnecting a Quickr Place from a Community caused Quickr to crash.
IBM quickly (no pun intended) gave us another hotfix – 14-005a – to resolve the two new issues unfortunately the Quickr Place widget for Lotus Connections Communities created whilst hotfix 14-003a was installed were still broken (thankfully this was only test Communities and Places), these Places needed to be disconnected from the Community and then deleted (qptool remove -cleanup) from Quickr.
The support and assistance from IBM has been good and the rollback to fix pack 11 was always an option, but the moral of the story is make sure you test hot fixes and for Quickr if your using Lotus Connections test the Connector functionality as well.
Meanwhile Ben and IBM are still working on the original issue of the Quickr 8.2 instability…..
Hi Jon,
The lastest quicker fix pack does indeed seem to have cured the majority of our wow’s and for now we have a stable solution again.
I’d like to point out that the 64 character limit is still an issue and will generate a failure should this limit be breached. IBM have, however, provided some additional code that can go into the qpconfig.xml which means that spaces are no longer using %20 saving a third on each space. It might be worth covering this in a seperate post as imtink they need to remove the limit peronsally
With regards to the quicker crashes at 4am. After all the debug and log trawling, the IBM suggested fix of rebuilding the Place Catalog seems to have done the trick.
Regards
Tony