vCenter Orchestrator Inventory view shows Error for vCenter plug-in”

[anuragvr]

I have set the username correctly without domain name in the Orchestrator’s connection properties tab, according to KB article: http://kb.vmware.com/kb/1017516.

I am using the self-signed certificates which were pre-generated during the installation of the vCenter and Orchestrator.

Please help me to resolve this issue

-AnuragR

[cdecanini_]

Is your configuration light green ?

Please check for the error message in the server.log file.

Christophe.

[anuragvr]

Thanks for immediate response, yes all configuration lights are green.

Error only in Orchestrator Client Inventory view.

-AnuragR

[cdecanini_]

There must be an error in the server.log. Please check. You cal also click in the client on the plug-in error and check what is written in the right. It may give you a clue.

Christophe.

[anuragvr]

When I click in the Orchestrator client on the plug-in error then in the right pane it shows following errors (check the attached screen shot)

As suggested for such type errors in blogs I make sure username format on the Orchestrator’s connection properties tab doesn't have the domain name, I also make sure that certificate is properly configured on the Orchestrator Configuration website.

All this effort not resolve my issue and I am still clueless.

Anybody have an idea on this so please help me.

-AnuragR

[dvatov · Accepted solution]

This is very generic error message. If you look in the server.log - the log file of the vco server you will find more specific error information. If not confidential you can attach it here so I can take a look at it.

Daniel

[anuragvr]

In the Sever log I can see following error

2012-01-13 20:02:42.004+0530 ERROR [VimSession] getRootFolder() -->
java.lang.Exception: getServiceContent() [Administrator@https://10.99.129.225:443/sdk/Main#4dffa9d] --> Invalid login
    at com.vmware.vmo.plugin.vi4.VimSession.getServiceContent(VimSession.java:625)
    at com.vmware.vmo.plugin.vi4.VimSession.getRootFolder(VimSession.java:1559)
    at com.vmware.vmo.plugin.vi4.VimPluginFactory.findRelation(VimPluginFactory.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at ch.dunes.vso.sdk.DirectInvoker.invoke(DirectInvoker.java:43)
    at ch.dunes.vso.sdk.SDKDatasourceInvoker.fetchRelation(SDKDatasourceInvoker.java:82)
    at ch.dunes.vso.sdk.SDKFinder.fetchRelation(SDKFinder.java:298)

[dvatov]

How is your plugin configured - shared session or session per user. In the configurator the plugin uses the administrative account to check the connectivity to the vCenter server and if it succeeds then it is green. For running workflows is used the second account if in shared session or the credentials you used to login in the orchestrator if in session per user. This account is not correct according to the vCenter server and it returns 'Invalid login'.

Daniel

[anuragvr]

Thanks Daniel for your valuable inputs, I make changes in the plug-in configuration “shared session” to “session per user” and it resolve the issue.  Even though you had explained but it still not clear to me why it is throwing error with “shared session”, can you elaborate to me once again.

Thanks a lot once again.

-AnuragR

[dvatov]

Happy beeing able to help In the vCenter plug-in you deal with 3 different credentials. First you have credentials to log-in vCO server itself. Second you have vCenter admin credentials used by the vCenter plug-in configurator to do some sanity checks in the vCenter server. Third is the vCenter server account used to actually run workflows and browse the vCenter plug-in inventory in the vCO client. For the third credentials you can use one vCenter server account - this is shared session mode. The account is specified in the vCenter plug-in configuration. You can also configure session per user mode and in this case first and third credentials are the same - you authenticate on the vCenter server with the same username/password as you used to authenticate to vCO. For this to work both vCO and vCenter server should use one active directory and the account you use should have permission in both systems.

Daniel