Experiencing "Internal View Composer Error" in Admin after upgrading.

[vmnoobee]

First, we have been using the 4.0 View trial version and our time was up so we had to upgrade the connection server, composer, and vsphere client to 5.0 since 4.0 versions where unavailable. Upgrade was completed and everything worked afterwards. Shut the machines down and moved them to another host and since then we are getting an error message stating "Internal View Composer Error" that pops up when we try to add a pool, it appears at the Guest customization where you would choose a domain. Also it is showing in the admin  under View Composer Server that "The service is not working properly" referencing https://composerserver:18443. Havent found any helpful info online as of yet.

[mittim12]

It seems that the View Connection broker is having issues communicating with the View compsor service installed on your vCenter box. 

[vmnoobee]

Where/how can I check this communication breakdown?

Thanks,

Kevin

[mittim12]

You can make sure the composer service is running on the vCenter box, make sure there are no firewalls between the two boxes that may block communication and make sure you are using correct user accounts to link vCenter.

[vmnoobee]

All the services are running, no firewall changes have been made or are blocking on either machines and we checked the user accounts running the services. Are there any other specific places to check the user accounts further?

[mittim12]

You can check the log files.  You can find the location in this KB article,  http://kb.vmware.com/kb/1027744.   Also what version of compsoer are you running?

[vmnoobee]

We are running composer 2.7.