VMware Horizon Community
DavoudTeimouri
Virtuoso
Virtuoso
Jump to solution

VMware View Error: vCenter at address https://<vCenter>:443/sdk has invalid credentials

Hi,

I got this warning on specific time in View server: vCenter at address https://<vCenter>:443/sdk has invalid credentials.

I verified my vCenter credential, it's correct but I got this error more and more.

BR

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
1 Solution

Accepted Solutions
Jemily
Enthusiast
Enthusiast
Jump to solution

I am having the same issues. I have confirmed that my password is correct and after re-establishing vcenter and view composer credentials on the view server everything is okay for a time period. I suspect SSO is the issue, but really don't know how to angle this one down. Any help is appreciated.

View solution in original post

Reply
0 Kudos
23 Replies
DavoudTeimouri
Virtuoso
Virtuoso
Jump to solution

Please help me. I'm sure the credential is entered to server settings correctly.

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
mittim12
Immortal
Immortal
Jump to solution

What formating are you entering the credentials in View admin?   In my experience when dealing with 5.1 vCenter I had to use domain\username format.   

Reply
0 Kudos
DavoudTeimouri
Virtuoso
Virtuoso
Jump to solution

I used this format also, please see the attched screenshot,

It's happening sometimes, I think, maybe it's related to our DC connection.

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
mittim12
Immortal
Immortal
Jump to solution

Is it possible that the account is getting locked out?    Is this account used for anything else?

Reply
0 Kudos
DavoudTeimouri
Virtuoso
Virtuoso
Jump to solution

I checked it before but we are using that for our vCenters services and also it wasn't locked out. I'm using that for 4 other View servers.

If you find anything please share it with me. I want to clear this event.

Many thanks.

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
JHT_Seattle
Hot Shot
Hot Shot
Jump to solution

I had the same issue, but it went away after re-entering credentials for vCenter in View Administrator and rebooting my View Composer server (disabled provisioning in View Administrator first).

Reply
0 Kudos
Jemily
Enthusiast
Enthusiast
Jump to solution

I am having the same issues. I have confirmed that my password is correct and after re-establishing vcenter and view composer credentials on the view server everything is okay for a time period. I suspect SSO is the issue, but really don't know how to angle this one down. Any help is appreciated.

Reply
0 Kudos
DavoudTeimouri
Virtuoso
Virtuoso
Jump to solution

Yes, I think this is related to DC or SSO, because I facing with that just on specific times, for example 3:00 AM.

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
DavoudTeimouri
Virtuoso
Virtuoso
Jump to solution

Hi,

The problem is related to vCenter SSO service absolutely, I've restarted service and problem is gone.

Thanks for help.

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
bretttenney
Enthusiast
Enthusiast
Jump to solution

You check the vCenter logs to see what they say?

Reply
0 Kudos
DavoudTeimouri
Virtuoso
Virtuoso
Jump to solution

Hi,

I didn't check them but problem is gone,

Please let me to check them.

BR

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
caocOW
Contributor
Contributor
Jump to solution

i have seen this few time, after reboot SSO, error goes away. 

Reply
0 Kudos
DavoudTeimouri
Virtuoso
Virtuoso
Jump to solution

Exactly. Smiley Wink

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
Jemily
Enthusiast
Enthusiast
Jump to solution

You have luck on your side, because I can reboot/restart the SSO service and be good for a few hours. Then it's right back to the beginning. Not sure, but I will have to dig through some logs I'm sure.

Reply
0 Kudos
Jimdotcom
Contributor
Contributor
Jump to solution

This is a workaround; not root cause analysis. I'd be really interested to hear if anyone has actually established what the root cause is and how this can be resolved.

Reply
0 Kudos
chiakidd
Contributor
Contributor
Jump to solution

I am curious to know if you isolated this issue to any Windows Updates that may have been processed on the server-side? I find the timing of your post, and others having the issue, similar to mine. The only conclusion in my searching for a cause is a recent Windows Update. Have you investigated this further? I am prepping to run a few updates of Horizon to bring it to current and figured these updates will clear the air with any errors with the sdk has invalid credentials, which maybe a result of re-plugging in credentials and configurations in Horizon as I go through the process.

Reply
0 Kudos
muxonarization
Contributor
Contributor
Jump to solution

resolved my issue by setting a more complex PW for the AD-User View uses for connecting to vCenter.

Old password was lowercase 4letter 3digit New Password  with lots of characters upper&lowercase, digits and special chars.

Reply
0 Kudos
matteoabrile
Enthusiast
Enthusiast
Jump to solution

Hello,

I have same issue, every couple hours I found this error, but horizon works fine, I can manage every feature but seems every time fail log in vCenter, I have complicated password for user that I use to connect.

I have vCenter 5.5 with Horizon 6.

Have you some help ? for solve this problem.

Thanks

M.

Reply
0 Kudos
Michael42
Contributor
Contributor
Jump to solution

This issue is still present using Horizon 6.2.1 Build 3284346 / vCenter Server 6.0.0 Build 2776511.

Error message shows up in the connection server log every 1-2 days:

ERROR (0BE0-05DC) <VCHealthUpdate> [ServiceConnection25] Invalid VC login: Check username and password for VirtualCenter VCHealth Test instance at https://<my_vcenter_server>:443/sdk

Reply
0 Kudos