8.2.1093 Gether Problems

(imported topic written by SystemAdmin)

Hi All,

I have just installed T.E.M. 8.2.1093 on a new Windows 2008 server, with a new licence key for the new server name. Everything installed fine and the Server Diagnostics Tool shows all green lights (especially the ‘Verifying that the BESGather service can reach the Internet’ bit). It has also sucessfully managed to ‘gather’ the BES Support content.

However, whenever I try and enable a external site within the Licence Overview dashboard I get and error about the Gather Service not being able to connect to the internet (I’ve attached a screen shot). I have verified the the URL’s aren’t being blocked by our proxies ( I guess they are still the same URL for 8.2.1093 - http://sync.bigfix.com/cgi-bin/bfgather/bessupport ).

I am also getting the followind errors in the GatherDB.log in the Bigfix Server installation directory:-

Tue, 13 Mar 2012 11:16:36 +0000 – Database Error:

Microsoft

SQL Native Client

Named Pipes Provider: Could not open a connection to SQL Server [2]. (08001:2)

Microsoft

SQL Native Client

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (08001:2)

Microsoft

SQL Native Client

Login timeout expired (S1T00:0)

Tue, 13 Mar 2012 11:16:36 +0000 – Disconnecting from database; will reconnect in 10 seconds.

Tue, 13 Mar 2012 11:16:52 +0000 – OpenSSL Initialized (Non-FIPS Mode)

And also these messages in the gather.log:-

I’m guessing I’ve missed something in the installation docs. But I can’t find anything!

Any help would be gratefully implemented.

Thanks, Mark.

(imported comment written by BenKus)

Hi Cidermark,

It might have been related to a temporary network slowdown this morning… Can you verify if it is still an issue?

Ben

(imported comment written by SystemAdmin)

Hi Ben,

Sorry for the dealy in replying to your question, I’ve been working with Doug Coburn to try and resolve. The Database connection error in the gatherdb.log was a red herring.

Will post a solution if/when I get one.

Mark.