VMware Cloud Community
suhaimim
Enthusiast
Enthusiast

Database error

Dear Supporter,

I am installing vCenter Orchestra inside vCenter. Database using MQSL 2005 Express.

This is the error:

Unknown host: Error when connecting to host /172.15.1.1, port 1433: Connection refused: connect

Here I attach the vmoconfig file.

Your support on this matter is highly appreciated.

Regards,

Tags (3)
Reply
0 Kudos
16 Replies
suhaimim
Enthusiast
Enthusiast

I did as per KB instructions. After restart the SQL service and re-apply the orchestra database, this error has been shown:

Cannot connect to jdbc:jtds:sqlserver://172.15.1.1:1433/SQL  Server;instance=SQLEXP_VIM;useNTLMv2=true. Connection error was: Login  failed for user 'administrator'. The user is not associated with a  trusted SQL Server connection.

Any info how to confirm or create the admin account? and how to make the account associated?

Reply
0 Kudos
tschoergez
Leadership
Leadership

ok, here we come to the difficult point, because it depends (as usual 🙂 😞

Is the server running the database a domain member? Do you use a local admin or a domain admin? was the SQL express installed before or after Domain Join? .....

To speed it up: Download the SQL Management Studio Express (from Microsoft, it's free), and try to figure out the proper credentials this way.

As workaround: Reconfigure SQL-Express that it allows SQL Authentication, then you can create a new SQL-User (like vcodbuser) completly independend from any windows stuff.

guide: http://eduzine.edujini-labs.com/archives/24-HOWTO-Configure-Microsoft-SQL-Server-for-Mixed-Mode-Auth... (old one, but it should point you in the proper direction...)

Cheers,

Joerg

suhaimim
Enthusiast
Enthusiast

Thank you for your information sharing regarding this problem.

However, the problem is not yet solved. After following the 2005 SQL Express re-configuration, here is the error:

Cannot connect to  jdbc:jtds:sqlserver://172.15.1.1:1433/SQLEXP_VIM;instance=SQLEXP_VIM;useNTLMv2=true.  Connection error was: Cannot open database "SQLEXP_VIM" requested by  the login. The login failed.

It seems that problem in login or database name, but I cant check what is the appropriate one.

Any advice on how to fix it?

orchestra_01.jpg

Reply
0 Kudos
suhaimim
Enthusiast
Enthusiast

According to manual/guide, no details regarding database connection setup with SQL Server.

It seem required MySQL (but for evaluation) .... any idea what its mean?

Here the manual screenshot.

orchestra_02.jpg

Reply
0 Kudos
tschoergez
Leadership
Leadership

Well, the error message is clear: the given username/password is not allowed to login to this database.

To to ensure: start SQL Management Studio express on the vco-server, and try to login with it.

(I expect, that also does'nt work).

So you have to double check the permissions on the SQL Server...

BTW.: The chapter about MySQL in the Install-Guide has nothing to do with it, it's just if you want to use an (unsupported) MySQL-instance as database.

The MS SQL Server is supported and works out of the box (if the permissions are correct :smileydevil::smileygrin:)

Regards,

Joerg

Reply
0 Kudos
suhaimim
Enthusiast
Enthusiast

Thanks again tschoergez! Smiley Wink

Yes, we are nearly to solve the problem.

Here is the screen shot of MSSQL database session via CLI:

orchestra_03.jpg

I can access the database with login and password via CLI. But not to orchestra web interface.

Is the any method to confirm account via CLI & via orchestra using the same database engine?

Regarding MySQL - clear - case ignore.

Reply
0 Kudos
Burke-
VMware Employee
VMware Employee

From the error you have posted in this latest msg, it seems you are trying to connect to a DATABASE named "SQLEXP_VIM" in instance "SQLEXP_VIM". This is not common as a you typically create a new Database in the "SQLEXP_VIM" instance named "vco" or similar... so your connection string would be more like:

jdbc:jtds:sqlserver://172.15.1.1:1433/VCO;instance=SQLEXP_VIM;useNTLMv2=true

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
Reply
0 Kudos
tschoergez
Leadership
Leadership

good point, Burke! 🙂

brings me to another idea: If I remember right : You have to leave the instance-name blank when using the default SQL express installation (even if it's a named instance from SQL-perspective).

Database-name has to be specified of course (and an empty database must exist on the server)

Cheers,

Joerg

Reply
0 Kudos
mcssschaefer
Enthusiast
Enthusiast

Hi suhaimin,

the problem is related to the MSSQL express editions. You have to set port 1433 in express editions manualy, this is a common pitfall.

  1. Start SQL Server Configuration Manager
  2. Select SQL Server 2005-Network Configuration
  3. Select protocols for SQLEXPRESS
  4. Right-Click TCP/IP -> Activate
  5. Right-Click TCP/IP ->Properties
  6. Select tab IP-Adresses
  7. Set TCP-Port / IPAll Port 1433 (see picture below, this is the common pitfall)

sql2005-tcp-ip-konfiguration.jpg

http://blog.mightycare.de http://www.mightycare.de
Reply
0 Kudos
suhaimim
Enthusiast
Enthusiast

Hi Burke,

Glad you are willing to support me on this matter.

I did as per advised, however, the problem has not solved yet.

(maybe I lost the way on how to troubleshoot them)

The error was same:

(connection error, cannot login database, login failed)

next post, I will attach the MSSQL screenshot.

Reply
0 Kudos
suhaimim
Enthusiast
Enthusiast

Hi mcssschaefer,

Thanks for your advise. I did the configuration, but the problem was same.

Here I attach the screenshot.

vCO_01.jpg

vCO_02.jpg

Reply
0 Kudos
mcssschaefer
Enthusiast
Enthusiast

Hi,

have you restarted your mssql service after changing the listening ports?

At first It would be great if you can verify that mssql is listening on port 1433 with i.e. " netstat -anb -p tcp" (CMD) or "netstat -anb -p tcp|select-string 1433" (PS).

http://blog.mightycare.de http://www.mightycare.de
Reply
0 Kudos
suhaimim
Enthusiast
Enthusiast

Hi,

1. Service restart - done after each modification

2. Port listening:

TCP: 0.0.0.0:1433          LISTENING

TCP: 127.0.0.1:1433         ESTABLISHED

Reply
0 Kudos
mcssschaefer
Enthusiast
Enthusiast

Hi,

okay, firewall is configured correctly? Have you tested to access the mssql service from an other server with sql managament studio with the same credentials you have configured at the orchestrator configuration interface? Do you use windows- or mixedmode authentication?

http://blog.mightycare.de http://www.mightycare.de
Reply
0 Kudos
suhaimim
Enthusiast
Enthusiast

Dear All,

Finnally, I just reformat my server.

OS - W2K8R2x64 Std.

And do fresh vCenter installation.

So far, work fine.

Thanks guy.

Reply
0 Kudos