1765690 - Installing patch 3 or 4 on BI 4.0 SP4 or BI 4.0 SP5 breaks SAP logon, viewing SAP users, roles, and all accounts with SAP aliases

• Receive error "Account information not recognized: All servers with CMS "CMSname:port", cluster @"clustername:port", kind cms which host service null, are down or disabled" when attempting to login with SAP auth or viewing users/groups/roles with SAP aliases.
• Receive error "Error: Server 'servername:6400' not found or server may be down (FWM 0103) null when logging in with SAP authentication
• Error can occur when logging in with SAP credentials, or another account with an SAP alias. A similar error can be seen when viewing users, groups, roles in the CMC which contain SAP users or accounts with SAP aliases
• Issue occurs after installing patch 3 or 4 on BI 4.0 SP04
• Issues also occur after installing BI 4.0 SP05
• CMS.exe will often be recycled during SAP communication, watch for the CMS to get a new PID (this makes tracing the issue difficult)
• In the CMS trace the final entry for the secSAPR3 update thread (although not necessarily the last entry in the log) shows

Other issues that could be indirectly broken or affected by this bug may include

• all types of authentication if SAP alias is involved such as AD SSO LDAP trusted auth, enterprise portal SSO, even manual logon via enterprise (if aliased with SAP)
• Viewing non SAP users and groups with sap aliases accounts, permissions, scheduling, almost anything in the system

• SAP BusinessObjects Business Intelligence Platform 4.0 SP 04 patch 03 (issue will also occur for patch 4)
• SAP BusinessObjects Business Intelligence Platform 4.0 SP 05
• So far it appears that the environments affected are all using a message server in the SAP entitlement page. We have not reproduced this on a system connected directly to an SAP application server.

zie ADAPT 01663266 1663266 install upgrade fix support pack service MSVCP80.dll , KBA , BI-BIP-AUT , Authentication, ActiveDirectory, LDAP, SSO, Vintela , Bug Filed