I’ve just updated my BES server to 7.0.7.96 from 7.0.1.376. The installation seemed to go through OK and there were no errors, but now all clients are greyed out in the console list. They haven’t reported in since shortly after the upgrade. The database is on a separate SQL server, and I’ve checked that I can connect to it from the BES server via the DSNs. The BESDiagnostics utility has green lights apart from ‘Checking that TCP/IP is enabled on SQL server’ which has a yellow light. However, it was like this before the upgrade.
The three ways the DSN connection usually get messed up are:
Pointing to the local server instead of the remote server. Set the DSN’s to point to the correct server.
Database permissions get lost. If you used NT Authentication, ensure that the FillDB and GatherDB services are still running as your user. If using SQL, ensure the registry keys are in place.
Pointing to the wrong database on the server. The DSN’s bes_bfenterprise and bes_EntepriseServer go to the BFEnterprise database, the LocalBESReportingServer DSN goes to the BESReporting database.
If you still can’t get it, check the FillDB log for error messages and post them here.
Thank-you both for your advice. I looked in the logs and found this error message:
Unexpected exception: Database Error:
Microsoft
ODBC SQL Server Driver
SQL Server
Login failed for user ‘’. The user is not associated with a trusted SQL Server connection. (28000:18452)
I had a look through the registry, but couldn’t spot any keys where the user and password were incorrect. I compared the registry to an export taken before the upgrade and found that this key had disappeared: