Article - CS167608
Modified: 19-Mar-2021
Applies To
- Windchill RV&S (formerly Integrity Lifecycle Manager) 2009 to 12.1
Description
- User cannot login to Integrity Lifecycle Manager and LDAP returns error The user <user> was not found in the directory.
- When using the LDAP security scheme with Integrity server or agent a message is returned stating that the user was not found in the directory
- LDAP returns Error: Login exception encountered while attempting authentication of user <user> via policy default_clear. Details of exception The user <user> was not found in the directory.
- Unable to find certain users when trying to update MKS Domain group membership
-----------Update 3------------
And it looks like they are working on it:
//kb.vmware.com/s/article/85962
---------------------------------------------------
Upgraded last night So far Lifecycle manager appears not to be working.
"Authentication Failed, Lifecycle Manager server could not be contacted"
A quick look at the logs says it thinks im not authenticated
[#18] 2021-10-06T11:38:51.077Z warning vmware-vum-server[13587] [Originator@6876 sub=SimpleConnection] [simpleConnection 85] Connection requested for ><, returning default connection
[#18] 2021-10-06T11:38:51.077Z info vmware-vum-server[13587] [Originator@6876 sub=VcIntegrity] Session: [sessionId masked]; user
[#18] 2021-10-06T11:38:51.079Z info vmware-vum-server[13587] [Originator@6876 sub=VcIntegrity] Active? false
[#18] 2021-10-06T11:38:51.079Z error vmware-vum-server[13587] [Originator@6876 sub=SessionMgr] [sessionMgr 189] Login: User's VC session is not active; User: ; VcSession id: [52a0acb4-5bc9-f0fc-69ba-06d9838561ca]
[#18] 2021-10-06T11:38:51.081Z error vmware-vum-server[13587] [Originator@6876 sub=SessionMgr] [sessionMgr 189] [backtrace begin] product: VMware Update Manager, version: 7.0.3, build: build-18649303, tag: vmware-vum-server, cpu: x86_64, os: linux, buildType: release
[#18] --> backtrace[00] libvmacore.so[0x0037E963]
[#18] --> backtrace[01] libvmacore.so[0x002C8917]: Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)
[#18] --> backtrace[02] libvmacore.so[0x002D7AB7]: Vmacore::System::SystemFactory::CreateBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
[#18] --> backtrace[03] libvci-vcIntegrity.so[0x00786BC7]: Integrity::SessionMgrImpl::Login(std::string const&, std::string const&, Vmacore::Optional<std::string> const&, Vmacore::Ref<Integrity::UserSession>&)
[#18] --> backtrace[04] libintegrity-types.so[0x001CF878]
[#18] --> backtrace[05] libvmomi.so[0x0013F1AE]
[#18] --> backtrace[06] libvmomi.so[0x0013F80B]
[#18] --> backtrace[07] libvmacore.so[0x00235A97]
[#18] --> backtrace[08] libvmacore.so[0x0023B03F]
[#18] --> backtrace[09] libvmacore.so[0x00377398]
[#18] --> backtrace[10] libpthread.so.0[0x00007F87]
[#18] --> backtrace[11] libc.so.6[0x000F35EF]
[#18] --> backtrace[12] (no module)
[#18] --> [backtrace end]
-------------------------Update-------------------
appears to have no issues
------------Update 2----------------
Tried clearing browser cache... no dice
Checked permissions, the users is part of administrators, dont see any new groups added.
Im also using windows Integrated auth, should not be an issue, but it is being depreciated.
When in doubt ,reboot!
Lets see where this takes us
No Joy after reboot
vCenter Update error after upgrade to 7.0.3
VMWare (Lifecycle Manager) Friday, 08 October 2021 by
After upgrading vCenter appliance to 7.0 Update 3 (7.0.3) there is an error displayed when accessing the Update tab (Lifecycle Manager) and logged in using a AD account.
According to the VMWare Knowledgebase article below there is currently no fix available but logging into vCenter using a @vsphere.local account allows access:
"Authentication failed, Lifecycle Manager server could not be contacted", Access to Lifecycle Manager fails in vCenter 7.0 Update 3 when logged in with an Active Directory account (85962) - //kb.vmware.com/s/article/85962