First things first...are you in a standalone of comprehensive environment?
 
Just so you know (if you don't already) CVP Reporting is one of the most undocumented systems out there. It leaves a lot for the designers imagination. I finally got up and running in a comprehensive environment and there are a lot of settings which have to be dead on to make it work.

When you restarted the VXML server, did wait until it was fully up to start the reporting server? When I was in this debacle, the process which worked for me was:
1. Make change in OAMP
2. Restart VXML and Call Servers (A and B side)
3. Restart OAMP
4. Reboot CVP Reporting server
 
When sending a call into the VXML application from ICM, are you concatenating the ICMInfokeys? If these aren't there, then CVP Reporting will not write that record into the Call table.  

David,

Seems like you have two seperate issues here. 1.) The VXML data not being written to the database. 2.) Not being able to add an application through the OAMP.
 
1.) Not to insult you, but just to check... you do have the "Enable reporting for VXML application details" radio button checked to yes, correct?
 
Ok good, you do. Now, in your Cisco ICM script, you have to make sure you are sending the appropriate variables neccessary for CVP Reporting. What is usually common in an ICM config is VXML[0] = concatenate("application=APPLICATION_A;","callid=",Call.user.media.id). The Call.user.media.id is what you will see in your "call" table as CALLGUID. 
 
I use VXML[4] to pass through the rest of the variables from ICM. VXML[4] = concatenate("ICMInfoKeys=",Call.RouterCallKey,"-",Call.RouterCallDay,"-",Call.RouterCallKeySequenceNumber). This puts all the data (hyphen delimited) into CVP and reporting parses it out. Meaning, there is no need to identify the session data in CVP. However, you can use whichever array you have room to put it in. But this string is required to begin writing to the succeeding tables.
 
2.) Have you tried deleting your *.*.*.* inclusive filter, save and deploy, reboot sequence, then readd? If that doesn't work (as much as it defeats the purpose of wildcards), you can try to keep the *.*.*.* inclusive filter in there and seperate it with a ; and put ApplicationA.*.*.*. This should at the very least kick start the reporting server into seeing that application. If that works, I'd let it run for a day, then remove it and see what happens.
 

Oh yeah, my mistake for not pointing that out, as well. Our initial configuration set VXML[0] to cvp_call_id. While this looks right, it's not. If it's not set as callID then nothing about it will work. It's like it doesn't exist.

Did you have a chance to remove that exclusive filter?
 
I really hope your in a lab environment doing all this. When I was working on mine it was in production. And nearly everyday I had to reboot servers, so I had to wait until the maintenance window to bring everything down...2am.