Hot Fix Readme (Adapt) - Business Intelligence
Hot Fix Readme (Adapt) - Business Intelligence
Hot Fix Readme (Adapt) - Business Intelligence
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
CHF13<br />
ADAPT00626886<br />
Description:<br />
Patch ID: 38,840,725<br />
When users click on a report parameter while running a report, the following error message appears: "Failed to process<br />
prompting."<br />
The cause of the problem is that the <strong>Business</strong>Objects Enterprise SDK function LogonWithToken may fail sporadically when<br />
made from server processes such as the cacheserver, pageserver, or Report Application Server (RAS) in a multi-process<br />
system. This failure can occur at any time but it is most common when the CMS is running with -port 6400 on its command<br />
line, or when the CMS is first started after modifying the -port argument.<br />
New Behavior:<br />
This problem is resolved.<br />
This fix will also improve performance slightly and reduce CPU usage from the CMS.<br />
ADAPT00628013<br />
Description:<br />
Patch ID: 38,936,263<br />
When changing the datasource of a report that uses a command with parameters, a NullPointerException is generated.<br />
New Behavior:<br />
This problem is resolved.<br />
ADAPT00629713<br />
Description:<br />
Patch ID: 38,917,044<br />
When the function logonWithToken is used, the Java SDK randomly selects an active CMS inside the target cluster to acquire<br />
the logon/session service.<br />
New Behavior:<br />
This problem is resolved.<br />
ADAPT00630143<br />
Description:<br />
Patch ID: 38,822,283<br />
When connecting to Data Direct ODBC drivers using a connection string, a Licensing warning appears.<br />
New Behavior:<br />
This problem is resolved.<br />
ADAPT00631740<br />
Description:<br />
Patch ID: 38,948,314<br />
When refreshing Web<strong>Intelligence</strong> documents that have been migrated from <strong>Business</strong>Objects version 6.5, the WIReportServer<br />
may consume large amounts of processor resource.<br />
New Behavior:<br />
This problem is resolved.