Documente Academic
Documente Profesional
Documente Cultură
Attachments:1
Added by Shiva Vishnubatla, last edited by Jason Chong on Dec 13, 2013 (view change)
Go to start of metadata
BI
Upgrade Series
sap.com/upgradebi
This page is part of the...
This Wiki is for documenting known issues and solutions for the SAP BusinessObjects
Intelligence Platform BI 4.0 SP04 or higher Full or patch Installations. Originally this page was
focused on SP04 updates, but this information is now considered applicable to all Service
Packs 4 or higher.
Best practices
Issue 6: Renaming SIA Node causes SP2 updates to FP3 or SP4 to fail
Related Content
Best practices
These are the best practices for all Support Pack and Patch installations:
Use the Update Installer when upgrading from BI Platform SP02 to SP04.
Use the Process Explorer or Windows Task Manager to ensure that all non-essential processes are terminated
after stopping them. The java.exe processes located in the Business Objects directory should be terminated. (The process
paths can be viewed under the Command Line column of the Processes tab for Windows Task Manager).
Note: If the Java processes associated with the BI Platform are not terminated, they may lock up files, causing them to be
updated or deleted. These file changes can cause issues with missing libraries. This issue is a Java Virtual Machine (JVM)
issue that is scheduled to be fixed in BI Platform Support Pack 05 (SP05).
The administrator would need to terminate the selected process in the image if it was still in memory after stopping the nonessential services.
The above information on best practices is available as SAP kbase 1757132 - BI4 Support Pack Upgrade and Patch Install
Best Practice Guide
First, update the CMS servers before moving onto other tiers.
2.
Run the Update Installer on one server at a time. If you run the Update Installer simultaneously on multiple servers,
you may cause a race condition which will result in missing metadata.
Note: Symptoms of a failed simultaneous install include:
Symptoms:
Crystal Cache
Xcelsius Cache
The behavior remains the same despite recreating processes and the Server Intelligence Agent(SIA), and
repairing/installing SP04.
Missing files/libraries
Resolution:
1.
2.
3.
a.
b.
Ensure there are only 3 files in the folder (InstallManifest.sqlite, setupexe.log and setupengine.log.
c.
If you see other log files such as InstallDU-*.log (e.g., InstallDU-cvom.java-4.0-core-nu, 14.0.4.738, etc),
then some files or libraries have not been installed properly.
Symptoms:
On the CMC Servers page, the AJS has started but it does not begin any child processes as it is
supposed to.
No schedules run because the server is not available to begin new jobs.
Install logs may show issues upgrading these servers.
Resolution:
Stop all services except the CMS, and Input and Output FRS prior to a BI4.0 upgrade. This prevents a service from
affecting the install when not stopped all the way.
Note: If non-essential services are not manually stopped before applying SP04, certain java services may fail to upgrade.
The above information is available as an SAP kbase 1742498 Scheduling workflow(s) affected after installing SP4 for
BusinessObjects Enterprise 4.0.
Symptoms:
Applications like BI Launchpad and CMC may fail unexpectedly although they were redeployed properly.
Setup log (setupengine.log) indicates that the installer was unable to connect to the CMS due to its inability to
restart in time. Log entries as below or similar can be noticed:
Server <servername> not found or server may be down or
com.crystaldecisions.sdk.occa.security.in ternal.LogonService||Is the CMS alive? Ensure the CMS supports SDK version
1400
[InstallEntDfoWrapper.Connect] Exception:
[com.crystaldecisions.sdk.exception.SDKException$OCAFramework:
[InstallEntDfoWrapper.Connect] Connection Failed. Please retry...
10:46:30.572 [InstallEntDfoWrapper.main] Connection Failed. Could not connect to CMS [SERVERNAME:6400]
Note: The reasons for the CMS being unable to restart may vary from environmental-related (resources, virus, etc) to
network-related, because this is not a common issue.
Resolution:
Before upgrading or repairing, follow the "Best Practices" section above.
1.
Ensure that all non-essential services are stopped as explained in the best practices.
2.
Run a Repair on the BASE BI 4.0 Install by going to Control Panel > Programs > Programs and Features . SAP
Business Objects BI Platform 4.0 > Uninstall/Change > REPAIR.
3.
4.
After the install, re-run the script to import the missing modules.
The above information is available as an SAP kbase 1603067 - java.lang.NullPointerException or usagesProperty error after
login to CMC or BI Launchpad.
Symptoms:
When upgrading an existing BI4 system with the Installer, the Installer may not install all files.
While the setup logs indicate a successful install, files are left in the .../setup/packagestemp folder e.g.,
"C:\Program Files(x86)\SAP BusinessObjects\setup\packagestemp" on a default windows platform installation.
Some of the files listed under the .../setup/packagestemp folder folder may look like:
BusinessObjects_ClientAction_Publication_DocumentLink_dfo.xml
BusinessObjects_ClientAction_Publication_ViewLatestInstance_df o.xml
BusinessObjects_DSL_Universe_pin.xml
BusinessObjects_InformationDesigner_dfo.xml
BusinessObjects_InformationDesigner_pin. xml
BusinessObjects_MLStrings_MetricDescriptions_DSLBridgeSessionService_dfo_frag.xml
BusinessObjects_PlatformSearchUniverseCont entExtractor_dfo.xml
BusinessObjects_Relation_WEBI_UNIVERSE_dfo.xml
Resolution:
This issue was tracked as ADAPT01628046 and resolved in SP04 Patch1 which is available in SMP patch
downloads.
This and other fixes & improvements can be validated in the Release notes document
at http://service.sap.com/~sapidb/011000358700000813222012E.
Symptoms:
After updating or patching SP04 you see the following error when accessing BI Launchpad or CMC:
Error: 500
Error: Java.lang.NullPointer Exception
Resolution:
Symptoms:
In an update to SP4 (but not FP3), the installer will alert you on the final screen that the installer encountered
errors.
If you perform a modified install after the original install to add RESTful Web Services, you will find that RESTful
Web Services does not appear as a service.
Dashboard Analytics Server and Dashboard Server will show as failed to start on the CMC Server management
page. The services themselves have been moved.
Resolution:
If you have renamed the original node, you can run a repair installation and name the new node to get a fixed system.
1.
To resolve this issue, you need to run a repair install from the command line, using the setup.exe located in your
installation folder:
2.
Follow the instructions below, where MasterCmsName and MasterCmsPort are your CMS name and port,
CMSPassword is your Administrator account's password, and SIAName is the name of your additional node:
Shut down the node being updated. Unless the MasterCms is on the node being updated, the node
running MasterCms must be running.
Run the following command line (on UNIX platforms, substitute addnode.bat with addnote.sh):
"<INSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\win64_x64\scripts\addnode.bat" -update -cms "[MasterCmsName]:
[MasterCmsPort]" -username Administrator -password "[CMSPassword]" -authentication secEnterprise -name [SIAName]
-cmsport [MasterCmsPort] -usetempcms
The above information is available as an SAP note 1731612 - SIA node renaming may affect SP2 updates to FP3 or SP4.
Symptoms:
You see the error: "Account information not recognized: All servers with CMS "CMSname:port", cluster
@"clustername:port", kind cms which host service null, are down or disabled".
Resolution:
For more details refer to kbase 1765690. where the issue is detailed and a fixed .dll targeted for patch 5 is attached, or
the SP04 Patch Release notes.
#SYNTAX is shown in some reports after updating from BO 4.0 SP4 to BO 4.0 SP6.
Resolution:
Between SP4 and SP6, updates to the calculation engine might have created an incompatibility with previous files in the
cache. Because of this, the binaries of SP6 are not able to properly process the files that were generated by th SP4
document cache. To resolve this issue, please clear the document cache as described in the note 1926596 - How to clear
Web Intelligence. document cache on BI 4.0.
Related Content
Related Documents:
Help Portal: http://help.sap.com/bobip40/
SP04 Patch Release notes: http://service.sap.com/~sapidb/011000358700000813222012E
Related Notes:
SAP Note 1729424 Business Intelligence platform 4.0 SP04 Patch Release Notes
SAP KBA 1603067 java.lang.NullPointerException or usagesProperty error after login to CMC or BI Launchpad
SAP KBA 1742498 Scheduling workflow(s) affected after installing SP4 for BusinessObjects Enterprise 4.0
SAP KBA 1743755 After installation of BI 4.0 Sp04, the crystal report cache server runs with errors and is disabled
SAP KBA 1671068 CMC in SAP BusinessObjects BI 4.0 returns a 500 error
SAP Note 1731612 SIA node renaming may affect SP2 updates to FP3 or SP4
SAP Note 1757132 BI4 Support Pack Upgrade and Patch Install Best Practice Guide
SAP Note 1765690 Installing patch 3 on BI 4.0 SP4 breaks SAP logon, viewing SAP users, roles, and accounts with SAP
aliases as well as SAP plug-in
SAP Note 1926596 How to clear Web Intelligence. document cache on BI 4.0.