vCenter plugin registration failing

[Dan_265]

vCenter Server v. 5.0.0, build 755629

We have (2) CS500 arrays, both running 2.2.8

Registration of the plugin from either array1 OR array2 works just fine, but not both.  Basically, whichever array is the second array to attempt to register fails and crashes the vcenter service on the vcenter server.

The windows application event log contains the following...

An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) "ODBC error: (23000) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Violation of PRIMARY KEY constraint 'PK_VPX_EXT_PRIVS'. Cannot insert duplicate key in object 'dbo.VPX_EXT_PRIVS'. The duplicate key value is (NIMBLESTORAGE.Datastore.com.nimblestorage.hi.View)." is returned when executing SQL statement "INSERT INTO VPX_EXT_PRIVS WITH (ROWLOCK) (PRIV_ID, EXT_ID, GROUP_NAME) VALUES (?, ?, ?)"

Has anyone seen or experienced this?

[Valdereth]

Are these two arrays in separate Nimble Groups, or under a single Group?

[Dan_265]

Two arrays in separate groups.

[Valdereth]

Do both groups have unique values?  (group name, ip addresses, array names, etc)

[Dan_265]

Yes, all unique names and addresses.

[Valdereth]

Hmm... my understanding is that when you register two unique groups with one vCenter Server you should see a tab for each group within the vSphere client.  Have you contacted support to see what they recommend?  Post back what the resolution is, I'm curious to hear what could be causing this!

[rshekar42 · Accepted solution]

Could you please check this VMware KB: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1017978

Although the KB does not indicate the issue affects vCenter Server 5.0, one possibility is that your vCenter server is an upgrade from an older version like 2.5.

If you have another instance of vCenter running a newer version like 5.5, you could try registering the arrays to that vCenter server, to confirm.

[Dan_265]

We came across this KB as well and have opened a ticket with VMWare to check its validity.  We're hoping to run the command against our DB soon and report back with the outcome.

[Dan_265]

The VMWare KB article was in fact the fix for our issue.  Running the SQL command as outlined in the article resolved our issue, we can now register the plugin from both of our Nimble arrays.