CE90WIN_EN_SP5
CE90WIN_EN_SP5
CE90WIN_EN_SP5
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>CE90WIN</strong>_<strong>EN</strong>_SP3<br />
Report processing<br />
ADAPT00251603<br />
Description:<br />
Patch ID: 36258146<br />
When a report that contains a blank memo field within a subreport is processed, it may cause Crystal Reports to exit memory.<br />
The problem is caused by memory that fails to be initialized.<br />
New Behavior:<br />
This problem is resolved.<br />
ADAPT00262773<br />
Description:<br />
Patch ID: 36010924<br />
Users are unable to connect from Crystal Reports 9 or earlier to a version 10 Crystal Management Server with LDAP authentication.<br />
The cause of the problem is that version 10 stores and interprets the LDAP authentication type differently than did earlier versions of<br />
Crystal Reports. In version 10, the LDAP authentication type is stored as an enum field. Prior to version 10, it was stored as a string<br />
field.<br />
New Behavior:<br />
The version 10 Crystal Management Server checks the version of Crystal Reports, before it interprets the authentication type, to<br />
determine how it should be read.<br />
ADAPT00264401<br />
Description:<br />
Patch ID: 36031560<br />
Users are unable to connect from Crystal Reports 9 or earlier to a version 10 Crystal Management Server with Windows AD<br />
authentication.<br />
The cause of the problem is that version 10 stores and interprets the Windows AD authentication type differently than did earlier<br />
versions of Crystal Reports. In version 10, the Windows AD authentication type is stored as an enum field. Prior to version 10, it was<br />
stored as a string field.<br />
New Behavior:<br />
The version 10 Crystal Management Server checks the version of Crystal Reports, before it interprets the authentication type, to<br />
determine how it should be read.<br />
ADAPT00265515<br />
Description:<br />
Patch ID: 36079624<br />
When Crystal Reports connects to Oracle, the pageserver sessions are not closed after reports with subreports are viewed, even after<br />
the idle time has passed.<br />
New Behavior:<br />
This problem is resolved.