451Solutionscom
Contributor
Contributor

Receiving Orchestrator Server Service error 1053

After installing vCenter Server, I am unable to get the vCenter Orchestrator Server Service to start. I receive the error 1053: The service did not respond to the start or control request in a timely fashion.

I've searched around the site here and none of the suggested fixes worked. I'm running Windows Server 2008 R2 Standard and the vCenter Server is running perfectly. The only service that will not start is the Orchestrator.

I've tried uninstalling and reinstalling the service multiple times as well as a few other suggested troubleshooting tips. Has anyone else had this issue as well?

0 Kudos
11 Replies
Andreas_Diemer
Enthusiast
Enthusiast

Hi 451Solutionscom,

After installing & configuring vSphere Server the vCO Service must be configured separate using the WebConfig. Did you configure the vCO?

Log in to http://:8282 with user and password "vmware" and configure VCO.

Regards, Andreas

-


dont't forget to award points if answer is helpful

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
0 Kudos
451Solutionscom
Contributor
Contributor

Thank you for your response.

I've configured the vCO and have all green lights. When I attempt to start the server from the vCO configuration the web application sits in "Server is starting." for between 10 and 15 minutes before going back to stopped.

I'm attempting to get some logs to post, but it seems that I can't get the log interface to update within the web application. Either that or nothing is being written to the log when I attempt to start the service.

Here is the last warning message I've received from the log;

2010-09-23 15:04:05.948-0400 WARN Plugin config file 'o11nplugin-vsphere41.dar' : SAX parsing exception 'Key 'linked-enumeration' with value 'HostSystemConnectionState' not found for identity constraint of element 'module'.'

Since that message there is nothing in the log.

0 Kudos
Andreas_Diemer
Enthusiast
Enthusiast

Hi,

I will try rebuild this on my system - how is yout vCO configured?

  • stand alone or on vCenter

  • Version

  • used vCO Database

-


if answers are helpful, please award points

Regards,

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
0 Kudos
451Solutionscom
Contributor
Contributor

It's an extremely vanilla configuration.

I used the included SQL Express, so the database is running on the same machine as vCenter.

The vCenter version is 4.1

Default Database (VIM_VCDB)

0 Kudos
Andreas_Diemer
Enthusiast
Enthusiast

Hi,

I've just installed a new VM W2k8-STD-64, fully updated, domain join, install vSphere.

After configuring vSphere and vCO (all green), same effect as your server.

Eventlog: The VMware vCenter Orchestrator Server service terminated with service-specific error Incorrect function..

Event-ID 7024

I've used an other DB on a SQL2008 - exact same problem.

Does anybody know this error or behavior??

I'll try other config....

-


if answers are helpful, please award points

Regards,

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
451Solutionscom
Contributor
Contributor

I'm glad to see that I didn't mess something up.

Should I contact VMWare for this issue or do support people browse these forums?

0 Kudos
Andreas_Diemer
Enthusiast
Enthusiast

Hi,

shame on me.

After RTFM:

  • page 16: you must use a separate DB

  • page 58: stand alone 2GB, on vCenter 4GB

I've build the same small vanilla server just for test and with low MEM - after adding 3GB RAM --> IT RUNS

I will test how deep I can go. Normally I use a stand alone and my system has 2GB, so it works.

-


if answers are helpful, please award points

Regards,

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
0 Kudos
admin
Immortal
Immortal

Hi,

had the same error with SQL 2008 express. Using the Database from the vCenter Server works (see screenshot). Also there are possible ways to limit the java memory usage in the apache tomcat config. In most cases with small memory amount the JVM consumption stops the service...

best regards

Christian

0 Kudos
Andreas_Diemer
Enthusiast
Enthusiast

Hi,

is your problem solved? --> pls close your discussion - for helpful anserwers award points.

Are there additional questions? --> let us know how we can help you.

-


Regards,

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
0 Kudos
Asru
Contributor
Contributor

Thanks, it worked after setting ram from 1.5GB to 4GB.

0 Kudos
SteveAdmin
Contributor
Contributor

I have same problem with start vCenter service.

But now i know that problem with low RAM.

Thanks , will add and letting you know

0 Kudos