Orchestrator 4.1 new install and Unable to create SDKSession for module 'VC'

[RUG201110141]

I've just updated to vCenter 4.1.  The installation went fine.  During the install of vCenter 4.1 it installs Orchestrator onto the vCenter server.  It's a beefy server so I'm going to run Orchestrator on the server.  The database for Orchestrator and vCenter reside on seperate individual boxes from the vCenter server.  The other reason why I'm running the Orchestrator service on the vCenter server is because I'm going to use Server Heartbeat to protect vCenter and Orchestrator.

I went to configure Orchestrator yesterday and when through the steps on the VMware vCenter Orchestrator Configuration web interface and everything is green.  I then installed the 32-BIT client on my desktop and can successfully connect.  I go to do a basic workflow like upgrade vmware tools and I run into an issue.  The Start Workflow : Upgrade tools window popls up where you can set a date / time and a vm to upgrade.  When you go to select a virtual machine to upgrade it brings up the vCenter Server 4.1 and you go to expand it and you get an Error in plug-in and cannot browse to a virtual machine.

When you look at the log in the VMware vCenter Orchestrator Configuration web interface I get an error in the log that says date / teim 642-0800 ERROR [ModulesFactory] Unable to create SDKSession for module 'VC', reason : null.  This error occurs at the exact time I log into Orchestrator.  The same thing happens when I use the 64-bit client installed on the vCenter server.

Any suggestions?

[Burke-]

I see that you went through the configuration and everything is green - that is a good sign... How about the vCenter plugin? Did you add your vCenter server to it with valid credentials AND did you import the SSL Certificate from the vCenter server to your vCO server?

Note: You can have all GREEN even when no vCenter has been added to the plugin.

[RUG201110141]

I ran through all the steps in the documentation for configuration vCenter Orchestrator to include imported the certificate from vCenter.  The credentials I used were full administrative credentials to vCenter.

[Andreas_Diemer]

Hi RUG,

your inventory should look like this:

If you expand the https://.... and there is an error and not the datacenter, the VC is not well configured.

How does it look in your environment?

Regards, Andreas

[RUG201110141]

[RUG201110141]

When I open a browser to my vCenters sdk url I get a webpage cannot be found i.e.

https://myvcenter.domain.com/sdk

I presume something is supposed to come up when I enter that url into a browser.

[Andreas_Diemer]

No, only a SSL cert warning if you are using self signed cert. There is no Website at this URL, only a Webservice. This means there is nothing to view in a browser, it is for communication with clients or self programmed interfaces using WebService SDK.

You have to step through vCO WebConfig again, checking all information.

Regards, Andreas

[Burke-]

No, not necessarily - my functional environment does not show anything there either when I try to access that URL in my browser. Please post a screenshot of your vCenter Orchestrator Configuration page with the "vCenter Server 4.1 (4.1.0) tab selected on the left. Feel free to blur out your actual url if security is of concern.

[RUG201110141]

Thanks to both of you for the quick assistance.  It was the configuration on the vCenter Server 4.1 (4.1.0) tab that was screwed up athough it was green.  I deleted and added the vCenter server back in and restarted the vCO server and I'm good to go now.

Thanks again.

[Burke-]

If you haven't already done so, please assign points for answering this topic.

Thank you.