Orchestrator 4.2.1 unable to configure due to folder permission errors

[mobcdi]

I recently upgraded to vCenter5 and decided to take a look at orchestrator but I seem to have permissions problems in that the readme.html in Program Files/VMware/Infastructure/Orchestrator/ appears blank unless I copy and paste a version to desktop. The paste command required admin permissions but I'm using the same AD account I used to upgrade vCenter with earlier

What obvious thing am I missing?

If I try and open installer_debug.txt I get "access is denied" by the AD account has full admin rights to the machine and was the AD account used to upgrade

If I expand the vmware folder in Programes every icon related to Orchestrator (Client, Configure, Readme) is the default windows variety instead of Vmwares produced unlike the other entries for generating log bundles and vSphere Client

[Burke-]

There were some changes in the installer routine that put pretty restrictive permissions on the path to the vCO install.. I have heard that a re-install of just vCO will resolve the issue... however, the approach I took was to Modify the permissions of the vCO folder (not bothering with path as you should be able to get that on your own). Once I changed the permissions, I had no issue.

Note: this only applies if you are attempting to run the vCO client ON your vCO server - and, possibly only when you are doing this all on the vCenter server. Ideally, you should use a different server for any workflow development work. Additionally, if you are running the vCO server on your vCenter server as part of the default install, it would be wise to run the client from another system on the network.

[mobcdi]

Hi Burke

Thanks for your reply and it did help in resolving my issue. I wasn't able to track it down to a particular strumbling block with the install but got to the configuration screen by propogating permissions for the install account to all child objects in the Orchestrator install directory. I also removed the "read-only" attribute flag and propogated that change as well. and restarted the "VMware vCenter Orchestrator Configuration" service 

In case it helps others here is a bit more detail

I am running in Win2008R2 64bit

My problem was I wasn't able to run the configuration on localhost:8282 to complete the vCO configuration which as of my reading of the documentation has to be completed on localhost first before clients from other systems can connect to vCO server to develop workflows

I un-installed just vCO 4.2.1 and reinstalled it again but the problem presisted including when running the installer as administrator. I also changed the install path back to the default but that didnt help either. By modifying the permissions to confirm the account used to install vCO had full permissions to all files and folder and propogating it to child objects in ../program files/VMware/Orchestrator/ as well as removing the read-only attribute and propogating that change I was able to get to the configuration webpage on http://localhost:8282/ After checking back the read-only attribute was partly reinstated (not all sub files/folders are marked as read-only but some are ) on /program files/VMware/Orchestrator/

[Burke-]

I just got settled back into my office after a trip... There is a KB regarding this overall issue here: http://kb.vmware.com/kb/2017578 - I have a lot on my plate (as usual after a trip) so this KB may or may not be helpful at this point. Good luck!