Just upgraded from ArubaOS 5.0.4.7 to 6.1.3.3 and I'm having the exact same issue as dexcrbed here:
http://community.arubanetworks.com/t5/ArubaOS-and-Controllers/OS-6-1-Error-in-getting-show-profile-list-aaa/td-p/13063
This only happens on my Master Controller. I can access the same location (Configuration, Authentication, AAA Profiles) on my Local controller without getting the messages.
In addition to the above, when I access Configuration, Authentication, L3 Authentication and then try to access any of the VIA information (VIA Authentication Profile, VIA Connection Profile or VIA Web Authentication), I get the same messages (twice) and I am not able to see any of those profiles. Again, on my local controller I am able to view the profiles I have there.
The main problem with this appears to be that any Windows VIA client that attempts to download the profile crashes the client, presumably because the Master controller either thinks it doesn't have one, or that it's corrupt. Clients that already have the profile are still able to successfully connect.
I have not yet attempted to open a case with Aruba, but am tempted to just roll back to 5.0.4.7. Really the only reason I moved to 6.x.x.x was for my handful of Mac users that would like to be able to use the VIA client. Just thought I'd throw it out here first to see if anyone's run into something similar or has any ideas.