Hi Raj
The only issues we had after upgrading to BI 4.1 SP6 (from BI 4.1 SP5 Patch 5) was the following:
- The CrystalReportsProcessingServer failed to start/restart. This occurred on our Development, Quality and Production systems.
The cause was that some command line parameters were missing after the upgrade, solution was to add "-documentType CrystalEnterprise.Report" to the end in the command line parameter.
Reference to the solution is in SAP Note: 2180731 - CrystalReportsProcessingServer fails to start/restart in BI4.x
- Tomcat did not start due to the max and initial heap settings
On our Development system we apply the upgrade as is with no changes to any settings to determine what issue can occur so we can prepare ourselves for the Quality and Production system upgrades to avoid these issues.
.
On our Quality and Production systems we first reset the max and initial settings to default values then apply the upgrade and afterwards set the values correctly.
Currently our Production system is running 1.5 weeks with no issues so far with BI 4.1 SP6.
Regards
Derek