NEWS: Engagement 6.1.2 Issues

This e-fxNews was released on 4/7/2010 and discusses specific issues identified when using version 6.1.2. Don't forget to take a look at the "NOTE REGARDING UPCOMING RELEASES" section. It specifically mentions that the next release (version 6.5, which is scheduled for a July release date) will not support 64-bit version of Office 2010 or IPv6. I find it a bit strange that CCH hasn't released more detailed information about their plans to move Engagement to a true 64-bit application. Interestingly enough, Engagement gained compatibility with 64-bit SQL 2005 with version 6.0.

Nevertheless, the newsletter is included below.

************************************************

Dear ProSystem fx Engagement Customer:

Based on your current e-fxNews profile, below is an item you may find of interest.

For more information about e-fxNews, or to update your profile, visit our web site at http://support.cch.com/notes/efxnews.aspx.

Online self-service help is now available. Find answers to your CCH questions in our knowledge base at http://support.cch.com.

*************************
Some customers who have moved to Engagement v. 6.1.2 are experiencing longer than normal refresh times for Microsoft Word workpapers containing large numbers of TBLinks. Most often these delays are occurring when the number of TBLinks in a document exceeds 1000, but smaller delays may exist with fewer links as well. We have identified the cause of this issue and have implemented changes to dramatically improve refresh times in Engagement v. 6.5 scheduled for July. However, because of the extensiveness of the change and the small number of customers likely impacted by this issue, we have decided to not issue an interim patch for Engagement. Users that routinely have large number of TBLinks in Microsoft Word documents may wish to consider delaying upgrade until v. 6.5.

Additionally, a small percentage of customers that have upgraded to Engagement v. 6.1.2 have reported the program becoming unresponsive when synchronizing a binder immediately after the upgrade. This situation happens when the Engagement synch service (PFXSYNPFTService) stops. The service will fail to start when manually starting it via the Services console. We are currently investigating this issue to determine the cause. In most instances, the resolution for this issue is to repair Engagement.

As a reminder, known issues like these, as well as FAQs and other information, are available 24/7 on our updated Engagement support website at http://support.cch.com/productsupport/productSupport.aspx?path=%2fTopics%2fproduct_support%2fpfx_office%2fpfx_engagement.

NOTE REGARDING UPCOMING RELEASES: Starting with our version 6.5 release of Engagement this summer, we will no longer be supporting direct upgrade from Engagement versions prior to v. 5.5. If you are using version 5.0 or earlier, we strongly recommend you upgrade to the latest version by July 2010 in order to support direct upgrade in the future. Also, please note that Engagement v. 6.5 will not support the 64-bit version of Office 2010 or IP v. 6.

If you have any questions or require assistance, please contact Technical Support at 1-800-739-9998, option 4.

Sincerely,CCH, a Wolters Kluwer business
Find answers to your CCH questions in our knowledge base at http://support.cch.com/answers/

****** UNSUBSCRIBE INFORMATION ******
To stop receiving e-fx News announcements, reply to this email, type UNSUBSCRIBE in the subject line, and include the following information in the body of the message:

- Account number
- Email address to unsubscribe

CCH, a Wolters Kluwer business
Attention: Customer Service
9111 E Douglas Avenue, Suite 200
Wichita, KS 67207