VMware Cloud Community
koushik_vmware
Enthusiast
Enthusiast
Jump to solution

Error : Not Authorized to execute the local process" during execution of a WF in vRO7.0

Hello All,

Need your help. We have encountered an issue - "Not Authorized to execute the local process"  during execution of  a WF in vRO7.0.

In this WF, it is trying to execute the ‘Command’ scripting class in vRO 7.0 server. Since by default Orchestrator applications do not have permission to run the Command class, we are getting an-authorized error.

To resolve this issue we need to set the system property ‘com.vmware.js.allow-local-process=true’ to the ‘vmo.properties’ properties file of the vRO 7.0 Orchestrator server.

We have already set the property true to the properties file  under ‘/etc/vco/app-server’ folder and after that the Orchestrator services are restarted. But still we are getting the issue.

Another thing is that we are using vRO cluster machines, so we have set the true in both vmo.properties file on both servers.


Can you please help me how to resolve the issue ?


We followed the below link.

https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.vco_administer.doc_42%2FGUI...

Thanks,

koushik

Reply
0 Kudos
1 Solution

Accepted Solutions
koushik_vmware
Enthusiast
Enthusiast
Jump to solution

Thanks llian , Full rebooting of the vRO appliances/machines did the resolution.

Now everything is working fine.

Thanks,

Koushik

View solution in original post

Reply
0 Kudos
2 Replies
iiliev
VMware Employee
VMware Employee
Jump to solution

Hi,

Could you post the content of your /etc/vco/app-server/vmo.properties file?

This 'You are not authorized to execute local process ...' error is thrown when vRO cannot read the property com.vmware.js.allow-local-process or its value is not true. The code for reading this property is really simple and it doesn't make sense to work for other properties specified in vmo.properties file but fail for just this particular property.

Reply
0 Kudos
koushik_vmware
Enthusiast
Enthusiast
Jump to solution

Thanks llian , Full rebooting of the vRO appliances/machines did the resolution.

Now everything is working fine.

Thanks,

Koushik

Reply
0 Kudos