Foglight Management Server does not start - ERROR: "The TDS protocol stream is not valid" (4259357)

The Foglight Management Server does not start. In the log files the following error can be found

2012-05-21 14:23:53.348 ERROR [main] com.microsoft.sqlserver.jdbc.TDS.TOKEN - TDSReader@38f18cc3 ( ConnectionID:1 TransactionID:0x1100000036000000): FetchBufferTokenHandler: Encountered unexpected unknown token (0x0)
2012-05-21 14:23:53.348 ERROR [main] com.microsoft.sqlserver.jdbc.TDSReader - TDSReader@38f18cc3 ( ConnectionID:1 TransactionID:0x1100000036000000) got unexpected value in TDS response at offset:5833
2012-05-21 14:23:53.363 WARN [main] org.hibernate.jdbc.AbstractBatcher - exception clearing maxRows/queryTimeout
com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
[...]
2012-05-21 14:23:53.488 WARN [main] org.jboss.system.ServiceController - Problem starting service com.quest.nitro:service=SpringBootstrap
org.springframework.beans.factory.access.BootstrapException: Unable to initialize group definition. Group resource name [classpath*:com/quest/nitro/service/core-beanref.ctx.xml], factory key [foglight-core-services]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'foglight-core-services-mbeans' defined in URL [jar:file:/C:/Quest_Software/Foglight/server/default/tmp/deploy/tmp4647399188840656004foglight.sar!/com/quest/nitro/service/core-beanref.ctx.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'exporter' defined in class path resource [com/quest/nitro/service/common.ctx.xml]: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '

Unknown

Reboot the FMS server solves the issue.