 |
<< Back
Volume 2 - Latest Patches & Hotfixes
The latest Patches and hotfixes can be easily viewed and downloaded from the Onxy website. Montera's CRM consultants are also available to assist you with any updates you require.
The most recent update descriptions are:
OEP 5.0, 5.0 SP1, 5.5 Hotfix 96408: Intermittent screen freezes occur in OEP after installing Windows Update MS06-61
A problem with the MSXML garbage collection that impacts OEP has been introduced by the Security Update MS06-61 causing intermittent screen freezes in the following transactions:
- Saving Incidents
- Saving Attachments
- Saving Customers
- Sending Emails
OnyxKB 4.0: Onyx Knowledge Base compatibility with SQL Server 2005
- To maintain compatibility between Onyx Knowledge Base (Onyx KB) and SQL Server 2005, the Extraction Engine has been updated to use ADO, rather than RDO, to communicate with SQL Server.
- This hotfix also includes an optional template that renames QA Incidents to WorkTicket Incidents.
- Before applying the resolution described in this article, please make sure you have already applied hotfix 72560.
OEAS 6.0: Fix Reminder Insert and Reminder Update to prevent more than a single Reminder per Incident or Task
- In versions 5.5 and earlier, the OEAS methods used to insert and update reminders would not allow more than one reminder to be created for a given incident or task. In OEAS 6.0, the reminder insert and update methods use standard generated SQL, and did not include any logic to prevent multiple reminders for an incident or task.
- Because OEP and other Onyx products expect only a single reminder, the additional reminders will be inaccessible and could cause unpredictable results and data corruption. In addition, any custom solution or integration that uses OEAS to insert or update reminders may not work properly and may be inserting reminders that are not accessible by other Onyx products.
OEAS 6.0: Onyx Web Services can cause timeout problems with Cognos integration or other clients
- Queries made by OEP or OEAS to the ReportNet step component periodically fail after a 30 second or 60 second timeout has elapsed. This can cause errors within OEP or a failure to display the list of reports within OEP. In the event log of the OEAS machine, the MSSOAP component will report HTTP timeout or other HTTP errors.
- This problem is the result of COM Interop issues between Onyx Web Services, which runs in ASP.NET managed code, and OEAS, which runs in unmanaged COM+. A relatively high number of calls to the Onyx Web Service in rapid succession causes a blocking problem within the .NET/OEAS interop layer that eventually results in a timeout.
- The problem can be more or less severe depending on several factors, such as how much load is presently on the OEAS server, and whether Onyx Web Services is running on the same server as OEAS. The problem may occur a small percentage of the time or not at all in some cases, but occur up to 80% of the time in a different environment.
To view all Onyx updates, log in to ...
|
