Skip to Content
0

Errors/Warnings during upgrade from SAP BO 4.1 sp6 to BO 4.2 SP4

Sep 20, 2017 at 09:35 AM

557

avatar image
Former Member

Errors/Warnings found during the installation are as follows 05:32:40.615 2017/09/20, 05:32:40: ntservice Error: Service is in pending state, unable to control service, exiting... 05:32:50.630 2017/09/20, 05:32:50: ntservice Error: Service is in pending state, unable to control service, exiting... 05:33:00.645 2017/09/20, 05:33:00: ntservice Error: Service is in pending state, unable to control service, exiting... 05:33:10.661 2017/09/20, 05:33:10: ntservice Error: Service is in pending state, unable to control service, exiting... 05:33:20.676 2017/09/20, 05:33:20: ntservice Error: Service is in pending state, unable to control service, exiting... 05:33:30.691 Error: SetSIAStateWithRetry: ControlNTService failed stoppingervice BOEXI40SIABODEV001 after 5 retries. 05:33:30.691 Error: unmarshalSizet: curPos past end of string 05:33:30.691 Error: Serialization error. Expecting at least 1 arg(s). Got 0. 05:33:30.691 Error: Poco Exception: Software caused connection abort 06:08:55.177 [InstallEntDfoWrapper.UploadDFO] UploadDFO Failed [E:\SAP BusinessObjects\setup\packagestemp\BusinessObjects_ICC_InformationControlCenter_dfo.xml] [InstallEntDfoWrapper.UploadDFO] UploadDFO Failed [E:\SAP BusinessObjects\setup\packagestemp\BusinessObjects_ICC_InformationControlCenter_pin.xml] ERROR: Deploy Files completed with errors. *#*_*|ERROR: Deploy Files completed with errors.|ERROR: Deploy Files completed with errors.*_*#* 06:09:53.238 ERROR: Cannot commit ServerIntelligence_Service_DestinationSchedulingService_dfo.xml. The DFO data is older than the DFO in the repository. The following properties are causing the problem: SI_CONFIG. 06:10:06.066 ERROR: Cannot commit ServerIntelligence_Install_BODEV001_OutOfBoxAdaptiveJobServer_DestinationSchedulingService_dfo_frag.xml. The DFO data is older than the DFO in the repository. The following properties are causing the problem: SI_RELATIONSHIPS.SI_SERVICE_HOSTS.1.SI_CONFIG. ERROR: Cannot commit ServerIntelligence_Service_DestinationSchedulingService_dfo.xml. The DFO data is older than the DFO in the repository. The following properties are causing the problem: SI_CONFIG. ERROR: Cannot commit ServerIntelligence_Install_BODEV001_OutOfBoxAdaptiveJobServer_DestinationSchedulingService_dfo_frag.xml. The DFO data is older than the DFO in the repository. The following properties are causing the problem: SI_RELATIONSHIPS.SI_SERVICE_HOSTS.1.SI_CONFIG. Refer SCN link and SAP Notes for DFO related Errors Contact system administrator for other errors

All CMS servers are running fine except APS which says running with errors.

How do I fix the above?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Denis Konovalov
Sep 20, 2017 at 12:00 PM
0

1. You did not follow best practices for upgrade installs KBA

https://launchpad.support.sap.com/#/notes/1757132

This is evidenced by the first set of errors.

2. "The DFO data is older than the DFO in the repository" means that the environment was at one point upgraded and then downgraded, but CMS DB remained at higher version or there was some other way the DFO info in the CMS DB is newer that the one being installed by upgrade.

3. APS running with errors could be result from above or something else. Needs closer examination of what exactly failing and where.


As the first step - run repair, but make sure you do pre-req steps 1-5 in the above KBA first.

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Denis,
Any suggestions on how to best solve bullet 2 (The DFO data is older than the DFO in the repository)? After our update from 4.2 sp02 to 4.2 SP04 we are not able to start Apache Tomcat from CMC and the logfile indicates the same problem as Venkata.

0

Tomcat not starting is not related to DFO's in any shape or form.
its a completely separate product that is not in any way connected to CMS DB, where DFO's are.

Tomcat not starting could be very many different things - tomcat logs needs to be checked etc to see why.
There are several reasons of tomcat not starting after upgrade that are documented in KBA's, please search SAP Knowledge base.

0