Last updated on DECEMBER 30, 2013
Applies to:Primavera P6 Professional Project Management - Version 6.2.1 to 6.2.1 [Release 6.2]
Primavera P6 Enterprise Project Portfolio Management - Version 6.2.1 to 6.2.1 [Release 6.2]
Primavera P6 Enterprise Project Portfolio Management - Version 7.0 and later
***Checked for relevance 30-Dec-2013***
At login to the Project Management client or Methodology Management Client on a citrix server or workstation produces the following error:
An application event has been intercepted
Event Code: CCCNB-3761-F
Description: Cryptographic context could not be acquired.
Microsoft provides several types of profiles that can be used in Windows Terminal Services:
- Local Profiles
- Mandatory Profiles
- Roaming Profiles
Within a MetaFrame Presentation Server environment, these three profile types can be defined as follows:
Local Profiles are stored on each MetaFrame Presentation Server, and are initially created based on the default user profile. Therefore, a user accessing applications in a load-managed MetaFrame Presentation Server farm would create an independent profile on each server. Users are able to retain changes to their local profile on each individual server, but changes will only be accessible for future sessions on that server. Local profiles require no configuration; if a user logging into a MetaFrame Presentation Server does not have a profile path specified, a local profile will be used.
Roaming Profiles are stored in a central location for each user. Roaming profiles differ from local profiles in that the information in the profile (whether it be a printer, a registry setting, or a file stored in 'My Documents') can be made available to all MetaFrame Presentation Servers in the environment. Configuring a user for a roaming profile requires an administrator to specify the user's Terminal Server Profile Path to a particular location on a file server. The first time the user logs into a MetaFrame Presentation Server, the default user profile will be used to create the user's roaming profile. During logoff, the profile will be copied to the administrator-specified location.
Mandatory Profiles, sometimes called 'roaming mandatory profiles,' are also stored in a central location for each user. They differ from roaming profiles in that the user's changes are not retained on logoff. Configuring a user for a mandatory profile requires an administrator to create a mandatory profile file (NTUSER.MAN) from an existing roaming or local profile, and assign users' Terminal Services profile path to the location where the file can be accessed.
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