Hi vCO Experts,
We configured a (working!) vCO appliance with MSSQL Server as the database. After rebooting the appliance, the licensing manager appears to throw an error - first we look for configuration under /var/lib/vco/app-server/temp/dars/o11nplugin-vsphere.dar/resources/licenses, then get a SQLException from the database looking for licenses!
Here's the start of the exception:
2014-04-04 14:31:58.426-0400 [Loading : o11nplugin-vsphere.dar] DEBUG {} [PluginConfigurationElement] No Valid License available in /var/lib/vco/app-server/temp/dars/o11nplugin-vsphere.dar/resources/licenses
2014-04-04 14:31:58.567-0400 [http-bio-142.42.194.85-8281-exec-5] ERROR {} [Config_KeyStore] getKeystoreManager() -->
java.sql.SQLException: Network error IOException: Connection refused
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:410)
at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
[continued grumbling]
Under the configuration UI, under "database", we see that the database installation is marked "up to date", but the error received when attempting to connect is:
Cannot connect to jdbc:jtds:sqlserver://<servername>:1433/<databasename>;domain=<domain>;instance=<instancename>. Network error IOException: Connection refused
Has anybody else seen this before? I'm at my wits end trying to troubleshoot this. Is my database corrupt (can't read from database as part of the getKeystoreManager() function?), is my vCO corrupt (can't read from /var/lib/vco/app-server/temp/dars/o11nplugin-vsphere.dar/resources/licenses?)
Keep in mind that this database was working before, so my configuration parameters on the database should not have changed. Added onto this, I'm able to make a connection to this database from a network-adjacent machine, and the database is on the same network as the vCO appliance (so, no firewall changes). For your information, we connect using Windows Authentication, to the database server's fqdn over port 1433, using a specified instance and database name. The domain is specified as <domain>.com as per the installation instructions. All of these things worked before, it broke upon rebooting the vCO appliance after experiencing directory issues (resolved after the reboot). vCO is 5.5.0 build 1281930, with plugins installed from the vCAC-embedded vCO (including the vCenter plugin).
Anything you can do to help would be spectacular.
Any ideas you have would be a great help.