View 4.5 Event Database Configuration

[Poort443]

I have some trouble adding the View 4.5 event database. It's a SQL Express 2005 on the vCenter server. It's configured to listen to static port 1433. I use SQL authentication, and an SQL account. I've attached screenshots with the settings. I keep getting "an error occurred while attempting to configurate the database" Anybody here know what I'm doing wrong? I'm thinking maybe the database name should be in a different format, but I've tried different things without success.

Tia,

-Poort.

[PaulWoodhouse]

I had the same issue, switching to Mixed Authentication mode on the SQL Server resolved it for me.

[mclark]

I had issues getting this to work also, and my SQL server is also SQL 2005 Express on the vCenter server. Here's what worked for me in the end:

1) Do not specify anything except the server name (i.e. use vCenter.fqdn.com, do not use vCenter\SQLEXP_VIM)

2) Check SQL Server Configuration Manager. My SQL server was set for Dynamic ports. I changed IP1 in config manager to a static port but it still used dynamic ports, because the All IP section was set for that. Once I used the correct dynamic port that was listed there, it was fine.

3) I had to change the SQL server properties to use both Windows and SQL Authentication.

4) Make sure your SQL server configuration is set to allow remote IP connections.

[vBaw]

just another hint: You created the User as SQL user not as local or AD User?

[riki78]

we have also problems with adding sql.

I have created a SQL Database: "view_events" on a SQL 2008 Server (Server 2008 R2)

I have added a SQL User in the management studio

I have set SQL to mixed mode

but still not luck

what i can check yet? how i can find logs?

Simon

[LarryBlanco2]

I'm in the same boat.

I have followed the documentation to the T. created a DB, created a user account for it, enabled sql/win auth. enabled IP on the config mgr. but no dice.

Larry B.

[mclark]

I followed everything also. The final thing I found that I had to deal with was dynamic IP ports in SQL server. I had to go to SQL Configuration Manager on the SQL server, and in the All IP section, you may see a dymanic port listed there, like 49800 or 51560 or whatever. Go into the event DB configuration dialog for View and change 1433 to what you found in the Dynamic Port value in SQL. That was the final piece that made it work for me.

You also have to make sure that the SQL user you create for the ViewEvents DB is a dbowner of the database.

[Poort443]

Everybody, thanks for the suggestions. They were helpful, but did not solve the problem. I checked the logs on the connection server ( C:\programdata\VMware\VDM\logs). Looking into these I found: "The specified schema name "dbo" either does not exist or you do not have permission to use it". I don't know why that is, but in SQL Admin I gave the account that I use all permissions on de dbo schema of my database. This finally solved my problem.

Regards,

-Poort

[LarryBlanco2]

Worked for me as well.

1) Setup the sql server to use sql server and windows auth. Create SQL user and gave user dbo permissions.

2) Verified that, under config manager, TCP/IP is enabled and that the port is set to static 1433 (MSSQL) and IP1 or IP2 is on and with the ip address of the DB server.

3) Entered the information in to the Event Configuration as follows:

3.1) Server name: (FQDN) DBServer.vmware.com

3.2) Port: 1433

3.3) DB name: VMVEVT

3.4) UserName: VMVEVT

3.5) Password: VMVEVTDB

3.6) Password: VMVEVTDB

3.7) Prefix: vmvevt

And it just came up without any errors.

[six4rm]

I can't for the life of me get this bloody Event Database config to work! I'm trying to do exactly the same and install the database on SQL Express running on my vCenter Server. I've created a database called VEDB and a user called vmview. SQL & Windows authentication is enabled within SQL Express. I've attached the TCP/IP settings as I'm not too sure about them and I'm thinking that's where the problem could lie. I'm also not too sure about the user permissions, so if someone could point me in the right direction there that would be very much appreciated. Within User Properties -> User Mapping, I have 'Map' ticked next to the VEDB database and then all roles ticked underneath. I'm using the following information within the View config:

DB Server: vcview.domain.com (using the FQDN)

Type: SQL

Port: 59717 (from TCP/IP settings, IPAll Dynamic Port)

Username: vmview

Password: (User Password)

The error I'm getting is the same as Poorts screenshot.

Please help!!

[mclark]

The TCP/IP port looks right. You selected the dynamic port shown at the bottom, which is what I did.

The only other thing I can think of is the rights the user vmview has to the VEDB database. You said that in User Mapping you have all the rights checked under Database Role Memberships. You should have ONLY 'db_owner' and 'public' checked. All others should not be marked. Also, under Default Schema in the top list, you should probably have 'dbo' as the schema for the vmview user.

You might also check the TCP/IP protocol in the SQL Server Configuration Manager and make sure that it allows connections, so that outside computers are allowed to talk to it.

[six4rm]

Thanks for the swift response.

OK, so I've changed the user properties as can be seen within the attached screenshot. I'm still getting the same error.

I'm not quite sure where to look within SQL Server Configuration Manager to check whether it is allowing connections other than my previous screenshots.

[mclark]

The screenshots in your prior posts show that you have one part enabled:

Start -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> SQL Server Configuration Manager

Under SQL Server 2005 Network Configuration -> Protocols for SQLEXP_VIM, TCP/IP should be enabled.

Also check the following:

Start -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools ->SQL Server Surface Area Configuration

Select the Surface Area Configuration for Services and Connections link

SQLEXP_VIM -> Database Engine -> Remote Connections

I have 'Local and Remote connections' marked, then under that 'Using both TC/IP and named pipes'

[six4rm]

Cool cool. I've checked both areas and they are configured as you've said.

I've just checked the firewall settings on this server, see attached. I'm a bit concerned about the "Block all connections to programs that are not on the list of allowed programs." statement. SQL certainly doesn't appear in the list. I assumed that with the firewall off that everything was open?

[mclark]

if the firewall is off then whatever else it says doesn't matter. From your screenshot the server is open. However, that brings up a good point. Do you have a network firewall that might be blocking this server? If so, you might need to check with your network people to see if the network firewall log shows any blocks to or from that server going to your View server.

[six4rm]

OK, that clears that up then.

No network firewall. The View Connection Server & vCenter Server are both VMs within the same environment. I can definitely ping between both servers.

[mclark · Accepted solution]

The OP said that he found errors in a log on the Connection Server that helped solve the problem. Can you look on your Connection Server in C:\programdata\VMware\VDM\logs and see if any of the logs provide any more insight on what it doesn't like about the configuration?

[six4rm]

Morning mclark.

Thanks for your continued support.

I did have a brief look at the log files previously but couldn't see anything obvious. There's two log files in the logs directory with todays date. One called log and the other debug. The debug one is filling up rapidly. I opened the debug file before attempting to connect to the Event DB and then again afterwards and copied down the additional entries.

Searching for "event" and the vCenter Server name "vcview" returns no entries.

[Poort443]

I noticed this in your log:

"SQL exception when connecting to database: Login failed for user 'vmview'. Reason: The password of the account must be changed."

Check the vmwview account at Security / Logins. See if "User must change password.." is checked.

-Poort

[six4rm]

Thanks for revisiting your post Poort.

I'm incredibly happy to say that you have resolved my issue.

I had enforce password policy and enforce password expiration ticked without really thinking about it. Despite being greyed out, 'user must change password at next login' was also ticked hence why it wasn't authenticating. I have now unticked the three boxes and all is now well.

SQL isn't my thing so it's been a bit of a learning curve to say the least!

Thank you both so much for all your help.