ClassPathComponentsMapper.folder.cannot.read | Cannot read from folder. |
Explanation |
Cannot read from file. The file was deleted with no read rights. |
Action |
Check to see if the file exists and if you have read rights. |
ClassPathComponentsMapper.folder.not.exists | The folder does not exist: |
Explanation |
The provided folder does not exist. |
Action |
You must specify an existing folder. |
ClassPathComponentsMapper.folder.not.valid | The specified path is not a valid folder. |
Explanation |
The specified path is not valid folder; it might be a file and not a folder. |
Action |
Specify a valid folder path. |
Error.POP.0.0.001 | Error sending mail |
Explanation |
When a forum message is retracted, an e-mail notification is sent to the configured forum administrator. This error occurs if there are any problems sending this e-mail to the administrator. |
Action |
Check the My webMethods Server logs for additional information about the specific e-mail failure. It may be caused by the e-mail server not being available, or because of an invalid forum administrator e-mail address. See Check the My webMethods Server logs for more details. See ..\MWS\server\<serverName>\logs |
POP.001.0002 | A "{0}" occurred with the Message "{1}" |
Class | E |
Explanation |
An unexpected error occurred during deployment. |
Action |
Examine the install.log, and optionally try again. In the log file, look for any information specific to the deployed component. |
POP.002.0004 | Context is in an invalid state. |
Class | E |
Explanation |
The server attempted to use an invalid context object. This error is the result of attempting to use a context object before it has been initialized or after it has been uninitialized. |
Action |
Always use the provider com.webmethods.portal.bizPolicy.IContextProvider (available through the com.webmethods.portal.system.PortalSystem) to acquire a context object. |
POP.002.0005 | Unable to locate command: {0} |
Class | E |
Explanation |
The requested command is not deployed on the server. |
Action |
Log in to My webMethods Server and use the Install Administration portlet to deploy the command to the server. |
POP.002.0006 | Unable to locate biz policy for resource: {0} |
Class | E |
Explanation |
The server cannot resolve the business policy for the specified resource because no policy has been registered for the resource type. |
Action |
Create and register a business policy for the resource type. Consult the My webMethods Server documentation to learn more about business policies. |
POP.002.0007 | Unknown error encountered while trying to resolve business policy for uri {0} |
Class | E |
Explanation |
The server cannot resolve a business policy for specified resource because of an internal error. |
Action |
Check the _problems_.log in the ..\MWS\server\default\logs directory for more specific error information. |
POP.002.0008 | Uri is not a valid thingID: {0} |
Class | E |
Explanation |
The server cannot invoke the RemoveAcess command on a resource that is not a metadata resource. |
Action |
Correct the command-invoking source code to specify a metadata resource using either the 'resourceURI' parameter or the context's current resource. |
POP.002.0009 | Invalid arguments to create Alias command |
Class | |
Explanation |
You cannot invoke this command without the required arguments: key and target. |
Action |
If you invoked this command programatically, review the Javadocs and make the required changes to the invoking code. |
POP.002.0010 | The arguments are not valid |
Class | |
Explanation |
When invoking the alias commands you must supply valid arguments. |
Action |
If you invoked this command programatically, review the Javadocs and make the required changes to the invoking code. |
POP.002.0011 | You cannot flush another user's cache |
Class | |
Explanation |
Only an Administrator can flush another user's cache. |
Action |
You must log in to My webMethods Server with Administrator credentials to be able to flush another user's cache. |
POP.002.0012 | Class group name is not specified |
Class | E |
Explanation |
You must specify the groupName parameter when invoking the ReloadClasses command. |
Action |
Correct the command-invoking code to specify the 'groupName' parameter. The parameter value should be the name of the group's class-loader bundle. |
POP.002.0014 | Unable to authenticate user: {0} |
Class | E |
Explanation |
The server cannot authenticate the user either because the user does not exist or because the user's password is incorrect. |
Action |
Try again with correct username and password. If necessary, log in to My webMethods or My webMethods Server and use the User Management feature to add the user to the server |
POP.002.0016 | Error listing directory groups |
Class | E |
Explanation |
The server cannot list the groups of a particular directory service, most likely because of a problem connecting to the directory service. |
Action |
If the directory service is a newly configured directory service, log in to the My webMethods Server and double-check the configuration using the Folders > System > Portlets > Administration > Directory Services Administration portlet. If the directory service is an existing directory service for which groups could be listed previously, validate that the LDAP or ADSI server to which the directory service is connected is up and running properly. Also check that the machine which hosts My webMethods Server is able to connect to the LDAP or ADSI server using the hostname and port specified in the directory service's configuration. |
POP.002.0017 | Error retrieving template list |
Class | E |
Explanation |
The server cannot list directory service templates, because an error occurred loading the templates. |
Action |
Check the ..\MWS\server\default\logs\_problems_.log file for more specific error information. |
POP.002.0018 | Error listing users |
Class | E |
Explanation |
The server cannot list the users of a particular directory service, most likely because of a problem connecting to the directory service. |
Action |
If the directory service is a freshly configured directory service, go back to the Portal Admin Dashboard, and double-check the configuration using the Directory Service Administration portlet (in the Portal Configuration category). If the directory service is an existing directory service for which groups could be listed previously, validate that the LDAP or ADSI server to which the directory service is connected is up and running properly. Also check that the machine which hosts the Portal server is able to connect to the LDAP or ADSI server using the hostname and port specified in the directory service's configuration. |
POP.002.0019 | Error updating directory |
Class | E |
Explanation |
The server cannot update the directory service configuration because an error occurred in validating or storing the configuration settings. |
Action |
Check the ..\MWS\server\default\logs\_problems_.log file for more specific error information. |
POP.002.0020 | Invalid command ID: {0} |
Class | |
Explanation |
The requested command is not found. |
Action |
Verify that the command has been properly installed. This can be done by logging in to My webMethods Server as sysadmin and viewing the commands in the folder Folders > System > Manager > Commands directory. |
POP.002.0021 | Cannot resolve install mechanics for: {0} |
Class | E |
Explanation |
An error occurred during the installation of a server component. |
Action |
Look in the ..\MWS\server\default\logs\_problems_.log file for the stack trace of the error. The stack trace may not provide enough detail to say why the error was thrown, but it will show where the error originated. |
POP.002.0022 | Location is not a folder: {0} |
Class | |
Explanation |
When the Install Services commands are instructed to deploy all of the components of a folder, the resource must be a folder and cannot be a file. |
Action |
Ensure that either the Autodeploy folder is properly configured or that the object passed to the InstallComponents command is a folder. |
POP.002.0023 | Cannot find folder: {0} |
Class | |
Explanation |
When the Install Services commands are instructed to deploy all of the components of a folder, the folder must be available. |
Action |
Ensure that either the Autodeploy folder is properly configured or that the objecgt passed to the InstallComponents command is an available folder. |
POP.002.0025 | Command name is not specified |
Class | E |
Explanation |
The Ant build file does not contain the command name needed to invoke the ExecuteCommand ant task. |
Action |
Correct the Ant build file to provide the command name with the 'name' attribute of the ExecuteCommand task. |
POP.002.0026 | Cannot resolve command [name, type] [{0}, {1}] |
Class | E |
Explanation |
The server cannot execute the command by means of an Ant task because the specified command has not been deployed to the server. |
Action |
Deploy the command specified by the error message. |
POP.002.0027 | Attribute target is required |
Class | E |
Explanation |
The target for invoking the ExecuteTargetLoop Ant task has not been specified. |
Action |
This error can occur if a developer modifies an Ant build file used to deploy comments to the server. Correct the Ant build file to add a 'target' attribute to the ExecuteTargetLoop task invocation. |
POP.002.0028 | Cannot create IInitializableComponentData from: {0} |
Class | E |
Explanation |
The component configuration data is not one of the following types: xml (serialized XML document), xmlLocation (URL specifying an XML document), properties (serialized properties map), propertiesLocation (URL specifying a properties file location). |
Action |
Correct the component configuration in the phaseProvider.xml configuration file to specify component configuration data as either xml, xmlLocation, properties, or propertiesLocation. |
POP.002.0029 | Attribute source is required |
Class | E |
Explanation |
The server cannot execute an Ant task because the task requires a source attribute to be specified. |
Action |
Correct the Ant build file to add a 'src' attribute to RunJavaScript and RunSQLScript tasks. The 'src' attribute must specify the file path to the script to be run. |
POP.002.0030 | Cannot create IInitializableComponentData from {0} for provider {1} |
Class | E |
Explanation |
The server cannot unregister the specified component. The component's configuration data has become corrupted. |
Action |
Reinstall the component with the Folders > Administrative Folders > Administration Dashboard > Configuration > Install Administration portlet, and then re-try uninstalling the component. |
POP.002.0031 | Cannot find IComponent using IComponentData {0} in provider {1} |
Class | |
Explanation |
An attempt was made to unregister a component that is not currently registered. |
Action |
No further action is required. |
POP.002.0032 | Cannot get IComponentData for component {0} from provider {1} |
Class | E |
Explanation |
An error occurred during the unregistration of a server component. |
Action |
Look in the ..\MWS\server\default\logs\_problems_.log file for the stack trace of the error. The stack trace may not provide enough detail to say why the error was thrown, but it will show where the error originated. It is likely that you need to restart the server. |
POP.002.0033 | Component Provider not found: {0} |
Class | E |
Explanation |
The server cannot unregister the component because component data has become corrupted. |
Action |
Re-install the component with the Folders > Administrative Folders > Administration Dashboard > Configuration > Install Administration portlet, then re-try uninstalling. |
POP.002.0034 | Attribute descriptorSrc is required |
Class | E |
Explanation |
The Ant task does not have skin descriptor content. |
Action |
Correct the Ant build file to provide skin descriptor content using the 'descriptorSrc' attribute to CreateSkinInstance, GetSkinInfo, and RemoveSkinInstance Ant tasks. |
POP.002.0035 | Skin name is empty |
Class | E |
Explanation |
The server cannot determine the skin name because the skin descriptor does not contain the skin name or because the skin descriptor is improperly structured. |
Action |
Correct the skin descriptor to include the skin name in the 'name' attribute value of the 'wm_xt_skin' element. |
POP.002.0036 | Portlet info is not specified |
Class | E |
Explanation |
Portlet descriptor content is not included in the GetPortletInfo Ant task. |
Action |
Correct the Ant build file to provide portlet descriptor content using the 'descriptorSrc' attribute. |
POP.002.0037 | Portlet name is empty |
Class | E |
Explanation |
The server cannot determine the portlet name because the portlet descriptor does not contain the portlet name or because the portlet descriptor is improperly structured. |
Action |
Correct the portlet descriptor to include the portlet name as the content of the 'name' element. |
POP.002.0038 | Portlet is not available: {0} |
Class | E |
Explanation |
The specified portlet is not deployed on the server. |
Action |
Use the Folders > Administrative Folders > Administration Dashboard > Configuration > Install Administration portlet to deploy the portlet specified by the error message. |
POP.002.0040 | Cannot find system folder for the portlet: {0} |
Class | E |
Explanation |
An error occurred during installation of a portlet. |
Action |
Look in the ..\MWS\server\default\logs\_problems_.log file for the stack trace of the error. It may be necessary to reinstall the component. |
POP.002.0041 | Page have to be a folder type |
Class | |
Explanation |
When cloning pages, the source of the cloning operation must be of the appropriate type |
Action |
Ensure that an appropriate source is used for the cloning operation. |
POP.002.0042 | Destination container is not a valid thing: {0} |
Class | E |
Explanation |
The server cannot clone a remote resource; the resource must be cloned to a metadata destination container. |
Action |
Correct the command-invoking source code to specify a metadata destination container using the 'destContainerURI' parameter. |
POP.002.0043 | Source item container is not a valid thing: {0} |
Class | E |
Explanation |
The server cannot clone the remote resource; only metadata resources can be cloned. |
Action |
Correct the command-invoking source code to specify a metadata resource using either the 'resourceURI' parameter or the server context's current resource. |
POP.002.0044 | Invalid XType: {0} |
Class | E |
Explanation |
The server cannot resolve the DBO type of the remote item to be cloned. The most likely reason is that the DBO type has been uninstalled from the system. |
Action |
Normally, a DBO type cannot be uninstalled from the system until all instances of the type have been deleted. This message may also indicate that a damaged instance of the remote item is still present but cannot be cloned or recovered. No further action can be taken. |
POP.002.0046 | Item is not a valid thing: {0} |
Class | E |
Explanation |
The server cannot invoke the metadata command because the command must be invoked against a metadata resource. |
Action |
Correct the command-invoking source code to specify a metadata resource using either the 'resourceURI' parameter or the server context's current resource. |
POP.002.0047 | Can not create an item with an empty name |
Class | |
Explanation |
When creating a new resource, a 'name' property is required. |
Action |
When creating the resource, ensure that a name is supplied. |
POP.002.0048 | Delete operation failed |
Class | E |
Explanation |
The container cannot be deleted because at least one of the items in the container cannot be deleted. Refer to the the list of contained items that cannot be deleted, displayed in the user interface along with this message. |
Action |
Manually delete the specified undeletable contained items individually. This may result in more detailed information as to why the items cannot be deleted. |
POP.002.0049 | Error obtaining owned folder |
Class | E |
Explanation |
The server cannot obtain the owned folder because of an internal server error. |
Action |
Check the ..\MWS\server\default\logs\_problems_.log file for more specific error information. |
POP.002.0050 | Cannot get current resource uri |
Class | E |
Explanation |
Cannot invoke the portlet command because a target portlet for the command is not specified. |
Action |
Correct the command-invoking code to specify the portlet with the 'resourceURI' parameter or with the server context's current resource. |
POP.002.0051 | ResourceURI is not specified |
Class | E |
Explanation |
The server cannot invoke the portlet command because a target portlet for the command is not specified. |
Action |
Correct the command-invoking source code to specify the portlet with the 'resourceURI' parameter or with the server context's current resource. |
POP.002.0052 | PortletBean is not ICommandBean |
Class | E |
Explanation |
The command cannot be invoked against the portlet because the portlet's portlet-bean does not implement the com.webmethods.portal.bizPolicy.command.ICommandBean interface. |
Action |
Modify portlet's portlet-bean source code to make the portlet-bean implement ICommandBean. Rebuild and redeploy the portlet. |
POP.002.0053 | UserID is not of type IThingID or String |
Class | E |
Explanation |
The command was invoked using RMI with an inappropriate userID data type. This error is usually a result of a bug in the command-invoking code. |
Action |
Correct the command-invoking code to ensure it invokes the command with a userID specified either as a java.lang.String or a com.portal.webmethods.meta2.thing.IThingID object. |
POP.002.0054 | Search library not found: {0}. |
Class | E |
Explanation |
An attempt was made to delete a search library that does not exist. |
Action |
Log in to My webMethods Server and use the Search Administration portlet to check the name of the search library against the available libraries. |
POP.002.0056 | Saved Searches folder not found. |
Class | E |
Explanation |
The server cannot save a search because the user's saved-searches folder does not exist. |
Action |
User folders such as the user's saved-searches folder are created automatically for users when they login to My webMethods Server. Try logging out as the user, and then logging in again. |
POP.002.0057 | No name parameter found |
Class | E |
Explanation |
The server cannot invoke the save-search command name; the command does not specify a name parameter. |
Action |
Correct the command-invoking source code to specify a 'name' parameter. |
POP.002.0058 | Not a valid skin: {0} |
Class | E |
Explanation |
The server cannot invoke the ReloadSkin command; the specified skin identifier does not identify a valid skin. |
Action |
Correct the command-invoking source code to specify a valid skin resource using the 'skin' parameter. |
POP.002.0059 | Default xmlimport requires an IThingID for the parent: {0} |
Class | E |
Explanation |
The server cannot import a metadata resource using xmlImport unless the parent of the resource is also a metadata resource. |
Action |
Correct the xmlImport file to move or remove elements contained by the element specified by the error message. |
POP.002.0060 | Default xmlimport requires the parent to be a container: {0} |
Class | |
Explanation |
When executing an XML import script, every new child must be created within a valid container. |
Action |
Check the script to ensure that each created item has a valid parent. |
POP.002.0061 | Unable to locate acl for aclName: {0} |
Class | E |
Explanation |
The server cannot modify the access control list (ACL) for a resource specified in xmlImport because the access control list was referenced by an alias that does not exist. |
Action |
Correct the xmlImport file to replace the 'aclName' attribute value specified by the error message with a valid value. |
POP.002.0062 | Unable to find value for acl |
Class | E |
Explanation |
The server cannot create an access control entry using xmlImport because the ACL element requires a value attribute. |
Action |
Correct the xmlImport file to add a 'value' attribute to the 'acl' elements. The 'value' attribute values must contain one of the following My webMethods Server access right names (comma separated): READ, CREATE_ITEM, CREATE_CONTAINER, MODIFY, DELETE, PORTLET_MODIFY_PROPERTIES_INSTANCE, PORTLET_MODIFY_PROPERTIES_USER, ALL. |
POP.002.0063 | Unable to find ace value for: {0} |
Class | E |
Explanation |
The server cannot create access an control entry using xmlImport because the xmlImport entry references an unknown right value. |
Action |
Correct the xmlImport file to add a 'value' attribute to the 'acl' elements. The 'value' attribute values must contain one of the following My webMethods Server access right names (comma separated): READ, CREATE_ITEM, CREATE_CONTAINER, MODIFY, DELETE, PORTLET_MODIFY_PROPERTIES_INSTANCE, PORTLET_MODIFY_PROPERTIES_USER, ALL. |
POP.002.0064 | Unable to find alias name to set the acl |
Class | |
Explanation |
The required argument 'value' was not set on this xmlimport element. |
Action |
Ensure that the ACL element has a 'value' attribute |
POP.002.0065 | Alias attribute missing on context node |
Class | E |
Explanation |
The server cannot establish the resource context during xmlImport because the context element requires an alias attribute. |
Action |
Correct the xmlImport file to add an 'alias' attribute to 'context' elements. The alias attribute value must contain the name of a valid alias; elements enclosed by the context apply to the resource identified by this alias. |
POP.002.0069 | Root users folder not found |
Class | S |
Explanation |
The server cannot create the user's home folder because the server users folder does not exist. |
Action |
Create a new server folder, and set its alias to 'folder.users'. |
POP.002.0076 | The basic update properties requires a thingID: {0} |
Class | E |
Explanation |
The server cannot invoke the ImportFiles command because it does not specify a target folder for the import. |
Action |
Correct the command-invoking source code to specify a folder using either the 'resourceURI' parameter or the server context's current resource. |
POP.002.0077 | Adding to version control requires a thingID: {0} |
Class | E |
Explanation |
The server cannot invoke the version-control command without specifying a versionable resource. |
Action |
Correct the command-invoking source code to specify a versionable resource using either the 'resourceURI' parameter or the server context's current resource. |
POP.002.0078 | The resource does not support IVersionableMechanics: {0} |
Class | E |
Explanation |
The server cannot invoke the version-control command on the resource because the resource is not versionable. |
Action |
Do not invoke the AddToVersion command against resources that are not versionable. Only server folders and server content items are versionable. |
POP.002.0079 | Command requires a thingID: {0} |
Class | E |
Explanation |
The server cannot invoke the version-control command without specifying a versionable resource. |
Action |
Correct the command-invoking source code to specify a versionable resource using either the 'resourceURI' parameter or the server context's current resource. |
POP.002.0080 | Invalid version Uri: {0} |
Class | E |
Explanation |
The server cannot display the server version information of an item because the identifier used to specify the version is not a valid version identifier. |
Action |
Correct the source code that invokes the ViewVersion command to provide a valid version identifier. |
POP.002.0081 | Invalid thing ID: {0} |
Class | E |
Explanation |
The server cannot display the server version information of an item because the identifier used to specify the item does not identify a valid resource |
Action |
Correct the command-invoking source code to provide a valid versioned-item identifier for the 'targetURI' parameter. |
POP.002.0082 | User {0} don't have rights to view {1} |
Class | |
Explanation |
The current user failed the permissions check to see a particular version of an item. |
Action |
Check the permissions on that item. |
POP.002.0083 | Could not acquire context, principal data not found on session |
Class | E |
Explanation |
The server cannot create a server context for the specified javax.servlet.http.HttpSession because the HttpSession has not been initialized with the necessary server session data. |
Action |
Restart My webMethods Server. |
POP.002.0085 | Can't create subscription for non Thing: {0} |
Class | E |
Explanation |
The server cannot create a subscription from xmlImport data because subscriptions are supported only for metadata resources. |
Action |
Correct the xmlImport file to remove 'subscription' elements from non-metadata resource contexts. The best way to determine specifically which subscription elements in the xmlImport file are causing this error is the trial-and-error approach: remove each subscription element in the xmlImport file one by one and then try re-importing from the xmlImport file. |
POP.002.0086 | Unable to import xml. No uid. |
Class | E |
Explanation |
An attempt to create an access control entry or subscription using xmlimport did not specify the user ID of the My webMethods Server user or group. |
Action |
Correct the xmlImport file to add a 'uid' attribute to 'subscription' and 'ace' elements. The 'uid' attribute value must contain the user ID (LDAP user ID) of a valid My webMethods Server user or the cn (LDAP group ID) of a valid My webMethods Server group. |
POP.002.0087 | Unable to import xml. Could not acquire uri for uid: {0} |
Class | W |
Explanation |
The user referenced in the xmlImport file does not exist on My webMethods Server. |
Action |
Log in to My webMethods or My webMethods Server with appropriate permissions and add the user, or change the xmlImport file. |
POP.002.0089 | Unable to import subscription. No value specified for 'deliveryMode'. |
Class | E |
Explanation |
The server cannot create a subscription from xmlImport data because the subscription element requires a deliveryMode attribute. This error is caused by importing from an improperly constructed xmlImport file. |
Action |
Correct the xmlImport file by adding a 'deliveryMode' attribute to 'subscription' elements. The valid value for 'deliveryMode' attribute is "email", indicating notifications for this subscription are to be delivered to the user's e-mail address. |
POP.002.0090 | Unable to import subscription. No value specified for 'criteria'. |
Class | E |
Explanation |
The server cannot create the subscription from xmlImport data because the subscription element requires a criteria attribute that contains the name of at least one criterion valid for the type of resource subscribed to. |
Action |
Correct the 'subscription' elements in the xmlImport file so that they all contain valid 'criteria' attribute values. Valid values are not empty; they must contain a comma-separated list of criterion names. The criterion names for basic folders are: 'added', 'removed', 'modified', 'deleted', and 'moved'. The criterion names for basic links, forms, portlets, and content items are 'modified', 'deleted', and 'moved'. Custom DBO types may have additional criteria. |
POP.002.0091 | No matching criteria found for type: {0} and for criteria: {1}. |
Class | E |
Explanation |
The server cannot create a subscription from xmlImport data because the subscription element requires a criteria attribute that contains the name of at least one criterion valid for the type of resource subscribed to. |
Action |
Correct the xmlImport file so that 'subscription' elements contained by any element of the type specified by the error message's resource-typeName have valid 'criteria' attribute values. Valid values are not empty; they must contain a comma-separated list of criterion names. The criterion names for basic folders are: 'added', 'removed', 'modified', 'deleted', and 'moved'. The criterion names for basic links, forms, portlets, and content items are 'modified', 'deleted', and 'moved'. Custom DBO types may have additional criteria. |
POP.002.0092 | Can't set ace for non Thing: {0} |
Class | E |
Explanation |
The server cannot modify the access control entry (ACE) for a resource specified in xmlImport because the resource does not support My webMethods Server access control entries. |
Action |
Correct the xmlImport file to remove the 'ace' element for the resource specified by the error message. |
POP.002.0093 | Unable to locate alias for: {0} |
Class | E |
Explanation |
The server cannot establish the resource context during xmlImport because the alias specified for the context does not exist. |
Action |
Log in to My webMethods Server and use the Alias Management portlet to create the alias specified by the error ,message or fix the xmlImport file to use an alias that does exist. To fix the xmlImport file, locate the alias attribute with the value specified by the error message and replace that value with the name of an existing alias. |
POP.002.0095 | Unable to create alias: {0} because it already exists. |
Class | |
Explanation |
The command failed because an alias of the same name has already been registered. |
Action |
Either apply a different name to the new alias or modify the existing alias that uses the same name. |
POP.002.0096 | Mechanics is not an IBasicMechanics |
Class | E |
Explanation |
The server cannot use xmlImport to update the properties of a resource that is not a metadata resource. |
Action |
Correct the xmlImport file to not update the properties of non-metadata resources. The best way to determine the element in the xmlImport file that is causing this error is the trial-and-error approach: remove each element in the xmlImport file one-by-one and then try re-importing from the xmlImport file. |
POP.002.0097 | Unable to complete import because type: {0} doesn't exist. |
Class | E |
Explanation |
The server cannot import a resource specified in xmlImport because the resource is an instance of a DBO that is not currently deployed in My webMethods Server. |
Action |
Deploy the DBO specified by the error message and then rerun the xmlImport. |
POP.002.0098 | Role xmlimport requires attributes of 'roleProvider' and 'name' |
Class | |
Explanation |
When creating a new role using an xmlImport script, the attributes must be available. |
Action |
Modify the xmlimport script to include the required 'roleProvider' and 'name' properties. |
POP.002.0099 | Role xmlimport unable to locate roleProvider: {0} |
Class | |
Explanation |
The type of role is not registered on the current system. |
Action |
Check the 'roleProvider' attribute to make sure it is correct. |
POP.002.0103 | Failed to set Alias {0} for resource {1}. |
Class | |
Explanation |
The system failed to correctly set an alias during the xmlimport. |
Action |
Check the server logs at ..\MWS\server\default\logs for any additional exceptions that occurred during the import. |
POP.002.0105 | Failed to load xml document from {0} |
Class | |
Explanation |
The XML file specified for the xmlimport script is either not found or not well-formed. |
Action |
Verify that the XML file exists in the specified location and that the contents of the file are valid XML. |
POP.002.0107 | Failed to invoke remote command: {0}. Original error message: {1} |
Class | |
Explanation |
A problem occured when executing a command on a remote server. |
Action |
Check the logs on the remote server for additional information. |
POP.002.0108 | User UID can not be found in MWS directories: {0} |
Explanation |
No user is found with the specific user ID. |
Action |
Specify a valid user ID. |
POP.002.0110 | You have insuffient privileges to impersonate other users. |
Explanation |
You have insufficient privileges to impersonate other users. |
Action |
The log file indicates how to grant user impersonate privileges. Contact a system administrator if you need such privileges. |
POP.002.0111 | Illegal Argument: Command result may not be serialized. |
Explanation |
The command result cannot be serialized. |
Action |
Make sure the command result can be serialized. |
POP.002.0113 | The parent of the task is already completed |
Explanation |
You cannot create a new child task if its parent task has been completed. |
Action |
Contact the parent task owner to determine how to handle the additional work. |
POP.002.0114 | User {0} does not have the functional privilege to delegate task {1} |
Explanation |
The user has not been granted the functional privilege to delegate the task. |
Action |
Please contact the system administrator if you need such privileges. |
POP.002.0118 | Thing with name "{0}" for locale "{1}" already exists in "{2}". Unable to rename "{3}" |
POP.003.0003 | No access model specified in property "{0}". |
Class | S |
Explanation |
The framework.access.model system property does not specify an access model. |
Action |
Update the portal.properties file to specify framework.access.model property value. The choices are permissive or restrictive. |
POP.003.0004 | Unable to register principal types: "{0}". |
Class | S |
Explanation |
The system directory is corrupted. |
Action |
Restore the underlying system user directory content from a backup or manually restore the user directory. In the case of LDAPd, you can reinstall the LDAPd server using the webMethods Installer. |
POP.003.0005 | Unable to register search service: "{0}". |
Class | S |
Explanation |
An error occurred in registering a new search service. |
Action |
You might need to reinstall My webMethods Server. |
POP.003.0006 | Error initializing content service: "{0}". |
Class | S |
Explanation |
The content service cannot be initialized. |
Action |
Check the Content Service Administration portlet to verify that the content service is properly configured. |
POP.003.0007 | Cannot list roles, directory service "{0}" not found. |
Class | E |
Explanation |
The directory service cannot be found. |
Action |
Check the Directory Service Administration portlet to verify that the directory service is properly configured and functional. |
POP.003.0008 | Could not locate system directory: "{0}". |
Class | E |
Explanation |
The server cannot find the system user directory. |
Action |
Verify that the system directory is present in Directory Services Administration portlet, and that it is configured and functional. |
POP.003.0009 | Error setting system directory: "{0}". |
Class | E |
Explanation |
The command failed to change the system directory service. |
Action |
Do not attempt to change the system directory. |
POP.003.0012 | "{0}" does not have permission to modify the Administrators group. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu to open the Permissions portlet to give the user access rights. |
POP.003.0013 | "{0}" does not have permission to modify the directory configuration. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu to open the Permissions portlet to give the user access rights. |
POP.003.0014 | Cannot update directory config, domain not found: "{0}". |
Class | E |
Explanation |
An attempt was mademto update the config information for a directory service using an invalid domain name. |
Action |
Use a valid domain name. |
POP.003.0015 | Cannot update directory config, Administrator user not found: "{0}". |
Class | S |
Explanation |
The system directory or the database is corrupted. |
Action |
Restore the underlying system user directory content from a backup or do so manually. If LDAPd, you can reinstall the LDAPd server using the webMethods Installer. |
POP.003.0016 | Cannot update directory config, Everyone group not found: "{0}". |
Class | E |
Explanation |
The system directory does not have an everyone group or the directory is corrupted. |
Action |
Restore the underlying system user directory content from a backup or do so manually. In the case of LDAPd, you can reinstall the LDAPd server using the webMethods Installer. |
POP.003.0017 | Cannot update directory config, Guest user not found: "{0}". |
Class | S |
Explanation |
The system directory is corrupted. |
Action |
Restore the underlying system user directory content from a backup or do so manually. In the case of LDAPd, you can reinstall the LDAPd server using the webMethods Installer. |
POP.003.0018 | Cannot remove the system directory. |
Class | E |
Explanation |
The system directory services cannot be removed. |
Action |
Do not try to remove the system directory. |
POP.003.0021 | System directory does not have Administrator user. |
Class | E |
Explanation |
The LDAP user store is missing the administrator user. |
Action |
Add a user to the system LDAP user store whose UID matches the Portal Administrator UID. This should only be necessary if the LDAP user store has become corrupted or the PortalAdmin user has been removed. |
POP.003.0022 | System directory does not have Everyone group. Everyone group access will not be available. |
Class | S |
Explanation |
The system directory is corrupted. |
Action |
Restore or create the everyone group in the system directory. Use the directory's administration UI or tools for that purpose. |
POP.003.0023 | System directory does not have Guest user. Guest access will not be available. |
Class | E |
Explanation |
The system directory does not have a guest user or it is corrupted. |
Action |
Restore the underlying system user directory content from a backup or do so manually. In the case of LDAPd, you can reinstall the LDAPd server using the webMethods Installer. |
POP.003.0024 | The type "{0}" is either 'disabled' or not deployed to this MWS cluster node. Please contact the My webMethods Server Administrator. |
Class | W |
Explanation |
An attempt was made to view a portlet for which the status has been set to disabled. |
Action |
Use the Manage Components portlet in the Administration Dashboard to change the status of the portlet type. |
POP.003.0025 | {0} cannot view the content of {1}. |
Class | W |
Explanation |
The user is denied access to view a portlet item |
Action |
Use the Permissions page to set the authentication scheme for the item to one of the installed authentication schemes. |
POP.003.0026 | {0} cannot list the shortcuts to {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0027 | {0} cannot list the notes for {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0028 | {0} cannot view the access list for {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0029 | {0} cannot view the authentication scheme for {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0030 | {0} cannot create an item of type {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open up the Permissions portlet to give the user access rights. |
POP.003.0031 | {0} cannot update the content of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0032 | {0} cannot add the note for {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0033 | {0} cannot remove the note for {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0034 | {0} cannot update the properties of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0035 | {0} cannot delete {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0037 | {0} cannot destroy {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0038 | {0} cannot store content {1}. |
Class | |
Explanation |
An attempt was made to store a document on a type that does not support document storage |
Action |
Ensure that content is stored on document types |
POP.003.0039 | {0} cannot contain a duplicate reference to {1}. |
Class | W |
Explanation |
You cannot create items with the same name under the same folder. |
Action |
When naming items in a folder, make sure each item uses a name that is unique within the folder. |
POP.003.0040 | Cannot uninstall "{0}" because it has "{1}" published instances. Please delete them first and try again. |
Class | W |
Explanation |
The DBO cannot be uninstalled because it has published instances. |
Action |
Manually delete all published instances of this DBO and try to uninstall it again. You can use Publish History portlet to help you find all published instances. |
POP.003.0044 | {0} is checked out. |
Class | W |
Explanation |
The item cannot be checked out because it is already checked out. |
Action |
Wait until the item is checked in and try again. |
POP.003.0045 | {0} is not versioned. |
Class | W |
Explanation |
The item is not versioned. |
Action |
Add the item to version control using the item's local menu. |
POP.003.0046 | {0} cannot view version number of {1}. |
Class | |
Explanation |
An attempt was made to view a version of a document that failed a permissions check |
Action |
Verify that the current user has sufficient permissions |
POP.003.0047 | {0} cannot list the versions of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0048 | {0} cannot add to versioning {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0049 | {0} cannot remove from versioning {1}. |
Class | |
Explanation |
An attempt was made to remove a version from version control that failed a permissions check |
Action |
Verify that the current user has sufficient permissions |
POP.003.0050 | {0} is checked out by {1}. |
Class | W |
Explanation |
The item is already checked out. |
Action |
Wait until the item is checked in and before trying to check out. |
POP.003.0051 | {0} cannot set the current version of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0052 | {0} cannot publish a version of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0053 | {0} cannot check out {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0054 | {0} is not checked out. |
Class | W |
Explanation |
You cannot check the item in because it is not checked out. |
Action |
Do not attempt to check in an item that was not checked out. |
POP.003.0055 | {0} cannot check in {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0056 | {0} cannot undo the check out of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's 'rmissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0057 | Source branch is not found: "{0}". |
Class | E |
Explanation |
The server cannot find a source version branch for this object. |
Action |
Do not try to add this object to version control. |
POP.003.0058 | Destination branch is not found: "{0}". |
Class | |
Explanation |
Version control system was unable to create a new branch required to complete the add to versioning command. |
Action |
Check the logs for additional information such as out of disk space. |
POP.003.0059 | {0} cannot be added to versioning because parent is null. |
Class | W |
Explanation |
The item is invalid because it does not have a parent. |
Action |
Use the local item menu to delete the item. |
POP.003.0060 | Not initialized: call init(PageData) first. |
Class | W |
Explanation |
An internal error has occurred. |
Action |
Try the operation again. |
POP.003.0061 | Column must be contained by a row. |
Class | W |
Explanation |
The page data xml is not valid. The column element must reside inside a row element. |
Action |
If you are using My webMethods Server when you got this message, the My webMethods Server page data has been corrupted. Try editing and then saving the page. If you cannot load the page into the page editor you need to delete the page and then recreate it. |
POP.003.0062 | Property must be contained by a portlet. |
Class | E |
Explanation |
The page data xml is not valid. The property element must be inside portlet element. |
Action |
If you are using My webMethods Server when you got this message, the My webMethods Server page data has been corrupted. Try to edit and then save the page. If you cannot load the page into the page editor you need to delete the page and then recreate it. |
POP.003.0063 | Portlet must contain 'uri' attribute. |
Class | E |
Explanation |
The page data xml file is not valid. The portlet definition does not have an URI attribute. |
Action |
If you are using My webMethods Server when you got this message, the My webMethods Server page data has been corrupted. Try to edit and then save the page. If you cannot load the page into the page editor you need to delete the page and then recreate it. |
POP.003.0064 | Property must contain 'name' attribute. |
Class | W |
Explanation |
The page data xml is not valid. The property element must have a name attribute. |
Action |
If you are using My webMethods Server when you got this message, the My webMethods Server page data has been corrupted. Try to edit and then save the page. If you cannot load the page into the page editor you need to delete the page and then recreate it. |
POP.003.0065 | Wiring must be contained by a portlet. |
Class | E |
Explanation |
The page data xml is not valid. The property element must reside inside the portlet element. |
Action |
If you are using My webMethods Server when you got this message, the My webMethods Server page data has been corrupted. Try to edit and then save the page. If you cannot load the page into the page editor you need to delete the page and then recreate it. |
POP.003.0066 | Wiring must contain 'name' attribute. |
Class | W |
Explanation |
The page data xml is not valid. The wiring element must have a name attribute. |
Action |
If you are using My webMethods Server when you got this message, the My webMethods Server page data has been corrupted. Try to edit and then save the page. If you cannot load the page into the page editor you need to delete the page and then recreate it. |
POP.003.0067 | Wiring must contain 'portlet' attribute. |
Class | E |
Explanation |
The page data xml file is not valid. The wiring definition does not have a portlet attribute. |
Action |
If you are using My webMethods Server when you got this message, the My webMethods Server page data has been corrupted. Try to edit and then save the page. If you cannot load the page into the page editor you need to delete the page and then recreate it. |
POP.003.0069 | The content service "{0}" is not available. Please contact the My webMethods Server Administrator. |
Class | E |
Explanation |
The server failed to update the contents of a file that was saved to My webMethods Server. |
Action |
Verify that the location for the My webMethods Server content repository exists. |
POP.003.0070 | "{0}" is not editable as it does not exist in a sandbox. |
Class | |
Explanation |
An invalid attempt to check in a versioned item was made. |
Action |
Check out a new version and the the item check in. |
POP.003.0071 | Cannot lookup install service: "{0}". |
Class | E |
Explanation |
The server cannot find the install service for this component. |
Action |
The component is not supported. |
POP.003.0072 | ComponentUri is not a thingID: "{0}". |
Class | E |
Explanation |
The server cannot determine the location of the installed component based on the passed URI. |
Action |
Correct the calling code to specify a thingID as the componentUri parameter of the uninstallComponent command. |
POP.003.0073 | {0} cannot install component. |
Class | E |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0074 | {0} cannot read search service. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0075 | {0} cannot set access entries on {1}. |
Class | |
Explanation |
An attempt was made to set permissions which failed a permissions check |
Action |
Ensure the current user has sufficient permissions to edit the permissions on the current object |
POP.003.0076 | {0} cannot remove access entries from {1}. |
Class | W |
Explanation |
The specified user cannot remove entries from the access control list of the specified item. |
Action |
Grant the user the rights to perform the operation, or have the operation performed by a different user with permission to change the access control list of the target item. |
POP.003.0077 | {0} cannot set the authentication scheme of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0078 | {0} cannot set the owner of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0079 | Internal error. Access right lengths do not match. |
Class | E |
Explanation |
Internal error. A database API inconsistency exists. |
Action |
Use the Manage Components portlet to edit permissions for this My webMethods Server object. |
POP.003.0080 | No auth scheme for auth Level: "{0}". |
Class | W |
Explanation |
The authentication scheme might not be installed yet, or the specified authentication level is not valid. |
Action |
Install the missing authentication scheme wm_<schema>Auth.cdp component or correct the authLevel attribute value of your custom xmlImport.xml file. |
POP.003.0081 | No implementation for auth scheme: "{0}". |
Class | E |
Explanation |
The authentication scheme for the target My webMethods Server item is invalid. |
Action |
Use the Permissions page to set the authentication scheme for the item to one of the installed authentication schemes. |
POP.003.0082 | {0} cannot list the contents of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0083 | {0} cannot add an item to {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0084 | {0} cannot add a shortcut to {1}. |
Class | W |
Explanation |
Most likely user does not have appropriate access rights.E145 |
Action |
Give the user access rights. |
POP.003.0085 | {0} cannot remove an item from {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open Permissions portlet to give the user access rights. |
POP.003.0086 | {0} cannot remove a shortcut from {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0087 | You cannot copy this container into a descendant of itself. |
Class | |
Explanation |
A paste operation was attempted inside the source container. |
Action |
Paste the clipboard contents into an external container. |
POP.003.0088 | You cannot move this container into a descendant of itself. |
Class | W |
Explanation |
The folder cannot move into one of its subfolders. |
Action |
If you need to move the folder, do not attempt to move it into a subfolder of itself. |
POP.003.0090 | {0} cannot contain a duplicate name. |
Class | W |
Explanation |
The folder or page cannot have items with duplicate names. |
Action |
When naming items in a folder, make sure each item has a name that is unique within the folder. |
POP.003.0091 | Unable to create xtype with null name: "{0}". |
Class | E |
Explanation |
The xtype id passed into the createChild command is not valid. |
Action |
Pass a valid xtype id parameter value. The valid values are listed in the tblXTypes tables. |
POP.003.0092 | {0} is a reserved folder and cannot be modified. |
Class | W |
Explanation |
The folder is a system folder and cannot be modified. |
Action |
Do not try to modify a system folder. |
POP.003.0093 | You cannot move a reserved item. |
Class | W |
Explanation |
The item is reserved and cannot be moved. |
Action |
Do not attempt to move reserved items. |
POP.003.0094 | {0} is a reserved folder and can not be versioned. |
Class | W |
Explanation |
The folder cannot be added to the version control because it is a special folder type. |
Action |
Do not try to add this folder to version control. |
POP.003.0095 | {0} cannot change the columns of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0096 | {0} cannot move portlet {1}. |
Class | |
Explanation |
An attempt to move a portlet failed a permissions check |
Action |
Verify that the current user has sufficient permissions |
POP.003.0097 | {0} cannot minimize portlet {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0099 | {0} cannot view this item. |
Class | W |
Explanation |
The user attempted to view an item but does not have permission to see it. |
Action |
The My webMethods Server administrator should use the Manage Components portlet to edit permissions for this My webMethods Server object. |
POP.003.0102 | Unable to locate: "{0}". |
Class | W |
Explanation |
The server cannot find the user in the directory. |
Action |
The user might have been removed from the directory. Determine if this user belongs in the directory. |
POP.003.0103 | Unable to locate: "{0}" invalid type. |
Class | W |
Explanation |
The directory might be corrupted or improperly configured. |
Action |
Check the Directory Service Administration portlet to verify that the directory service is properly configured and functional. |
POP.003.0104 | {0} cannot modify user. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0105 | Cannot modify attribute on principal, {0} not found. |
Class | W |
Explanation |
The server cannot find the user in the directory. |
Action |
The user might have been removed from the directory. Determine if this user belongs in the directory. |
POP.003.0106 | Cannot set email address on principal, email address attribute not configured properly. |
Class | W |
Explanation |
The email attribute is not configured for this user directory. |
Action |
Update the directory configuration in Directory Service Administration portlet to specify an email attribute name and try again. |
POP.003.0107 | {0} cannot create an alias. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0108 | Alias not found: "{0}". |
Class | W |
Explanation |
An attempt was made to remove an alias that does not exist. |
Action |
Verify that the remove alias call uses an existing alias name. |
POP.003.0109 | {0} cannot delete the "{2}" alias. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0110 | Internal ScheduleMechanics error. |
Class | E |
Explanation |
The paging cookie is invalid. |
Action |
Close the browser, then open it again, and retry the action. |
POP.003.0111 | {0} cannot view the subscription of {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0112 | {0} cannot list the subscriptions to {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0113 | {0} cannot edit the subscription to {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0115 | Cannot create cookie for URI: "{0}". |
Class | W |
Explanation |
The system directory or the database is corrupted. |
Action |
Restore the underlying system user directory content from a backup or do so manually. In the case of LDAPd, you can reinstall the LDAPd server using the webMethods Installer. |
POP.003.0116 | User page size must be >= 0 (zero indicates default). |
Class | W |
Explanation |
The page size cannot be negative. |
Action |
Correct the calling code to pass the pageSize parameter as a positive number. |
POP.003.0117 | Cannot set password on user, user not found: "{0}". |
Class | W |
Explanation |
The system directory or the database is corrupted. |
Action |
Restore the underlying system user directory content from a backup or do so manually. In the case of LDAPd, you can reinstall the LDAPd server using the webMethods Installer. |
POP.003.0118 | Cannot get roles for user, user not found: "{0}". |
Class | E |
Explanation |
The server cannot find the user in the directory. |
Action |
The user might have been removed from the directory. Determine if this user belongs in the directory. |
POP.003.0119 | Unable to locate mechanics: "{0}". |
Class | E |
Explanation |
Mechanics were not found for the given name or URI. |
Action |
If the error is related to a standard portlet, try to redeploy the portlet using the Install Administration portlet. If you have created a custom portlet, you need to correct the calling code in CAF and redeploy the portlet. |
POP.003.0120 | {0} cannot cut {1}. |
Class | W |
Explanation |
The user does not have appropriate access rights. |
Action |
Use the item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0121 | {0} cannot cut {1}. |
Class | W |
Explanation |
The user does not have the appropriate access rights. |
Action |
Use the item's Permissions local menu item to open the Permissions portlet to give the user access rights. |
POP.003.0122 | A datasource named "{0}" already exists. |
Class | W |
Explanation |
An attempt was made to register a SQL datasource with a datasource name that has already been used for another datasource. |
Action |
Use a different name for the new datasource. |
POP.003.0123 | You cannot copy a reserved item. |
Class | W |
Explanation |
The item is reserved. |
Action |
Do not attempt to copy a reserved item. |
POP.003.0124 | {0} cannot access datasource. |
Class | |
Explanation |
An attempt to issue a SQL statement was made with an invalid argument for the datasource |
Action |
Ensure that the datasource is registered |
POP.003.0126 | compression not allowed. |
Class | W |
Explanation |
The presentation cache content cannot be compressed. |
Action |
Correct the calling code to not call PresentationCacheContent.setCompressed(true). |
POP.003.0129 | Cannot initialize principal, invalid type: "{0}". |
Class | W |
Explanation |
The directory might be corrupted or improperly configured |
Action |
Check the Directory Service Administration portlet to verify that the directory service is properly configured and functional. |
POP.003.0130 | Error in thread resyncing group properties [domain]: "{0}". |
Class | E |
Explanation |
The server failed to refresh the metadata for a Group from the LDAP server. |
Action |
Validate the connectivity to the LDAP server using an LDAP browser tool, the directory native Administration UI, or other tools. |
POP.003.0132 | "{0}" depends on "{1}". |
Class | |
Explanation |
During the wiring resolution phase an error occurred |
Action |
Check the wiring configuration for the portlets on the current page. |
POP.003.0134 | {0}'s account has been disabled. |
Class | W |
Explanation |
The user account has been disabled. |
Action |
Enable the user account in the underlying user directory. Use the directory Administration UI or other tools for that purpose. |
POP.003.0135 | Unable to find the content location for: "{0}". Content service is not available or out of sync with the database. Please try again. If the problem persists, contact the My webMethods Server Administrator. |
Class | W |
Explanation |
The content store is corrupted. |
Action |
Delete the item and try again. |
POP.003.0136 | Cannot install component "{0}" because it requires "{1}" to be installed first. |
Class | W |
Explanation |
The component being installed depends on another component that is not yet installed and not listed in the items to install list. |
Action |
Install the required components before attempting to install the component that raised the error. |
POP.003.0137 | Unable to create with unknown type: "{0}". |
Class | W |
Explanation |
Cannot create an item because the xtype is invalid. |
Action |
Pass a valid xtype parameter to createChild command. All valid xtypes are found in the XTypes system folder in the My webMethods Server UI. |
POP.003.0139 | Component "{0}" installation failed. System state is recovered by uninstalling the component. Original error: {1} |
Class | W |
Explanation |
The installation of the component failed. |
Action |
Uninstall the component to recover the system state. Look at the install.log file for details of why the installation failed. |
POP.003.0140 | Component "{0}" installation failed. System state is recovered by reinstalling the previous version of the component. Original error: {1}" |
Class | E |
Explanation |
The installation of the component failed. |
Action |
Uninstall the component to recover the system state. Look at the install.log file for details of why the installation failed. |
POP.003.0141 | The username/password you entered is invalid. |
Class | |
Explanation |
The login attempt failed. |
Action |
Verify that the username and password are correct. |
POP.003.0142 | Invalid principal type: "{0}". |
Class | |
Explanation |
An attempt to modify a group's membership failed. |
Action |
Verify that the group exists prior to attempting to modify the group. |
POP.003.0143 | {0} cannot set policy on {1}. |
Class | |
Explanation |
An attempt was made to add an item to a Security Realm failed a permissions check. |
Action |
Verify that the current user has sufficient permissions. |
POP.003.0144 | {0} cannot remove policy from {1}. |
Class | |
Explanation |
An attempt to remove an item from a Security Realm failed a permissions check. |
Action |
Verify that the current user has sufficient permissions. |
POP.003.0146 | {0} cannot modify the members of group: {1} |
Class | |
Explanation |
An attempt to modify the members of group failed a permissions check. |
Action |
Verify that the current user has sufficient permissions. |
POP.003.0147 | {0} cannot modify the membership of principal: {1} |
Class | |
Explanation |
An attempt to modify the groups and roles a principal belongs to failed a permissions check. |
Action |
Verify that the current user has sufficient permissions. |
POP.003.0148 | Command Error, Parent is not a container. Class= {0} |
Class | |
Explanation |
An attempt was made to create a new item inside a parent that is not a valid container. |
Action |
Ensure that the attempt is made to create a child inside a valid container. |
POP.003.0150 | {0} cannot create users or groups in the "{1}" directory service." |
Class | |
Explanation |
An attempt was made to create a user or group failed a permissions check. |
Action |
Verify that the current user has sufficient permissions. |
POP.003.0151 | {0} cannot modify the members of role: {1} |
Class | |
Explanation |
An attempt to modify the members of a role failed a permissions check. |
Action |
Verify that the current user has sufficient permissions. |
POP.003.0153 | {0} cannot add a {2} to {1}. |
Class | |
Explanation |
An attempt to create a new child failed a permissions check. |
Action |
Verify that the current user has sufficient permissions. |
POP.003.0154 | {0} cannot remove a {2} from {1}. |
Class | |
Explanation |
An attempt to remove a child from a folder failed a permissions check. |
Action |
Verify that the current user has sufficient permissions. |
POP.003.0155 | My webMethods Server webspace {0} should have an valid alias |
Class | |
Explanation |
Webspaces must have a valid name in order to be created. |
Action |
Ensure that a valid alias name is supplied. |
POP.003.0156 | Unclosed skin property: "{1}". Please close with "]. |
Class | |
Explanation |
During the dynamic skin property resolution, a malformed skin property was referenced. |
Action |
Ensure that the javaScript file with the dynamic skin property is properly formed. |
POP.003.0160 | Failed to resolve wiring for property "{0}" |
Class | E |
Explanation |
Wiring cannot be resolved for the <propertyName> property of a portlet instance. |
Action |
Open the Wiring settings for this portlet, make sure the source portlet and its property are still available. Adjust the wiring settings if necessary. |
POP.003.0162 | A group cannot be a member of itself. |
Class | |
Explanation |
A malformed attempt to modify a group was made. |
Action |
Do not set a group as a member of itself. |
POP.003.0163 | Invalid username or Password. |
Explanation |
The username or password is invalid. |
Action |
Specify a valid username and password. |
POP.003.0164 | {0} cannot copy {1}. |
Explanation |
The user does not have the privilege to copy. |
Action |
Please contact the system administrator if you need this privilege. |
POP.003.0165 | {0} cannot clone {1}. |
Explanation |
The user does not have the privilege to clone. |
Action |
Please contact the system administrator if you need this privilege. |
POP.003.0166 | {0} is a system component. And will not be uninstalled. |
Explanation |
System components cannot be uninstalled. |
Action |
Do not attempt to uninstall a system component. |
POP.003.0167 | Too many failed login attempts for: "{0}". You may try to login again in {1} minutes. |
Explanation |
The user is not allowed to login because of too many failed login attempts. The user must wait a specified amount of time before trying again. |
Action |
Make sure you are using a valid username and password. Contact the system administrator if your existing credentials are not working. |
POP.003.0168 | Password has expired for: "{0}". Please contact an administrator to reset your password. |
Explanation |
The user's password has expired. |
Action |
Contact an administrator to reset your password. |
POP.003.0169 | {0} is reserved and cannot be used for an alias. |
Explanation |
The specified name is reserved by the system and cannot be used for an alias name. |
Action |
Specify a differnt name as an alias. |
POP.003.0171 | The uploaded file type is not allowed. The allowed file extensions are: {0} |
Explanation |
The uploaded file type is not supported by the system. |
Action |
Be sure to upload only supported file types. |
POP.004.0001 | The Resource Bundle for "{0}" was not found. |
Class | E |
Explanation |
The server cannot load the specified resource bundle class. The bundle is a portlet class that has not been deployed or was deployed in a different portlet. |
Action |
Use the Portlet Developer to add the resource bundle class to the invoking portlet. Redeploy the portlet. |
POP.004.0002 | The Message Key "{0}" was not found in the Resource Bundle "{1}". |
Class | E |
Explanation |
The resource bundle message key is missing. |
Action |
Correct the resource bundle to include a resource for the key specified by the error message. |
POP.004.0003 | There was no Object found for Message Key "{0}". |
Class | |
Explanation |
No object was found for the specified message key. |
Action |
Specify a valid message key. |
POP.004.0004 | An error occurred while formatting the Message Key "{0}". |
Class | E |
Explanation |
The resource bundle message key is missing or the message could not be formatted because its content is invalid. |
Action |
Correct the resource bundle to include the key specified by the error message, or correct the resource content identified by the key. |
POP.004.0005 | Error creating search pools "{0}". |
Class | S |
Explanation |
The server cannot initialize some search service data structures because an internal portal error occurred. |
Action |
Use the specific error message details to diagnose the problem. |
POP.004.0006 | Invalid cache ID: "{0}". |
Class | S |
Explanation |
The server cannot initialize an invalid cache. |
Action |
Correct the thing cache configuration in the cache.xml My webMethods Server configuration file. A valid entry is: <cache name="Thing Cache" class="com.webmethods.portal.service.cache.impl.TransientCache" maxSize="10000" isClustered="true" ID= "1" enabled="true"/> |
POP.004.0008 | Unable to initialize content service component: "{0}". |
Class | E |
Explanation |
Cannot initialize the content service. |
Action |
If you cannot reconfigure the offending content service. Call Software AG Global Support for a reset directive. |
POP.004.0010 | No provider for directory [name, type] : [{0}, {1}] |
Class | E |
Explanation |
The server cannot initialize the specified directory service because the directory service is an unknown type. |
Action |
Correct the directoryConfig.xml My webMethods Server configuration file to remove the Service element with the name attribute value specified by the error message. |
POP.004.0011 | Invalid XML for directory, no DirectoryConfig element found: "{0}". |
Class | E |
Explanation |
The server cannot initialize the directory service because its configuration data is corrupt. |
Action |
Correct the directoryConfig.xml My webMethods Server configuration file to remove the Service element with the name attribute value specified by the error message. |
POP.004.0012 | Unable to construct component data for directory: "{0}". |
Class | S |
Explanation |
The server cannot initialize the directory service. |
Action |
Use the Directory Services Administration portlet to create a new directory service and then delete the old one. |
POP.004.0013 | Alias Cache not found. |
Class | S |
Explanation |
The server cannot initialize the alias service because the alias cache is not configured. |
Action |
Add the following entry to the cache.xml My webMethods Server configuration file: <cache name="AliasCache" class="com.webmethods.portal.service.cache.impl.AliasCache" maxSize="5000" isClustered="true" ID="2" enabled="true"/> |
POP.004.0014 | Can't create alias cache. |
Class | E |
Explanation |
The server cannot initialize the metadata service because the required cache was not located. |
Action |
Correct the thing cache configuration in the cache.xml My webMethods Server configuration file. A valid entry is: <cache name="Thing Cache" class="com.webmethods.portal.service.cache.impl.TransientCache" maxSize="10000" isClustered="true" ID= "1" enabled="true"/> |
POP.004.0015 | Unable to create MetaContext: "{0}". |
Class | E |
Explanation |
The server cannot create a connection to metadata datasource because the configuration information for the datasource was not retrieved. |
Action |
Correct the metaContext.xml My webMethods Server configuration file to remove the Context element with the connection attribute value specified by the error message. |
POP.004.0016 | Can't get schedule list: "{0}". |
Class | S |
Explanation |
The server was unable to list all of the My webMethods Server schedules. |
Action |
Verify that the database has been properly configured and that the My webMethods Server schema was properly installed by paying close attention to the installation process. |
POP.004.0017 | Thing Cache not found. |
Class | S |
Explanation |
The server cannot initialize the metadata service because the required cache was not located. |
Action |
Correct the thing cache configuration in the cache.xml My webMethods Server configuration file. A valid entry is: <cache name="Thing Cache" class="com.webmethods.portal.service.cache.impl.TransientCache" maxSize="10000" isClustered="true" ID= "1" enabled="true"/> |
POP.004.0018 | Can't create thing cache. |
Class | S |
Explanation |
The server cannot initialize the metadata service because the thing cache configuration is invalid. |
Action |
Correct the thing cache configuration in the cache.xml My webMethods Server configuration file. A valid entry is: <cache name="Thing Cache" class="com.webmethods.portal.service.cache.impl.TransientCache" maxSize="10000" isClustered="true" ID= "1" enabled="true"/> |
POP.004.0019 | No queue specified. |
Class | S |
Explanation |
The server cannot initialize the e-mail notification deliverer because the notification queue name was not specified in the deliverer's configuration. |
Action |
Specify the queue name in the queue attribute of the delivery initializers in the phaseProvider.xml My webMethods Server configuration file. |
POP.004.0020 | Unexpected exception: "{0}". |
Class | S |
Explanation |
The server cannot initialize the e-mail notification deliverer because an unexpected error occurred. |
Action |
Check the _problems_.log in the My webMethods Server current logging directory for more specific error information. |
POP.004.0021 | Invalid ConnectionManager config file. |
Class | S |
Explanation |
The server cannot initialize the datasource connection manager because it cannot acquire its configuration file. |
Action |
Validate that the portal.properties My webMethods Server configuration file contains the following entry: 'sled.connectionmanager.config=config:/db.xml'. |
POP.004.0022 | Could not acquire meta context : version service name: "{0}". |
Class | E |
Explanation |
The server cannot acquire the metadata datasource by name because the specified name is unrecognized. |
Action |
Restart the server where My webMethods Server is installed. |
POP.004.0023 | Could not find root folder of version services. |
Class | E |
Explanation |
The root folder of the version service does not exist. |
Action |
Reinstall the version service using the My webMethods Server Configurator. |
POP.004.0024 | Could not create service thing : version service name: "{0}". |
Class | S |
Explanation |
The server cannot initialize the version service. |
Action |
Verify that all of the versioning components have been deployed. This includes the version service and version portlet which can be located in the system portal folders. |
POP.004.0027 | Ftp login failed for user [{0}] : {1}. |
Class | E |
Explanation |
The server cannot login to the remote FTP server. |
Action |
Verify that the credentials are valid for the FTP connection service, and that the network connectivity is valid. |
POP.004.0028 | Ftp Connection Error: Access Denied |
Class | E |
Explanation |
The server cannot connect to the remote FTP server. |
Action |
Validate that the credentials and configuration are valid for the FTP connection service, using the Content Service Admin portlet. Verify that the network connectivity is valid. |
POP.004.0029 | Ftp Connection Error: "{0}". |
Class | E |
Explanation |
The server cannot connect to the remote FTP server. |
Action |
Validate that the credentials and configuration are valid for the FTP connection service, using the Content Service Admin portlet. Verify that the network connectivity is valid. |
POP.004.0032 | Invalid ID's in createThing. |
Class | E |
Explanation |
The server was unable to publish a new My webMethods Server object. |
Action |
Correct the invoking method to pass in a valid owner and parent ID parameters. |
POP.004.0033 | Database is busy or unavailable. |
Class | E |
Explanation |
The server cannot execute the SQL command because the database is not responding to My webMethods Server in a timely fashion. The database could be experiencing too much load preventing it from responding to My webMethods Server and the server might not be able to access the database's server or port. In addition, the database might not be running. |
Action |
Verify that the database is running, and is not experiencing heavy load. Verify that the database has an adequate number of connection threads available. Verify that the machine on which the My webMethods Server is running can access the datasource's configured host name and port. |
POP.004.0034 | Datasource Mismatch, passed ({0}) to API on ({1}). |
Class | E |
Explanation |
The metadata datasource cannot operate on a resource from a different datasource. |
Action |
Correct the invoking source code to use a metadata service to operate on a resource that belongs to the service's datasource. Consult the API documentation for more information. |
POP.004.0035 | Invalid URI |
Class | E |
Explanation |
The server cannot resolve the datasource for a metadata My webMethods Server identifier. |
Action |
The identifier that caused this error does not identify a resource, do not use it to identify a resource. |
POP.004.0036 | Invalid schedule info: interval "{0}", timeAt "{1}": Unable to parse 'timeAt' and/or 'interval' |
Class | E |
Explanation |
An attempt to create or modify a schedule has failed because of invalid schedule parameters. |
Action |
Correct the invoking code to pass valid schedule parameters. Valid interval and timeAt parameter values are the time values formatted according to the ISO 8601 date/time format. |
POP.004.0037 | Invalid schedule info: interval "{0}", timeAt "{1}": 'timeAt' overlaps with 'interval' |
Class | E |
Explanation |
The server cannot execute the scheduled event because the time to wait (timeAt), after the interval setting but before executing the event, is approximately as long as the interval itself. |
Action |
Edit the schedule using the Event Administration portlet, in the Portal Configuration category in the My webMethods Server Admin Dashboard, so the interval is longer than the On/At time-to-wait, such that weeks instead of days, hours instead of minutes. |
POP.004.0038 | Unknown thing type: {0} |
Class | E |
Explanation |
The server was unable to identify the base type of the metadata service object. |
Action |
Verify that the portlet was built using the My webMethods Server. |
POP.004.0039 | Unable to unregister XType: {0} |
Class | E |
Explanation |
The xtype was not registered or there are published instances of that xtype. |
Action |
Ensure that all instances of that xtype have been deleted prior to unregistering. These types are found by using the Publish History reporting portlet. |
POP.004.0040 | Can't convert to xtype of different base type |
Class | E |
Explanation |
Xtype conversion is unsupported. |
Action |
Correct the invoking method and do not attempt to modify the xtype parameter. |
POP.004.0041 | Invalid Principal. |
Class | E |
Explanation |
The server cannot modify the access control entry. |
Action |
Correct the invoking method to specify a principal parameter. |
POP.004.0042 | Invalid Ace. Cannot set both granted and denied on the same right. |
Class | E |
Explanation |
The server cannot set a single access control entry to grant and deny the same access right. |
Action |
Correct the invoking source code. Consult the API documentation for more information. |
POP.004.0043 | Invalid Ace. Unknown right. |
Class | E |
Explanation |
The server cannot set access control entry with the right bit outside of the defined right bit range, as defined by the access service API. |
Action |
Correct the invoking source code. Consult the API documentation for more information. |
POP.004.0045 | Invalid Ace. Cannot delegate a right not granted. |
Class | E |
Explanation |
The server cannot modify the access control entry. |
Action |
Correct the invoking method to include the proper right set parameter. |
POP.004.0046 | Setting user name is not supported. |
Class | |
Explanation |
Internal group and user objects cannot have their name set |
Action |
Check and correct directory API usage |
POP.004.0047 | Cookie is not set in this view. |
Class | E |
Explanation |
The server cannot display the inbox notifications because a paging cookie was not set. |
Action |
Log out, log in, and try again. |
POP.004.0048 | Unable to load Subscription object. Subscription no longer exists. |
Class | E |
Explanation |
The server cannot locate the subscription information that triggered the notification. |
Action |
Delete the notification by locating the offending notification in the My webMethods Server inbox and deleting it. |
POP.004.0049 | Unable to load Event. |
Class | E |
Explanation |
The server cannot load event data because an error occurred in querying the database. |
Action |
Check the _problems_.log in My webMethods Server current logging directory for more specific error information. |
POP.004.0050 | Unable to remove Notification. |
Class | E |
Explanation |
The server was unable to locate the notification in order to delete it. |
Action |
Correct the invoking method to specify a valid notification parameter. |
POP.004.0051 | Unable to remove Event. |
Class | E |
Explanation |
The server cannot remove the event item from the database due to a SQL error while executing the stored procedure that performs the removal. |
Action |
Check the _problems_.log in My webMethods Server current logging directory for more specific error information. |
POP.004.0052 | Start index beyond end of list. |
Class | E |
Explanation |
The server cannot list a page of metadata resources because the specified start index of the page is greater than the total number of resources in the list. |
Action |
Correct the source code that executes the query. Specify a start index that is less than the total number of resources in the list by modifying the start property of the com.webmethods.portal.service.view.IPagingCookie. |
POP.004.0053 | Paged before first item. |
Class | E |
Explanation |
The server cannot list a page of metadata resources because the specified start or end index of the page is less than one. |
Action |
Correct the source code that executes the query. Specify a start index that is less than the total number of resources in the list by modifying the start or end properties of the com.webmethods.portal.service.view.IPagingCookie. |
POP.004.0054 | Invalid end index. |
Class | E |
Explanation |
The server cannot execute a paged container query because the page-start index is greater than the page-end index. |
Action |
Correct the source code that executes the query. Specify a start index that is less than the end index by modifying the start and end properties of the com.webmethods.portal.service.view.IPagingCookie. |
POP.004.0055 | Invalid sort order for getTreeView. |
Class | E |
Explanation |
The server cannot sort the tree view's results with the supplied sort parameter. |
Action |
Correct the invoking code to pass valid sort parameters. |
POP.004.0056 | Error saving subscription. No subscription or source information. |
Class | E |
Explanation |
The server cannot add the subscription because the subscription information is corrupted. |
Action |
Correct the invoking method to specify a valid subscription parameter. |
POP.004.0057 | Error adding subscription. No subscription or source information. |
Class | E |
Explanation |
The server cannot add the subscription because the subscription information is corrupted. |
Action |
Correct the invoking method and ensure that the proper parameters are passed. |
POP.004.0059 | Can't create an archived thing, use deactivate or delete. |
Class | |
Explanation |
The archived thing type cannot be created directly. It is created automatically when object is deleted |
Action |
Check and correct MWS API used when creating new object instance |
POP.004.0060 | Unable to save Role. |
Class | |
Explanation |
A database error occurred when saving role information |
Action |
Check logs for additional exception details |
POP.004.0061 | Unable to load Role. |
Class | E |
Explanation |
The server cannot load the metadata information for a registered role. |
Action |
Using the Role Administration portlet, regenerate and configure the role. |
POP.004.0062 | Missing results from the database. |
Class | E |
Explanation |
The server has received invalid results from a stored procedure. |
Action |
Verify that the database has been properly configured and that the schema was properly installed by paying close attention to the installation process. |
POP.004.0063 | Access model not set. |
Class | E |
Explanation |
The access service cannot evaluate access rights for a user until its access model has been specified. |
Action |
Correct the portal.properties file in the My webMethods Server config directory so that it has the following line: framework.access.model=restrictive. |
POP.004.0064 | Access model is not valid. |
Class | E |
Explanation |
The server cannot set the access model because the specified model is unknown. The valid model values are 1 (permissive) and 2 (restrictive). |
Action |
Correct the portal.properties file in the My webMethods Server config directory so that it has the following line: framework.access.model=restrictive. |
POP.004.0065 | Serialized object version is different then current version: [version, currentVersion] [{0},{1}] |
Class | E |
Explanation |
The server cannot read the alias stored in the database because its serialized object version is out of date. |
Action |
Revert to the previous version of wm-caf-server.jar, and restart the My webMethods Server. |
POP.004.0066 | Unknown type: {0} |
Class | E |
Explanation |
The server cannot initialize the directory search control because the specified query type is unknown. |
Action |
Correct the code invoking directory search to specify a type of 1 (users) or 2 (groups). |
POP.004.0067 | Attempted to set subkey on primary-key only key. |
Class | E |
Explanation |
The server cannot create the cache key. |
Action |
Correct the invoking method to include appropriate cache key parameter. |
POP.004.0068 | Can't find or create valid cache. |
Class | E |
Explanation |
The cache update stored procedure cannot resolve the cache identifier. |
Action |
Correct the invoking source code to provide a cache-key with a valid cacheID. Consult the API documentation for more information. |
POP.004.0069 | Cache error: data is not a serializable object |
Class | E |
Explanation |
The server attempted to cache an object that is not serializable. |
Action |
Correct the source code that invokes the com.webmethods.portal.service.cache.impl.DBCache.getBytesFromObject() method to pass serializable object. |
POP.004.0070 | Invalid connection parameters. |
Class | E |
Explanation |
The server cannot connect to the remote FTP server. |
Action |
Verify that the credentials and configuration are valid for the FTP connection service, using the Content Service Admin portlet. Verify that the network connectivity is valid. |
POP.004.0071 | Error persisting directory config. |
Class | E |
Explanation |
The server cannot store the directory configuration modifications. |
Action |
Use the Directory Services Administration portlet to create a new directory service and then delete the old one. |
POP.004.0072 | Cannot lookup non user or group thing based objects : {0} |
Class | E |
Explanation |
The server cannot look up directory service resources using metadata identifiers unless the resource is a user, group, or role. |
Action |
The identifier specified by the error message does not identify a directory resource, do not try to use it to identify a directory resource. |
POP.004.0073 | Invalid URI, no directory service specified for URI - "{0}" |
Class | E |
Explanation |
The server cannot locate an invalid directory user. |
Action |
Use the Directory Service Administration portlet to verify that the directory service is properly configured. |
POP.004.0074 | Specified domain in URI not found [domain, uri] -- [{0}, {1}]. This can be due to directory service being disabled or removed |
Class | E |
Explanation |
The server cannot look up the directory service based on a Portal identifier because the identified directory service does not exist. |
Action |
This error may have happened because the specified directory service configuration was deleted. Try re-adding the directory service using the Directory Services Administration portlet (in the Portal Configuration category of the Portal Admin Dashboard). |
POP.004.0075 | Cannot add directory service, service already exists: {0} |
Class | |
Explanation |
Directory service name must be unique. |
Action |
Check and correct directory service name being created. |
POP.004.0076 | Error adding new directory service: {0} |
Class | E |
Explanation |
The server cannot add or update a directory service because of an error in validating or storing the directory service configuration. |
Action |
Check the _problems_.log in the My webMethods Server current logging directory for more specific error information. |
POP.004.0077 | Cannot build URI, unknown type 0 |
Class | E |
Explanation |
The server cannot construct a My webMethods Server identifier for the directory service object because the specified type is not one of user, group, or role. |
Action |
Correct the source code that invokes the com.webmethods.portal.server.directory.impl.DirectoryTools.constructDirectoryURI() method to specify only either user, group, or role. |
POP.004.0078 | Invalid escape character in {0} at position {1} |
Class | E |
Explanation |
The server was unable to normalize the LDAP DN. |
Action |
Investigate the original DN and try to remove offending characters if possible. |
POP.004.0079 | Cannot retrieve most significant attribute; invalid DN: "{0}" |
Class | E |
Explanation |
The server cannot parse a directory service object DN (the object's LDAP ID), because the DN is invalid. |
Action |
Supply a valid DN to the com.webmethods.portal.service.directory.impl.jndi.JNDITools class's getMostSignificantAttr() and getMostSignificantAttrSet() methods. |
POP.004.0080 | Unable to connect to: {0} |
Class | E |
Explanation |
The server cannot connect to the remote LDAP directory store. |
Action |
Verify that the Directory configuration is valid by using the Directory Service Administration portlet. |
POP.004.0081 | No user class specified in directory factory config |
Class | E |
Explanation |
The server cannot store the directory configuration modifications. |
Action |
Use the Directory Services Administration portlet to create a new directory service and then delete the old one. |
POP.004.0082 | No group class specified in directory factory config |
Class | E |
Explanation |
The server cannot initialize the directory service. |
Action |
Verify that the Directory service is properly configured by using the Directory Service Administration portlet. |
POP.004.0083 | Unable to wrap object. Unkown type: {0} |
Class | E |
Explanation |
The server was unable to read an LDAP entry. |
Action |
Use the Directory Services Administration portlet to verify that the Directory configuration is valid. |
POP.004.0084 | Unable to wrap LDAP object: {0} |
Class | |
Explanation |
There was an error fetching LDAP object properties |
Action |
Check MWS logs for additional exception details |
POP.004.0085 | Error setting attribute [name, value, action, message] - [{0}, {1}, {2}, {3}] |
Class | E |
Explanation |
The server cannot modify the LDAP attribute. |
Action |
Verify that the connection to the LDAP directory store has adequate privileges to modify LDAP entries. Use your LDAP vendor's administration tool. |
POP.004.0086 | No response controls for directory: {0} |
Class | E |
Explanation |
The server cannot update the directory search control. |
Action |
Start a new search. |
POP.004.0087 | Cannot page backward |
Class | E |
Explanation |
The server cannot page directory search control backwards because the control is at the first page of results. |
Action |
Correct the source code invoking the directory search to check if the search has previous results before trying to page back to previous results. You can determine if a search has previous results by inspecting the value of the hasPrevious property of the com.webmethods.portal.service.view.IPagingCookie that you used to perform the search. |
POP.004.0088 | Cannot page forward |
Class | E |
Explanation |
The server cannot page the directory search control forward because the search has no more results. |
Action |
Correct the source code invoking the directory search to check if the search has more results before trying to page forward. You can determine if a search has more results by inspecting the value of the hasNext property of the com.webmethods.portal.service.view.IPagingCookie that you used to perform the search. |
POP.004.0089 | Unable to retrieve user list |
Class | E |
Explanation |
The server cannot list the users of a directory service, there might be a problem connecting to the directory service. |
Action |
If the directory service was recently configured directory service, go back to the My webMethods Server Admin Dashboard, and double-check the configuration using the Directory Service Administration portlet. Verify that the LDAP or ADSI server that connects to the directory service is up and running properly. Verify that the server the hosts My webMethods Server is able to connect to the LDAP or ADSI server using the hostname and port specified in the directory service's configuration. |
POP.004.0090 | Unable to lookup user {0} |
Class | E |
Explanation |
The server cannot locate the specified user. |
Action |
Use the User and Group Management portlet to verify that the group exists in the LDAP directory store. |
POP.004.0091 | Invalid username or password |
Class | E |
Explanation |
You have supplied invalid credentials. |
Action |
Try authenticating again with proper user name and password. |
POP.004.0092 | Could not lookup DN {0} |
Class | E |
Explanation |
The server cannot look up a user or group by directory DN, the user or group's LDAP ID, because an error occurred while querying the directory store. |
Action |
Check the _problems_.log in My webMethods Server current logging directory for more specific error information. |
POP.004.0093 | Error looking up group {0} |
Class | E |
Explanation |
The server cannot locate the specified group. |
Action |
Verify that the Directory service is configured by using the Directory Service Administration portlet. |
POP.004.0094 | Unable to perform search : {0} |
Class | E |
Explanation |
An unknown error occurred while performing an LDAP directory search. |
Action |
Correct the invoking method to specify a valid query parameter. |
POP.004.0095 | Error getting memberships |
Class | E |
Explanation |
The server cannot get membership information from the LDAP directory store. |
Action |
Verify that the Directory configuration is valid by using the Directory Service Administration portlet. |
POP.004.0096 | Unable to modify password of user {0} because the supplied old password is incorrect. |
Class | E |
Explanation |
An attempt was made to change a user's password without supplying the user's existing password. |
Action |
Supply the correct existing password. |
POP.004.0097 | INSTALL is not supported operation for: {0} |
Class | E |
Explanation |
Installation of the deployable object has failed. |
Action |
The deployable object does not have any installation code associated with its file extension. Do not attempt to deploy an unsupported type to the My webMethods Server. |
POP.004.0098 | UNINSTALL is not supported operation for: {0} |
Class | E |
Explanation |
The server cannot uninstall the specified type of component. |
Action |
The specified component was not uninstalled; try again. |
POP.004.0100 | Component file not found: {0} |
Class | E |
Explanation |
The server cannot install the component the component was not found at the specified location. |
Action |
Specify the correct location. If you are installing a component using the Install Administration portlet, select a valid location using the portlet's Browse button. |
POP.004.0101 | Cannot set properties for installer: {0} |
Class | E |
Explanation |
The server cannot set install services because an internal error occurred. |
Action |
Check the _problems_.log in My webMethods Server current logging directory for more specific error information. |
POP.004.0102 | Script file not found: {0} |
Class | E |
Explanation |
The server cannot execute a portlet deployment script. |
Action |
Using My webMethods Server, rebuild and redeploy the portlet. |
POP.004.0103 | Install script finished with {0} error(s). Please look at the install.log for details |
Class | E |
Explanation |
An error occurred while installing or uninstalling a deployable component. |
Action |
Examine the logs, and try again. Look for the information specific to the deployed component in the install.log file. |
POP.004.0104 | Error installing/uninstalling component |
Class | E |
Explanation |
An error occurred while installing or uninstalling a deployable component. |
Action |
Examine the logs, and optionally try again. Look for the information specific to the deployed component in the install.log file. |
POP.004.0105 | Failed to initialize LoggingCollector: {0} |
Class | E |
Explanation |
The server cannot initialize logging over the JMS provider. |
Action |
Verify that the JMS server is running and configured. |
POP.004.0106 | PortletInfo is not available for uri [{0}]. Probably the portlet is not properly installed. Try to uninstall and then install it again. |
Class | E |
Explanation |
Portlet is not currently available. |
Action |
Try to uninstall and then re-install the portlet again. |
POP.004.0107 | Invalid portlet descriptor. Portlet/DBO name is not defined |
Class | E |
Explanation |
The server cannot load portlet information from the portlet descriptor because the portlet descriptor does not contain the portlet's name, or the portlet descriptor is incorrectly structured. |
Action |
Using the My webMethods Server to correct the portlet descriptor and redeploy it to the My webMethods Server. |
POP.004.0109 | Portlet URI is not published instance of the portlet or type. Unable to persist properties |
Class | E |
Explanation |
The server cannot persist the properties of a portlet type without a valid portlet or portlet type identifier. |
Action |
Supply a valid portlet or portlet type identifier to the com.webmethods.portal.service.portlet.impl.PortletType.setProperties() method. |
POP.004.0110 | Portlet bean class is invalid: {0} |
Class | E |
Explanation |
The server cannot initialize the portlet because the portlet does not implement the required interface. |
Action |
Using My webMethods Server to correct the portlet's deployment descriptor or regenerate the portlet, and then redeploy it. |
POP.004.0111 | Portlet bean is not poolable: {0} |
Class | E |
Explanation |
The server cannot instantiate the portlet bean because the bean does not implement the com.webmethods.portal.system.pool.IPooledObject interface. |
Action |
Use My webMethods Server to correct the portlet bean source code to implement IPooledObject. |
POP.004.0112 | Portlet title bar class is invalid: {0} |
Class | E |
Explanation |
The server cannot initialize portlet type information because the portlet titlebar class specified by the portlet's descriptor was not found. |
Action |
Using the Portlet Developer, remove the titlebar class specification from the portlet descriptor and then redeploy the portlet. |
POP.004.0113 | Invalid URI, no search service specified: {0} |
Class | E |
Explanation |
The server cannot locate search provider because of an invalid URI. |
Action |
Correct the invoking code to use a valid URI. |
POP.004.0114 | Invalid datasource name: {0} |
Class | E |
Explanation |
The server cannot execute a SQL statement against an invalid datasource. |
Action |
Correct the invoking method to pass the correct parameters. One of the critical parameters is the handle of the datasource, which can be obtained from the DataManager's API. |
POP.004.0115 | Can't find data service folder: {0} |
Class | S |
Explanation |
The server cannot locate the system folder. |
Action |
It is possible that a system administrator has deleted a critical system folder. If so, you might need to reinstall My webMethods Server. |
POP.004.0116 | Cannot obtain database connection from pool: {0} |
Class | E |
Explanation |
The server cannot obtain a database connection because all connections allocated for My webMethods Server are already in use or My webMethods Server cannot connect to the database. |
Action |
Verify that the database is running and is not experiencing a heavy load. Verify that the database has an adequate number of connection threads available. Verify that the machine on which the My webMethods Server is running can access the datasource's configured host name and port. |
POP.004.0117 | Database connection is closed. |
Class | E |
Explanation |
The server cannot execute the SQL query because the database connection is closed. |
Action |
Execute the statement again. If problems persist, shut down and restart My webMethods Server. |
POP.004.0118 | Error updating Clob field |
Class | E |
Explanation |
An error occurred while updating an unbounded size database field at the database level. |
Action |
Try the operation again. |
POP.004.0119 | Error updating Blob field |
Class | E |
Explanation |
An error occurred in updating an unbounded size database field at the database level. |
Action |
Try the operation again. |
POP.004.0120 | Could not find content service for: {0} |
Class | E |
Explanation |
The server cannot store versioned content for a resource because the content service for the resource was not found. |
Action |
Delete the resource. |
POP.004.0121 | Versioned content uri is null or empty: {0} |
Class | E |
Explanation |
The server cannot access the versioning information. |
Action |
The version information is corrupted. Try to obtain a different version and recreate the changes. |
POP.004.0122 | Content doesn't exist: {0} |
Class | E |
Explanation |
The server cannot read a resource's versioned content because the resource has no content. |
Action |
Delete the resource using the UI. |
POP.004.0123 | User ID is invalid: {0} |
Class | E |
Explanation |
The server cannot locate the user's information about the versioned object. |
Action |
The version information is corrupted. Use the Publish portlet to publish a new instance of the item, and add the item to versioning. Consult the My webMethods Server documentation. |
POP.004.0124 | Could not find user: {0} |
Class | E |
Explanation |
Cannot locate the user's information about the versioned object. |
Action |
The version information is corrupt. Publish a new instance of the item, and add the item to versioning. |
POP.004.0125 | Could not find thing: {0} |
Class | E |
Explanation |
Cannot resolve metadata resource identifier from string. |
Action |
The resource specified by the identifier does not exist; do not use the identifier. |
POP.004.0126 | Cookie is not set on the List View |
Class | E |
Explanation |
The server cannot sort or slice the list without a paging cookie. |
Action |
Correct the invoking source code to associate the paging cookie with the list by setting the cookie property of the list. |
POP.004.0127 | Unable to initialize directory service {0}: {1} |
Class | E |
Explanation |
The server cannot initialize the directory service due to an error. |
Action |
Verify the connection information to the directory service using the Directory Service Administration portlet. Verify that the login credentials are accurate. Verify that there is network connectivity to the directory service from My webMethods Server. |
POP.004.0128 | Invalid directory Uri: "{0}" |
Class | E |
Explanation |
The URI is malformed. |
Action |
Correct the invoking method to specify a valid URI parameter. |
POP.004.0129 | Uri "{0}" should resolve to principal object, but was found: {1} |
Class | |
Explanation |
Attempting to look up a directory principal by a URL that does not resolve to a valid directory object. |
Action |
Check and correct directory API usage. Verify that the URI value used to look up directory object is valid. |
POP.004.0130 | Unidentified Clob implementation class: {0} |
Class | E |
Explanation |
The server cannot retrieve an unbounded-length field from the database because the database driver is incompatible with My webMethods Server. |
Action |
Modify the datasource driver settings in the db.xml My webMethods Server configuration file to use approved driver. |
POP.004.0131 | Unidentified Blob implementation class: {0} |
Class | S |
Explanation |
The server cannot retrieve result set data because of an incompatible database implementation. |
Action |
Verify that the correct version of Oracle is installed and that you are using the My webMethods Server supplied database drivers. You can consult your Oracle installation documentation to verify the version of Oracle and ensure that you have nt added any custom Oracle drivers in the class path. |
POP.004.0132 | Xtype not found: {0} |
Class | E |
Explanation |
The server cannot locate the portlet xtype in the metadata store. |
Action |
Most likely the portlet has been undeployed. Use the Install Administration portlet to redeploy the portlet. |
POP.004.0133 | XType already registered: {0} |
Class | |
Explanation |
Every XType (Portlet Name, Dynamic Business Object) must have a unique name. An attempt was made to install a new portlet or application that contains a portlet or Dynamic Business Object which is already registered in MWS. |
Action |
Check to see if an application or portlet was renamed. It is also possible that a component un-install was not fully successfull, in this case use /compnonent/development/tools/wm_remove_portlet to clean up and delete component registration in MWS. |
POP.004.0134 | Error loading class group: {0} |
Class | E |
Explanation |
The server cannot load all the classes for the specified class loader group. |
Action |
Check the _problems_.log in My webMethods Server current logging directory for more specific error information. |
POP.004.0135 | Error setting config on directory, rolling back to previous config. |
Class | E |
Explanation |
The server cannot store the directory configuration modifications. |
Action |
Use the Directory Services Administration portlet to create a new directory service and then delete the old one. |
POP.004.0136 | Unable to retrieve group list. |
Class | E |
Explanation |
The server cannot get group information from the LDAP directory store. |
Action |
Verify that the directory configuration is valid by using the Directory Service Administration portlet. |
POP.004.0141 | No configuration information found for content service, not initializing: {0}. |
Class | E |
Explanation |
The server cannot initialize the content service. |
Action |
If you cannot reconfigure the offending content service by using the Content Service Admin portlet call Software AG Global Support for a reset directive. |
POP.004.0144 | FTPconnection connect to {0}. |
Class | I |
Explanation |
A connection was initiated with the remote FTP server. |
Action |
This is an informative statement. No action is necessary. |
POP.004.0152 | No Query Parameters specified. |
Class | E |
Explanation |
The server cannot execute the search because there is no search query. |
Action |
Navigate to the Search portlet and try again. |
POP.004.0153 | Search Server is unavailable or not properly configured |
Class | E |
Explanation |
The server cannot access the search service. |
Action |
Verify that the search service is properly configured by using the Search Admin portlet. |
POP.004.0155 | Error adding file to search index: {0} |
Class | E |
Explanation |
The server was unable to properly index a My webMethods Server component object. |
Action |
Determine if the document is in an unknown format or is malformed. Examine the Lucene Search Admin portlet for details on formats. |
POP.004.0156 | content stream is null |
Class | E |
Explanation |
The server cannot locate the content file in the content repository. |
Action |
Verify that the existence of the content repository and network connectivity. The content repository has some configuration information in the storageConfig.xml. If a custom content service has been mounted, then verify that connectivity between the My webMethods Server process and the network file system is intact. Verify that you can browse to the content using My webMethods Server. Purge all items pending deletion with the Manage Deleted Items Admin Portlet. |
POP.004.0157 | Error getting resync list for library: {0} |
Class | E |
Explanation |
The server cannot resynchronize the search library index because an error occurred in querying the database for the list of resources to index. |
Action |
Restart the My webMethods Server. |
POP.004.0158 | Malformed Language Pack: {0} |
Class | E |
Explanation |
The server cannot use the language pack because its name is malformed. The name should be one of [language], [language]_[country], or [language]_[country]_[variant], where [language] is a language code such as en or ja, [country] is a country code such as US or JP, and [variant] is a variant code. |
Action |
Correct the language pack name and re-install language pack. |
POP.004.0187 | Could not lookup URI {0} |
Class | |
Explanation |
If the URI points to an invalid directory object (user or group) an error occurs. |
Action |
Check and correct directory API usage. Check what URI value was used. This error might also occur if the user was deleted immediately before logging in. The error will go away when MWS caches are updated, usually within seconds. |
POP.004.0196 | Role Modification is not supported for: {0}. |
Class | |
Explanation |
Only static roles support modification of role membership. This error is thrown when attempting to modify membership using the directory APIs for non-static roles |
Action |
Check and correct directory API usage. Check to see if the role being modified is static role |
POP.004.0197 | Failed to set property "{0}". Reason: {1} |
Class | |
Explanation |
Error has occurred when setting the thing object properties. This might happen when attempting to set the property of a specific java type, but passing in an incompatible value. |
Action |
Check MWS logs for additional error information. Check the values the code attempted to update and determine if the actual property types are valid. |
POP.004.0198 | Cannot create a user with a duplicate id: {0} |
Class | E |
Explanation |
An attempt was made to create a new user with a duplicate ID of an existing user. |
Action |
Use a unique identifier when creating a new user, group or role. |
POP.004.0199 | Cannot create a group with a duplicate id: {0} |
Class | E |
Explanation |
An attempt was made to create a new user with a duplicate ID of an existing user. |
Action |
Use a unique identifier when creating a new user, group or role. |
POP.004.0200 | Cannot create database connection to default MWS datasource. |
Class | |
Explanation |
Unable to create database connection to MWS database schema. |
Action |
Check MWS database connection configuration in MWS/server/default/config/mws.db.xml config file. |
POP.004.0201 | Cannot initialize MWS, invalid database schema is specified |
Class | |
Explanation |
MWS validates if database schema contains correct tables and then throws this error if it is not configured. |
Action |
Check if MWS database schema was correctly created by dbConfigurator tool. You might need to drop and re-create MWS schema. |
POP.004.0202 | Cannot create database connection to default MWS datasource. Please verify database connection parameters in the MWS/server/{0}/config/mws.db.xml configuration file |
Class | |
Explanation |
An issue has occurred with the database connection configuration file such as invalid XML or an incorrect JDBC driver name. |
Action |
Verify the database connection parameters in the MWS/server/default/config/mws.db.xml configuration file. |
POP.004.0203 | User {0} can not set access on {1} |
Class | |
Explanation |
User does not have access rights to set or update permissions. |
Action |
See if the user or groups and roles, the user is a member of has access rights to set permissions on a given object. |
POP.004.0204 | Failed to search business data with the "taskTypeID" query term specified. |
Explanation |
The taskTypeID is not specified in task search term. |
Action |
Provide a valid taskTypeID as a task search term. |
POP.004.0205 | Unable to locate whitelist storage object |
Explanation |
The required whitelist storage object cannot be located. |
Action |
Contact the system administrator to make sure that whitelist storage has been configured. |
POP.004.0206 | Failed to connect to database at {0}. Verify hostname/port and connection credentials. |
Explanation |
Failed to connect to database. |
Action |
Make sure the database is running and has a network connection, and that the proper credentials are in use. Otherwise, contact the system administrator to make sure database has been configured correctly. |
POP.004.0207 | Unable to update whitelist storage object |
Explanation |
Your user account has not been granted the privilege for updating a whitelist storage object. |
Action |
Contact the system administrator if you need this privilege. |
POP.004.0209 | Role name is empty. |
POP.005.0002 | Can Not Re-initialize CDS library |
Class | E |
Explanation |
An attempt was made to initialize the system twice. |
Action |
After My webMethods Server is initialized, do not attempt to do so again. |
POP.005.0003 | Error parsing segment urls: "{0}" |
Class | E |
Explanation |
One of the My webMethods Servers in the cluster has an incorrect URL. |
Action |
Determine the correct URL for the My webMethods Server, then log in to My webMethods Server as sysadmin and use the Cluster Administration portlet to correct the error. |
POP.005.0004 | Unable to register component: "{0}" due to "{1}" |
Class | E |
Explanation |
My webMethods Server could not register the specified component. |
Action |
Look in the _problems_.log file for the stack trace of the error. It might be necessary to reinstall the component. |
POP.005.0005 | Unable to reload component: "{0}" due to "{1}" |
Class | |
Explanation |
During dynamic reloading of a component (for example, a portlet), an error occurred. |
Action |
Check the logs to investigate what component failed to be reloaded. If the component is a portlet, then try uninstalling the portlet and reinstalling it, or try to revert to a previous version of the portlet. |
POP.005.0006 | This server node is not defined in the MWS cluster configuration: "{0}" |
Class | E |
Explanation |
The specified My webMethods Server is not included in the cluster configuration. |
Action |
Log in to My webMethods Server as sysadmin and use the Cluster Administration portlet to add the specified My webMethods Server to the cluster. |
POP.005.0007 | Front End URL is not specified in the MWS cluster configuration |
Class | |
Explanation |
The cluster doesn't have a valid configuration. |
Action |
Log in to My webMethods Server as sysadmin and use the Cluster Administration portlet to check the cluster configuration. |
POP.005.0008 | internal cache error |
Class | E |
Explanation |
An internal error occurred while removing an item from a cache. |
Action |
Inspect the _problems_.log for details of the failure. This error could indicate that there is invalid data in a cache. Restart My webMethods Server to address the problem. |
POP.005.0009 | Unable to loadComponent: "{0}" |
Class | E |
Explanation |
A failure occurred while loading a My webMethods Server component. |
Action |
Look in the _problems_.log file for the stack trace of the error. It may be necessary to reinstall the component. |
POP.005.0010 | Unknown object: "{0}" |
Class | E |
Explanation |
The ComponentData object for a component is of an unknown type. |
Action |
The componentData must be one of the handled object types. This error means that a My webMethods Server component could not initialize because it is invalid. Check the component for a valid configuration. |
POP.005.0013 | Command not found: "{0}" |
Class | |
Explanation |
A request to obtain a registered command failed. The command does not exist. |
Action |
Check the custom portlet invoking the command and ensure that it is specifying a deployed command. |
POP.005.0014 | Unbalanced "{1}" in value expression: "{0}" |
Class | |
Explanation |
A legacy portlet has created an illegal dynamic expression. |
Action |
Review the custom portlet for proper syntax of any dynamic expressions. |
POP.005.0021 | Attempting to use non empty My webMethods Server database for fresh deployment. Please make sure to create new empty My webMethods Server database |
Class | |
Explanation |
A first time startup check determined that the configured database is not a new database. A new database is required for a new installation. |
Action |
You must create new (empty) My webMethods Server database and configure My webMethods Server to connect to it. Please refer to the Software AG documentation for installing webMethods products. |
POP.005.0022 | Wrong version of My webMethods Server database: {0} but expected: {1} |
Class | |
Explanation |
A first time startup check determined that the configured database does not match the schema required by My webMethods Server. |
Action |
Verify that the specified database is properly configured. The database is likely configured with an old or incomplete schema. Please refer to the Software AG documentation for installing webMethods products. |
POP.005.0026 | Must have at least one server node defined |
Class | |
Explanation |
The cluster does not have a valid configuration. No server nodes are defined. |
Action |
Log in to My webMethods Server as sysadmin and use the Cluster Administration portlet to check the cluster configuration. |
POP.005.0028 | "{0}" server node must have at least one web stack listener enabled |
Class | |
Explanation |
Each node in the cluster is required to have at least one port enabled for accepting web requests. |
Action |
Log in to My webMethods Server as sysadmin and use the Cluster Administration portlet to check the cluster configuration. |
POP.005.0029 | server node name must not be empty |
Class | |
Explanation |
The cluster does not have a valid configuration. A server node name is not defined. |
Action |
Log in to My webMethods Server as sysadmin and use the Cluster Administration portlet to check the cluster configuration. |
POP.005.0030 | Credentials required. |
Explanation |
Credentials of a valid My webMethods Server user are required. |
Action |
Provide the user name and password of a valid My webMethods Server user account. |
POP.005.0031 | Credentials should be String[]. |
Explanation |
Credentials must be supplied in a string array format. |
Action |
Configure the JMX client to provide credentials in a string array format. |
POP.005.0032 | Credentials should have 2 elements. |
Explanation |
Two credential elements (user name and password) were expected, but a non-matching number of elements were provided. |
Action |
Provide only the user name and password. |
POP.005.0033 | JMX Authentication failed! |
Explanation |
The user cannot be authenticated within My webMethods Server. |
Action |
Provide a valid My webMethods Server user. |
POP.005.0034 | JMX Authorization failed! |
Explanation |
The provided user does not have sufficient privileges for connecting via JMX. |
Action |
Provide a user with the "Connect to JMX" privilege. |
POP.005.0035 | Insufficient privileges for establishing JMX communication! |
Explanation |
The provided user does not have sufficient privileges for connecting via JMX. |
Action |
Provide a user with the "Connect to JMX" privilege. |
POP.005.0036 | JMX Server Port number cannot be parsed. Port parameter value "{0}". |
Explanation |
The provided JMX port number is not an available port number. |
Action |
Change the JMX port configuration property to an available port number. |
POP.005.0037 | JDK 1.6 or higher is required to run JMX over SSL. |
Explanation |
My webMethods Server is currently started with JDK 1.5. |
Action |
Update the My webMethods Server JDK to JDK 1.6. |
POP.005.0039 | Cannot start CDS library because MWS did not initialize yet |
Explanation |
The CDS library cannot start because My webMethods Server has not initialized yet. |
Action |
Wait for My webMethods Server to initialize before starting the CDS library. |
POP.005.0040 | Cannot start common directory service because IS was started before MWS. Complete the MWS upgrade, which includes starting MWS, before performing the IS upgrade, which includes starting IS. See the upgrade guide for correct order. |
Explanation |
The CDS library cannot start because the My webMethods Server upgrade has not completed yet. |
Action |
Complete the My webMethods Server upgrade before starting the CDS library. |
POP.005.0041 | Unable to start server at port number {0} on host {1} (for: {2}) , reason : {3}. Perhaps another MWS process is already running? |
Explanation |
The server cannot be started at the specified port on the specified host due to the specified reason. |
Action |
Make sure that no other My webMethods Server instance is running on the same host using the same port. |
POP.005.0042 | Unable to start. The server name {0} could not be found in the cluster definition |
Explanation |
The server cannot start because the specified server name cannot be found in the cluster definition. |
Action |
Make sure that the server name matches the name specified in the cluster definition. |
POP.005.0043 | The JMS communication layer for common directory services (CDS) failed to initialize, which causes CDS assets to be out of sync. To enable JMS communication, specify a valid JNDI Provider URL on the Cluster Administration page in My webMethods and restart Integration Server. |
POP.006.0003 | portlet bean URI not specified |
Class | E |
Explanation |
The portlet:bean JSP tag does not contain a uri attribute to identify a valid portlet instance. |
Action |
Ensure that all instances of the 'portlet:bean' JSP tag include a 'uri' attribute. The attribute value must identify a valid portlet instance. Also, ensure that the portlet type referenced by the 'uri' attribute has been deployed and that all instances referenced by the attribute exist. |
POP.006.0004 | cannot create portlet bean for the URI "{0}" |
Class | E |
Explanation |
The portlet:bean JSP tag does not contain a uri attribute that identifies a valid portlet instance. |
Action |
Ensure that all instances of the 'portlet:bean' JSP tag include a 'uri' attribute. The attribute value must identify a valid portlet instance. Also, ensure that the portlet type referenced by the 'uri' attribute has been deployed, and that all instances referenced by the attribute exist. |
POP.006.0005 | parent "{0}" not found |
Class | |
Explanation |
The JSP page is invalid, because a JSP tag that is only valid when it is inside of a parent JSP tag is not inside the expected parent. |
Action |
Locate the error in the JSP page and correct the problem. |
POP.006.0006 | cannot find portlet bean named "{0}" in the current page context |
Class | E |
Explanation |
The portlet:portletController JSP tag does not contain a portlet attribute. The value of this attribute is the key to the pageContext entry in which a com.webmethods.portal.service.portlet.IPortletBean object is stored. |
Action |
Ensure that all instances of the 'portlet:portletController' JSP tag include a 'portlet' attribute that references a valid IPortletBean. |
POP.006.0007 | cannot obtain portlet info |
Class | E |
Explanation |
The portlet:info JSP tag does not contain an info attribute. The value of this attribute is the key to the pageContext entry in which a com.webmethods.portal.service.portlet.info.IPortletInfo object is stored. |
Action |
Ensure that all instances of the 'portlet:info' JSP tag include an 'info' attribute that references a valid IPortletInfo object. |
POP.006.0008 | cannot find portlet info named "{0}" in the current page context |
Class | E |
Explanation |
The portlet:propertyGroups, portlet:propertyGroup, or portlet:propertyLine JSP tag does not contain an info attribute. The value of this attribute is the key to the pageContext entry in which a com.webmethods.portal.service.portlet.info.IPortletInfo object is stored. |
Action |
Ensure that all instances of the 'portlet:propertyGroups', 'portlet:propertyGroup', and 'portlet:propertyLine' JSP tags include an 'info' attribute that references a valid IPortletInfo object. |
POP.006.0015 | cannot obtain portlet property info |
Class | |
Explanation |
The portlet configuration information could not be found. This problem could result from an invalid JSP page or a portlet installation that has been corrupted. |
Action |
Review the JSP page and ensure the portlet:propertyLine JSP tag is contained within a portlet:bean tag. If the JSP is correct and the problem persists, try re-installing the broken portlet. |
POP.006.0016 | cannot find portlet property info named "{0}" in the current page context |
Class | E |
Explanation |
The portlet:propertyLine JSP tag does not contain a propertyInfo attribute. The value of this attribute is the key to the pageContext entry in which a com.webmethods.portal.service.portlet.info.IPortletPropertyInfo object is stored. |
Action |
Ensure that all instances of the 'portlet:propertyLine' JSP tag include a 'propertyInfo' attribute that references a valid IPortletPropertyInfo. |
POP.006.0017 | portlet property name not specified |
Class | |
Explanation |
The JSP page contains a portlet:propertyLine tag that is missing the required "name" property. |
Action |
Review the JSP page and correct any missing "name" properties. |
POP.006.0018 | cannot obtain portlet property bag |
Class | E |
Explanation |
The portlet:propertyLine JSP tag does not contain a propertyInfo attribute. The value of this attribute is the key to the pageContext entry in which a com.webmethods.rtl.util.obj.IPropertyBag object is stored. |
Action |
Ensure that all instances of the 'portlet:bean' JSP tag include a 'propertyInfo' attribute that references a valid IPropertyBag. |
POP.006.0019 | cannot find portlet property bag named "{0}" in the current page context |
Class | E |
Explanation |
The portlet:propertyLine JSP tag does not contain a propertyInfo attribute. The value of this attribute is the key to the pageContext entry in which a com.webmethods.rtl.util.obj.IPropertyBag object is stored. |
Action |
Ensure that all instances of the 'portlet:bean' JSP tag include a 'propertyInfo' attribute that references a valid IPropertyBag. |
POP.006.0020 | object named "{0}" in the current page context is not a portlet property bag |
Class | E |
Explanation |
The portlet:propertyLine JSP tag does not contain a propertyInfo attribute. The value of this attribute is the key to the pageContext entry in which a com.webmethods.rtl.util.obj.IPropertyBag object is stored. |
Action |
Ensure that all instances of the 'portlet:bean' JSP tag include a 'propertyInfo' attribute that references a valid IPropertyBag. |
POP.006.0021 | "{0}" requires body content |
Class | |
Explanation |
A JSP page contains an sql:query tag with missing SQL query text in the tag body. |
Action |
The JSP page must be edited to either remove the tag or add the SQL query text as the tag body. |
POP.006.0022 | skin property not found |
Class | |
Explanation |
In a JSP page, the ui:img tag is trying to render an image from the skin, but the image was not defined in the skin. |
Action |
Edit the skin to add the missing image, or change the JSP page to reference an image that does exist. |
POP.006.0024 | 'IterateTag' container is null |
Class | E |
Explanation |
The util:iterate JSP tag does not contain a container attribute. The value of this attribute is the key to the pageContext entry in which a java.util.Collection, java.util.Iterator, or java.lang.Object[] object is stored. |
Action |
Ensure that all instances of the 'util:iterate' JSP tag include a 'container' attribute that references a valid container object. |
POP.006.0025 | "{0}" class not supported as an 'IterateTag' container |
Class | |
Explanation |
A JSP page uses the util:iterate tag, but the value of the 'container' property is not one of the supported data types. |
Action |
The JSP page must be edited to correct the problem. |
POP.006.0026 | "{0}" requires "{1}" attribute |
Class | |
Explanation |
A JSP page uses the util:iterate tag, but the "indexVar" tag attribute was not supplied. |
Action |
The JSP page must be edited to add the missing tag attribute. |
POP.006.0027 | cannot find 'PerfStartTag' token named "{0}" |
Class | |
Explanation |
A JSP page uses the util:perfEnd tag, but the perf token supplied in the "name" tag attribute does not exist. |
Action |
This problem most likely results from a malformed JSP page. The JSP developer should review the JSP page for any mismatched util:perfStart/util:perfEnd pairs. |
POP.006.0028 | cannot find XML DOM node named "{0}" in the current page context |
Class | E |
Explanation |
Use of the xml:valueOf JSP tag causes this exception. |
Action |
Remove all instances of the 'xml:valueOf' JSP tag. |
POP.006.0029 | cannot create XML DOM document from given XML stream |
Class | E |
Explanation |
The XML stream specified for the xml:xml JSP tag does not contain well-formed XML. |
Action |
Check the _problems_.log in the Portal's current logging directory for more specific error information. |
POP.006.0030 | cannot load XML DOM document for the specified location "{0}" |
Class | E |
Explanation |
The xml:xml JSP tag could not load a file from the location specified by the 'location' attribute. |
Action |
Edit instances of the 'xml:xml' JSP tag to include a 'location' attribute that correctly specifies the url to an XML document. |
POP.006.0031 | Required Property Editor parameter "{0}" not specified. |
Class | |
Explanation |
A JSP page is rendering a property editor, but a required parameter has not been supplied. |
Action |
The JSP developer should edit the JSP page to supply the missing required parameter. |
POP.006.0032 | Property Editor "{0}" not deployed. |
Class | |
Explanation |
A JSP page is trying to render a property editor that is not deployed to My webMethods Server. |
Action |
Deploy the missing property editor to My webMethods Server, or change the JSP page to use a property editor that is deployed to My webMethods Server. |
POP.006.0033 | invalid portlet bean URI: {0} |
Class | |
Explanation |
A JSP page is using either the portlet:bean or the portlet:controller tag in which the supplied portlet URI does not match an existing portlet instance. |
Action |
Deploy the missing portlet instance. Or, edit the JSP page to change the URI to match an exisitng portlet instance. |
POP.007.0002 | Error getting directory mechanics: "{0}" |
Class | |
Explanation |
The My webMethods Server instance was not properly installed. |
Action |
Re-create the My webMethods Server database schema and the My webMethods Server server instance. |
POP.007.0003 | Error rendering layout "{0}" due to "{1}" |
Class | |
Explanation |
There was an error either compiling or executing the application *.JSP page. |
Action |
You may need to run My webMethods Server with a full JDK which includes the Java compiler. Or, if you have modified any system JSP or NBSP pages, there may have been a syntax error. |
POP.007.0006 | Requested content was not found: "{0}" |
Class | |
Explanation |
An error occurred when attempting to browse to a page or file; the page or file does not exist in My webMethods Server. |
Action |
Verify that the URL being browsed to is correctly formed and specifies a valid URL. |
POP.007.0007 | Command not Found: "{0}" |
Class | E |
Explanation |
An attempt was made to execute a server command that is not deployed. |
Action |
Log in to My webMethods Server and use the Install Administration portlet to deploy the missing portlet. |
POP.007.0008 | The requested resource is not a webservice: "{0}" |
Class | |
Explanation |
An attempt was made to obtain a WSDL for a resource that is not a web service. |
Action |
Modify the request to specify a resource that is a web service. |
POP.007.0009 | You are not authorized to view the resource. |
Class | |
Explanation |
The current user does not have permission to view the specified object or page. |
Action |
Check the permissions for the object or page to ensure that the user has read rights |
POP.007.0010 | This renderer is unable to render: "{0}" |
Class | E |
Explanation |
An attempt was made to use the FolderRenderer to render an item that is not a folder. |
Action |
You cannot use the FolderRenderer for non-folders; specify a valid folder. |
POP.007.0011 | Unknown response: "{0}" |
Class | E |
Explanation |
The dispatch handler returned an unknown return code. |
Action |
Correct the dispatch handler to return a valid return code. |
POP.007.0012 | Cannot redirect to an invalid data type: "{0}" |
Class | |
Explanation |
An incorrect API was called when redirecting to new URL. This error is most likely to occur with a custom portlet. |
Action |
Verify that the portlet specifies the correct API for redirection. |
POP.007.0013 | Unable to find adequate authentication information to instantiate an http session |
Class | |
Explanation |
My webMethods Server is unable to authenticate an HTTP session. |
Action |
This error can occur because of incorrect implementation of custom authentication (such as, agent based authentication). Review the custom authentication scheme and verify that it is correctly implemented. |
POP.007.0023 | getWriter() has already been called on this response. |
Class | |
Explanation |
This error indicates an incorrect usage of the HttpResponse.getWriter() API and most likely occurred in a custom CAF application. |
Action |
Review the CAF application and check the implementation of the HttpResponse APIs. |
POP.007.0024 | getOutputStream() has already been called on this response. |
Class | |
Explanation |
This error indicates an incorrect usage of the HttpRespose.getOutputStream() API and most likely occurred in a custom CAF application. |
Action |
Review the CAF application and check the implementation of the HttpResponse APIs. |
POP.007.0026 | Response body content already written. |
Class | |
Explanation |
This error occurs when attempting to set the HttpResponse header when the response has been already partially or fully committed. This most likely occurred in a custom CAF application. |
Action |
Review the CAF application and check the implementation of the HttpResponse APIs. |
POP.007.0027 | Internal Error! Portlet Controller Bean is null. |
Class | |
Explanation |
The system cannot serve as the internal controller bean for the portlet. |
Action |
This error occurs only for non-CAF portlets. Log out and log back in to resolve this problem. |
POP.007.0028 | User not found: "{0}" |
Class | |
Explanation |
This error occurs when a user ID passed into My webMethods Server by a custom authentication handler cannot be matched. |
Action |
Verify that the specified user exists in the My webMethods Server directories, and check the custom authentication handler logic. |
POP.007.0029 | No authentication information was found. |
Class | |
Explanation |
No user name was supplied to My webMethods Server when authenticating a user. This error can occur with a custom authentication handler. |
Action |
Check the implementation of the custom authentication handler. Verify the proper operation of any custom login forms. |
POP.007.0033 | No portlet found to render "{0}" view. |
Class | |
Explanation |
This error can occur if there is a registered portlet renderer, but the portlet defined in the renderer is not found. |
Action |
Renderers are used internally by My webMethods Server to define certain system pages. If this error occurs, check to see if any of the My webMethods Server system components have been un-installed. |
POP.007.0035 | The value {0} can not be changed |
Class | |
Explanation |
An attempt has been made to change the value of an invalid portlet preference. |
Action |
Verify that the correct portlet preference name is used. |
POP.007.0036 | The store() method can not be called from a render method |
Class | |
Explanation |
An attempt was made to change and persist portlet preferences from the render() method. |
Action |
Portlet preferences can be changed only with the portlet action method. Correct the code which updates portlet preferences to use the proper method. |
POP.007.0037 | The state of the portlet can not be changed |
Class | |
Explanation |
Portlet preferences can be updated only during the action() request. |
Action |
Correct the usage of the portlet preferences APIs to change preferences during the action() request. |
POP.007.0038 | The key given is null. |
Class | |
Explanation |
An attempt was made to use the portlet preferences API with a NULL preference name. |
Action |
Correct the portlet preferences API implementation to specify a valid preference name. |
POP.007.0044 | The map given is null |
Class | |
Explanation |
This error indicates an incorrect usage of the portlet URL APIs; the parameter map setting is NULL. |
Action |
Correct the portlet URL APIs implementation to specify a valid parameter map. |
POP.007.0045 | The map given contains a null key |
Class | |
Explanation |
This error indicates an incorrect usage of the portlet URL APIs; the parameters map setting contains a NULL key. |
Action |
Correct the portlet URL APIs implementation to specify a valid parameter map key. |
POP.007.0046 | The map contains a non String key |
Class | |
Explanation |
This error indicates an incorrect usage of the portlet URL APIs; the parameters map setting contains non-String values. |
Action |
Correct the portlet URL APIs implementation to pass in only String type parameters. |
POP.007.0047 | Namespace prefix defined more than once for {0} |
Class | |
Explanation |
An incorrect URL was passed into My webMethods Server; more than one namespace prefix is provided. |
Action |
Check that the URL passed into My webMethods Server contains only one single value for the namespace prefix. |
POP.007.0048 | Namespace prefix is not defined for {0} and the prefix id is not a valid thingID |
Class | |
Explanation |
An incorrect URL was passed into My webMethods Server; no namespace prefix is provided. |
Action |
Modify the URL passed into My webMethods Server to define the missing namespace prefix. |
POP.007.0049 | The portlet mode {0} is not supported for the {1} markup language. |
Class | |
Explanation |
The requested mode is not implemented in the portlet or is not supported. |
Action |
Check the portlet URL API usage if attempting to set the mode with APIs. If this is a custom portlet, check to see if the portlet implements this mode. |
POP.007.0051 | Output generated because of an exception |
Class | |
Explanation |
An exception occurred while rendering portlet content. |
Action |
Refer to the server logs at ..\MWS\server\default\logs for additional exception details. |
POP.007.0052 | sendRedirect was already called |
Class | |
Explanation |
An attempt was made to change the portlet window state, mode, or parameters after a redirect request was sent. |
Action |
Examine and correct the usage of the redirect request in the portlet code. |
POP.007.0053 | The portlet mode is null |
Class | |
Explanation |
An attempt was made to set a NULL portlet mode. |
Action |
Examine and correct the usage of the Portlet URL API. |
POP.007.0054 | The window state {0} is not supported by the portlet container |
Class | |
Explanation |
An attempt was made to set an invalid window state. |
Action |
Examine and correct the window state being set by the Portlet URL APIs. |
POP.007.0055 | The window state is null |
Class | |
Explanation |
An attempt was made to set a NULL window state. |
Action |
Examine and correct the window state being set by the Portlet URL APIs. |
POP.007.0056 | The portlet mode {0} is not supported by the portlet container |
Class | |
Explanation |
An attempt was made to set an invalid portlet mode. |
Action |
Examine and correct the portlet mode being set by the Portlet URL APIs. |
POP.007.0057 | The map contains a non String[] value |
Class | |
Explanation |
An attempt was made to set a parameter with a value that is not of the type String[]. |
Action |
Examine and correct parameters being by the Portlet URL API; these values must be String or String[] types only. |
POP.007.0058 | The key given is null |
Class | |
Explanation |
An attempt was made to pass in a NULL key value. |
Action |
Examine and correct the key value that is being passed in by the Portlet URL AP1. |
POP.007.0059 | The value given is null |
Class | |
Explanation |
An attempt was made to pass in a NULL value. |
Action |
Examine and correct the value being passed in by the Portlet URL API. |
POP.007.0060 | The sendRedirect method can not be invoked after any of the following methods of the ActionResponse interface has been called: setPortletMode, setWindowState, setRenderParameter, setRenderParameters |
Class | |
Explanation |
The sendRedirect method can not be invoked after any of the following methods of the ActionResponse interface has been called: setPortletMode, setWindowState, setRenderParameter, setRenderParameters |
Action |
Correct the code to ensure that the sendRedirect() method does not occur after these calls during the same action request. |
POP.007.0061 | A relative or incorrect path URL is given |
Class | |
Explanation |
An attempt was made to redirect to an invalid URL. |
Action |
Check the URL that is the target of the redirect. It must start with "http://", "https://", or "/". |
POP.007.0062 | You cannot have null as a parameter |
Class | |
Explanation |
An attempt was made to pass in a NULL parameter name. |
Action |
Examine and correct the parameter name used in the PortletContext and PortletRequest APIs. |
POP.007.0063 | Content type cannot be application/x-www-form-urlencoded |
Class | |
Explanation |
Incorrect API usage. The ServletRequest.getReader() and getInputStream() methods are not available for requests where a form is submitted. |
Action |
Examine and correct the ServletRequest.getReader() and getInputStream() API usage. |
POP.007.0064 | This method cannot be called, when getReader() method has been called |
Class | |
Explanation |
The ServletResponse method cannot be used when the getReader() method has been called. |
Action |
Examine and correct the ServletResponse API usage. |
POP.007.0065 | The attribute name cannot be null |
Class | |
Explanation |
An attempt was made to get or set an attribute using a NULL name. |
Action |
Examine and correct the attribute name being passed to the API. |
POP.007.0066 | Path must start with / |
Class | |
Explanation |
An attempt was made to get a resource using an invalid path. The path of the resource must start with "/". |
Action |
Examine and correct the path name set by the PortletContext API. |
POP.007.0069 | The content type {0} is not supported. |
Class | |
Explanation |
An attempt was made to set an invalid content type. |
Action |
Check and correct the content type being set by the PortletResponse API. |
POP.007.0070 | The content type has not been set before calling the getPortletOutputStream() method. |
Class | |
Explanation |
The response content type must be set before obtaining the output stream. |
Action |
Examine and correct the API calls. |
POP.007.0071 | the output stream has already been called |
Class | |
Explanation |
A Writer cannot be obtained for the response after obtaining the output stream. |
Action |
Examine and correct the API usage. |
POP.007.0072 | the PrintWriter object has already been called |
Class | |
Explanation |
A Writer cannot be obtained for the response because the output stream has already been obtained. |
Action |
Examine and correct the API usage. |
POP.007.0073 | Can not serialize Portlet Preferences |
Class | |
Explanation |
There was error when serializing portlet preferences. Portlet preferences cannot contain non-serializable objects. |
Action |
Check the server log for more details. Examine and correct any portlet preferences being set to ensure only serializable objects are used. |
POP.007.0074 | Portlet Application "{0}" is not properly installed or unavailable. |
Class | |
Explanation |
The system cannot load the specified portlet application. It is either not installed or is disabled in the cluster partition. |
Action |
Re-install the portlet application. Check the server logs for errors during installation. Verify that the application is enabled in the cluster partition. |
POP.007.0075 | Portlet "{0}" is not found |
Class | |
Explanation |
The specified portlet is not installed or is disabled in the cluster partition. |
Action |
Verify that the portlet application is installed; install if necessary. Check the server logs for any installation errors. Verify that the portlet is enabled in the cluster partition. |
POP.007.0076 | PortletContainer Servlet "{0}" is not found. Check default web application configuration file (defaultPortletAppWeb.xml) |
Class | |
Explanation |
System servlet is not found. |
Action |
Determine if any changes were made to system configuration files in ../MWS/server/default/deploy/portal.war. Re-install My webMethods Server. |
POP.007.0077 | You are not authorized to view the resource. {0} |
Class | |
Explanation |
The current user does not have permission to read the specified object or resource. |
Action |
Examine and correct the user account permissions. |
POP.007.0078 | This action requires an anti-cross-site-request-forgery token. |
Class | |
Explanation |
The executed command or action did not specify an anti-cross-site-request-forgery token. |
Action |
Check if the given command or action does require an AXRF token. If it does require a token, the token must be explicitly generated and passed in as a URL parameter. For example, when calling a CAF action from a portlet URL, the action must either be configured to not require a token (which lessens security), or a token must be generated when calling this action from a direct URL. |
POP.007.0101 | Illegal Property Editor name: "{0}". |
Class | |
Explanation |
A legacy portlet property uses an invalid property-editor name. |
Action |
Examine and correct the property-editor name in the wm-portlet.xml file (this applies only to legacy non-CAF portlets). |
POP.007.0102 | Illegal Property Editor parameter value for "{0}": "{1}". |
Class | |
Explanation |
An incorrect parameter value was passed to the property editor. |
Action |
Check the property editor configuration in the wm-portlet.xml file (this applies only to legacy non-CAF portlets). |
POP.007.0103 | Property Editor requires DHTML. |
Class | |
Explanation |
The property editor "dhtml" property configuration is invalid. The property editor requires DHTML to be enabled. |
Action |
Examine the property editor configuration in the wm-portlet.xml file. Set dhtml=true (this applies only to legacy non-CAF portlets). |
POP.007.0105 | Property editor "{0}" parameter "{1}" of type "choice" defined without choices. |
Class | |
Explanation |
An invalid 'choice' parameter value was supplied to the property editor. |
Action |
Examine the property editor configuration in the wm-portlet.xml file (this applies only to legacy non-CAF portlets). |
POP.007.0106 | Illegal property editor "{0}" attribute: "{1}" value: "{2}". |
Class | |
Explanation |
An invalid property editor attribute was encountered. |
Action |
Examine the property editor configuration in the wm-portlet.xml file (this applies only to legacy non-CAF portlets). |
POP.007.0107 | Illegal property editor "{0}" parameter "{1}" attribute "{2}" value: "{3}". |
Class | |
Explanation |
An invalid property editor attribute was encountered. |
Action |
Examine the property editor configuration in the wm-portlet.xml file (this applies only to legacy non-CAF portlets). |
POP.007.0108 | Illegal property editor "{0}" parameter "{1}" choice "{2}" attribute "{3}" value: "{4}". |
Class | |
Explanation |
An invalid property editor attribute was encountered. |
Action |
Examine the property editor configuration in the wm-portlet.xml file (this applies only to legacy non-CAF portlets). |
POP.007.0109 | Property Editor not deployed: "{0}". |
Class | |
Explanation |
An incorrect property editor was specified for use |
Action |
Examine the property editor configuration in the wm-portlet.xml file (this applies only to legacy non-CAF portlets). |
POP.007.0110 | Illegal Redirect URL: "{0}". |
Class | |
Explanation |
An invalid redirect URL was provided. |
Action |
Check and correct the redirect URL used in the API calls. |
POP.009.0001 | WebService invocation is disabled for the requested command |
Class | |
Explanation |
An attempt was made to invoke a My webMethods Server command as a web service, but the command does not allow invocation as a web service. |
Action |
1. Enable the command if it is disabled. 2. For some commands it is not possible to execute them with a web service. If this is one of those commands, no other action can be taken. |
POP.009.0002 | No WebService type mapping found for java class: {0} |
Class | |
Explanation |
For a My webMethods Server command being invoked as a web service, one or more of the command bean (input) fields to the command does not have a SOAP serializer (or deserializer) defined. Therefore, the My webMethods Server framework cannot convert the data to a SOAP message. |
Action |
The command developer must either mark the command as not enabled for web service invocation, or write the custom serializer/deserialzer code for the data type and register it in the type mapping registry by overriding the "initializeSOAPMappingRegistry" method of the command Java class. |
POP.009.0003 | The CommandBean must implement ISoapComplexTypeBean to be used as a WebService |
Class | |
Explanation |
For a My webMethods Server command being invoked as a web service, the command bean Java class does not implement the interface that is required to be used as a web service. |
Action |
The command developer must either mark the command as not enabled for web service invocation, or change the command bean Java class to have it implement the interface. |
POP.009.0004 | Error initializing ServiceDesc for WebService: {0} |
Class | |
Explanation |
An unexpected exception was detected while preparing a My webMethods Server command to be invoked as a web service. |
Action |
Inspect the stack trace in the My webMethods Server server log files to determine the cause of the exception. |
POP.009.0005 | No WebService marshalling factories are defined for type {0}, and the type can not be treated as a javabean because it does not contain a public no-arg constructor |
Class | |
Explanation |
For a My webMethods Server command being invoked as web service, one of the inputs or outputs is a complex Java class that does not have a no-arg constructor. Therefore, it cannot be automatically marshalled into a SOAP message. |
Action |
The command developer must either mark the command as not enabled for web service invocation, or add a no-arg constructor to the Java class. |
POP.009.0006 | SAML or Hybrid authentication can not be used. Please deploy SAML Security Service component or use Basic authentication instead |
Explanation |
The SAML security service is not available. |
Action |
Deploy the SAML security service component or use basic authentication instead. |
POP.009.0007 | Could not find a user context. |
Explanation |
Cannot find UID for the user. |
Action |
Specify a correct UID. |
POP.009.0008 | The SAML service you are trying to access is not available right now. |
Explanation |
The SAML service is currently unavailable. |
Action |
Inspect the stack trace in the My webMethods Server log files to determine the cause of the exception. |
POP.009.0009 | Failed to initialize WS-Stack clients within {0} milliseconds. They will be disabled. |
Explanation |
The Web Services Stack client failed to initialize in the specified period. |
Action |
Check the OSGi configuration at com.softwareag.platform.config.propsloader or restart My webMethods Server to re-initialize Web Services Stack. |
POP.009.0102 | {0}: {1} is not a IThingIDList |
Class | |
Explanation |
The SOAP serializer that is intended to marshall a IThingIDList object into a SOAP message was passed the wrong type of object. |
Action |
This is most likely a defect in the way the type mapping registry was initialized. Examine the related code to determine the problem and correct as required. |
POP.011.0001 | The method "{0}" has not been implemented. |
Class | |
Explanation |
An attempt was made to improperly invoke a Dynamic API. |
Action |
Examine the logs for an indication of what component and user action caused this error. |
POP.011.0002 | must specifiy both 'prefix' and 'uri' parmeters for 'taglib' directive |
Class | |
Explanation |
A syntax error occurred while parsing a JSP page. |
Action |
Correct the syntax error on the JSP page. |
POP.011.0003 | expected "{0}" end tag but found "{1}" end tag |
Class | |
Explanation |
A syntax error occurred while parsing a JSP page. |
Action |
Correct the syntax error on the JSP page. |
POP.011.0005 | "{0}" tag declared invalid by TagExtraInfo |
Class | |
Explanation |
A syntax error occurred while parsing a JSP page. |
Action |
Correct the syntax error on the JSP page. |
POP.011.0006 | "{0}" tag requires "{1}" attribute |
Class | |
Explanation |
A syntax error occurred while parsing a JSP page. |
Action |
Correct the syntax error on the JSP page. |
POP.011.0007 | specified attribute "{0}" for "{1}" tag not declared in tld |
Class | |
Explanation |
A syntax error occurred while parsing a JSP page. |
Action |
Correct the syntax error on the JSP page. |
POP.011.0008 | specified attribute "{0}" value for "{1}" tag cannot be request-time expression |
Class | |
Explanation |
A syntax error occurred while parsing a JSP page. |
Action |
Correct the syntax error on the JSP page. |
POP.011.0009 | request cannot be null |
Class | |
Explanation |
An error occurred while uploading a file. |
Action |
Check the logs for additional information. |
POP.011.0010 | saveDirectory cannot be null |
Class | |
Explanation |
An error occurred while uploading a file. |
Action |
Use the Content Service page to ensure that a directory is configured to store the uploaded files. |
POP.011.0011 | maxPostSize must be positive |
Class | |
Explanation |
An error occurred while uploading a file. |
Action |
Use the Content Service page to ensure that a maximum size for uploaded fixes is configured. |
POP.011.0012 | "{0}" is not a directory. |
Class | E |
Explanation |
The temporary location for for saving a file upload is not valid. |
Action |
Delete all files in the Portal/server/default/temp folder. |
POP.011.0013 | "{0}" is not writable directory. |
Class | W |
Explanation |
The temporary location for saving a file upload is not writable. |
Action |
Make sure My webMethods Server was started by a user who has rights to the portal temp folder. |
POP.011.0014 | Posted content type "{0}" isn't multipart/form-data. |
Class | E |
Explanation |
My webMethods Server expects to upload a multipart portlet, but the specified content type does not match. |
Action |
Check the source file for corruption. If the file is valid and correct, try uploading it again. |
POP.011.0015 | Posted content length of "{0}" MB exceeds limit of "{1}" MB. |
Class | E |
Explanation |
An uploaded file is larger than the size allowed by the system administrator. |
Action |
Upload a smaller file or have the system administrator use the Content Service Administration portlet to increase the maximum allowed file size. |
POP.011.0016 | Separation boundary was not specified. |
Class | E |
Explanation |
The specified file was corrupted before or during the upload process. |
Action |
Check the source file for corruption. If the file is valid and correct, try uploading it again. |
POP.011.0017 | Corrupt form data. No leading boundary was found. |
Class | E |
Explanation |
The specified file was corrupted before or during the upload process. |
Action |
Check the source file for corruption. If the file is valid and correct, try uploading it again. |
POP.011.0018 | Malformed line after disposition "{0}" |
Class | E |
Explanation |
The specified file was corrupted before or during the upload process. |
Action |
Check the source file for corruption. If the file is valid and correct, try uploading it again. |
POP.011.0019 | The published file was empty or invalid. |
Class | E |
Explanation |
The specified file was corrupted before or during the upload process. |
Action |
Check the source file for corruption. If the file is valid and correct, try uploading it again. |
POP.011.0020 | Content disposition "{0}" is corrupt. |
Class | E |
Explanation |
The specified file was corrupted before or during the upload process. |
Action |
Check the source file for corruption. If the file is valid and correct, try uploading it again. |
POP.011.0021 | Invalid content disposition "{0}". |
Class | |
Explanation |
An error occurred while processing the uploaded file. |
Action |
Investigate the contents of the HTTP POST to see if the data was corrupted. |
POP.011.0022 | Content type corrupt "{0}". |
Class | E |
Explanation |
The specified file was corrupted before or during the upload process. |
Action |
Check the source file for corruption. If the file is valid and correct, try uploading it again. |
POP.011.0023 | Malformed line after disposition "{0}". |
Class | E |
Explanation |
The specified file was corrupted before or during the upload process. |
Action |
Check the source file for corruption. If the file is valid and correct, try uploading it again. |
POP.011.0024 | No file name available. |
Class | |
Explanation |
An error occurred while uploading a file. |
Action |
Examine the contents of the HTTP POST to see if the data was corrupted. |
POP.011.0025 | Failed to create a DocumentBuilderFactory. |
Class | E |
Explanation |
The XML parser appears to be missing. |
Action |
Check for the xercesImpl.jar file in the portal class path. If the file is missing, reinstall My webMethods Server. |
POP.011.0026 | Failed to create a TransformerFactory. |
Class | E |
Explanation |
The Xalan XSTL processor could not be loaded. |
Action |
Check for the xalan.jar file in the portal classpath. If the file is missing, reinstall My webMethods Server. |
POP.011.0027 | JMS already initialized with "{0}". |
Class | |
Explanation |
An error occurred during startup. |
Action |
Ensure that startup routines are invoked only once. |
POP.011.0028 | JMSProvider: failed to get configuration file. |
Class | E |
Explanation |
The JMS provider appears to be disconnected. |
Action |
Verify that the Broker is running and that My webMethods Server can connect to the computer on which the Broker is running. |
POP.011.0029 | JMSProvider: failed to get configuration file "{0}", due to "{1}". |
Class | E |
Explanation |
The JMS provider appears to be disconnected. |
Action |
Verify that the Broker is running and that My webMethods Server can connect to the computer on which the Broker is running. |
POP.011.0030 | JNDI name not found: "{0}". |
Class | E |
Explanation |
The JMS provider appears to be disconnected. |
Action |
Verify that the Broker is running and that My webMethods Server can connect to the computer on which the Broker is running. |
POP.011.0031 | Can't initialize perf service: "{0}". |
Class | |
Explanation |
The specified Performance Service failed to initialize. |
Action |
Check the perfUtils.properties configuration file for spelling errors. |
POP.011.0032 | Perf Service Not Initialized. |
Class | |
Explanation |
An attempt was made to use the Performance Service before it was initialized. |
Action |
The Performance Service might be disabled. Check the contents of the perfUtils.properties configuration file. |
POP.011.0033 | Cannot open stream. Location: "{0}". |
Class | |
Explanation |
An attempt to access a file failed. |
Action |
Ensure that the file exists at the specified location. |
POP.011.0034 | Size read mismatch "{0}" vs "{1}" |
Class | E |
Explanation |
An InputStream corruption error occurred. |
Action |
Examine the _problems_.log file for the stack trace of the error. The stack trace may not provide enough detail to explain why the error was thrown, but it will show where the error originated. |
POP.011.0035 | Cannot create temporary folder: "{0}" |
Class | |
Explanation |
Folder creation failed. |
Action |
Most likely, the current process lacks Write access to the configured temporary folder. |
POP.011.0036 | Unable to delete file: "{0}" |
Class | E |
Explanation |
An error occurred while removing a temporary file. |
Action |
Find the specified file and remove it manually. |
POP.011.0037 | Unable to delete directory: "{0}" |
Class | E |
Explanation |
An error occurred while cleaning up temporary files. |
Action |
Find the specified directory and manually remove the temporary files. |
POP.011.0039 | ObjectUtil: illegal arguments. |
Class | E |
Explanation |
An error occurred while setting a property on an object, because the target object is null or the property name is null or empty. |
Action |
Examine the _problems_.log file for the stack trace of the error. The stack trace may not provide enough detail to expalin why the error was thrown, but it will show where the error originated. |
POP.011.0044 | Error obtaining JMS topic for name: "{0}" |
Class | E |
Explanation |
The requested JMS topic is not available. |
Action |
Verify that Broker is running and that My webMethods Server can connect to the computer on which Broker is running. |
POP.011.0045 | no JMS provider, requesting topic name: "{0}" |
Class | E |
Explanation |
The JMS provider appears to be disconnected. |
Action |
Verify that Broker is running and that My webMethods Server can connect to the computer on which Broker is running. |
POP.011.0046 | JMSTopic.createTopicSession(), no JMS provider. |
Class | E |
Explanation |
The JMS provider appears to be disconnected. |
Action |
Verify that Broker is running and that My webMethods Server can connect to the computer on which Broker is running. |
POP.011.0047 | Unable to connect to registry. |
Class | E |
Explanation |
The My webMethods Server configuration registry is unavailable. |
Action |
In a cluster deployment, make sure the Master server is started before starting the other cluster nodes. |
POP.011.0048 | no protocol defined for: "{0}" |
Class | |
Explanation |
The system tried to load a file from an unknown protocol. |
Action |
Check the protocol string spelling. |
POP.011.0053 | Error obtaining JMS queue for name: "{0}" |
Class | E |
Explanation |
The requested JMS queue is unavailable. |
Action |
Verify that Broker is running and that My webMethods Server can connect to the computer on which Broker is running. |
POP.011.0054 | no JMS provider, requesting queue name: "{0}" |
Class | E |
Explanation |
The JMS provider appears to be disconnected. |
Action |
Verify that Broker is running and that My webMethods Server can connect to the computer on which Broker is running. |
POP.011.0055 | JMSTopic.createQueueSession(), no JMS provider. |
Class | E |
Explanation |
The JMS provider appears to be disconnected. |
Action |
Verify that Broker is running and that My webMethods Server can connect to the computer on which Broker is running. |
POP.011.0056 | Invalid line: "{0}" |
Class | E |
Explanation |
An error occurred in parsing a .properties file. |
Action |
Look in the _problems_.log file for the stack trace of the error. The stack trace may not provide enough detail to explain why the error was thrown, but it will show where the error originated. |
POP.011.0057 | JMSDestination.Subscriber, unable to create consumer on: "{0}" |
Class | E |
Explanation |
The JMS provider appears to be disconnected. |
Action |
Verify that Broker is running and that My webMethods Server can connect to the computer on which Broker is running. |
POP.011.0058 | JMSDestination.Subscriber, unable to create session for: "{0}" |
Class | E |
Explanation |
The JMS provider appears to be disconnected. |
Action |
Verify that Broker is running and that My webMethods Server can connect to the computer on which Broker is running. |
POP.011.0062 | Stream exhausted. |
Class | E |
Explanation |
An error occurred in decoding a BASE64 String. |
Action |
Examine the _problems_.log file for the error stack trace. The stack trace may not provide enough detail to explain why the error was thrown, but it will show where the error originated. |
POP.011.0063 | BASE64Encoder: Bad Padding byte. |
Class | E |
Explanation |
An error occurred in decoding a BASE64 String. |
Action |
Examine the _problems_.log file for the error stack trace. The stack trace may not provide enough detail to explain why the error was thrown, but it will show where the error originated. |
POP.011.0065 | There must be a default entry --> default=icon_def.gif. |
Class | |
Explanation |
The iconMap.properties file is corrupted. |
Action |
Revert any changes made to this file. |
POP.011.0068 | Output stream not set for: "{0}" |
Class | |
Explanation |
An error occurred during page rendering. |
Action |
Check the logs for problems that result in this situation. |
POP.011.0076 | Unable to convert data type "{0}" to "{1}" |
Class | |
Explanation |
The system failed in the attempted type coercion. |
Action |
If possible, check the input value to ensure that it can be properly coerced to the target data type. |
POP.012.0001.tagname_error | Not a valid value!Tag Name cannot contain spaces. |
Class | |
Explanation |
The Tag Name cannot contain spaces. |
Action |
Make sure the value of the Tag Name field is correct. |
POP.012.0001.wm_axsrftconfig | This action requires a custom anti-cross-site-request-forgery token. |
Class | |
Explanation |
An invalid custom token is provided during portlet configuration. |
Action |
Check and, if needed, re-configure the New Secret Interval and Oldest Secret preferences in wm_axsrftconfig. |
POP.012.0001.wm_caf_task | Cannot upload this file as it is empty.Uploading empty files is not allowed. |
Explanation |
Content cannot contain an empty file, therefore uploading is not allowed |
Action |
Make sure that the file contains content. |
POP.012.0001.wm_calendar | Illegal "{0}" parameter value: "{1}". |
Class | |
Explanation |
The start date of an entry in the calendar is missing. |
Action |
Specify the start date of the entry in the calendar. |
POP.012.0001.wm_cforms_layout | Recursive use of Composite Form for "{0}". |
Class | |
Explanation |
The composite form for "{0}" is attempting to display an item that displays the same composite form for "{0}". For instance, the composite form for "{0}" is displaying a form containing the same composite form for "{0}"). |
Action |
Change the composite form for "{0}" "view" property to a different item. |
POP.012.0001.wm_commonsearchbar | Search Context Portlet URI is not valid: {0} |
Class | |
Explanation |
Search context portlet URI is not valid. |
Action |
Specify a valid search context portlet. |
POP.012.0001.wm_commonsearchresults | Search Context Portlet URI is not valid: {0} |
Class | |
Explanation |
The search context portlet URI is not valid. |
Action |
Specify a valid search context portlet. |
POP.012.0001.wm_contentrenderer | Unable to parse regexps: {0} |
Class | E |
Explanation |
The My webMethods Server installation is missing RegEx support jars. |
Action |
Reinstall My webMethods Server. |
POP.012.0001.wm_dirsearchcontext | This portlet is not intended to be viewed standalone |
Class | |
Explanation |
This portlet is not intended to be viewed as standalone. |
Action |
Do not view this portlet as a standalone portlet. |
POP.012.0001.wm_discotres_forumview | Forum or category not specified. |
Class | |
Explanation |
The forum or category should not be null. |
Action |
Specify the forum or category for the forum view. |
POP.012.0001.wm_discotres_forumwizard | Must specify "parent" property. |
Class | |
Explanation |
The "parent" property must not be empty. |
Action |
Enter a valid "parent" property. |
POP.012.0001.wm_discotres_messageview | Forum message not specified. |
Class | |
Explanation |
The forum requires some messages for proper notification. |
Action |
Provide the messages needed for the message view resources. |
POP.012.0001.wm_discotres_topicview | Forum topic not specified. |
Class | |
Explanation |
Specify the correct forum topic. |
Action |
Specify a valid forum topic. |
POP.012.0001.wm_fabric_addtostart | You already have an instance of this portlet on the target page. |
Class | |
Explanation |
You already have an instance of this portlet on the target page. |
Action |
Choose another portlet to add. |
POP.012.0001.wm_formattedxml | No content available for {0}. |
Class | |
Explanation |
No content can be retrieved from the specified style sheet. |
Action |
Make sure that the style sheet has content. |
POP.012.0001.wm_inlinecontent | No content available for {0}. |
Class | |
Explanation |
No content can be retrieved. |
Action |
Make sure the resource has content. |
POP.012.0001.wm_jazzy | Not a valid dictionary identifier: "{0}". |
Class | |
Explanation |
The dictionary ID provided is not valid. |
Action |
Provide a valid dictionary ID. |
POP.012.0001.wm_mws_diagnostics | No Performance Service is currently available. To enable the Service, please go to the properties page of this portlet. |
Explanation |
No performance service is currently enabled. |
Action |
To enable a service, go to the properties page of the Performance Analysis portlet. |
POP.012.0001.wm_noodle | Cannot load page content. |
Class | |
Explanation |
The page fails to load the content. |
Action |
Check if the file exists and if the path of the file is correct. |
POP.012.0001.wm_noodle_context_wiring | This portlet has no UI. |
Class | |
Explanation |
The specified portlet deployed on the server has no user interface. |
Action |
Go to Folders > Administrative Folders > Administration Dashboard > Configuration > Install Administration and re-install the portlet. |
POP.012.0001.wm_ntlmv2authadmin | NTLM autentication failed because login has been disabled for the {0} user. |
Explanation |
The Directory Service reports that the 'Diisabled' attribute for the user record is set to true. This user cannot authenticate with My webMethods Server. |
Action |
To enable this user to authenticate with My webMethods Server, set the 'Diisabled' attribute to false in the appropriate directory server. |
POP.012.0001.wm_portletinportlet | Recursive use of Portlet-in-Portlet for "{0}". |
Class | E |
Explanation |
Portlet-in-Portlet is attempting to display an item that displays the same Portlet-in-Portlet (for instance, the Portlet-in-Portlet is displaying a portal page containing the same Portlet-in-Portlet). |
Action |
Change the Portlet-in-Portlet's "Portal Page" property to a different item. |
POP.012.0001.wm_principalprofileadmin | You don't have rights to modify the properties of this item. |
Explanation |
The current user does not have sufficient privileges to make changes to this portlet |
Action |
Contact a My webMethods Server system administrator to modify the current user's permissions. |
POP.012.0001.wm_properties | {0} is not specified. |
Class | E |
Explanation |
The Properties portlet could not locate the object to show its properties. |
Action |
Close and reopen the internet browser window. |
POP.012.0001.wm_publish.NotLicensed | The "Publish" feature is disabled because this deployment is not licensed. |
Class | |
Explanation |
The requested feature is not part of the used license. |
Action |
If you want to use this feature, you should buy and install the appropriate license. |
POP.012.0001.wm_publish.ToEnable | To enable the "Publish" feature please contact webMethods to obtain a Portal license. |
Class | |
Explanation |
The requested feature is not part of the used license. Contact Software AG to obtain the Portal license to enable the "Publish" feature. |
Action |
To use the "Publish" feature, you should buy and install the appropriate Portal license. |
POP.012.0001.wm_sessionmonitor | The view "{0}" is not available. |
Class | |
Explanation |
Unable to fetch the view context from the server. |
Action |
Try republishing the portlet to the server. |
POP.012.0001.wm_shelladmin | A shell with the system name "{0}" already exists. |
Class | |
Explanation |
The same system name is not allowed for two different shells. This error occurs when an attempt is made to save a shell with a system name that already exists. |
Action |
Specify a unique system name for the shell. |
POP.012.0001.wm_shelleditor | Cannot clone parent''s shell section because it is not a Portal Page. |
Class | E |
Explanation |
Some legacy shells created before Portal 6.2 or customer-created shells may have a raw JSP page assigned to a shell section. Such shells cannot be cloned. |
Action |
Rework the legacy shell to use portal pages instead of JSP pages. |
POP.012.0001.wm_skinadmin | A skin with the system name "{0}" already exists. |
Class | |
Explanation |
The same system name is not allowed for two different skins. This error occurs when an attempt is made to save a skin with a system name that already exists. |
Action |
Specify a unique system name for the skin. |
POP.012.0001.wm_skineditor | {0} is not a valid skin. |
Class | E |
Explanation |
The specified skin object is not a valid portal skin. |
Action |
Log off from My webMethods and log back in. |
POP.012.0001.wm_spm_commandex | "{0}" does not identify a user or group. |
Explanation |
The supplied URI is not a valid user or group. |
Action |
Specify a correct URI. |
POP.012.0001.wm_sysdirsvc | Unable to locate principal: {0} |
Class | |
Explanation |
The principal cannot be retrieved using the provided principal URI. |
Action |
Check the server log for the principal URI that was used and make sure the principal URI is valid. Contact an administrator if the principal URI is valid but the issue persists. |
POP.012.0001.wm_table | Illegal "{0}" property value: "{1}". |
Class | |
Explanation |
An invalid value is specified for the property. |
Action |
Check the log for information about the value that was specified for the property. Specify a valid value for the property. |
POP.012.0001.wm_tabs | Illegal "{0}" property value: "{1}". |
Class | |
Explanation |
An invalid value is specified for the property. |
Action |
Check the log for information about the value that was specified for the property. Specify a valid value for the property. |
POP.012.0001.wm_thumbnailagent | Error executing external process |
Class | E |
Explanation |
The Thumbnail agent has failed to execute an external process to prepare thumbnails. |
Action |
Use the Install Administration portlet to reinstall the wm_thumbnailagent portlet. |
POP.012.0001.wm_tree | Illegal "{0}" property value: "{1}". |
Class | |
Explanation |
An invalid value is used for the specified property. |
Action |
Check the server log for the value used for the property. Make sure a valid value is used. |
POP.012.0001.wm_universalpicker | Cannot resolve portlet ID for "{0}". |
Class | |
Explanation |
Cannot retrieve the thing using the specified ID. |
Action |
Check the server log for the ID that cannot be retrieved and make sure that the ID is valid. Contact an administrator if you think that the ID is valid but the error persists. |
POP.012.0001.wm_userhomefolder | Empty "{0}" property. |
Class | E |
Explanation |
The user ID is either invalid or was not found. |
Action |
Use the User Home folder portlet to refresh the page. |
POP.012.0001.wm_userprofilewiring | This portlet has no UI. |
Class | |
Explanation |
The specified portlet deployed on the server has no user interface. |
Action |
Go to Folders > Administrative Folders > Administration Dashboard > Configuration > Install Administration and re-install the portlet. |
POP.012.0001.wm_version | Unable to acquire publish portlet controller bean. |
Class | E |
Explanation |
An internal portlet error has occurred. |
Action |
Log off from My webMethods and log back in. |
POP.012.0001.wm_webclip | Cannot clip from "{0}" because it is not an HTTP resource. |
Class | E |
Explanation |
The Webclip portlet has failed to connect to the specified URL and get its HTML content. |
Action |
Check the URL specified for the Webclip portlet. |
POP.012.0001.wm_wiring | Can only wire portlets |
Class | E |
Explanation |
An attempt was made to wire a non-portlet. |
Action |
You can only wire portlets. |
POP.012.0001.wm_xt_dbdirsvc | Directory could not authenticate this user |
Class | |
Explanation |
The user cannot be authenticated with the specified credentials. |
Action |
Make sure the user credentials are valid. |
POP.012.0001.wm_xt_dbrole | An error occured executing the SQL query: "{0}". Please type a valid query and try again. |
Class | |
Explanation |
The SQL query is invalid. |
Action |
The server log contains the invalid SQL query. Use a valid SQL query. |
POP.012.0001.wm_xt_extdirsvc | Directory could not authenticate this user |
Explanation |
The user cannot be authenticated with the specified credentials. |
Action |
Make sure the user credentials are valid. |
POP.012.0001.wm_xt_ldapdirsvc | This directory service does not support creating Users or Groups |
Class | |
Explanation |
The LDAP directory service does not support creating users or groups. |
Action |
Contact an administrator if you want to create users or groups. |
POP.012.0001.wm_xt_oauthsvc | Verification of the IdToken failed! |
Explanation |
Verification of the ID Token (security token) that contains claims about the authentication of a user by an authorization server failed. The failure may occur due to the following reasons: 1.The issuer identifier for the OpenID Provider obtained during discovery does not match the value of the iss (issuer) claim.2. The ID Token does not list the client (client_id) as a valid audience (aud). |
Action |
Check the OAuth configuration 'OAuth 2.0 Client Identifier' parameter. |
POP.012.0001.wm_xt_portalrules | Unknown rule thing: {0} |
Class | |
Explanation |
The type of rule cannot be determined. |
Action |
Check the server log for the rule ID that cannot be determined and make sure that the ID is valid. Contact an administrator if you think that the ID is valid but the error persists. |
POP.012.0001.wm_xt_rssfeed | age not found: {0} |
Class | |
Explanation |
The specified RSS Feed Resource age "{0}"does not exist. |
Action |
Examine the warning message and confirm that the age {0} exists. |
POP.012.0001.wm_xt_rule | The current IDirectoryUser is null. |
Class | E |
Explanation |
Rule matching has failed to load the user. |
Action |
Log off from My webMethods and log back in. |
POP.012.0001.wm_xt_samlsecurityservice | The input document contains no elements. |
Class | |
Explanation |
The input document contains no elements. |
Action |
Make sure that a valid document that is not empty is passed. |
POP.012.0001.wm_xt_shell | Cannot delete "{0}" because it is the default system shell. |
Class | |
Explanation |
The default system shell cannot be deleted. |
Action |
Do not attempt to delete the default system shell. |
POP.012.0001.wm_xt_shortcut | Unhandled object type found for the wm_xt_shortcut URL property: {0} |
Class | E |
Explanation |
An invalid object type was referenced by a shortcut. |
Action |
Delete the specified object and start over. |
POP.012.0001.wm_xt_skin | Cannot delete "{0}" because it is the default system skin. |
Class | E |
Explanation |
The portal skin specificed as the default skin cannot be deleted. |
Action |
Before deleting the skin, use the Skin Administration portlet to specify another skin as the default. |
POP.012.0001.wm_xt_ssolink | Failed to generate SAML artifact, artifact is null |
Class | |
Explanation |
The SAML artifact cannot be generated. |
Action |
Make sure that the item thing ID and user ID are valid, and that the SAML service is running. |
POP.012.0001.wm_xtypeview | You have not specified an object to display in this portlet. |
Class | E |
Explanation |
The Xtype View portlet does not have a valid target object to display. |
Action |
Update the Xtype View portlet properties and specify a valid DBO to display. |
POP.012.0002.wm_caf_task | Cannot connect to webMethods Content Service Platform Server on {0} : {1} . Please make sure the server is available. |
Explanation |
webMethods Content Service Platform is either not running, disconnected, or the environment configuration defined in My webMethods is incorrect. |
Action |
Make sure the CSP server is running; ensure that network connectivity is available; check the CSP environment configuration in My webMethods and verify the connection values. |
POP.012.0002.wm_commonsearchbar | Search Context Portlet does not implement ISearchContext interface |
Class | |
Explanation |
The search context portlet does not implement the ISearchContext interface. |
Action |
Make sure the search context portlet implements the ISearchContext interface. |
POP.012.0002.wm_commonsearchresults | Search Context Portlet does not implement ISearchContext interface |
Class | |
Explanation |
The search context portlet does not implement the ISearchContext interface. |
Action |
Make sure the search context portlet implements the ISearchContext interface. |
POP.012.0002.wm_contentrenderer | Requested content was not found: "{0}" |
Class | E |
Explanation |
The server attempted to download invalid content. |
Action |
Verify that valild content is present at the source location and can be downloaded. |
POP.012.0002.wm_dirsearchcontext | Failed to move to next principal in directory services, service={0}, error={1} |
Class | |
Explanation |
The directory search cannot continue because an exception was thrown when attempting to go to the next page search. No search results are returned. |
Action |
Check the My webMethods Server log for the directory service used for the search and the exception that was thrown. Provide the log details to an administrator. |
POP.012.0002.wm_discotres_forumview | Can display listing for forum or category only. |
Class | |
Explanation |
Only the listing for forum or category is displayed successfully. |
Action |
No action required. |
POP.012.0002.wm_discotres_forumwizard | Must specify "target" property. |
Class | |
Explanation |
The "target" property must not be empty. |
Action |
Enter a valid "target" property. |
POP.012.0002.wm_discotres_messageview | Can display forum message only. |
Class | |
Explanation |
Only forum messages are displayed successfully. |
Action |
No action is required. |
POP.012.0002.wm_discotres_topicview | Can display listing for forum topic only. |
Class | |
Explanation |
Only the listing for forum topic is displayed successfully. |
Action |
No action required. |
POP.012.0002.wm_jazzy | Not a valid dictionary: "{0}". |
Class | |
Explanation |
The dictionary specified is not valid. |
Action |
Provide a valid dictionary. |
POP.012.0002.wm_publish | Please select a type to publish. |
Class | |
Explanation |
The 'type' input parameter must be set to 'publish'. |
Action |
Provide an allowed value. The 'type' input parameter must be set to 'publish'. |
POP.012.0002.wm_sessionmonitor | Use this portlet to monitor real-time user activity and send status messages to user(s) via e-mail. Click the appropriate column heading to sort by User Name, Location (Host ID), or Administrator status. |
Class | |
Explanation |
Use this portlet to monitor real-time user activity and to send status messages to users by e-mail. Click the appropriate column heading to sort by User Name, Location (Host ID), or Administrator status. |
Action |
For more information, see the PDF publication, "My webMethods Server Portlet Reference." |
POP.012.0002.wm_shelladmin | A shell with the display name "{0}" already exists. |
Class | |
Explanation |
The same display name is not allowed for two different shells. This error occurs when an attempt is made to save a shell with a display name that already exists. |
Action |
Specify a unique system name for the shell. |
POP.012.0002.wm_skinadmin | A skin with the display name "{0}" already exists. |
Class | |
Explanation |
The same display name is not allowed for two different skins. This error occurs when an attempt is made to save a skin with a display name that already exists. |
Action |
Specify a unique display name for the skin. |
POP.012.0002.wm_skineditor | feature not recognized: {0} |
Class | |
Explanation |
The feature is not recognized. |
Action |
Contact Software AG Global Support. For contact information, log in to https://empower.softwareag.com/. |
POP.012.0002.wm_spm_commandex | Invalid argument supplied. |
Explanation |
An invalid argument was supplied as a parameter in the request map. |
Action |
Check the arguments for the command request. |
POP.012.0002.wm_sysdirsvc | Password attribute is missing |
Class | |
Explanation |
No password information is provided when creating a new principal. |
Action |
Provide a password attribute when creating a new principal. |
POP.012.0002.wm_systemcontent | <div class="portlet-msg-error"><h3>Attempted redirect to a restricted host. </h3></div> |
Explanation |
My webMethods Server does not allow redirects to arbitrary URLs. In this case the URL was not configured as an acceptable redirect host. |
Action |
Ask the My webMethods Server administrator to modify the Server Redirect WhiteList to allow redirects to this foreign URL. |
POP.012.0002.wm_userhomefolder | This user does not have a home folder. Note that the Portal typically does not create a home folder for a user until the user logs in for the first time. |
Class | |
Explanation |
The user does not have a home folder. |
Action |
Note that the Portal typically does not create a home folder for a user until the user logs in for the first time. Contact an administrator if this problem persists after the user logs in. |
POP.012.0002.wm_version | Unable to acquire target resource: {0} |
Class | E |
Explanation |
An internal portlet error has occurred. |
Action |
Log off from My webMethods and log back in. |
POP.012.0002.wm_wiring | {0} is not a normal thing |
Class | E |
Explanation |
An attempt was made to wire an invalid portlet instance. |
Action |
Delete the specified portlet and locate the correct portlet. |
POP.012.0002.wm_xt_extdirsvc | This directory service does not support creating Users or Groups |
Explanation |
This external directory service does not support creating users or groups. |
Action |
Create an administrator if you want to create users or groups. |
POP.012.0002.wm_xt_ldapdirsvc | This directory service does not support deleting Users or Groups |
Class | |
Explanation |
The LDAP directory service does not support deleting users or groups. |
Action |
Contact an administrator if you want to delete users or groups. |
POP.012.0002.wm_xt_oauthsvc | The discovery document response is not valid. |
Explanation |
Unable to obtain configuration information about the OpenID provider, including information about all the necessary endpoints and public key location. |
Action |
Check the OAuth configuration 'Discovery Document URL' parameter. |
POP.012.0002.wm_xt_portalrules | Unable to resolve user id: {0} |
Class | |
Explanation |
The principal information cannot be retrieved using the specified ID. |
Action |
Check the server log for the principal ID that cannot be retrieved and make sure that the ID is valid. Contact an administrator if you think that the ID is valid but the error persists. |
POP.012.0002.wm_xt_rssfeed | refresh interval not found: {0} |
Class | |
Explanation |
The specified RSS Feed Resource refresh interval "{0}"does not exist. |
Action |
Provide a valid value for the input variable refresh interval :{0}. |
POP.012.0002.wm_xt_samlsecurityservice | The SAML artifact is invalid or has expired. |
Class | |
Explanation |
The SAML artifact is invalid because it provides wrong information for the cluster index. |
Action |
Make sure the SAML artifact has the correct information. |
POP.012.0002.wm_xt_shell | Cannot delete "{0}" because it is the base system shell. |
Class | |
Explanation |
The base system shell cannot be deleted. |
Action |
Do not attempt to delete the base system shell. |
POP.012.0002.wm_xt_skin | Cannot delete "{0}" because it is the base system skin. |
Class | E |
Explanation |
The portal skin specified as the base system skin cannot be deleted. |
Action |
The base portal skin cannot be deleted because it is used as a parent for all other portal skins. |
POP.012.0002.wm_xt_wikiobject | Wiki with such name already exists |
Class | |
Explanation |
A wiki with such a name already exists. |
Action |
Use a unique name for the wiki. |
POP.012.0003.wm_commonsearchbar | None of the portlet tabs are visible |
Class | |
Explanation |
None of the portlet tabs are visible for the search bar. |
Action |
Make sure that the search options are set. |
POP.012.0003.wm_commonsearchresults | Failed to parse the max search results setting of "{0}", using default of "{1}" |
Class | E |
Explanation |
The common search code is attempting to build a search query object from a query string that was passed into it. The query string supplied contains an invalid value for the 'maxResults' setting. The warning message is written to the logs and the process continues with the default maxResults value. |
Action |
Make sure the portlet that invokes the API supplies a valid number for the 'maxResults' setting in the search query string. Typically, the end user would not cause this scenario because the wm_commonsearchbar portlet that usually builds the query string validates the maxResults field before allowing the submission of the search form. |
POP.012.0003.wm_contentserviceadmin | Cannot start a new content import process because another content import process is currently running. |
Class | |
Explanation |
You cannot start a new content import process because another content import process is currently running. |
Action |
Wait until the content import in progress completes. |
POP.012.0003.wm_dirsearchcontext | Failed to convert short move to next principal in directory services, service={0}, error={1} |
Class | |
Explanation |
The internal ID is not a valid integer. |
Action |
Check the My webMethods Server log for the directory service used for the search and the exception that was thrown. Provide the log details to an administrator. |
POP.012.0003.wm_discotres_topicview | Must specify "target" property. |
Class | |
Explanation |
The "target" property must not be empty. |
Action |
Enter a valid "target" property. |
POP.012.0003.wm_jazzy | Cannot load dictionary "{0}" because an I/O error occurred. |
Class | |
Explanation |
The specified dictionary cannot be loaded. |
Action |
Make sure that the dictionary is accessible. |
POP.012.0003.wm_noodle | Cannot load portlet content. |
Class | |
Explanation |
The portlet fails to load the content. |
Action |
Check if the portlet has content and if the path of the portlet is correct. |
POP.012.0003.wm_ntlmv2authadmin | Field [{0}] is required. |
Explanation |
A necessary form field was not provided. |
Action |
Review the form and fill out all required fields, then resubmit. |
POP.012.0003.wm_sessionmonitor | No sessions are available for this Portal Node. |
Class | |
Explanation |
No sessions are available for this portal node. |
Action |
Try republishing the portlet to the server. |
POP.012.0003.wm_shelladmin | The URI "{0}" does not identify a valid shell. |
Class | E |
Explanation |
The shell instance is not a valid portal shell object type. |
Action |
Restart the My webMethods Server to flush the internal caches. |
POP.012.0003.wm_skinadmin | The URI "{0}" does not identify a valid skin. |
Class | E |
Explanation |
The skin instance is not a valid portal skin type. |
Action |
Restart My webMethods Server to flush the internal caches. |
POP.012.0003.wm_skineditor | property not recognized: {0} |
Class | |
Explanation |
The property is not recognized. |
Action |
Make sure this particular editor resource is declared correctly. |
POP.012.0003.wm_spm_commandex | Cannot create env entry. Entry already exsists. |
Explanation |
There is a duplicate entry with that name. |
Action |
Specify a different name for the entry. |
POP.012.0003.wm_tree | The "{0}" property value must begin with a '{' character. |
Class | |
Explanation |
The property value should begin with a "{" character. |
Action |
Make sure that the property value begins with a "{" character. |
POP.012.0003.wm_wiring | You don't have rights to modify the wiring of this item. |
Explanation |
The current user does not have sufficient permissions to modify the wiring properties of this portlet. |
Action |
Contact your My webMethods Server administrator to modify your user permissions. |
POP.012.0003.wm_xt_dbdirsvc | This directory service does not support deleting Users or Groups |
Class | |
Explanation |
The database directory service does not support deleting users or groups. |
Action |
Contact an administrator if you want to delete users or groups. |
POP.012.0003.wm_xt_extdirsvc | This directory service does not support deleting Users or Groups |
Explanation |
This external directory service does not support deleting users or groups. |
Action |
Contact an administrator if you want to delete users or groups. |
POP.012.0003.wm_xt_ldapdirsvc | This directory service does not support modifying User or Group memberships |
Class | |
Explanation |
The LDAP directory service does not support modifying users or groups. |
Action |
Contact an administrator if you want to modify users or groups. |
POP.012.0003.wm_xt_oauthsvc | Unable to obtain OSGI service reference: {0} |
Explanation |
The lookup for the OAuth user service failed. |
Action |
If a user service application is defined in the OAuth configuration, check if the user service application is deployed correctly. |
POP.012.0003.wm_xt_portalrules | Deprecated method {0} is not valid on wm_xt_portalrules |
Class | |
Explanation |
The method is deprecated and should not be invoked. |
Action |
Use only supported methods. |
POP.012.0003.wm_xt_rssfeed | Unable to find suitable factory for: {0} |
Class | E |
Explanation |
An RSS feed has failed to parse RSS content. |
Action |
Choose another RSS feed. |
POP.012.0003.wm_xt_samlsecurityservice | Unable to locate principal "{0}". |
Class | |
Explanation |
Directory principal information cannot be retrieved. |
Action |
Make sure the SAML artifact contains correct directory principal information. |
POP.012.0004.wm_commonsearchbar | Saved Search Name has already been used. |
Class | |
Explanation |
The saved search name has already been used. |
Action |
Specify a different search name. |
POP.012.0004.wm_commonsearchresults | Failed to retrieve data from : {0} LDAPs |
Explanation |
The specified directory services failed to return a result due to an error. |
Action |
Check the My webMethods Server logs for errors related to the specified directory services. |
POP.012.0004.wm_contentserviceadmin | Content service not found: "{0}". |
Class | E |
Explanation |
The content service is no longer valid. |
Action |
If you cannot reconfigure the offending content service by using the Content Service Admin portlet, contact Software AG Global Support for a reset directive. |
POP.012.0004.wm_dirsearchcontext | Failed to evaluate expression for object, exp={0}, obj={1}, error={2} |
Class | |
Explanation |
The expression cannot be evaluated. |
Action |
Check the My webMethods Server log to determine the expression and the exception that was thrown. Provide the log details to an administrator. |
POP.012.0004.wm_mws_diagnostics | Performance Service does not support serialization. |
Explanation |
The currently running performance service does not support data serialization, therefore a snapshot cannot be exported. |
Action |
Switch to a performance service that supports serialization. |
POP.012.0004.wm_ntlmv2authadmin | Jespa library is required. |
Explanation |
NTLMV2 will not function without the Jespa library. |
Action |
Contact Software AG Global Support for information about downloading the Jespa library from jespa.org. |
POP.012.0004.wm_portalaliassearchcontext | One or more of the requested aliases can not be removed |
Class | |
Explanation |
One or more of the requested aliases can not be removed. |
Action |
Before deleting an alias, verify that it exists and that it is not a system alias. |
POP.012.0004.wm_shelladmin | Cannot delete "{0}" because it is the default system shell. |
Class | E |
Explanation |
The default portal shell cannot be deleted. |
Action |
Use the Shell Administration portlet to specify another shell as the default, and then delete the first shell. |
POP.012.0004.wm_skineditor | can't resolve input source: {0} |
Class | |
Explanation |
The input resource provided is incorrect. |
Action |
Provide the correct input resource. |
POP.012.0004.wm_spm_commandex | "{0}" argument not supplied. |
Explanation |
The required argument is not provided. |
Action |
Check the provided arguments. |
POP.012.0004.wm_tree | Cannot render resource as tree fragment. |
Class | |
Explanation |
The resource content is empty. |
Action |
Make sure that the resource has content. |
POP.012.0004.wm_wiki_createnew | Please provide the container for wiki |
Class | |
Explanation |
The container is not provided for the wiki. |
Action |
Provide the container for the wiki. |
POP.012.0004.wm_xt_dbdirsvc | This directory service does not support modifying User or Group memberships |
Class | |
Explanation |
The database directory service does not support modifying users or groups. |
Action |
Contact an administrator if you want to modify users or groups. |
POP.012.0004.wm_xt_extdirsvc | This directory service does not support modifying User or Group memberships |
Explanation |
This external directory service does not support modifying users or groups. |
Action |
Contact an administrator if you want to modify users or groups. |
POP.012.0004.wm_xt_ldapdirsvc | No valid "{0}" found for the principal "{1}" from "{2}" directory service. Please check if ID attribute is valid in the Directory Services Configuration |
Class | |
Explanation |
No principal is found in the LDAP directory service using the specified name. |
Action |
Use a valid name when searching for the principal in the LDAP directory service. |
POP.012.0004.wm_xt_portalrules | Web application is not deployed or available {0}. Cannot evaluate {1} |
Class | |
Explanation |
The specified web application is not deployed or available. As a result, My webMethods Server cannot evaluate the specified function. |
Action |
Make sure that the specified web application is deployed and available. |
POP.012.0005.wm_contentserviceadmin | Cannot remove default content service. |
Class | E |
Explanation |
The default content service cannot be deleted. |
Action |
My webMethods Server disallows the deletion of the default content service. |
POP.012.0005.wm_dirsearchcontext | Failed to create a directory service iterator, dirService={0}, error={1) |
Class | |
Explanation |
A problem was encountered while trying to iterate through a directory service. |
Action |
Check the server log for information about the directory service and the exception that was thrown. Provide the log details to an administrator. |
POP.012.0005.wm_jazzy | Please specify text to check. |
Class | |
Explanation |
The specified text is empty. |
Action |
Specify the text to check. |
POP.012.0005.wm_mws_diagnostics | Wrong Import File format. |
Explanation |
The file you are trying to import was exported from a performance service that is different from the one currently running. |
Action |
Check the portlet preferences and make sure the correct performance service is running. |
POP.012.0005.wm_ntlmv2authadmin | Configuration test failed. Please double check all the required parameters. |
Explanation |
The specified configuration is not valid. NTLMv2 authentication will not succeed until the parameters are corrected. |
Action |
Review the NTLMv2 configuration and modify parameters as required. |
POP.012.0005.wm_portalaliassearchcontext | Unable to add alias "{0}" because an alias with that name already exists. |
Class | |
Explanation |
Unable to add alias because an alias with that name already exists. |
Action |
Create a unique alias name. |
POP.012.0005.wm_shelladmin | Cannot delete "{0}" because it is the base system shell. |
Class | E |
Explanation |
The shell could not be deleted because it is a parent shell for other deployed shells. |
Action |
My webMethods Server explicitly disallows deletion of the base shell. |
POP.012.0005.wm_skineditor | cannot rename "{0}" to "{1}" |
Class | |
Explanation |
The field name "{1}" already exists. |
Action |
Specify a unique field name. |
POP.012.0005.wm_spm_commandex | Neither "{0}" or "{1}" arguments are supplied. |
Explanation |
Neither the first nor the second argument was provided. |
Action |
Provide at least one argument. |
POP.012.0005.wm_xt_dbdirsvc | Directory could not load principal data, "{0}" attribute is missing |
Class | |
Explanation |
The principal data cannot be loaded because the specified attribute is missing. |
Action |
Check the log file for the missing attribute. Contact an administrator to make sure the specific principal is valid and has the specified attribute. |
POP.012.0005.wm_xt_extdirsvc | No data service defined |
Explanation |
The OSGi external directory service could not be found. |
Action |
Check if the external directory service is defined correctly. |
POP.012.0005.wm_xt_ldapdirsvc | Unable to locate "{0}" directory service. It might have been disabled. |
Class | |
Explanation |
The LDAP directory service cannot be located. |
Action |
Make sure the LDAP directory service is enabled. |
POP.012.0006.wm_contentserviceadmin | You do not have sufficient rights to modify content service "{1}". |
Class | |
Explanation |
You do not have sufficient rights to modify this content service. |
Action |
An administrator must assign modify permission to the current user. Otherwise, modify the content service as an Administrator user. |
POP.012.0006.wm_dirsearchcontext | Not a valid attribute filter string, string={0} |
Class | |
Explanation |
The attribute filter string specified is not valid. |
Action |
Provide a valid attribute filter string. The server log file contains information about the invalid value. |
POP.012.0006.wm_portalaliassearchcontext | Unable to update alias "{0}" because an existing alias with that name could not be found. |
Class | |
Explanation |
Unable to update alias because an existing alias with that name could not be found. |
Action |
Select an existing alias to update, or create a new alias. |
POP.012.0006.wm_shelladmin | "{0}" does not identify a legacy shell. |
Class | |
Explanation |
The shell instance is not a valid legacy shell object type. |
Action |
Restart the My webMethods Server to flush the internal caches. |
POP.012.0006.wm_spm_commandex | Could not modify environment variable. Variable not found |
Explanation |
The variable was not found. |
Action |
Check and refresh the environment variables list. |
POP.012.0006.wm_xt_dbdirsvc | An error occurred executing the SQL query: "{0}". Please type a valid query and try again. |
Class | |
Explanation |
The SQL query is invalid. |
Action |
Make sure that the SQL query is valid. Contact an administrator if you are sure your SQL is valid. |
POP.012.0006.wm_xt_extdirsvc | Unable to instantiate class: {0} |
Explanation |
The OSGi external directory service is not defined or exposed correctly. |
Action |
Check if the external directory service is defined correctly. |
POP.012.0006.wm_xt_samlsecurityservice | Unable to locate server within cluster to validate the SAML artifact, index={0} |
Class | |
Explanation |
The server specified in the SAML artifact cannot be located within the cluster. |
Action |
Make sure the SAML artifact contains the correct server index information. |
POP.012.0007.wm_contentserviceadmin | A content service with a name of "{0}" already exists. |
Class | |
Explanation |
A content service with the same name already exists. |
Action |
Define a unique name when adding a new content service, |
POP.012.0007.wm_dirsearchcontext | Not a valid attribute filter string, missing separator, string={0} |
Class | |
Explanation |
The specified string does not have a valid attribute filter separator. |
Action |
Provide a valid attribute filter separator. You can find the invalid value in the server log file. |
POP.012.0007.wm_mws_diagnostics | Performance Service is not running. No data is available. |
Explanation |
No performance service currently is running, so there is no data to display. |
Action |
Enable a performance service and allow time for it to collect some data, then retry. |
POP.012.0007.wm_portalaliassearchcontext | This portlet is not intended to be viewed standalone |
Class | |
Explanation |
This portlet is not intended to be viewed as an individual portlet, outside of another portlet. |
Action |
Avoid using this portlet as a single stand-alone portlet. |
POP.012.0007.wm_shelladmin | Cannot convert legacy shell because it uses JSP pages instead of Portal pages. |
Class | |
Explanation |
My webMethods Server cannot convert a legacy shell because it uses JSP pages instead of Portal pages. |
Action |
Contact Software AG Global Support. For contact information, log in to https://empower.softwareag.com/. |
POP.012.0007.wm_xt_dbdirsvc | {0} is required |
Explanation |
The SQL query is invalid because the required property is missing. |
Action |
Make sure the SQL query includes the required property. |
POP.012.0007.wm_xt_extdirsvc | Unable to get the OSGI service: {0} |
Explanation |
The OSGi external directory service is not defined or exposed correctly. |
Action |
Check if the external directory service is defined correctly. |
POP.012.0008.wm_contentserviceadmin | A content service with a root of "{0}" already exists. |
Class | |
Explanation |
A content service with the same root already exists. |
Action |
Verify that no other service uses the same root location. |
POP.012.0008.wm_dirsearchcontext | Unable to locate the attribute provider for URI={0} |
Class | |
Explanation |
The principal attribute provider for the specific directory service cannot be found. |
Action |
Find the directory service in the server log and contact an administrator with the log information. |
POP.012.0008.wm_migration | Your download should begin shortly. |
Class | |
Explanation |
Informational message indicating that the download to begin shortly. |
Action |
No action required. |
POP.012.0008.wm_portalaliassearchcontext | Unable to remove alias "{0}" because it is a system alias |
Class | |
Explanation |
Unable to remove the alias because it is a system alias. |
Action |
No action available. You cannot delete a system alias. |
POP.012.0008.wm_xt_dbdirsvc | {0} "{1}" is invalid. It is missing required field "{2}" |
Class | |
Explanation |
The SQL query is invalid because the required property is missing. |
Action |
Make sure the SQL query includes the required property. |
POP.012.0009.wm_portalaliassearchcontext | Unable to remove alias "{0}" because it does not exist |
Class | |
Explanation |
Unable to remove the alias because it does not exist. |
Action |
Before attempting to delete an alias, verify that it exists. |
POP.012.0009.wm_xt_dbdirsvc | {0} "{1}" is invalid. It does not implement case-insensitive lookup for uid attribute |
Class | |
Explanation |
The database directory service does not support case-insensitive lookup for the UID attribute. |
Action |
Check the server log for information about the UID attribute and the query. Contact an administrator to make sure that the database directory service supports case-insensitive lookup for the UID attribute. |
POP.012.0010.wm_spm_commandex | LDAP directory service not found: {0} |
Explanation |
An LDAP directory service with the specified name does not exist or is not available. |
Action |
Verify that:1. The name of the LDAP directory service is correct.2. The LDAP directory service is enabled. |
POP.012.0010.wm_xt_dbdirsvc | Directory could not load principal "{0}" |
Class | |
Explanation |
No principal is found in the database directory service using the specified name. |
Action |
Use a valid name when searching the principal in the database directory service. |
POP.012.0011.wm_spm_commandex | LDAP directory service already exists: {0} |
Explanation |
An LDAP directory service with the specified name already exists. |
Action |
Specify a unique name for the LDAP directory service. |
POP.012.0012.wm_skineditor | You can not set skin parent to itself |
Class | |
Explanation |
The skin parent cannot be set to itself. |
Action |
The skin parent cannot be set to itself because it is used as a parent for all others. |
POP.012.0015.wm_migration | May not export resource which does not have a parent |
Class | |
Explanation |
You cannot export a resource that does not have a parent. |
Action |
Ensure that the resource has a valid parent. |
POP.012.0019.wm_migration | Export failed : Calender Id/Name Invalid |
Class | |
Explanation |
An invalid Calendar ID or Name is specified for Task Definition export. |
Action |
Specify a valid Calendar ID or Name for export. Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0020.wm_migration | Export failed : Shell Id/Name Invalid |
Class | |
Explanation |
An invalid Shell ID or Name is specified for Task Definition export. |
Action |
Specify a valid Shell ID or Name for export. Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0020.wm_securityrealmadmin | Warning: Selecting 'OK' will permanently remove the SecurityRealm from the system. |
Class | |
Explanation |
Before proceeding, verify that permanent deletion of the security realm will not affect your application or solution. |
Action |
Clcik OK to permanently remove the security realm from the system. |
POP.012.0021.wm_migration | Export failed : Skin Id/Name Invalid |
Class | |
Explanation |
An invalid Skin ID or Name is specified for Task Definition export. |
Action |
Specify a valid Skin ID or Name for export. Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0021.wm_securityrealmadmin | Warning: Selecting 'OK' will permanently remove this Container and all its contents from the system. |
Class | |
Explanation |
Before proceeding, verify that permanent deletion of the container will not affect your application or solution. |
Action |
Clcik OK to permanently remove this container and all its contents from the system. |
POP.012.0022.wm_migration | Export failed : Security Realm Id/Name Invalid |
Class | |
Explanation |
An invalid Security Realm ID or Name is specified for Task Definition export. |
Action |
Specify a valid Security Realm ID or Name for export. Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0023.wm_migration | Exception Closing Stream continuing with processing |
Class | |
Explanation |
An exception occurred during resource migration. |
Action |
Check the detailed error message and take appropriate action. |
POP.012.0024.wm_migration | Export failed : Certificate Id/Name Invalid |
Class | |
Explanation |
An invalid Shell ID or Name was specified for Task Definition export. |
Action |
Specify a valid Shell ID or Name for export. Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0025.wm_migration | Export failed : Invalid depth specified {0} |
Class | |
Explanation |
An invalid depth is specified for Task Definition export. |
Action |
Specify the valid path for Task Definition export. Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0026.wm_migration | Export failed : Invalid URI/alias specified for Export |
Class | |
Explanation |
An invalid URL or alias has been specified for Task Definition export. |
Action |
Specify a valid URL or alias for export. Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0027.wm_migration | Export did not containing any DLS Objects |
Class | |
Explanation |
The DLS object specified for export is not found. |
Action |
Specify the correct object for export. Consult the logs at ..\MWS\server\<instanceName>\logs for more details. |
POP.012.0028.wm_migration | Export failed : Invalid ID/URI/alias/Name specified for Task Definition Export |
Class | |
Explanation |
An invalid ID, URL, alias, or Name is specified for Task Definition export. |
Action |
Specify a valid ID, URL, aliias, or Name for export. Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0029.wm_migration | Export failed : Unable to get the skin archive content for {0} |
Class | |
Explanation |
Unable to get the field value using the specified path. |
Action |
Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0032.wm_migration | The Descriptor file specified is invalid |
Class | |
Explanation |
An invalid Descriptor file is specified. |
Action |
Specify a valid Descriptor file for export. See the log files in <Software AG_directory>\MWS\server\<instance_name>\logs for further information. |
POP.012.0033.wm_migration | Please specify valid target folder path |
Class | |
Explanation |
An invalid target folder path was encountered while trying to execute migration. |
Action |
Specify a valid target folder path. |
POP.012.0034.wm_migration | Import failed for entry :--> {0} |
Class | |
Explanation |
An invalid entry is specified for Task Definition export. |
Action |
See the log files in <Software AG_directory>\MWS\server\<instance_name>\logs for further information. |
POP.012.0035.wm_migration | No Task Instances found for Task application name {0} and task_type_id {1} |
Class | |
Explanation |
No task instances are found that match the specified search criteria. |
Action |
Verify that the task application name and task type ID specified for the task instance search are valid. Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0036.wm_migration | Export failed : Invalid ID/URI/alias/Name specified for Task Rules Export |
Class | |
Explanation |
An invalid ID, URL, alias, or Name is specified for Task Rules export. |
Action |
Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0037.wm_migration | Export successful for :--> {0} |
Class | |
Explanation |
The specified export completed successfully. |
Action |
No action required. |
POP.012.0038.wm_migration | Failed to get bizPolicy for :--> {0} |
Class | |
Explanation |
An invalid bizpolicy is specified. |
Action |
Specify a vaild bizPolicy. Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0039.wm_migration | Failed to get view details for thingID:--> {0} |
Class | |
Explanation |
The view details for the specified object could not be retrieved. |
Action |
Consult the log file at ..\MWS\server\<instanceName>\logs for further information. |
POP.012.0041.wm_migration | Import functionality is not supported. |
Class | |
Explanation |
The import function is not supported. |
Action |
No action required. |
POP.012.0055.wm_migration | Import info file {0} is invalid |
Explanation |
The migration portlet was unable to find the control file that lists the My webMethods Server assets to be imported. |
Action |
The user has specified an invalid path and file for the import control file. Check that the specified file exists and has read permission for the current user. |
POP.012.0056.wm_migration | Failed to list principals from directory service {0} |
Explanation |
My webMethods Server failed to build a list of principals from the specified directory service. This can happen if the directory service is non-functional and cannot access the underlying directory privider, such as an LDAP server or database. |
Action |
Check the Directory Services Administration portlet to verify that the directory service provider is correctly configured and is enabled. Also check the error logs for directory service provider connection failures. |
POP.012.0058.wm_migration | WARNING:Command not found: {0} |
Explanation |
My webMethods Server was unable to locate an internal command by name. |
Action |
This is an internal failure and cannot be remedied by the end-user. |
POP.012.0059.wm_migration | Error applying ACL for {0} |
Explanation |
A general error occured applying an import ACL to a principal. |
Action |
This is a system error that cannot be remedied by the end-user. |
POP.012.0060.wm_migration | WARNING: Profile Attribute Import failed: {0} |
Explanation |
A general error occured when applying the profile attributes to a user during import. The details of the failure will be appended to the error message. |
Action |
This is a system error that cannot be remedied by the end-user. |
POP.012.0061.wm_migration | Error importing skin {0} |
Explanation |
A general error occured when importing a skin. The details of the failure are appended to this message. |
Action |
This is a general message meant to capture any errors that occur during skin import. Refer to the My webMethods Server logs or the additional error text to troubleshoot the specific problem. |
POP.012.0062.wm_migration | Error occurred post-processing ACLs |
Explanation |
A general error occurred applying ACLs to imported users, groups, or roles. |
Action |
This is a general message meant to capture any errors that occur when applying ACLs. Refer to the My webMethods Server logs or the additional error text to troubleshoot the specific problem. |
POP.012.0063.wm_migration | Rule target not found for {0}. |
Explanation |
The target of a My webMethods Server rule could not be resolved to a specific My webMethods Server object. For example, a shell rule would display this error if it referenced a shell that did not exist. |
Action |
Examine the rule that is reporting the warning to determine the rule target, then confirm that the rule target exists. |
POP.012.0065.wm_migration | Unable to register datasource {0} |
Explanation |
A general failure occured importing a datasource. |
Action |
This is a general message meant to capture any errors that occur during datasource import. Refer to the My webMethods Server logs or the additional error text to troubleshoot the specific problem. |
POP.012.0067.wm_migration | Unable to import saved search for {0} |
Explanation |
A general error occured when importing a set of saved searches for the specified resource (for example, Task List Management or My Inbox). |
Action |
This is a general message meant to capture any errors that occur during a saved search import. Refer to the My webMethods Server logs or the additional error text to troubleshoot the specific problem. |
POP.012.0068.wm_migration | Unable to locate principal for applying saved searches to {0} |
Explanation |
The import includes private saved searches for a user that does not exist in the target My webMethods Server. |
Action |
Import or create the missing user and then import the saved searches. Otherwise, this error can be ignored, and the private saved searches will not be imported. |
POP.012.0069.wm_migration | Unable to locate principal for {0} |
Explanation |
A general warning message that the import references a user, group, or role that could not be located in the target My webMethods Server. |
Action |
Make sure any users, groups, or roles used by the asset that generates this warning are imported or created prior to the import. |
POP.012.0070.wm_migration | Unable to apply members to {0} |
Explanation |
A general error occurred importing the role or group membership. |
Action |
This is a general message meant to capture any errors that occur during import. Refer to the My webMethods Server logs or the additional error text to troubleshoot the specific problem. |
POP.012.0073.wm_migration | Attempting to import deprecated XType {0} |
Explanation |
The import contained a My webMethods Server asset that is no longer supported in My webMethods Server. For example, older versions of wm_xt_savedsearch are no longer supported in 8.0 and generate this warning. |
Action |
Because the My webMethods Server asset that generated this error is no longer supported, the message is for informational purposes only. |
POP.012.0107.wm_portalcontent | This is not meant to be viewed |
Class | |
Explanation |
An attempt was made to view a portal content resource that does not have a user interface. |
Action |
Do not attempt to view the portal content resource directly. If the resource must be viewed, you must create a renderer that is capable of displaying a user interface for the object. |
POP.012.1001.wm_mws_diagnostics | Cannot find file to parse. |
Explanation |
Unable to load the file for analysis. |
Action |
Select a file to upload for analysis. |
POP.012.1002.wm_mws_diagnostics | Unable to parse the log file; possible wrong log file format. |
Explanation |
The selected log file cannot be parsed. It is possible that the log file is in an incorrect format. |
Action |
Make sure the selected log file is in the appropriate format. |
POP.012.1003.wm_mws_diagnostics | Error during XML marshalling. Possible wrong log file format. |
Explanation |
My webMethods Server was unable to parse the xml log file. |
Action |
Select a log file generated by My webMethods Server and upload again. |
POP.012.1004.wm_mws_diagnostics | Unable to locate default {0} |
Explanation |
Unable to locate default {0} |
Action |
Check the My webMethods Server instance configuration. |
POP.012.1005.wm_mws_diagnostics | The given host: {0} does not exist |
Explanation |
My webMethods Server was not able to reach the remote host. |
Action |
Check the connection settings for the remote host, verify that My webMethods Server has network access to the host, then try again. |
POP.012.1006.wm_mws_diagnostics | An error has occurred while downloading the file: {0} |
Explanation |
There was a problem when parsing the file. |
Action |
Check the My webMethods Server logs for more details. See ..\MWS\server\<serverName>\logs |
POP.012.1007.wm_mws_diagnostics | An error has occurred while processing the downloaded file: {0} |
Explanation |
There was a problem processing the file. |
Action |
Check the My webMethods Server logs for more details. See ..\MWS\server\<serverName>\logs |
POP.012.wm_httpheaderauth.userDisabled | HTTP header autentication failed because login has been disabled for the {0} user. |
Explanation |
A My webMethods Administrator disabled the user. |
Action |
Contact your My webMethods Administrator. If the user is not disabled, but this message still appears, contact Software AG. |
POP.013.0005 | This item is either inactive or deleted and can not be viewed. |
Class | E |
Explanation |
The item is deleted but has not yet been purged. |
Action |
Use the Deleted Items Administration portlet to remove the deleted items completely from the user interface. |
POP.013.0096 | This was not meant to be viewed |
Class | |
Explanation |
An attempt was made to view a My webMethods DBO that does not have a user interface. |
Action |
Do not attempt to view the resource directly. If the resource must be viewed, you must create a renderer that is capable of displaying a user interface for the object. |
POP.013.0097 | Datasource {0} not found |
Class | |
Explanation |
A portlet is attempting to open a database connection to a data source that is not available on the My webMethods Server. |
Action |
The My webMethods Server administrator should add the missing database connection information using the "Data Sources" portlet. |
POP.013.0099 | Unable to construct a secure URL because the MWS secure front end URL is not available |
Explanation |
Constructing a secure URL is not possible because the My webMethods Server secure front-end URL is not available. |
Action |
Make sure that the front-end URL has been specified. |
POP.013.0100 | You must enable JavaScript to use this site. |
Explanation |
You must enable JavaScript to use this site. |
Action |
Make sure that JavaScript is enabled. |
POP.015.0001 | No constant was specified for {0}. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the syntax expected a number and none was found. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0002 | Incorrect number of children. Expected {0} and found {1}. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser expected to find another term and none was found. For instance, the rule might have been a comparison, and only one term was found to compare. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0003 | Both child terms must be numbers. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser expected to find a numeric value or a value that can be converted into a number. None was found. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0006 | Unknown types for comparison: {0} and {1}. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser expected to find valid terms that can be compared to each other but was unable to do so. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0007 | Unable to find object Reference: {0}. |
Class | |
Explanation |
When the system attempted to evaluate a My webMethods Server rule, the rule referred to an object reference which could not be located. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0008 | No object Reference name is set. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser expected to find an object identifier and none was found. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0009 | Incorrect number of children. Expected 0 or 1 and found {0}. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser found an unexpected term in the sequence. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0010 | Incorrect number of children. Expected 2 or more and found {0}. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser expected to find additional terms and no more were found. For instance, the rule might have been a comparison, and only one term was found to compare. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0011 | Unable to find method to invoke: {0}. |
Class | |
Explanation |
When the system attempted to evaluate a My webMethods Server rule, it was unable to invoke the specified method. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0012 | Incorrect number of children. Expected 1 or more and found {0}. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser expected to find additional terms and no more were found. For instance, the rule might have been a comparison, and only one term was found to compare. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0013 | XML Parse Exception. Expected {0} tag and found {1} tag. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser was unable to find the correct XML schema. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0014 | XML Parse Exception while parasing tag {0}. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser was unable to find the correct XML schema. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0015 | Parse Exception at char: {0} {1}. |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser encountered a syntax error at the specified position. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.015.0029 | Expected to find matching char "{0}" |
Class | |
Explanation |
When the system attempted to parse a My webMethods Server rule, the parser encountered a syntax error at the specified position. |
Action |
Review the recently modified or uploaded rule to ensure that the syntax is valid. |
POP.016.0001 | unbalanced end element: expected "{0}" but was "{1}" |
Class | |
Explanation |
The optional PrettyPrintingResponseWriter that was enabled manually by the developer to tidy up the rendered html for a page in the web.xml of the webapp, has detected html that was not well-formed. |
Action |
This should never happen. If this happens a defect in one of the JSF component renderers has not properly closed one of the html tags that was written to the response writer. |
POP.016.0002 | Portlet Preferences are only available inside the Portlet Context |
Class | |
Explanation |
This error message is not used in the current trunk code anymore. |
Action |
N/A |
POP.016.0003 | Else control must be preceded directly by If control |
Class | |
Explanation |
The CAF view contains an "Else" control without a sibling "If" control. |
Action |
The developer should change the "Else" control to an "If" control or remove it from the CAF view. |
POP.016.0004 | Duplicate component ID: {0} (IDs must be unique within naming-container) |
Class | |
Explanation |
In a CAF view two controls have the same ID value. |
Action |
The developer must change the ID of all the controls that are using the same ID to make the control's ID unique. |
POP.016.0005 | Resource bundle is not available: {0} |
Class | |
Explanation |
The specified resource bundle could not be loaded. |
Action |
The developer should check the resource bundle name to make sure it is correct and make sure the resource bundle file is included in the war file. |
POP.016.0006 | View source is not found: {0} |
Class | |
Explanation |
When attempting to load a CAF .view file, the file was not found. |
Action |
The developer should inspect the deployed war file to make sure the missing view file exists. |
POP.016.0007 | Can only switch portlet modes within an action request |
Class | |
Explanation |
A portlet attempted to change the portlet mode outside of an action request which is not allowed per the JSR-168 specification. |
Action |
The developer should change the portlet source code and not attempt to change the portlet mode from a code path that does not originate in a portlet action handler. |
POP.016.0008 | Unable to locate control ID {0} in view: {1} |
Class | |
Explanation |
There was no control in the view that had the specified control id. |
Action |
The developer should review their application code to make sure the correct control ID is used for the lookup. |
POP.016.0009 | Connection failed to datasource {0}. Caused by: {1} |
Class | |
Explanation |
A SQLException was caught while retrieving the data for a RowSetTableContentProvider. |
Action |
Review the server log file to inspect the stack trace of the exception to try to determine the cause of the error. |
POP.016.0010 | Search Results Table Control could not be located |
Class | |
Explanation |
The Export Table Button control could not find the table control to use for exporting data. |
Action |
The developer should check the Export For property of the Export Table Button control to make sure it matches the ID of the table control. |
POP.016.0011 | DateInput component value must be a java.util.Date instance |
Class | |
Explanation |
The value bound to a Date Input control is not the expected data type. |
Action |
The developer should review the binding expression of the Date Input control to make sure it resolves to a java.util.Date object. |
POP.016.0012 | DateRangeInput component value must be a com.webmethods.caf.faces.data.object.DateRange instance |
Class | |
Explanation |
The value bound to a Date Range Input control is not the expected data type. |
Action |
The developer should review the binding expression of the Date Range Input control to make sure it resolves to a com.webmethods.caf.faces.data.object.DateRange object. |
POP.016.0013 | managed-bean-scope value "pageflow" should be changed to "session" for managed-bean "{0}" in application "{1}". |
Class | |
Explanation |
A managed-bean declaration in the faces-config.xml is using the deprecated pageflow managed-bean-scope. |
Action |
The application developer should change the managed-bean-scope value pageflow to session for the managed-bean and then rebuild and redeploy the application. |
POP.016.0014 | ScheduleInput component value must be a com.webmethods.caf.faces.data.object.Schedule instance |
Class | |
Explanation |
The value bound to a Schedule Input control is not the expected data type. |
Action |
The developer should review the binding expression of the Schedule Input control to make sure it resolves to a com.webmethods.caf.faces.data.object.Schedule object. |
POP.016.0015 | Interval must be set to calculate previous or next date |
Class | |
Explanation |
The Schedule.nextDate(..) or Schedule.previousDate(..) api was called but the schedule does not have an interval configured. |
Action |
Set the interval on the Schedule object before attempting to calculate the next or previous date. |
POP.016.0016 | Source table provider does not expose currentRow data and thus cannot be used with PageableTableContentProvider. |
Class | |
Explanation |
Source table provider does not expose currentRow data and cannot be used with the PageableTableContentProvider. |
Action |
Review the configuration of the table content provider to ensure that it is configured properly. |
POP.016.0017 | Cannot find value for script parameter: {0} |
Class | |
Explanation |
The value of a script parameter is null. |
Action |
The developer should review the source of the script parameter value to determine why it has no value. |
POP.016.0018 | Cannot find control with id "{1}" for script parameter: {0} |
Class | |
Explanation |
The control id specified as the value of a script parameter did not match a control in the view. |
Action |
The developer should review the script paramater value to ensure it matches an exisitng control in the view. |
POP.016.0019 | Cannot create null method binding. |
Class | |
Explanation |
An attempt was made to create a method binding object without supplying an expression string. |
Action |
The developer should review the application code to determine why the expression is null. |
POP.016.0020 | Cannot create null value binding. |
Class | |
Explanation |
An attempt was made to create a value binding object without supplying an expression string. |
Action |
The developer should review the application code to determine why the expression is null. |
POP.016.0021 | Cannot convert null locale string. |
Class | |
Explanation |
The com.webmethods.caf.faces.convert.ConvertUtils.getLocalFromToString API was called with a null string. |
Action |
The developer should review the application code to determine why the supplied locale string is null. |
POP.016.0022 | Portlet control can only be used within a portlet request |
Class | |
Explanation |
The Portlet Include control is used in a non-portlet environment. |
Action |
Do not use the Portlet Include control in a standalone CAF web application. |
POP.016.0023 | Cannot export from this context or phase |
Class | |
Explanation |
An attempt was made to export a file, but a compatible export handler was not found. |
Action |
You should not get this error. |
POP.016.0024 | Cannot export control of specified type (id={0},type={1}) |
Class | |
Explanation |
An attempt was made to export a control but the control specified was not an UIData based control so it cannot be exported. |
Action |
The developer should review the configuration of the export button to make sure the correct control is being exported. |
POP.016.0027 | Cannot parse string "{0}" as date (using pattern "{1}"). |
Class | |
Explanation |
A Date Import control value was a string but it could not be converted to a Date object. |
Action |
The developer should verify that the value pattern matches the format of the string bound to the control. |
POP.016.0029 | The "rowVariable" property must be set to use BoundPropertiesSelectItemGroupProvider. |
Class | |
Explanation |
The rowVariable property must be set to use BoundPropertiesSelectItemGroupProvider. |
Action |
The developer should review the application code to ensure that the rowVariable property was set. |
POP.016.0030 | The "rowType" property must be set to use as an IUpdateableTableContentProvider. |
Class | |
Explanation |
An attempt was made to add a new row to an updatable table content provider but the row type was not specified. |
Action |
The developer should review the application code to ensure that the rowType property was set. |
POP.016.0031 | Cannot create response for {0}. |
Class | |
Explanation |
The CAF view handler was unable to get a response writer to render the output. |
Action |
This should not occur. If this error occured, there is a catastrophic problem with the server instance. Other errors in the server logs might provide some guidance. |
POP.016.0032 | AutoRefresh is not supported |
Class | |
Explanation |
An attempt was made to autorefresh a LazyNodeTreeContentProvider instance that does not support autorefresh. |
Action |
The developer should review the application code to remove any calls to the autorefresh API. |
POP.016.0033 | NeedRefresh is not supported |
Class | |
Explanation |
An attempt was made to mark a LazyNodeTreeContentProvider instance as needing a refresh that does not support autorefresh. |
Action |
The developer should review the application code to remove any calls to the setNeedRefresh API. |
POP.016.0034 | Child not in parent's children list |
Class | |
Explanation |
There is a problem building the structure of a LazyNodeTreeContentProvider instance. |
Action |
The developer should review the application code that is providing the values to the tree content provider to make sure that the parent/child relationships of the tree data are correct. |
POP.016.0035 | The "rowIdBinding" property must be set to add or remove rows to or from a SelectableListTableContentProvider. If the table does not need to be selectable, try using a ListTableContentProvider instead. |
Class | |
Explanation |
The rowIdBinding property must be set to add or remove rows to or from a SelectableListTableContentProvider. If the table does not need to be selectable, try using a ListTableContentProvider instead. |
Action |
Set the rowIdBinding property for a SelectableListTableContentProvider. If the table does not need to be selectable, try using a ListTableContentProvider instead. |
POP.016.0036 | The "rowIdBinding" property must be set to move rows within a SelectableListTableContentProvider. |
Class | |
Explanation |
The rowIdBinding property must be set to move rows within a SelectableListTableContentProvider. |
Action |
This error message is no longer used. |
POP.016.0037 | Saved Search Not Found: {0} |
Class | |
Explanation |
An attempt was made to change the active saved search for a SearchBar control but the target saved search no longer exists. |
Action |
The end user should refresh the page and select a saved search. |
POP.016.0039 | cannot load external resource: {0} |
Class | |
Explanation |
When loading an app-nav.xml file, there was a reference to an external resource which is not allowed. |
Action |
The developer should review the app-nav.xml and remove the references to external resources. |
POP.016.0040 | cannot have more than one root page |
Class | |
Explanation |
When loading an app-nav.xml file more than one root page element was detected. |
Action |
The developer should review the app-nav.xml file to ensure that there is only one root page declared. |
POP.016.0042 | Error updating control value ("{1}" property of "{0}" control). |
Class | |
Explanation |
An error was detected updating a control value. The cause of the error is contain within the message details displayed to the user. |
Action |
Review the error message details displayed to the user to determine the cause of the error. |
POP.016.0043 | Toggle target control "{0}" could not be located. |
Class | |
Explanation |
The For property in a Toggle control does not resolve to a control. |
Action |
The application developer should review the application code to ensure that the For property of the toggle control matches the expected target control. |
POP.016.0043.details | Check the configuration of the control with this id: {0} |
Class | |
Explanation |
Provides additional details for the "POP.016.0043" error. |
Action |
See action for the "POP.016.0043" error. |
POP.016.0044 | Calendar StartDay is not set |
Class | |
Explanation |
A calendar control is being rendered but the start day has not been set. |
Action |
The developer should review the application code to ensure that the calendar has a start day. |
POP.016.0045 | Invalid value for height property of the "{0}" control. |
Class | |
Explanation |
The value of the height property of a Static Row or Static Cell control is not a valid height. |
Action |
The developer should review the application code to ensure that the height value is a valid unit of measure. |
POP.016.0046 | Invalid value for width property of the "{0}" control. |
Class | |
Explanation |
The value of the width property of a Static Row or Static Cell control is not a valid width. |
Action |
The developer should review the application code to ensure that the width value is a valid unit of unit of measure. |
POP.016.0047 | Can only reset portlet navigation state within an action request |
Explanation |
Portlet navigation state such as if portlet maximized or minimized can only be changed from an ActionRequest |
Action |
Do not attempt to change the portlet navigate state from the RenderRequest. Use ActionRequest. |
POP.016.0048 | The target action was invalid |
Explanation |
Request portlet action in PortletUrl is invalid and cannot be found |
Action |
Check the name action being requested and determine if it is defined in the portlet Java code |
POP.016.0048.detail | The target action was: {0} |
Explanation |
The request portlet action in PortletUrl is invalid and cannot be found |
Action |
Check the name action being request and determine if it is defined in the portlet Java code |
POP.016.0049 | The target action was invalid |
Explanation |
It is possible to invoke actions on the designated portlet via PortletURL. To prevent a malicious user from invoking an arbitrarily action on the portlet, each action defined must be annotated in Java code with @PortletAction annotation which instructs MWS runtime that a given action code is allowed when invoked from a url. |
Action |
Check portlet action definition code, and determine if it has the @PortletAction annotation defined. |
POP.016.0049.detail | The target action requires a @PortletAction annotation: {0} |
Explanation |
It is possible to invoke actions on the designated portlet via PortletURL. To prevent malicious user to invoke an arbitrarily action on the portlet, each action defined must be annotated in Java code with @PortletAction annotation which instructs MWS runtime that a given action code is allowed from a url. |
Action |
Check portlet action definition code if it has @PortletAction annotation defined |
POP.016.0050 | The target action was invalid |
Explanation |
To prevent cross-site scripting attacks when malicious script might invoke a porlet action using a URL, the URL used to call a portlet action must obtain and use AXSRF token. |
Action |
When producing a Portlet URL, make sure that the AXSRF token is included in the URL using com.webmethods.caf.portlet.IPortletUrl.setAXSRFT(true) API. |
POP.016.0050.detail | The target action "{0}" requires an anti-xsrf token. |
Explanation |
To prevent cross-site scripting attacks when malicious script might invoke a porlet action using an URL, the URL used to call a portlet action must obtain and use an AXSRF token. |
Action |
When producing a Portlet URL, make sure that an AXSRF token is included in the URL using com.webmethods.caf.portlet.IPortletUrl.setAXSRFT(true) API. |
POP.016.0051 | The target action was invalid |
Explanation |
To prevent cross-site scripting attacks when malicious script might invoke a porlet action using an URL, the URL used to call a portlet action must obtain and use a valid AXSRF token. |
Action |
When producing a Portlet Url, make sure that AXSRF token is included in the URL using com.webmethods.caf.portlet.IPortletUrl.setAXSRFT(true) API. |
POP.016.0052 | The target action was invalid |
Explanation |
The Portlet Url can invoke portlet actions from a URL. If the CAF application does not force use of Annotated Portlet Actions, see CAF documentation for more details, then it is possible to use a JSF binding expression to specify the action to invoke. This error is thrown if binding expression does not resolve to a valid method. |
Action |
Check and correct the binding expression used for portlet action because it does not resolve to a valid action method. |
POP.016.0052.detail | The target action was: {0} |
Explanation |
The Portlet Url can invoke portlet actions from a URL. If the CAF application does not force the use of Annotated Portlet Actions, see the CAF documentation for more details, then it is possible to use a JSF binding expression to specify the action to invoke. This error is thrown if binding expression does not resolve to a valid action method. |
Action |
Check and correct binding expression used for portlet action because it does not resolve to a valid action method. |
POP.016.0053 | Invalid content type. The allowed content types are: {0} |
Explanation |
An attempt was made to upload a file of an unsupported type to an Attachment Panel control. |
Action |
Upload a file of a supported type for attachments. |
POP.016.0054 | Invalid file extension. The allowed file extensions are: {0} |
Explanation |
An attempt was made to upload a file of an unsupported type to an Attachment Panel control. |
Action |
Upload a file type that is supported as an attachment. |
POP.016.0055 | Invalid file size. The maximum file size is: {0} |
Explanation |
The file uploaded to an Attachment Panel control is larger than the allowed size of an attachment. |
Action |
Upload a smaller file. |
POP.017.0001 | Task is locked and you may not update it at this time. Please wait till task is unlocked |
Class | |
Explanation |
Task instance is locked in following cases: when a task is being updated, or when task events and assignments are being processed. To ensure state consistency when a task is locked, no other updates to the task are possible (though the task can still be read and searched on). Typically lock time is very short (similar to database transaction). |
Action |
Enable MWS "task" logging category Debug logging and investigate timing and duration of task locks. |
POP.017.0003 | Task auditing level is not sufficient to rollback task state |
Class | |
Explanation |
Task state should be kept in task audit in order for task rollback to function. If task state is not present in the audit, rollback is not possible |
Action |
Make sure to audit full task state. Task audit options can be controlled as properties on task definition object. You must login as sysadmin, browse to /task.storage, navigate to "Task Definitions" and open properties of task type, then change audit settings. |
POP.017.0004 | You don't have permissions to queue new task |
Class | |
Explanation |
User does not have a task functional priviliege to queue task of specific task type. |
Action |
Configure Permissions on the user to enable "Queue Task" functional privilege. |
POP.017.0007 | You don't have permissions to view this task |
Class | |
Explanation |
The current user does not have permission to view task information. Prior to MWS_7.1.3_Fix9, the mechanism to determine if a user had permission to view a task required the user to hold "view task data" permission. With the introduction of MWS_7.1.3_Fix9, the user/role must have this permission and also must be present in the "assigned to" or "delegated to" lists. Under these conditions, if the user holds only "view task data" permission, permission to view the task is denied and this error occurs. A task client option, task.base.permission, is available to apply the simpler "view task data" permission even if MWS_7.1.3_Fix9 is applied. For more information, see the Task Engine Optional Settings section in the PDF publication, Task Engine User's Guide. |
Action |
If your system does not have MWS_7.1.3_Fix9 applied, make sure that the user holds "view task data" permission. If your system has MWS_7.1.3_Fix9 applied, make sure the user holds "view task data" permission and is also present on the "assigned to" or "delegated to" lists. Also, see the explanatory text above concerning the task.base.permission option. |
POP.017.0008 | You don't have permissions to view task data |
Class | |
Explanation |
Current User does not have permissions to view task business data. |
Action |
Configure Permissions on the user to enable "View Task Data" functional privilege. |
POP.017.0009 | You don't have permissions to view audit log |
Class | |
Explanation |
Current user does not have permissions to view task audit. |
Action |
Configure Permissions on the user to enable "View Task Audit" functional privilege. |
POP.017.0010 | You don't have permissions to accept this task |
Class | |
Explanation |
Current user does not have permissions to accept task instance. |
Action |
Configure Permissions on the user to enable "Accept Task" functional privilege. |
POP.017.0011 | You don't have permissions to accept other users on this task |
Class | |
Explanation |
Current user does not have permissions to accept task instance. |
Action |
Configure Permissions on the user to enable "Accept Task" functional privilege. |
POP.017.0012 | You don't have permissions to assign this task |
Class | |
Explanation |
Current user does not have permissions to assign task instance. |
Action |
Configure Permissions on the user to enable "Assign Task" functional privilege. |
POP.017.0013 | You don't have permissions to rollback this task |
Class | |
Explanation |
Current user does not have permissions to rollback task instance. |
Action |
Configure Permissions on the user to enable "Rollback Task" functional privilege. |
POP.017.0014 | You don't have permissions to modify task data |
Class | |
Explanation |
Current user does not have permissions to update task business data. |
Action |
Configure Permissions on the user to enable "Modify Task Data" functional privilege. |
POP.017.0015 | You don't have permissions to modify task info |
Class | |
Explanation |
Current user does not have permissions to update generic task info properties. |
Action |
Configure Permissions on the user to enable "Modify Task Info" functional privilege. |
POP.017.0016 | Task Type ID is not valid {0} |
Class | |
Explanation |
This error is reported when attempting to queue a task and specifying an invalid task type ID (from APIs). |
Action |
Check if the specified Task Type is deployed to MWS. |
POP.017.0017 | Task ID is not valid {0} |
Class | |
Explanation |
This error is reported when attempting to operate on invalid task. |
Action |
Check if the specified task is still available in MWS, it may already be deleted. |
POP.017.0018 | Unable to find task client bean: {0} |
Class | |
Explanation |
During task searches, assignments and events evaluation, Task Engine needs access to task generated beans which are part of task application. This error is reported when it fails to instantiate these beans. |
Action |
Check if task application was deployed properly, and if there are any errors in the install.log, re-install task application. |
POP.017.0020 | Cannot obtain FacesContext for Task application: {0} |
Class | |
Explanation |
Indicates that task application was not properly deployed. |
Action |
Investigate any possible errors during task application installation. Re-install task application. |
POP.017.0022 | You don't have permissions to delegate this task |
Class | |
Explanation |
Current user does not have permissions to delegate task instance. |
Action |
Configure Permissions on the user to enable "Delegate Task" functional privilege. |
POP.017.0024 | You don't have permissions to complete this task |
Class | |
Explanation |
Current user does not have permissions to complete task instance. |
Action |
Configure Permissions on the user to enable "Complete Task" functional privilege. |
POP.017.0025 | You don't have permissions to cancel this task |
Class | |
Explanation |
Current user does not have permissions to cancel task instance. |
Action |
Configure Permissions on the user to enable "Cancel Task" functional privilege. |
POP.017.0026 | You don't have permissions to suspend this task |
Class | |
Explanation |
Current user does not have permissions to suspend task instance. |
Action |
Configure Permissions on the user to enable "Suspend Task" functional privilege. |
POP.017.0027 | You don't have permissions to resume this task |
Class | |
Explanation |
Current user does not have permissions to resume task instance. |
Action |
Configure Permissions on the user to enable "Resume Task" functional privilege. |
POP.017.0028 | User {0} not found |
Class | |
Explanation |
This error is reported when using Task Engine API from WmTaskClient IS package and "impersonated" user name is not valid. |
Action |
Check the name of the "impersonated" user in the Task Engine API calls. |
POP.017.0029 | You can not rollback non-Active task |
Class | |
Explanation |
Only tasks in "Active" state can be rolled back. |
Action |
Set the status of the task to "Active". |
POP.017.0030 | You can not queue new task. Task type is not enabled |
Class | |
Explanation |
Task Type, which the task is about to be queued for, is disabled. |
Action |
Enable the Task Type from the Task Engine Administration. |
POP.017.0032 | Connecting user does not have Impersonate Users privilege |
Class | |
Explanation |
When using remote Task Engine API (from WmTaskClient IS package or web services), the API allows to impersonate user so task operations are performed on behalf of a different user. This is useful because typically passwords of end user are not known, so 'sysadmin' account should be used for remote APIs invocation. It is possible to connect to remote API using a non-sysadmin account, but in this case the user account needs to have "Impersonate Users for Remote Clients" Task Engine privilege. |
Action |
Grant the user the "Impersonate Users for Remote Clients" Task Engine privilege. |
POP.017.0033 | You can not update non-Active task: {1} |
Class | |
Explanation |
Tasks whose status is "Completed", "Cancelled" or "Expired" cannot be updated. |
Action |
Administrator can set task status back to "Active". |
POP.017.0034 | You can not rollback non-Active task |
Class | |
Explanation |
Tasks whose status is "Completed", "Cancelled" or "Expired" cannot be rolled back. |
Action |
Administrator can set task status back to "Active". |
POP.017.0037 | Task is out of date, please refresh |
Class | |
Explanation |
Task Engine updates from UI or API implement "optimistic locking" to ensure that data being updated is up-to-date. This error is reported if task data being passed in from UI or API call is not the latest. |
Action |
UI needs to be refreshed to reload up-to-date task data. When using Task Engine APIs task data needs to be re-loaded. |
POP.017.0039 | You don't have permissions to add task comments |
Class | |
Explanation |
Current user does not have permissions to add comments to task instance. |
Action |
Configure Permissions on the user to enable "Add Comment" functional privilege. |
POP.017.0040 | You don't have permissions to delete task comments |
Class | |
Explanation |
Current user does not have permissions to delete comments from task instance. |
Action |
Configure Permissions on the user to enable "Delete Comments" functional privilege. |
POP.017.0041 | You don't have permissions to delete other user's task comments |
Class | |
Explanation |
Current user does not have permissions to delete comments from task instance which were created by other people. |
Action |
Configure Permissions on the user to enable "Delete Other People's Comment" functional privilege. |
POP.017.0042 | You don't have permissions to create new collaboration tasks |
Class | |
Explanation |
Current user does not have permissions to queue collaboration task of another task. |
Action |
Configure Permissions on the user to enable "Queue Collaboration Tasks" functional privilege. |
POP.017.0045 | You can not update suspended task |
Class | |
Explanation |
If current task status is "Suspended", it can only be updated back to "Active" status. No other updates are allowed. |
Action |
Administrator can set task status back to "Active". |
POP.017.0051 | You can not set the parent task ID using the self task ID |
Class | |
Explanation |
This error is reported when attempting to update an existing task via APIs and set its "parentTaskID" property to the ID of the task itself. |
Action |
Check "parentTaskID" being set. |
POP.017.0052 | You can not set the parent task ID using non integer value |
Class | |
Explanation |
This error is reported when updating or queuing a new task via API and "parentTaskID" property is not a valid task ID value. |
Action |
Check value of "parentTaskID" being used. |
POP.017.0053 | You can not set the parent task ID using invalid task ID |
Class | |
Explanation |
This error is reported when updating or queuing a new task via API and "parentTaskID" property is not a valid task ID value. |
Action |
Check "parentTaskID" value used. |
POP.017.0061 | You can not set the delegated to or delegated from list if their size does not match |
Class | |
Explanation |
When updating task delegation via APIs both "delegatedFromList" and "delegatedToList" list values should contain the same number of items. |
Action |
Check "delegatedFromList" and "delegatedToList" values used. |
POP.017.0071 | Task indexTableDis is null or emptys |
Explanation |
Invalid task index configuration is provided from taskDefinition.xml file. |
Action |
Re-create task index configuration by re-configuring task index fields in Designer. |
POP.017.0072 | Task indexTableDis format is invalid: {0} |
Explanation |
Invalid task index configuration is supplied in taskDefinition.xml file. |
Action |
Re-create task index configuration by re-configuring task index fields in Designer. |
POP.017.0090 | Failed to invoke IS service: {0} |
Explanation |
Failed to invoke IS service when executing task decision table assignment. The reason could be that related rule project is not deployed on the corresponding IS server, or that IS service parameters, such as project name, rule set name, etc. are invalid. |
Action |
Please make sure the related rule project is deployed and correct IS service parameters are used when configuring task decision table assigment. |
POP.017.0091 | You can not change status of scheduled task |
Explanation |
If the current status of the task is "scheduled", no other status updates are allowed. |
POP.017.0092 | You can not update task schedule date if task not in scheduled status |
Explanation |
The task schedule date field cannot be updated if the task is not in a "scheduled" status. |
POP.017.0093 | Task Schedule Date cannot be before current date |
Explanation |
The Task Schedule Date attribute specifies the start time of the schedule. However, the value specified in the Task Schedule Date element is for a start time that is before the current time. |
Action |
Specify a date/time value for the Task Schedule Date attribute that is after the current time. |
POP.017.0094 | Task Schedule Date cannot be after Expire date |
Explanation |
The Task Schedule Date attribute specifies the start time of the schedule. However, the value specified in the Task Schedule Date element is for starting the schedule after the Expire date of the schedule. |
Action |
Specify a date/time value for the Task Schedule Date attribute that is before the Expire date. |
POP.017.0095 | You can not change status of active/suspended task to scheduled |
Explanation |
Tasks with an "active" or "suspended" status cannot be updated to “scheduled”. |
POP.017.0096 | You can not accept a scheduled task |
Explanation |
Tasks with a “scheduled” status cannot be accepted. |
POP.017.0097 | Child task schedule date cannot be before parent task schedule date |
Explanation |
A child task should be scheduled to start after its parent task started. |
Action |
Reschedule the child task for a date after the parent task's start date. Alternatively, move back the parent task schedule date. |
POP.017.0098 | Child task schedule date cannot be after parent task expiredate |
Explanation |
A child task should be scheduled for a date before its parent task expires. |
Action |
Reschedule the child task for a date before the parent task's expiration date. Alternatively, extend the parent task's expiration date. |
POP.017.0100 | Task has reached maximum number of modifications |
Explanation |
The task has reached the maximum number of modifications set by the Infinite Loop task rule. |
Action |
Keep a smaller number of modifications to avoid such an error. |
POP.017.0101 | Unhandled Exception during rule processing. Rule [{0}] |
Explanation |
An exception was caught during processing Task Rules. |
Action |
Check the My webMethods Server logs at ..\MWS\server\<instancename>\logs for additional exception details to determine the cause. |
POP.017.0102 | Unhandled Exception during task change processing |
Explanation |
An exception was thrown while publishing a new notification or processing task events. |
Action |
Check the My webMethods Server logs at ...\MWS\server\<instanceName>\logs for additional exception details to determine the cause. |
POP.017.0103 | Unable to deliver task completion to Process runtime (PRT) |
Explanation |
Task completion cannot be delivered to the Process runtime. |
Action |
Check the My webMethods Server logs at ..\MWS\server\<instanceName>\logs for additional exception details to determine the cause. |
POP.017.0104 | Process runtime (PRT) task step failed |
Explanation |
An exception was thrown while processing the task completion. Most likely the time for redelivery was exceeded. |
Action |
Check the My webMethods Server logs at ..\MWS\server\<instanceName>\logs for additional exception details to determine the cause. |
POP.017.0106 | Indexed task searches are not available in Preview Server. Please use standalone MWS server instead |
Explanation |
Indexed task searches are not available when the portal system is running in a preview server mode. |
Action |
Use a standalone My webMethods Server instead. |
POP.017.0107 | Cannot process rule [{0}] for Task [{1}] due to [{2}] |
Explanation |
An exception was thrown while processing the task rule, which may mean that the task cannot be found. |
Action |
Check the My webMethods Server logs at ..\MWS\server\<instanceName>\logs for additional exception details to determine the cause. |
POP.017.0108 | Failed to acquire lock for [{0}] in {1} milliseconds |
Explanation |
The exception occurs when a timeout occurs while waiting to acquire a task lock in the task locking service. |
Action |
Internally used. Some handlers may re-send an event to be re-delivered later. |
POP.017.0120 | RuleName is null or empty |
Explanation |
The RuleName attribute of the schedule rule to be added or updated cannot be null. |
Action |
Specify a valid non-null RuleName attribute. |
POP.017.0121 | TaskTypeID is null or empty |
Explanation |
The TaskTypeID attribute of the schedule rule to be added or updated cannot be null. |
Action |
Specify a valid non-null TaskTypeID attribute. |
POP.017.0122 | StartDate is null or empty |
Explanation |
The StartDate attribute of the schedule rule to be added or updated cannot be null. |
Action |
Specify a valid non-null StartDate attribute. |
POP.017.0123 | Failed to obtain a task index engine manager for: {0}. |
Explanation |
Task Engine cannot obtain a task index engine manager of the specified type. |
Action |
Verify whether: 1. The specified task index manager is registered as an OSGi service. 2. The OSGi service id for the task index manager is correct. 3. The service is running without errors in the My webMethods Server OSGi runtime. |
POP.018.0001 | IView object does not support indexed properties |
Class | |
Explanation |
A binding expression attempted to resolve a property of an IView object by index. This operation is not supported. |
Action |
The ViewPropertyResolver does not support lookup of a property by index. Change the application code so that it does not attempt an unsupported operation. |
POP.018.0002 | IView object is readonly |
Class | |
Explanation |
A binding expression attempted to update a property of an IView object which is not supported. |
Action |
The ViewPropertyResolver does not support update of an IView property. Change the application code so that it does not attempt an unsupported operation. |
POP.018.0003.DirSearchProvider | Failed to move to next principal in directory services, service={0}, error={1} |
Class | |
Explanation |
An unexpected exception occurred during the directory service search API call. |
Action |
Review the server log files for the stack trace of the cause. |
POP.018.0004.DirSearchProvider | Failed to evaluate expression for object, exp={0}, obj={1}, error={2} |
Class | |
Explanation |
An unexpected error was caught while evaluating the value of the property used to sort the principal. |
Action |
Review the server log files for the stack trace of the cause. |
POP.018.0005.DirSearchProvider | Failed to create a directory service iterator, dirService={0}, error={1} |
Class | |
Explanation |
An unexpected error was caught while creating a directory service iterator. |
Action |
Review the server log files for the stack trace of the cause. |
POP.018.0006.DirSearchProvider | Unable to locate the attribute provider for URI={0} |
Class | |
Explanation |
While filtering a principal by an attribute, the provider of the attribute was not located. |
Action |
Check the server to make sure the logged provider URI resolves to a attribute provider. |
POP.018.0007.AttachmentsProvider | Attachments container id is not valid: {0} |
Class | |
Explanation |
The attachements provider for an Attachment Panel control does not have a valid container id for read/write of attachment files. |
Action |
The developer should review the application code to ensure the attachment provider container id is a valid folder id or alias. |
POP.018.0008.AttachmentsProvider | Specified attachments container id is not a container: {0} |
Class | |
Explanation |
The attachements provider for an Attachment Panel control does not have a valid container id for read/write of attachment files. |
Action |
The developer should review the application code to verify that the attachment provider container id is a valid folder id or alias. |
POP.018.0009.AttachmentsProvider | Attachment id has not been specified |
Class | |
Explanation |
The attachements provider updateAttachment or removeAttachment API was called but the attachment id parameter was null. |
Action |
The developer should review the application code to verify that the API calls are passing an attachment id value that is not null. |
POP.018.0010.AttachmentsProvider | FileItem has not been specified |
Class | |
Explanation |
The attachements provider addAttachment or updateAttachment API was called but the fileItem parameter was null. |
Action |
The developer should review the application code to verify that the API calls are passing a a fileItem value that is not null. |
POP.018.0011.AttachmentsProvider | The specified attachment id is not a child of the attachment container: {0} |
Class | |
Explanation |
The attachments provider updateAttachment or removeAttachment API was called with an attachment id that is not a child of the attachments container. |
Action |
The developer should review the application code to verify that the API calls are passing an attachment id value that is a child of the attachments folder. |
POP.019.0001 | Unable to convert data type "{0}" to "{1}" |
Explanation |
The system failed to convert an object from the source data type to the destination data type. |
Action |
Review the error stack trace in the My webMethods Server server logs to determine the cause. |
POP.019.0002 | Cannot load "{0}" because it is not an HTTP resource |
Explanation |
The html parser failed to load the resource. |
Action |
Inspect the error stack trace in the My webMethods Server server logs to determine the cause. |
POP.023.0001 | Failed to start HPSTRA engine |
Explanation |
An error occurred and the HPSTRA engine failed to start. |
Action |
Check the HPSTRA configuration and restart My webMethods Server. |
POP.023.0002 | Failed to save HPSTRA configuration |
Explanation |
An internal error occurred when saving the specified HPSTRA configuration. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
POP.023.0003 | Failed to configure HPSTRA engine |
Explanation |
An error occurred when configuring the HPSTRA engine. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
POP.023.0004 | Error occurred while stopping HPSTRA |
Explanation |
An internal error occurred when stopping the HPSTRA engine. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
POP.023.0005 | Invalid HPSTRA configuration specified. Details: {0} |
Explanation |
The specified HPSTRA congfiguration is invalid or incomplete. |
Action |
Check the HPSTRA configuration and retry the previous operation. |
POP.023.0006 | Failed to perform operation, HPSTRA engine is not enabled. Please configure it properly |
Explanation |
The HPSTRA engine is disabled and cannot perform the requested operation. |
Action |
Enable the HPSTRA engine and retry the operation. |
POP.023.0007 | HPSTRA action execution failed, Reason: |
Explanation |
An internal error occurred and the HPSTRA engine failed to execute the requested operation. |
Action |
Gather error information from the server logs and contact Software AG Global Support. |
POP.023.0009 | Failed to authenticate against an Elasticsearch instance, please check your credentials |
Explanation |
The user name and/or password, specified in the HPSTRA configuration are not valid. |
Action |
Check your credentials in the Authentication section of the HPSTRA configuration and retry the operation. |
POP.023.0010 | An Elasticsearch exception occurred. Details: {0} |
Explanation |
The Elasticsearch server returned an error message in response to the request from the HPSTRA engine. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
POP.101.0001.com.softwareag.caf.shared.diagnostics | The directory does not exist |
Explanation |
The specified directory is not found. |
Action |
Provide a valid directory location as a parameter. |
POP.101.0002.com.softwareag.caf.shared.diagnostics | The specified path is not a valid directory |
Explanation |
The specified location is not a directory. |
Action |
Provide a valid directory location as a parameter. |
POP.101.0006.com.softwareag.caf.shared.diagnostics | Unsupported report type |
Explanation |
A report was generated by an AeventProcessor which is not supported. |
Action |
Use an existing report or add the new one to the list of supported reports in LogAnlyzer.java |
POP.101.0007.com.softwareag.caf.shared.diagnostics | An error occurs while adding a root element to the analyzed log file |
Explanation |
A root element cannot be added to the analyzed log file. |
Action |
Check the log file for any discrepancies. |
POP.101.0010.com.softwareag.caf.shared.diagnostics | Either one or both of the provided documents are null |
Explanation |
The method load() was not invoked beforehand or it was invoked using incorrect parameters. |
Action |
You need to call the load() method before you continue using EnvDiff API. |
POP.101.0011.com.softwareag.caf.shared.diagnostics | At least one argument has to differ from null |
Explanation |
This invocation is not supported. |
Action |
Contact Software AG Global Support. |
POP.101.0012.com.softwareag.caf.shared.diagnostics | Cannot read the following file: {0} |
Explanation |
The file cannot be read. |
Action |
Check file and directory permissions; if the file is accessed over a network, check network connectivity. |
POP.101.0013.com.softwareag.caf.shared.diagnostics | No output channel found |
Explanation |
This behavior is not supported. |
Action |
Contact Software AG Global Support. |
POP.101.0014.com.softwareag.caf.shared.diagnostics | Input directory or file does not exist: {0} |
Explanation |
The specified directory or file does not exist. |
Action |
Specify an existing directory or file. |
POP.101.0015.com.softwareag.caf.shared.diagnostics | The system variable %1$s and the %2$s parameter are not set |
Explanation |
The required system properties are incorrect or are not set. |
Action |
Set the system variables using proper values. For more information, see the product documentation. |
POP.101.0016.com.softwareag.caf.shared.diagnostics | Similarity level must be in the following range: 0-100 |
Explanation |
Similarity level is not set to a valid value. |
Action |
Set a similarity level between 0 and 100. |
POP.101.0017.com.softwareag.caf.shared.diagnostics | Java artifact mapping file does not exist in: {0}; cannot generate {1} report. |
Explanation |
A Java artifact mapping file cannot be found. The report cannot be generated. |
Action |
Specify a valid Java artifact mapping XML file. Use the --java-artifact-mapping parameter to specify the path. |
POP.101.0018.com.softwareag.caf.shared.diagnostics | File not found in: {0} |
Explanation |
The specified file does not exist. |
Action |
Specify an existing file. |
POP.101.0019.com.softwareag.caf.shared.diagnostics | File name is null |
Explanation |
The name of the file was not set in java artifact mapping XML file and this is a unsupported scenario. |
Action |
Contact Software AG Global Support. |
POP.101.0020.com.softwareag.caf.shared.diagnostics | Product ID is null. |
Explanation |
The product ID was not set in a Java artifact mapping XML file; this is a unsupported scenario. |
Action |
Contact Software AG Global Support. |
POP.101.0021.com.softwareag.caf.shared.diagnostics | Database configuration is not specified |
Explanation |
This error occurs when the file mws.db.xml is not specified or cannot be found. |
Action |
Specify a valid mws.db.xml file. |
POP.102.0001.com.webmethods.caf.shared.bpm.common | This configuration is missing important parameters! Session and node id are mandatory! |
Explanation |
This error occurs: 1) when a node id is not provided when trying to search for a content type, or 2) when a session is not opened. |
Action |
For 1), select a node that the searched content is associated with.For 2), verify that the CSP server is running, properly configured, and connected. |
POP.102.0002.com.webmethods.caf.shared.bpm.common | Illegal connection parameters |
Explanation |
An attempt has been made to connect to the CSP server without providing username/password values. |
Action |
In My webMethods, check the Environment entries for the "wm_csp_task" portlet. If they are empty, next check the Global Environment entries. If no values are provided, specify a value for "csp/default/username" and "csp/default/password" entries. In general, the user name and password are specified in the Global Environment entries, except in cases when you have multiple CSP servers and want different portlets to connect to different servers. Otherwise, the Global Environment values are inherited by all portlets. |
POP.102.0003.com.webmethods.caf.shared.bpm.common | The provided session is null! |
Explanation |
The session which is the client primary access point to the CSP server is not instantiated. |
Action |
Verify that the username and password are correct in the CSP configuration in My webMethods Server. |
POP.102.0005.com.webmethods.caf.shared.bpm.common | Error while marshalling! |
Explanation |
This error indicates that a low-level communication problem exists between Task Engine and webMethods Content Service Platform. |
Action |
Stop and restart the Task Engine and the CSP server and try again. If the problem persists, contact Software AG Global Support. |
POP.102.0006.com.webmethods.caf.shared.bpm.common | Error while unmarshaling result! |
Explanation |
This error indicates that a low-level communication problem exists between Task Engine and webMethods Content Service Platform. |
Action |
Stop and restart the Task Engine and the CSP server and try again. If the problem persists, contact Software AG Global Support. |
POP.102.0008.com.webmethods.caf.shared.bpm.common | This configuration is missing important parameters! Content id is mandatory! |
Explanation |
The Content ID value is not set. |
Action |
Verify that a Content ID is set for this provider; ensure that the binding expression is correctly configured. |
POP.102.0009.com.webmethods.caf.shared.bpm.common | No retrieval module initiated! Please set proper session! |
Explanation |
The CSP session is not set for the provider; the retrieval module cannot be initiated. |
Action |
Verify that a session is set for this provider; ensure that the binding expression is correctly configured. |
PerformanceMonitorDefaultviewView.errorMessage.unsupportedPerfServiceImpl | Currently enabled performance service implementation {0} does not support analysis. Cannot proceed. |
Explanation |
The performance service implementation specified for support analysis is not supported. Without these mandatory parameters, the execution cannot proceed. |
Action |
Provide the supported parameters required for the currently enabled performance service. |
WSC.001.0002 | Failed to bind to endPoint: {0} and interface: {1} |
Class | |
Explanation |
The error occurs at binding to the WS-Stack registry. |
Action |
Inspect the stack trace in the My webMethods Server log files to determine the cause of the exception. |
WSC.001.0004 | Context instance does not allow access of inbound SOAP request interceptors |
Class | |
Explanation |
An exception occurred while registering the interceptor with a context at the WS Server service provider. |
Action |
Inspect the stack trace in the My webMethods Server log files to determine the cause of the exception. |
WSC.001.0005 | Context instance does not allow access of outbound SOAP request interceptors |
Class | |
Explanation |
An exception occurred while registering the request interceptor with the context. |
Action |
Verify that the context is an instance of ProxyContext. |
WSC.001.0006 | Exception occurred while invoking webservice: {0}. Details: {1} |
Class | |
Explanation |
An exception occurred while invoking the specified web service. |
Action |
Inspect the stack trace in the My webMethods Server log files to determine the cause of the exception. |
WSC.001.0007 | Unable to connect to web service at {0} |
Class | |
Explanation |
The reason for the web service connection failure is specified in the error message. |
Action |
Check the detailed error message and take the appropriate action. |
WSC.002.0002 | SAML artifact not found in request |
Class | |
Explanation |
The exception occurs when SAML authentication has to be performed, and indicates that the SAML artifact was not found within the SOAP headers of the incoming SOAP request. |
Action |
Check the SOAP request regarding the SAML artifact. |
WSC.002.0009 | SAML Assertion is missing the subject name |
Class | |
Explanation |
An exception was thrown during the verification of the SAML Assertion showing that the subject name is missing. |
Action |
Check the subject name. |
WSC.002.0010 | SAML Assertion has an invalid authentication method, method: {0} |
Class | |
Explanation |
The SAML Assertion passed is not valid. |
Action |
Specify a valid authentication method. |
WSC.002.0012 | SAML Assertion has an invalid statement format |
Class | |
Explanation |
While validating the SAML Assertion the format of the statement is invalid. |
Action |
Specify a valid statement format. |
WSC.002.0013 | SAML Assertion has an invalid assertion id. |
Class | |
Explanation |
The SAML Assertion has an invalid assertion ID. |
Action |
Check the assertion ID. |
WSC.002.0014 | The credential type is not supported: {0} |
Class | |
Explanation |
An exception occurred during realm authentication. |
Action |
Supply a correct credential type. |
WSC.002.0015 | User failed to authenticate with basic auth: {0} |
Class | |
Explanation |
An exception occurred during realm authentication. |
Action |
Check the username and password supplied. |
ascii.only.name.validation.msg | Name cannot contain non ASCII characters! |
Explanation |
The Name field can contain only ASCII charachters. |
Action |
Remove the non-ASCII characters from the Name field. |
config.connection.authentication.password.value | 'Password' cannot be null or empty |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "password" key under connection > authentication does not exist, or has a null or empty value. |
Action |
Check the HPSTRA configuration file, supply a valid password for connecting to the Elasticsearch server, and restart My webMethods Server. |
config.connection.authentication.username.value | 'Username' cannot be null or empty |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "username" key under connection > authentication does not exist, or has a null or empty value. |
Action |
Check the HPSTRA configuration file, supply a valid user name for connecting to the Elasticsearch server, and restart My webMethods Server. |
config.connection.autoDiscovery.pollingInterval.value | Autodiscovery 'polling interval' parameter should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "pollingInterval" key under connection > autoDiscovery has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "pollingInterval" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
config.connection.connectTimeout.value | The 'connect timeout' parameter should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "connectTimeout" key under connection has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "connectTimeout" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
config.connection.connectionPool.maxConnections.value | The 'maximum pool connections' parameter should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "maxConnections" key under connection has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "maxConnections" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
config.connection.requestTimeout.value | The 'request timeout' parameter should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "requestTimeout" key under connection has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "requestTimeout" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
config.connection.servers.size.value | The 'servers' parameter should contains at least one server URL (http, https) |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "servers" key under connection is empty, or has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "servers" key, and restart My webMethods Server. Valid values are unique http or https URLs. |
config.connection.servers.type.value | All entries of the 'servers' parameter should be unique and valid server URLs (http, https) |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "servers" key under connection has one or more invalid values. |
Action |
Check the HPSTRA configuration file, supply valid values for the "servers" key, and restart My webMethods Server. Valid values are unique http or https URLs. |
config.connection.value | Configuration's connection information cannot be null |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "connection" key does not exist. |
Action |
Check the HPSTRA configuration file, supply a valid configuration under the "connection" key, and restart My webMethods Server. |
config.persistence.consistency.value | Index operation 'consistency' parameter should be either null (use default settings) or one of the values: 'one' | 'quorum' | 'all' |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "consistency" key under "persistence" has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "consistency" key, and restart My webMethods Server. Valid values are null (default), "one", "quorum", and "all". |
config.persistence.createIndex.numberOfReplicas.value | The parameter 'number_of_replicas' for the index should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "numberOfReplicas" key under connection > createIndex has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "numberOfReplicas" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
config.persistence.createIndex.numberOfShards.value | The parameter 'number_of_shards' for the index should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "numberOfShards" key under connection > createIndex has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "numberOfShards" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
config.persistence.timeout.value | Index operation 'timeout' parameter should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "timeout" key under "persistence" has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "timeout" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
config.search.searchType.value | Search operation 'search_type' parameter should be either null (use default settings) or one of the values: 'query_then_fetch' | 'dfs_query_then_fetch' |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "searchType" key under "search" has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "searchType" key, and restart My webMethods Server. Valid values are null (default), "query_then_fetch", and "dfs_query_then_fetch". |
config.search.timeout.value | Search operation 'timeout' parameter should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "timeout" key under "search" has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "timeout" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
config.synchronization.batchSize.value | Synchronization's 'batch size' parameter should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "batchSize" key under "synchronization" has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "batchSize" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
config.synchronization.lockTimeout.value | Synchronization's 'lock timeout' parameter should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "lockTimeout" key under "synchronization" has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "lockTimeout" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
config.synchronization.pollingInterval.value | Synchronization's 'polling interval' parameter should be greater or equal to 1 |
Explanation |
My webMethods Server stores the configuration for the HPSTRA engine in the hpstra_config.json file. This exception occurs when the configuration file was modified manually, and the "pollingInterval" key under "synchronization" has an invalid value. |
Action |
Check the HPSTRA configuration file, supply a valid value for the "pollingInterval" key, and restart My webMethods Server. Valid values are positive integers from 1 to 2147483647. |
error.msg.noDebug | The requested URL {0} resulted in an error. |
Class | |
Explanation |
An error occurred while processing the URL. |
Action |
Verify that the URL is correct. |
error.msg.withDebug | The requested URL {0} resulted in an error in {1}. |
Class | |
Explanation |
An error occurred while processing the URL. |
Action |
Verify that the URL is correct. |
g11n.Spregistration.propertygroup.customErrMsg6 | SAML Attribute Name cannot be empty |
Explanation |
You did not provide a value in the reqired field SAML Attribute Name. |
Action |
Provide a valid value in the SAML Attribute Name field. |
g11n.Spregistration.propertyline.non-ascii | Only alphabet, numbers and underscores allowed and Length should not be more than 25 |
Explanation |
The Attributes field can contain up to 25 symbols. Only alphanumerical characters and underscores are allowed. |
Action |
Remove any illegal or excess characters from the field. |
g11n.UmConnectionConfiguration.service.unavailiable | Configuration store service unavailiable |
Explanation |
The OSGI service that stores the SSL configuration in the platform secure store is not available. |
Action |
Retry saving the SSL configuration. If the issue persist, contact your system administrator. |
g11n.UmConnectionConfiguration.validation.path | Invalid path specified |
Explanation |
The location of the truststore/keystore for CA/client certificates is not a valid file path. |
Action |
Check the specified path and supply a valid entry. |
http.status.401 | Unauthorized |
Class | |
Explanation |
Invalid basic authentication credentials. |
Action |
Contact the security officer/web master for this resource and obtain the proper authorization for your credentials. |
http.status.403 | Forbidden |
Class | |
Explanation |
The action is prohibited. |
Action |
The owner of this resource does not allow access to the resource. Contact the security officer/web master for this resource and obtain the proper authorization for your credentials. |
http.status.404 | Not Found |
Class | |
Explanation |
The specified value was not found. |
Action |
Verify that the URL is correct. This error most often occurs when the resource has been removed from the server. It can also be caused by a DNS failure, if the server has been assigned a new IP address, or if the server no longer exists. |
http.status.405 | Method Not Allowed |
Class | |
Explanation |
This HTTP method (GET, PUT, etc.) is not allowed on this server for the specified URL. |
Action |
Use only supported methods. Contact the security officer/web master for this resource for more information. |
http.status.406 | Not Acceptable |
Class | |
Explanation |
The content returned from the server is not specified as acceptable by the client. |
Action |
Investigate the problem by looking at the Accept headers generated by the client system and the data stream returned by the web server. |
http.status.407 | Proxy Authentication Required |
Class | |
Explanation |
Access to the URL resource requires the prior use of a proxy server that needs authentication which has not been provided. |
Action |
Log in to the proxy server with valid credentials and retry. |
http.status.408 | Request Time-out |
Class | |
Explanation |
The interval of time between the establishment of an IP connection (socket) between the client and the server and the receipt of any data on that socket is too long. The server has dropped the connection. |
Action |
Attempt reconnecting to the resource. This error is typically caused by high server loads or network traffic. Contact the web master for this resource if the problem persists. |
http.status.409 | Conflict |
Class | |
Explanation |
The request submitted by the client cannot be completed because it conflicts with an existing condition or rule. For example, a file on the server cannot be replaced with a file that has an older timestamp. |
Action |
Examine the client action and consult with the web master for this resource. |
http.status.413 | Request Entity Too Large |
Class | |
Explanation |
The HTTP data stream sent by the client is too large to be accepted by the server. |
Action |
Attempt sending data in smaller batches. Otherwise, consult with the web master for this resource. |
http.status.415 | Unsupported Media Type |
Class | |
Explanation |
The HTTP data stream sent by the client identifies a URL resource with a media type that does not agree with the media type specified on the request, is incompatible with the current data for the resource, or is incompatible with the HTTP method specified on the request. |
Action |
Examine the request and correct the media type if possible. Otherwise, consult with the web master for this resource. |
http.status.422 | Unprocessable Entity (WebDAV) |
Class | |
Explanation |
The request was well-formed but was unable to be processed due to semantic errors.[ |
Action |
Examine and correct the entity definition. |
http.status.423 | Locked (WebDAV) |
Class | |
Explanation |
The resource that is being accessed is locked. |
Action |
Unlock the resource if possible. Otherwise, contact the web master for this resource. |
http.status.424 | Failed Dependency (WebDAV) |
Class | |
Explanation |
The method could not be performed on the resource because the requested action depended on another action and that action failed (for example, a PROPPATCH). |
Action |
Examine the action request, correct as necessary, and perform again. |
http.status.500 | Internal Server Error |
Class | |
Explanation |
The server encountered an unexpected condition that prevented it from fulfilling the request by the client. |
Action |
Make sure that the required services are running, communication channels are accessible, and parameters are valid. Examine the server logs for more information if possible. Otherwise, contact the server administrator. |
http.status.501 | Not Implemented |
Class | |
Explanation |
The server does not understand or does not support the HTTP method it finds in the HTTP data stream sent to it by the client. |
Action |
Make sure the request contains a vallid HTTP method. |
http.status.507 | Insufficient Storage (WebDAV) |
Class | |
Explanation |
The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request. |
Action |
This condition is usually temporary. If persisten, verify that sufficient storage is available on the server, or contact the system administrator. If the request that received this status code was the result of a user action, the request must not be repeated until it is requested by a separate user action. |
install.fixes.1 | Installing update XML component {0} |
Class | |
Explanation |
The update XML file must be in the proper format and an installation location must be specified. |
Action |
Make sure the file contains the correct XML format and specify the correct location. |
install.fixes.2 | Failed to install update XML component {0} |
Class | |
Explanation |
Update manager has attempted to install the update XML component but the attempt has failed. |
Action |
Make sure that My webMethods Server is running and is connected to the network, and that network connectivity exists to the server. Retry the installation. Otherwise, contact the system administrator. |
install.fixes.3 | Failed to delete update XML component {0} |
Class | |
Explanation |
Update Manager attempted to delete the XML component but was not successfull. |
Action |
Make sure that My webMethods Server is running and is connected to the network, and that network connectivity exists to the server. Retry the deletin. Check the server log file for more information. Otherwise, contact the system administrator. |
install.fixes.4 | Failed to process all update XML components |
Class | |
Explanation |
The update XML components operation could not be processed. |
Action |
Verify that the parameters are appropriately specified in the request. Otherwise, contact the system administrator. |
install.fixes.5 | Completed processing of update XML components |
Class | Not Used |
Explanation |
XML components were updated successfully. |
Action |
No actiion required. |
ldap.exceptions | Unable to retrieve data from {0} ldaps |
Explanation |
The specified directory services failed to return a result due to an error. |
Action |
Check the My webMethods Server logs for errors related to the specified directory services. |
message.um.remoteupdate.fail | MWS node with name "{0}" failed to update with new Universal Messaging URL. |
Explanation |
During an update of the cluster configuration, the specified node failed to be updated. |
Action |
Log into the specified node, and on the Cluster Administration page, click Reload to manually update the node. |
message.um.remoteupdate.fail.ctx | MWS failed to acquire user context, before notifying other nodes about UM URL change. |
Explanation |
During an update of the cluster configuration, the specified node failed to be updated. |
Action |
Log into the specified node, and on the Cluster Administration page, click Reload to manually update the node. |
message.um.update.fail | Current MWS node failed to update with new Universal Messaging URL. |
Explanation |
While updating the JNDI URL of the specified node, the JMS system of that node failed to reload. |
Action |
Restart the node. If My webMethods Server cannot connect to Universal Messaging, check the logs for errors. If the errors are not related to network connectivity, contact Software AG. |
message.um.url.invalid | The specified JNDI URL "{0}" is not valid. |
Explanation |
The specified JNDI URL does not conform to the Universal Messaging standards. |
Action |
The URL must start with a valid UM protocol, such as nsp, nsps, nhp, or nhps, for example: nsp://myurl:9000. |