CE10WIN_EN_SP6

CE10WIN_EN_SP2
Server management
ADAPT00263175 Patch ID: 36537291
Description:
If users go to view a large report over Crystal Enterprise, the report may fail to display and the following error message may appear in
the viewer: “Communication Error, Communication failed with all configured Web Component Servers because they are disabled or
not currently running. If this problem continues, please contact the system administrator.”
This problem is due to a limitation in the Windows' socket layer. When a failure in the Windows' socket layer occurs, many retries are
made, which may cause the Web Component Server to allocate large amounts of memory. This memory allocation can lead to a slow o
non-responding Web Component Server, and then result in the error message being displayed.
New Behavior:
A Change has been made to the Web Connector so that it will identify the communication error and make no more requests.
In this case, a revised error appears in the web browser: “Internal Error in Web Component Server Connector; an internal error
occurred preventing this request from completing successfully. If this error continues, please contact the system administrator.”
In the application event log, the following error is reported in the wcsisapi.dll file: “The requested file can not be transferred from the
WCS to the web server because its size exceeds the socket buffer size limit. Error: error number WSAENOBUFS.”
ADAPT00317980 Patch ID: 36499941
Description:
If the auditing data cannot be contained due to length restrictions, the connection to the CMS is lost.
New Behavior:
If the auditing data cannot be contained in the field due to length restrictions it truncates the data, to maintain the connection to the
CMS.
Set Location
ADAPT00300801 Patch ID: 36313174
Description:
A report that is migrated with the Data Source Migration Wizard may fail to migrate properly.
That is, if the report contains a subreport that is based on a Dictionary that contains table aliases with spaces, the migrated report still
contains links to the old dictionary file, rather than to the new Business View.
The problem is that the report is not migrated in an order that prevents unexpected sharing. The function that adds tables from the
Business View to the report is unable to distinguish between information from a table in the report and information from a table in a
subreport.
New Behavior:
The function that adds tables to the report from the Business View is fixed to make copies of tables before it adds them to the report.
Special fields