Symptom
- Running UMT in the command line fails and returns the following error:
warning: ORB.init: unknown property `ooc.orb.policy.request_timeout' warning: ORB.init: unknown property `ooc.orb.policy.connect_timeout' Upgrade management tool will now perform a Complete Upgrade. Logging on to source CMS... Logging on to destination CMS... Querying source system for objects requiring parameters... Preparing for object retrieval... Retrieving objects... 0 com.crystaldecisions.thirdparty.org.omg.CORBA.UNKNOWN minor code: 0x0 completed: No at com.crystaldecisions.thirdparty.com.ooc.OB.Util.unmarshalSystemException(Util.java:295) at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorker.execute (GIOPClientWorker.java:598) at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorkerThreaded.receiverRun(GIOPClientWorkerThreaded.java:595) at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorkerThreaded$ReceiverThread.run(GIOPClientWorkerThreaded.java:137) An unexpected error of type "com.crystaldecisions.thirdparty.org.omg.CORBA.UNKNOWN minor code: 0x0 completed: No" has occurred. (UMT 20005) |
- Enabling the UMT traces using KB 1602551 produces the following log entries:
|196236B167B5414384AC0D00773D8A8217c5|2012 02 16 15:36:34.311|+0000|<<| | |upgrademanagementtool|4415528| 18|sap.bobj.umt.mainOSGiThread| |42|1|0|0|BIPSDK.InfoStore:query|server.example.com:4415528:18.512:1|-|-|BIPSDK.InfoStore:query|server.example.com:4415528:18.512:1|Ck1bLpzfPEOruq5HyxU7uzU1ff|||||||||com.crystaldecisions.sdk.occa.infostore.internal.InfoObjects||startUnpack(): exit |196236B167B5414384AC0D00773D8A8217c7|2012 02 16 15:36:34.312|+0000|==| | |upgrademanagementtool|4415528| 18|sap.bobj.umt.mainOSGiThread| |42|1|0|0|BIPSDK.InfoStore:query|server.example.com:4415528:18.512:1|-|-|BIPSDK.InfoStore:query|server.example.com:4415528:18.512:1|Ck1bLpzfPEOruq5HyxU7uzU1ff|||||||||com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore||batchQuery(): need more data |196236B167B5414384AC0D00773D8A8217c8|2012 02 16 15:36:34.315|+0000|==| | |upgrademanagementtool|4415528| 18|sap.bobj.umt.mainOSGiThread|{|42|2|0|1|BIPSDK.InfoStore:query|server.example.com:4415528:18.512:1|-|-|BIPSDK.InfoStore:query|server.example.com:4415528:18.512:1|Ck1bLpzfPEOruq5HyxU7uzU1ff|||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.InfoStore:query#server.example.com:4415528:18.512:1] |
- Enabling the cms traces on the SAP BOE XI 3.1 system produces the following log entries:
012/02/16 15:36:34.797|<<| | |3313756|10795| |||||||||||||||CObjectSS::GetObjectInternal: Object was found in cache. obj ID=9069 2012/02/16 15:36:34.797|==| | |3313756|10795| |||||||||||||||GetChildren from plugin for secSAPR3:QB6~500@Z:BI_AA_ALL 2012/02/16 15:36:34.798|==| | |3313756|10795| |||||||||||||||SAP: Loaded ICU converter "ibm-5348_P100-1997". 2012/02/16 15:36:34.799|==| | |3313756|10795| |||||||||||||||SResourceSource::LoadString 15 2012/02/16 15:36:34.799|==| | |3313756|10795| |||||||||||||||SResourceSource::LoadString CSecSAPR3Binding::XRFCCnxBroker::BorrowConnection() failed. See following log entries for details. 2012/02/16 15:36:34.799|==| | |3313756|10795| |||||||||||||||SResourceSource::LoadString 7 2012/02/16 15:36:34.800|==| | |3313756|10795| |||||||||||||||SResourceSource::LoadString Failed while trying to log on to SAP system. The following RFC error was returned: [Group, Key, Message]: [%1, ""%2"", ""%3""]. The entitlement system has therefore been disabled in memory. This may be because the SAP system is unavailable or because the credentials are invalid. The entitlement system has to be re-enabled before it can be used again. 2012/02/16 15:36:34.815|==| | |3313756|22103| |||||||||||||||*** Freeing InfoObjectWireIterator_Impl servant object! |
Read more...
Environment
- Windows
- Unix/Linux
- SAP BusinessObjects Enteprise XI 3.1 SP3
- SAP BusinessObjects Business Intelligence 4.0 SP 02 Patch 2.11 (4.0.2.11)
- Upgrade Management Tool (UMT) from BI 4.0.2.11
Product
SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.0, feature pack 3 ; SAP BusinessObjects Enterprise XI 3.1
Keywords
corrupt report, corrupt connection, , KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , BI-BIP-UMT , Upgrade management tool , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.