cancel
Showing results for 
Search instead for 
Did you mean: 

getting XML error on AFO start

james_batchelor2
Active Participant

I have just a 4 users out of ~1000 that see a specific error( afo-error-jun82021.png)that seems associated with the custom User interface we are deploying. So I removed completely all /Cof files in roaming and AppData. Uninstalled and ran the base installer for 2.8.7 with no customization. Then started AFO and got the same message. How? with no settings files present, where is this information coming? Registry? I purposely removed everything and did base install hoping to at least get it to start 'vanilla' without an error.

Attaching trace from startup as well. launcher-trace-8864glf.txt.. doesn't say much other than cannot complete.

attaching ao-trace-14532.txt

although AFO runs fine after the message closed. Users are not stopped.

and it not happening 90+% of the time.

ideas?

thx!

james

Accepted Solutions (0)

Answers (5)

Answers (5)

shivakrishnaj
Employee
Employee

Hi James,
Try the below solution once.
Open Cof_user_roaming.config file from %appdata%Roaming\SAP\Cof

As per your log your default profile pointed to
C:\ProgramData\SAP\Cof\User Interface\WATERS_AAO_USER_1.xml

So replace below line cof user roaming file
From
<AppBuilderDefaultProfilePath value="C:\Users\xyz\AppData\Roaming\SAP\Cof\UserInterface\SK_P_02_REname.xml" />

To
<AppBuilderDefaultProfilePath value="Standard" />

Restart AO with run as admin

Thanks & Regards,
Shiva

0 Kudos

Thanks for Sharing it with us Must visit Calculadorapp.

james_batchelor2
Active Participant
0 Kudos

Quick feedback.. the changes to the user roaming COF did not resolve the error the users are seeing. Even an uninstall, delete ALL cof folders and installation did not resolve. Are there any registry settings that may be corrupt that are not removed on uninstall?

There is no reason a clean install shouldn't work. Unless removal is not a complete removal.

luckily the error does not stop AO from running for the users in question.. the 3-4 out of 1000 or so.

I'll keep digging and trying things and update if a solution is found.

james

0 Kudos

Thanks for your information. It really helpful for us.

shivakrishnaj
Employee
Employee
0 Kudos

Hi James,
Try the below solution once.
Open Cof_user_roaming.config file from %appdata%Roaming\SAP\Cof

As per your log your default profile pointed to
C:\ProgramData\SAP\Cof\User Interface\WATERS_AAO_USER_1.xml

So replace below line cof user roaming file
From
<AppBuilderDefaultProfilePath value="C:\Users\xyz\AppData\Roaming\SAP\Cof\UserInterface\SK_P_02_REname.xml" />

To
<AppBuilderDefaultProfilePath value="Standard" />

Restart AO with run as admin

Thanks & Regards,
Shiva

DebjitSingha
Active Contributor
0 Kudos

Hello james.batchelor2,

We had similar issue in recent past during a deployment to new set of users. We were not able to pin point this exact cause, though were able to resolve it by uninstalling AO and office from local system. We had to uninstall with MS tool for clean uninstallation of Office package. Then it worked.
In our case, issue was isolated to a small group of users, so uninstallation was easy fix.

Note: Assuming you already deleted files from all AO locations.

Thanks,

Debjit