Unable to login to server

Usage and Config Platform
1

(imported topic written by Federico.Vietti)

Dear All,

I’ve launched the upgrade of TEM server thorugh TEM fixlet/action to the last version.

But now, when I try to login with the console I receive the following error: “Unable to login to server. Have you run BESAdmin to create the signing key on the server?”

I’ve tryed to use the BESAdmin but inserting the sa credential I cannot logon to the DB.

Any ideas? What can I do to verify?

thank you

2

(imported comment written by Federico.Vietti)

Othe information.

In the BESRelay.log I have the following error:

Tue, 17 Dec 2013 10:01:49 +0100 - Main Thread (1412) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [53]. (08001:53)

[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (08001:53)

[Microsoft][SQL Server Native Client 10.0]Login timeout expired (S1T00:0)

Tue, 17 Dec 2013 10:01:49 +0100 - Main Thread (1412) - Will retry in 5 seconds

3

(imported comment written by Tim.Rice)

On your server, are all the services running? Is the SQL server local or on a different box?

4

(imported comment written by o6soloist)

I am having the same problem and Yes all the services are running

5

(imported comment written by vincent.h)

o6soloist, did you also perform the upgrade?

Can you provide more details on the issue you are having? Is your SQL server local or running remote?

Check your DSNs to make sure that remote connections to the SQL server still work.

6

(imported comment written by Alex Alas)

Hello to all,

I am having the same issue. In my case the SQL instance is local and all BES services are up and running. When I run BESAdmin,I got a pop-up window with the following “In order to run IBM Endpoint Manager Administration Tool, you need to specify the location of the site level signing key for the database you would like to administer”. When I enter the password (and I know is the correct one), it comes back with an error saying “Incorrect password or Error reading private key file. Please try again”

By the way, I am running BES on a Windows SErver 2003 R2 SP2 and also running on MS SQL Express 2008.

7

(imported comment written by Niraj Kumar Mishra)

Hi Alex,

Are you able to telnet “dbserver hostname” 1433 from bigfix server machine. If both sql and bigfix installed on same machine… please “telnet localhost 1433”. let me know the result.

Thanks

Niraj

8

(imported comment written by Alex Alas)

Hello Niraj,

Thanks for your quick response. Both SQL and BigFix are installed on the same box but I cannot telnet using command as specified “telnet localhost 1433”. Since the telnet services, due to my rigid configuration compliance, had been disabled while ago, even before installing BigFix on it. I don’t know if this limitation might affecting my deployment now that I pushed the upgrade.

Thanks for your help,

Alex

9

(imported comment written by Niraj Kumar Mishra)

Hi Alex,

If you can’t to do the telnet… can you please check in regedit for odbc connection information.

Below is the registry path:

HKLM\SOFTWARE\Wow6432Node\ODBC\ODBC.INI

There is four key:

bes_bfenterprise

enterprise_setup

LocalBESReportingServer

ODBC Data Sources

Thanks

Niraj

10

(imported comment written by Alex Alas)

This is not a 64 bit box, sorry I was not explicit enough before. It’s a Windows 2003 Server R2 SP2 Enterprise (32 bit ed).

11

(imported comment written by Niraj Kumar Mishra)

Ok… can you please check those registry key ? else run bes diagonostic tool and check that all are green.

12

(imported comment written by Alex Alas)

I found them at HKLM\SOFTWARE\ODBC\ODBC.INI but this location also had other values;

  • bes_EnterpriseServer

  • MQIS

  • ODBC File DSN

13

(imported comment written by Niraj Kumar Mishra)

what is showing for bes_EnterpriseServer ? show me print snap for this as well as for bes diagnostic tool.

14

(imported comment written by Alex Alas)

Niraj,

I got print screens as requested, I edited some, mostly removing any private information. I forgot to mention but this server is part of a private network with no access to the Internet. All updates are done using the air-gapped process.

Alex

15

(imported comment written by Niraj Kumar Mishra)

So Finally I got your problem.

p

Please enable the tcpip as show in attached image. you have restart all sql services. Then check again in bes diagnostic tool.

This will resolve the problem 100%.

Thanks

Niraj

16

(imported comment written by Niraj Kumar Mishra)

I mean after enabling the tcpip… you have to restart the sql services.

17

(imported comment written by Alex Alas)

Good Morning Niraj,

TCP/IP was enabled but I disabled/re-enabled it then restart SQL services. Same thing, same error messages. I attached an image of how I found the TCP/IP already enabled.

Alex

18

(imported comment written by Niraj Kumar Mishra)

Hi Alex,

Very good morning to you. Hope You are doing good.

Can you please also check under the SQL Server Network Configuration as shown in attched snapshot.

Thanks

Niraj

19

(imported comment written by Alex Alas)

Niraj,

I am sending a snapshot of the same exact setting you requested to be checked in my SQL Server Network Configuration, of course I edited to remove any identifiable information.

Thanks for your help,

V/R,

Alex

20

(imported comment written by Alex Alas)

Niraj,

Where you able to open my previous attachment?

If not please let me know?

Alex