topic Thanks Neno! in Network Access Control

ACS 5.4 AA Protocol Report Error

andrecsthompson — Mon, 11 Mar 2019 07:16:39 GMT

I have ACS 5.4 running as an appliance.

The reporting was working fine up to a few weeks ago and now when I run a AAA Protocol report I get the following error:

org.xml.sax.SAXParseException: Attribute "xmlna" bound to namespace "http://www.w3.org/2000/xmlns/" was already specified for element "Envelope"

Please see screenshot.

It seems any report results in this error.

Any help offered will be greatly appreciated.

Thanks in advance.

I seen ts error before and a

nspasov — Mon, 05 Dec 2016 22:23:18 GMT

I seen ts error before and a simple reboot fixed it for me. I have a couple of questions:

- Have you tried a reload on the server

- Are all of the services running? You can check this with "show application status acs"

- What patch level are you running on the 5.4 version?

Thank you for rating helpful posts!

Hi Neno

andrecsthompson — Tue, 06 Dec 2016 12:31:34 GMT

Hi Neno

Yes I tried a reload.

All services are running.

Here is the show version:

STACITSACS01/admin# sho ver

Cisco Application Deployment Engine OS Release: 2.0
ADE-OS Build Version: 2.0.3.058
ADE-OS System Architecture: i386

Version information of installed applications
---------------------------------------------

Cisco ACS VERSION INFORMATION
-----------------------------
Version : 5.4.0.46
Internal Build ID : B.221

OK a couple of things I would

nspasov — Tue, 06 Dec 2016 19:16:45 GMT

OK a couple of things I would suggest:

1. Try a different browser. More specifically try Firefox

2. You should definitely patch the system. At the moment Patch-9 is the latest patch for the 5.4 train. Those patches address tons of bugs and vulnerabilities. The nice thing is that the patches are cumulative so you can install patch-9 directly without having to install 1 through 8 first.

Thank you for rating helpful posts!

Thanks Neno!

andrecsthompson — Wed, 07 Dec 2016 12:32:41 GMT

Thanks Neno!

It was indeed the browser.

I thought IE was compatible but I should have known better.

Thanks!!

No problem! Glad that fixed

nspasov — Thu, 08 Dec 2016 01:14:40 GMT

No problem! Glad that fixed the problem! 🙂

Still though, I would highly recommend you upgrade to the latest release (5.8) or at least install the latest patch so other bugs and vulnerabilities are addressed.

Thank you for rating helpful posts!