Starting Orchestrator server service fails with error 1053

[FSvcoe]

Hello all,

One of our VCO servers will not start the VMwareOrchestrator service, it returns the error above. It was running successfuly, but the VCO service account password expired, so I had to update it. I've checked the following:

- VCO service account enabled and correct password verified

- VCO service account member of local admin group for this server

- Re-ran VCO web config, all items configured and green status

- Able to connect successfully to VCO database and VirtualCenter server using the VCO Service account

The other interesting thing is I removed the server.log file, but it's not getting recreated when I try to restart the service.

Can anyone advise on what I might be missing with this config? Thanks.

[cdecanini_ · Accepted solution]

Locate the orchestrator.bat file and start it from the command line.

Christophe.

[FSvcoe]

Thanks for the help. Interesting..a bunch of files were missing from the 'Orchestrator\app-server\bin' folder, including this batch file. I copied them over from another server, ran the Orchestrator.bat file, however the service still would not start, although it took longer for it to time out. I had to go back in thru the web config and fix the IP as it was using the one from the source server than I had copied the files from.

Is running this .bat file documented somewhere as a troubleshooting measure? Is there some reason a group of files would suddenly disappear from this folder?

[cdecanini_]

Not sure if it is documented. The windows service is basicaly a wrapper starting vCO with the same parameters as does the batch file.

I have never noticed files being deleted. Have you run an upgrade ?

Christophe.

[FSvcoe]

No upgrade. I did notice the source server had 44 files in it; the one that wasn't woking had maybe 20. Very odd, no one that I know of logged in and changed anything, looked through the secuirty logs just to be sure.

[igorstoyanov]

This sounds very odd. Could you please let us know the exact version of vCO. Also, if there is a corruption of the files (not sure about the reason), probably backing up (export of configuration) and reinstall of vCO would be the best approach in such a situation.

Thanks.

[FSvcoe]

Igor,

It's version 4.1.0 build 581 Everything is running now, but I really don't know how these partial delete would have happened. If it re-occurs, I will post the symptoms again.

In the meantime, documenting what the Orchestrator.bat does would be helpful for troubleshooting. I can't imagine I'm the only one who has had to deal with this occuring. Thanks.

[igorstoyanov]

>It's version 4.1.0 build 581

This version and buld has been used for quite some time now but haven't had issues with missing files. There could be some issue but definitely it is extremely rare. Posting the use of the orchestrator.bat in the comunity in my opinion is already some form of documentation ;-). I would be a bit hesitant to have it in the official documents since this could be a source of confusion of how the vCO server is started on windows. We would take this suggestion into consideration thought.

Thanks for your feedback.

[CKitchens]

HI guys,

I just wanted to also say that we have run into this issue numerous times in our environment also. We have 3 VCO servers and each one has had the same issue eventually. I had to copy over the bin files and then restart the service to get vco back. We are on version 4.1. We can't seem to figure out what's deleting the files in the bin directory.    

[cdecanini_]

Is this on Windows ? If so have you checked the AV software ?

I have been running the appliance for many years and never had such an issue.