Last updated on MAY 06, 2016
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 188.8.131.52 and later
Primavera P6 Professional Project Management - Version 184.108.40.206 and later
Information in this document applies to any platform.
After a new installation is configured for LDAP authentication and Claim Digger is launched, the user is prompted for the username and password.
After providing the username and password, the following error is received:
"The application and database versions do not match"
STEPS TO REPRODUCE
1. Access a new P6 EPPM 15.1 environment with P6 Professional installed
2. Log into P6 Web with an admin superuser account
3. Access Administration / User Access
4. Create a new user that matches an LDAP user account.
- Assign admin superuser global security profile
- Assign proper module access
5. Log into P6 Administration Application natively
6. Configure for LDAP authentication as per NOTE 1340406.1
7. Save changes.
8. Restart P6
9. Log-in to P6Web with LDAP account - confirm this is successful
10. Log-in to P6 Professional with LDAP account.
11. Launch Claim Digger
12. Observe prompt for login username/password
13. Enter LDAP username and password
14. Observe error: "The application and database versions do not match"
15. Access the P6 Administration application
16. Confirm the INTERNAL_PLUGINS configuration was created as a result of launching Claim Digger
17. Observe, on the Authentication tab, when expanding INTERNAL_PLUGINS:
Log-in Mode: NATIVE
Database instance: pmdb15
Authentication Mode: LDAP
18. Change Authentication Log-in Mode to LDAP
19. Save changes
20. Log out of the P6 Administration Application
21. Re-launch P6 Professional
22. Launch Claim Digger successfully.
When Claim Digger is launched, the LDAP settings for the INTERNAL_PLUGINS configuration are not being carried over to match the database configuration, rather, they are being created using 'Native' mode.
This issue occurs repeatedly after each subsequent P6 EPPM database upgrade and when the INTERNAL_PLUGINS configuration is created again the authentication mode is reset to 'Native'. This MUST be updated to match the database configuration.
The issue has the following business impact:
Due to this issue, the INTERNAL_PLUGINS configuration must be manually reset for LDAP authentication upon first launch of Tools / Claim Digger and/or post-upgrade.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms