I'm having issues configuring the vCOPS for View adapter. When I want to configure the event database, I get the error:
Per the release notes:
vCenter Operations for View is compatible with these releases:
Both the View VDI environment and vCenter Operations Enterprise must be up and running.
I haven't used this integration as of yet, but at least I can answer part of what you are asking.
In the logfile I see the following error:
Could not read View event database information...retrying
The View connection server has been updated from 5.0 to 5.1. I don't know if that has something to do with it.
What type of SQL authentication are you using? Mine is working and I used SQL auth.
Any errors on your database server?
Did you have any issues running the EnableViewPS.cmd script on your connection server?
I'm using SQL authentication and there was no error when I executed the script on the connection server.
The problem seems to be that the vCOPS for View adapter config utility can't read the configuration for the event database.
I've tested with a View 5.0 server which I still had available, and now I'm able to succesfully connect to the View Event database. So View 5.0 works, View 5.1 doesn't. I will now upgrade the View 5.0 server and see if it still works.
The DB connection information is gathered using the get-monitor View PowerCLI API. You may try running the following command on the View Connection Server from the View PowerCLI command window and report what it returns.
When I run that command on a View 5.0 server I get a correct result. When I run that command on a View 5.1 server, I get the following result:
Everything is ok with the event DB config. The View 5.0 and the View 5.1 server are in the same View "farm".
I have removed View 5.1 from one of the servers and reinstalled View as a replica server. Still got the same error. Other powershell command work correctly like: get-viewVC.
Can you confirm your build numbers for 5.0 and 5.1?
I've tried to use get-monitor without parameters, same error.
I've tried to uninstall View 5.1 and reinstall it as a clean server (standard), then the command works.
Buildnumber View 5.1: 704644
Buildnumber View 5.0: 481677
Looks like the issue has been identified, and a workaround is being sought. If something becomes available, I'll post as a reply. Thank you for helping to identify this concern.
There may be a work around developing for this.
Can you verify that the credentials configured for the View Adapter have an Administrators role in the View Admin console either directly or by group membership?
Just in case people are still having this issue.
As of 5.1, you must now grant the account used in your View Adapter Configuration at least the "Administrator (Read Only)" privilege to the View Connection server.
Fixed everything up for me.