I’ve been hunting this problem down for almost a week now, and was finally able to resolve the issue.
Having spoken to others, not sure why we were affected by this, but I suppose that is life, and if nothing else, I got to dig into the weeds with the View Event DB configuration.
We’ve apparently been having this problem for some time, but it only recently was brought to my attention. We have been trying to add an Event DB to our view configuration, which comes in quite handy when it’s working correctly. Problem is, every time we’ve tried to add it, we’ve gotten an error:
An error occurred while attempting to configure the database. Double check the database parameters and ensure that the database is not down, restarting, or otherwise unavailable.
So, right off, tried to make sure the my db was good. Made sure db was up and running. Used SQL Server Studio to verify connectivity, check. Used ODBC to check connectivity, check. All was well with the db itself.
So, I went back into the view server and tried again, making sure all the configuration was correct. In case you don’t know, the config screen is below as well.
Check. All looks good here, but still no love from View. Started poking around into every log I could find, and found some interesting messages in the catalina log (\VMware\VMware View\Server\broker\logs\catalina-*.log).
Nov 17, 2011 8:42:44 AM com.microsoft.sqlserver.jdbc.TDSReader readPacket
WARNING: TDSReader@40e830ec ( ConnectionID:4 TransactionID:0×0000000000000000) Unexpected message type:18 in TDS header; expected type:4
Nov 17, 2011 8:42:44 AM com.microsoft.sqlserver.jdbc.TDSReader throwInvalidTDS
SEVERE: TDSReader@40e830ec ( ConnectionID:4 TransactionID:0×0000000000000000) got unexpected value in TDS response at offset:4088
Nov 17, 2011 8:42:44 AM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
WARNING: TDSChannel ( ConnectionID:4 TransactionID:0×0000000000000000) SSL handshake failed: The TDS protocol stream is not valid.
That lead me to find an interesting KB article which specifically referenced a similar issue, but with the Management WebServices on vCenter, and not specifically for the View Connection Servers. Regardless, the idea was to update the SQL Server JDBC 1.2 driver to the version 2 driver from Microsoft, Driver located here.
Downloaded the file, and extracted, which gave me a few folders with some DLL’s in it, and 2 jar files in the Microsoft SQL Server JDBC Driver 2.0\sqljdbc_2.0\enu folder, sqljdbc.jar and sqljdbc.jar.
Since nothing else appears to be using this jar file, I may as well give it a shot.
- Took a snapshot on my connection server
- Shutdown the ‘VMware View Connection Server’ service.
- Went into the jar library (<install_dir>\VMware\VMware View\Server\broker\shared\lib), moved the existing driver (sqljdbc-1.2.jar) to another location
- Dropped in the sqljdbc.jar file from the extracted location earlier.
- Started the ‘VMware View Connection Server’ service.
Now, log back in, and. . . . Still no good. Almost had it. Went back to the catalina log, and found some new errors, getting closer I think.
Nov 18, 2011 9:56:54 AM com.microsoft.sqlserver.jdbc.SQLServerConnection <init>
SEVERE: Java Runtime Environment (JRE) version 1.6 is not supported by this driver. Use the sqljdbc4.jar class library, which provides support for JDBC 4.0.
Looks like I need the other file from that download sqljdbc4.jar. It’s very handy that file is actually mentioned. So, following the steps from above, I remove the sqljdbc.jar, and drop in sqljdbc4.jar.
Success!
-KjB
