AlexAllenExpedi
Enthusiast
Enthusiast

vCO Unable run workflows - Log is being spammed with this message

2014-08-18 11:43:53.575-0400 [vcoInitializerScheduler-1] INFO  {} [VCOApplicationContextInitializer] The initial context is not active yet. Trying to establish a connection to the database again in 5s.

2014-08-18 11:43:53.587-0400 [vcoInitializerScheduler-1] INFO  {} [VCOApplicationContextInitializer] The initial context is not active yet. Trying to establish a connection to the database again in 5s.

2014-08-18 11:43:53.593-0400 [vcoInitializerScheduler-1] INFO  {} [VCOApplicationContextInitializer] The initial context is not active yet. Trying to establish a connection to the database again in 5s.

2014-08-18 11:43:58.076-0400 [vcoInitializerScheduler-1] INFO  {} [VCOApplicationContextInitializer] The initial context is not active yet. Trying to establish a connection to the database again in 5s.

2014-08-18 11:43:58.576-0400 [vcoInitializerScheduler-1] INFO  {} [VCOApplicationContextInitializer] The initial context is not active yet. Trying to establish a connection to the database again in 5s.

2014-08-18 11:43:58.587-0400 [vcoInitializerScheduler-1] INFO  {} [VCOApplicationContextInitializer] The initial context is not active yet. Trying to establish a connection to the database again in 5s.

2014-08-18 11:43:58.593-0400 [vcoInitializerScheduler-1] INFO  {} [VCOApplicationContextInitializer] The initial context is not active yet. Trying to establish a connection to the database again in 5s.

I have tried reapplying LDAP Creds
Reapplying vCenter Creds
Verified Licensing Information by reconnecting it to vCenter.

~Alex

0 Kudos
2 Replies
gkostova
VMware Employee
VMware Employee

Hi Alex,

Did you check the connection with your database, also the database credentials that you entered are valid? This info message appears while the server trying to establish the connection with your database. Also did the vco server came up at some moment? You can attach some server.log if further investigation is needed.

Regards,

Galina

AlexAllenExpedi
Enthusiast
Enthusiast

I rebooted the server and this seemed to have fixed itself. Thank you for your assistance.

0 Kudos