CE90WIN_EN_SP5

CE90WIN_EN_SP1
User management
ADAPT00142867
Description:
Patch ID: 35181616
When multiple users are simultaneously logged on to a customized Crystal Enterprise server, the server crashed or a core dump
occurred.
New Behavior:
In the Security Subsystem Library, a user's information is added to a list when he or she logs on, and a pointer is created to show the
information's location in the list. When more user information was then added to the list, the list would sometimes resize and
reallocate its internal structure. In doing so, the pointer could be shifted to point to an invalid location; thereby causing a crash or core
dump. Crystal Enterprise now keeps copies of each pointer. This increases the reference count by one, but prevents the crash and core
dump.
ADAPT00149489
Description:
Patch ID: 35330146
The Web Component Server times-out users after 10 minutes, regardless the what value the user specifies for the time-out. The cause of
that behaviour is that the DefaultSessionTimeout is
hard-coded with a value of 10 minutes, which overrides any other specified value for the time-out.
New Behavior:
The hard-coded value for the time-out has been removed and replaced with a default value of 20 minutes, and the Web Component
Server now respects a value that the user sets in the
DefaultSessionTimeout option. The acceptable range for the value is 1-60. Any number outside of this range automatically defaults
back to 20, (i.e. if the value is set to 0, 61, 120, etc.).
Known Limitations:
The sessions are cleaned up every 2 minutes, so if the session timeout is set to 1 minute, there will still be a wait of two minutes before
the expired sessions are cleaned up.
Verify
ADAPT00130107
Description:
Patch ID: 35102302
When the RDC is used to pass an ADO record that is set to a report that is based on a TTX file, the fields from the record set are
mapped to the report by name, rather than by index. Consequently, if the fields in the record set do not use the same names as the
fields in the report structure, the field is removed from the report.
New Behavior:
When all of the field names in the record set do not match any of the field names in the report, the fields are mapped by position. If one
of the field names in the record set matches any field names in the report, all fields are mapped by name. In a situtation where the
mapping is mixed, the fields are mapped by name; any fields that do not match are dropped from the report.
Known Limitations:
1) If the fields are mapped by name, all record set fields must map by name.
2) The report field headings are not replaced with the associated field names from the ADO record set.