Hi everybody,
I upgrade first from BO platform SP4 Patch 1 to BO Platform SP5 patch 8
Then started with the upgrade that went very smooth except for this error, but I was able to finished the installation succesfully.
I tried that solution but when I ran the "RunAddNode.bat"
It finished with:
The following errors occurred during the operation:
ERROR: ▄bergabe von ServerIntelligence_ServiceCategory_XcelsiusServiceCategory_d
fo.xml nicht m÷glich. Die DFO-Daten sind Σlter als die DFO-Daten im Repository.
ERROR: ▄bergabe von ServerIntelligence_ServiceCategory_WebIServiceCategory_dfo.x
ml nicht m÷glich. Die DFO-Daten sind Σlter als die DFO-Daten im Repository.
ERROR: ▄bergabe von ServerIntelligence_ServiceCategory_MDASServiceCategory_dfo.x
ml nicht m÷glich. Die DFO-Daten sind Σlter als die DFO-Daten im Repository.
ERROR: Standardobjektfragment aus Datei ServerIntelligence_Install1_Extensions_C
MS_dfo_frag.xml konnte nicht auf Objekt (Name: ; CUID: ) angewendet werden.
Weitere Informationen finden Sie in der Datei assert.log. (FWB 00075)
In English should be something like this
ERROR: ▄ bergabe of ServerIntelligence_ServiceCategory_XcelsiusServiceCategory_d
fo.xml m ÷ not possible. The DFO data are greater than the DFO data in the repository.
ERROR: ▄ bergabe of ServerIntelligence_ServiceCategory_WebIServiceCategory_dfo.x
ml m ÷ not possible. The DFO data are greaterthan the DFO data in the repository.
ERROR: ▄ bergabe of ServerIntelligence_ServiceCategory_MDASServiceCategory_dfo.x
ml m ÷ not possible. The DFO data are greater than the DFO data in the repository.
ERROR: Default object fragment from file ServerIntelligence_Install1_Extensions_C
MS_dfo_frag.xml could not access object (name:; CUID:) are applied.
For more information, see the file assert.log. (FWB 00075)
The Same happened to me when I Upgrade to IS 4.2
EIM APS Services or IS JobServer could not be deployed successfully. After the installation completes, please follow the instructions below to re-deploy the services or servers:
1. In the Central Configuration Manager (CCM), stop the local Server Intelligence Agent (SIA).
2. Wait until CMS is completely shutdown. Check the Windows Task Manager -> Processes tab to make sure CMS.exe is not running.
3. Open a command prompt, navigate to "D:\BOBJ\InformationSteward\Utilities" directory and run the command "RunAddNode.bat". Enter your CMS password used during installation.
4. After completion of Step 3, start local SIA using CCM.
And I got the same error when I ran
the "RunAddNode.bat".
Thanks,
Matias Mannino