In VRA 7.0.1 when adding a property that uses a VRO action which returns a list of items from a DB we keep getting:
Error while saving property definition: System exception
Does anyone know why this is occurring? The return type of the action is ANY however it doesn't seem to matter as the error is always the same.
The actions work perfectly fine using an XaaS form this error occurs only with property definitions and external values/actions.
look at the /var/log/vcac/catalina.out file on the application appliance. That will usually have the information you need.
Did you ever find an answer?
I did look in the catalina.out and found this error: Error making request to vCO. Reason: 404 Not Found
Based on that I found this KB article: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=21405...
First of all that KB article is very disappointing. It's simply not acceptable to have all tenants on the same vRO server. If only because it is common practice to have a development tenant for developing vRO workflows.
But anyways, I tried pointing all tenants to the same vRO and still have the same problem.
I also tried different vRO actions, even without inputs but they all give me the same error when saving the property definition.
Anyone with a solution?
ok, I'm one step further..... turns out the external values thing only works on the default tenant.
So I created the property definition on the default tenant. Set it to be available for all tenants.
Then i try to use it in another tenant and the field actually shows up in the request form. But without values. When I click the dropdown it keeps "loading..."
In catalina.out I find a 404 error first then this error: Property definition not found with id [customprpertyIdhere]
Now what?
Still an issue in 7.1...
This provided a "fix", but not permanent. Changing the default tenant from the built in local vro to using the external vro appliance built for the tenant with the issue solved it, but unfortunately this is not a viable solution since we have separate vro servers for each tenant. I'm hoping that this gets fixed soon!
Thanks for posting!
Hello Dears,
it is still on vra 7.2 also.
the solution is :
- Create new local admin on your tenant by visiting the main Tenant Administration > Tenants > Local users
- login on the tenant with the new created local admin
- create the property and make the relation it will work 100%
Ayham