Search This Blog

Thursday, August 20, 2015

VMware vCenter Server SQL problems

When installing vCenter server and you plan to use a external SQL 2012 server, you might see this error even though you already created the required System DSN:

No system DSNs were found on this machine. Please create a DSN for your external database, and click the refresh button.

image

One thing to be aware of is that the driver used must be SQL Server Native Client, not the build in SQL Server or ODBC Driver 11 for SQL Server:

image

You can find the SQL Server Native Client here:

Microsoft® SQL Server® 2012 Feature Pack

Under Install Instructions scroll down to the native client and download (x64):

image

Direct download link as of 09-07-2015) http://go.microsoft.com/fwlink/?LinkID=239648&clcid=0x409

If you by mistake installed Microsoft ODBC Driver 11 for SQL Server uninstall it, you don’t need it:

image

In Programs and Features you only need Microsoft SQL Server 2012 Native Client as shown here:

image

And then when the DSN is available and you click next you might get this error:

The user associated with the DSN has insufficient privileges. Please provide sufficient privileges for the user by granting the user the following permissions:

* VIEW SERVER STATE

* VIEW ANY DEFINITION

image

Let’s do as we are told. On the SQL Management Studio right click on the SQL Server in question and select properties:

image

Select Permissions, select the service account used by the vCenter service and Grant View any definition and View Server state:

image

You specified the service account right before selecting the DSN in the installation:

image

And finally the last problem I have chosen to present here is this error:

The user associated with the DSN has insufficient privileges. Please provide sufficient privileges for the user by granting the user the following permissions:

* SELECT msdb..sysjobs

* SELECT msdb..sysjobsteps

……………..

image

As we probably all can see the is related to msdb access, again in SQL Management Studio, select Security – Logins at the SQL server in Question.

Select the service account used by the vCenter service and select Properties:

image

Select User Mapping. In Users mapped to this login select the msdb database and select db_owner as role membership:

image

Now you should be able to get past the database settings and on to Configure Ports:

image

11 comments:

  1. That helps me to resolve the issue.
    Great thanks!

    ReplyDelete
  2. thanks, this page definitely helped me..i was experiencing all of the above issues.

    ReplyDelete
  3. Thank you this was very helpful!

    ReplyDelete
  4. Awesome details. I ran into several of these issues (No system DSNs found and Insufficient privileges) and was able to resolve them following your instructions. Thanks

    ReplyDelete
  5. Great Post....very helpful!

    ReplyDelete
  6. Thank you!!!!

    ReplyDelete
  7. Thank you! In case anyone can't find the match services account let's try to grand permission to vpxuser, my post here: https://jaxvn.wordpress.com/2016/09/27/upgrade-vcenter-5-5-to-6-0-u2/

    ReplyDelete
  8. thanks a lot from me as well.

    ReplyDelete
  9. Perfect explanation! Thank you!

    ReplyDelete
  10. We ran into issues as well with the upgrade and this document helped us. Thanks, Wim

    ReplyDelete
  11. This helped me in the past and just helped me again. Installed fresh vCenter 6.7 on fresh SQL express named instance. Created empty db and pointed to it within mentioned ODBC. All went through. Bookmarked your article url this time, so wont have to crawl search engine again when needed.

    ReplyDelete