The WLSS.Profile1.0 catalog contains messages in the range
BEA50000 - BEA50999. Messages in this catalog are part of the
com.bea.wcp.sip.i18n
Internationalization package and the com.bea.wcp.sip.i18n Localization package.
|
BEA-50000
|
Error: No provider with name has been configured.
|
Description
| No provider with name has been configured. |
|
Cause
| The profile.xml file does not contain a element with equal to name. |
|
Action
| Check the list of configured providers. |
|
|
BEA-50001
|
Error: No class named name exists.
|
Description
| No class named name exists. |
|
Cause
| No class named name has been loaded into the server. It should probably exist in a JAR file in the domain lib directory. |
|
Action
| Find the class in your domain directories. |
|
|
BEA-50002
|
Error: Class className is not an instance of com.bea.wcp.profile.ProfileServiceSpi
|
Description
| Class className is not an instance of com.bea.wcp.profile.ProfileServiceSpi |
|
Cause
| The class named in the element must implement ProfileServiceSpi to be loaded. |
|
Action
| Check the implementation of the class. |
|
|
BEA-50003
|
Error: Class className is not an instance of com.bea.wcp.profile.ProfileRouter
|
Description
| Class className is not an instance of com.bea.wcp.profile.ProfileRouter |
|
Cause
| The class named in the element must implement ProfileRouter to be loaded. |
|
Action
| Check the implementation of the class. |
|
|
BEA-50004
|
Error: Every <parentElementName> must have a <elementName> element. One is missing or null.
|
Description
| Every <parentElementName> must have a <elementName> element. One is missing or null. |
|
Cause
| The schema requires that every parentElementName element contain a elementName element. |
|
Action
| Check the profile.xml file. |
|
|
BEA-50005
|
Error: Found multiple elements with name name
|
Description
| Found multiple elements with name name |
|
Cause
| The elements must be unique. |
|
Action
| Check the profile.xml file. |
|
|
BEA-50006
|
Error: Found multiple parameters with parameterName for providerName.
|
Description
| Found multiple parameters with parameterName for providerName. |
|
Cause
| Parameter names must be unique. |
|
Action
| Check the profile.xml file. |
|
|
BEA-50007
|
Error: "Unexpected value in : value
|
Description
| "Unexpected value in : value |
|
Cause
| The legal value in the map-by element are: router, prefix, and provider-name. |
|
Action
| Check the profile.xml file. |
|
|
BEA-50008
|
Error: <elementName> must exist.
|
Description
| <elementName> must exist. |
|
Cause
| The element is required for a correct profile.xml file. |
|
Action
| Check the profile.xml file. |
|
|
BEA-50009
|
Error: Expected a <elementName> element in the <parentName> element.
|
Description
| Expected a <elementName> element in the <parentName> element. |
|
Cause
| The element is required for a correct profile.xml file. |
|
Action
| Check the profile.xml file. |
|
|
BEA-50010
|
Error: Found element with providerName. No corresponding element exists.
|
Description
| Found element with providerName. No corresponding element exists. |
|
Cause
| The name in the provider-prefix-set must be the same as the name of one of the providers. |
|
Action
| Check the list of configured providers. |
|
|
BEA-50011
|
Error: In element, found multiple elements with value prefix.
|
Description
| In element, found multiple elements with value prefix. |
|
Cause
| The provider-prefix-set elements are used to map requests to providers by prefix value. Accordingly, each prefix value should appear for only one provider. |
|
Action
| Check the list of configured providers. |
|
|
BEA-50012
|
Error: Unable to initialize provider class className.
|
Description
| Unable to initialize provider class className. |
|
Cause
| The class either cannot be found or it does not implement interface com.bea.wcp.profile.ProfileServiceSpi. |
|
Action
| Check the location of the class in the domain lib directory, and its declared interfaces. |
|
|
BEA-50013
|
Error: Unable to initialize router class className.
|
Description
| Unable to initialize router class className. |
|
Cause
| The class either cannot be found or it does not implement interface com.bea.wcp.profile.ProfileRouter. |
|
Action
| Check the location of the class in the domain lib directory, and its declared interfaces. |
|
|
BEA-50014
|
Error: Profile service has not been configured, and is therefore unavailable.
|
Description
| Profile service has not been configured, and is therefore unavailable. Look for a profile.xml file in the domain directories. |
|
Cause
| The config.xml file does not have the custome resource ProfileService configured. |
|
Action
| Check the config.xml file. |
|
|
BEA-50015
|
Error: Null document selector.
|
Description
| Null document selector. |
|
Cause
| A call was made to the profile service with a null document name. |
|
Action
| Check the calling code. |
|
|
BEA-50016
|
Error: Unknown map-by type value
|
Description
| Unknown map-by type value |
|
Cause
| The WlssProfileService data structure is corrupt. The legal values are: ROUTER, PREFIX, PROVIDER_NAME. |
|
Action
| Stop all attempts to use the profile service. Contact support immediately. |
|
|
BEA-50017
|
Error: No service provider configured for document selector docSel.
|
Description
| No service provider configured for document selector docSel. |
|
Cause
| The given document name does not map to any configured service provider. |
|
Action
| Examine the profile.xml file. Pay particular attention to the element. |
|
|
BEA-50018
|
Error: Document docSel mapped to provider providerName which is not currently active.
|
Description
| Document docSel mapped to provider providerName which is not currently active. |
|
Cause
| This should happen only if the profile service is mapping by prefix, and the provider has no prefixes mapped to it. |
|
Action
| Examine the profile.xml file. Does the providers name appear in any prefix set? |
|
|
BEA-50019
|
Error: ProfileServiceResource can not be initialized with null descriptor beans.
|
Description
| ProfileServiceResource can not be initialized with null descriptor beans. |
|
Cause
| The initialization of the Profile Service is corrupt somehow. |
|
Action
| Examine the config.xml file and the profile.xml file. Is the profile.xml file empty? |
|
|
BEA-50020
|
Error: ProfileServiceResource must be initialized using a ProfileServiceBean.
|
Description
| ProfileServiceResource must be initialized using a ProfileServiceBean. |
|
Cause
| The initialization of the Profile Service is corrupt somehow. |
|
Action
| Examine the config.xml file and the profile.xml file, and compare them to the examples in the documentation. |
|
|
BEA-50021
|
Error: Update to unknown type of bean: bean
|
Description
| Update to unknown type of bean: bean |
|
Cause
| An attempt to update the Profile Service configuration failed because of an unexpected type of Descriptor Bean. |
|
Action
| This is probably a programming error. Contact support. |
|
|
BEA-50022
|
Error: Unexpected update operation for ProfileServiceBean: bean
|
Description
| Unexpected update operation for ProfileServiceBean: bean |
|
Cause
| An attempt to update the Profile Service configuration failed because of an unexpected type of update operation. |
|
Action
| This is probably a programming error. Contact support. |
|
|
BEA-50023
|
Error: Unexpected failure when trying to modify ProfileService setup.
|
Description
| Unexpected failure when trying to modify ProfileService setup. |
|
Cause
| An attempt to update the Profile Service configuration failed for expected reasons. |
|
Action
| This is probably a programming error. Contact support. |
|
