WebSphere Commerce messages

Action: No action required.

Action: No action required.

Action: No action required.

Action: If this error becomes frequent, add a new JVM system property to the WebSphere Commerce Server instance to increase the maximum number of results.

Action: No action required.

Action: Ensure the registry was initialized and contains the valid entries. During the servlet startup, restart the instance and try again. If the error occurred during refresh registry, retry to refresh the registry identified by the class name.

Action: Review the WebSphere Commerce log file to check if there was an error during the servlet initialization. If an error is found, fix the servlet startup error and then retry.

Action: Review the WebSphere Commerce log file to check if there was an error during the servlet initialization. If an error is found, fix the servlet startup error and then retry.

Action: Verify that the class name {0} is correct and it implements the interface {1} and that it is included in the classpath.

Action: Ensure the command class name is valid and the view exists in the view registry. Review the WebSphere Commerce log to make sure the servlet starts successfully.

Action: React accordingly to the wrapped exception and the associated error log.

Action: Verify that the path you have specified is correct or specify a new path.

Action: Ensure that the specified command has been defined in the appropriate configuration files.

If the command is a URL request, ensure the struts configuration files contains the action configuration between the URL and the command interface name that represents that URL.

If the command cannot be resolved based on the command interface name, update the CMDREG table to contain a mapping between the interface name and the command implementation.

If the changes were made to the configuration files while the server is running, the registries may need to be refreshed. Refreshing the registries can be done using the Administration Console by navigating to the Configuration > Registry menu and updating either the struts or command registry.

Action: Provide all the mandatory input parameters to the command according to the product documentation and re-execute it.

Action: Fix the problem according to the exception information as shown.

Action: Check to ensure the task command in which the current command is trying to invoke, has been registered in CMDREG, and the name matches the one used by the command factory. Also, ensure that the task command does not encounter any exceptions during its execution.

Action: Contact your system administrator.

Action: Ensure that the payment command sets the appropriate environment variable before calling the cashier function. If the payment command does not expect the cashier extension function to be called, review the cashier profile to ensure that there are no ExtensionValue elements in any of the Parameter elements. Update the cashier profile if necessary, and retry the command.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: View the substitution text, correct any problems, and rerun the command.

Action: 1. Ensure the file exists. 2. Ensure the file has the appropriate file permissions. 3. Review the WebSphere Commerce log files. The location of the log files is specified in the Configuration Manager.

Action: Contact WebSphere Commerce support.

Action: Contact WebSphere Commerce support to check for any updated messages.

Action: Ensure the primary key used for the lookup exists.

Action: React accordingly to the wrapped exception. If the problem persists, contact WebSphere Commerce support.

Action: Ensure that the values specified for the create operation do not violate database constraints.

Action: System Administrators should review the WebSphere Commerce log files and take action to correct any previous errors. Contact WebSphere Commerce Support if the problem is not resolved.

Action: If this problem persists, contact WebSphere Commerce support.

Action: Ensure the specified data is a number.

Action: React accordingly to the wrapped exception.

Action: Contact WebSphere Commerce support.

Action: React accordingly to the wrapped exception and the accompanying exception stack.

Action: React accordingly to the wrapped exception.

Action: Check if there is any missing arguments and the object types of the arguments are correct.

Action: React accordingly to the wrapped exception. If the problem persists, contact WebSphere Commerce support.

Action: React accordingly to the wrapped exception and the exception stack.

Action: React accordingly to the wrapped exception and the exception stack.

Action: Review the WebSphere Commerce log for more details.

Action: Check the content of the above mentioned file. If need further assistance, contact WC support with the configuration file.

Action: Ensure the merchant key is valid. Re-encrypt the merchant key and reset the key.

Action: Ensure the attribute name that are currently prohibited are not regularly used attribute names.

Action: Ensure the characters in attribute values that are currently prohibited are not regularly used attribute values.

Action: 1. Ensure that the WebSphere Commerce database is configured and working correctly. Retrace your steps on installing and setting up the database carefully. 2. Examine the WebSphere Commerce log files that are located in the logs subdirectory. If there is a different database or access bean exception thrown within the same transaction or request that puts the database in rollback state, this error message is simply a result of the previous exception.

Action: No action required.

Action: 1. Check that the directory server is running and that the conneciton is on. 2. Check the directory environment properties, such as the directory URL, directory type (SecureWay, Domino, ActiveDirectory or others), authentication credentials and principal, service provider interface (SPIs), and access object class.

Action: Check the following paramters in the directory configuration properties settings: 1. The directory configuration file exists and it is not empty. 2. The directory URL is provided and correct. 3. The directory type is indicated. For example, IBM Directory Server (SecureWay). 4. The directory authentication credentials and principal are provided. 5. The acess object class of the directory is correct. 6. The directory service provider interface (SPIs) is provided.

Action: Re-attempt the authentication by updating the resolved context's environment properties with the appropriate credentials.

Action: 1. Check that the directory server is running and that the conneciton is on. 2. Check if the directory object exists.

Action: 1. Check that the directory server is running and that the conneciton is on. 2. Check if the directory object exists.

Action: Check the user attributes to see if mandatory attributes are missing or ensure that the specified input attribute values are valid.

Action: Ensure the logon ID belongs to a valid X509 user.

Action: Check first to ensure that the database server is responding. If the database server is responding, ensure that the database type is set correctly. The database type is configured at deployment time and can be verified by checking the value of the WCDBType environment variable on the Configurator enterprise bean (in the Enablement-BaseComponentsData module). The correct values are "DB2" for IBM DB2, "DBJ" for IBM Cloudscape, and "Oracle" for Oracle. The default if the attribute is not found is "DB2".

Action: Create an entry in the USERPVCDEV table, mapping the user to the PvC device format ID.

Action: View the Command Reference in the online help to determine the mandatory set of parameters that must be supplied to this command.

Action: Ensure that the interest item list reference number parameter of the command refers to a valid interest item list for the user.

Action: Check the logic of the DataCrytCmd command and ensure it does not throw invalid exceptions.

Action: Modify the attribute value parameters to represent an existing SKU. Use the WebSphere Commerce Accelerator to view and modify the attribute values assigned to a SKU.

Action: No action required.

Action: There are multiple causes for this problem. Contact IBM support for assitance with problem determination.

Action: No action required.

Action: No action required.

Action: Check the ADDRESS table to see if there is an Address object with the specified addressId attribute in the ADDRESS_ID column. If its status attribute in the STATUS column is not 'P', then check to see if there is another Address object with the same nickname and memberId attributes with a status attribute value of 'P'.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: Enter the correct password for this WebSphere Commerce user.

Action: No action required.

Action: The order needs to be in the appropriate state prior to issuing this command.

Action: To lock an Order, prepare it using the OrderPrepare command.

Action: The field needs to be defined as Integer or BigDecimal.

Action: No action required.

Action:

Action: No action required.

Action: Ensure that the category id that is specified refers to a valid category. When this error occurs in the CategoryDisplay command, also check the DISPCGPREL table to ensure that a valid display page has been defined.

Action: Ensure that the category is in the published state for the given language by using the WebSphere Commerce Accelerator to view the category's properties. Alternatively, check that the PUBLISHED column in the CATGRPDESC table is set to 1 for the category in the given language.

Action: Ensure that there is a JSP template registered in the DISPCGPREL table for the specified category, current store, and current language.

Action: Ensure that the catalog entry id that is specified refers to a valid catalog entry. When this error occurs in the ProductDisplay command, also check the DISPENTREL table to ensure that valid display pages have been defined for all catalog entry types.

Action: Use the WebSphere Commerce Accelerator to mark the catalog entry as published. Alternatively, set the PUBLISHED field to "1" in the CATENTDESC table for the catalog entry in the given language.

Action: Use the WebSphere Commerce Accelerator to mark the catalog entry as published. Alternatively, set the PUBLISHED field to "1" in the CATENTDESC table for the catalog entry in the given language.

Action: Ensure that the value of the specified input parameter is valid.

Action: No action required.

Action: Ensure the cookie is being received by the server and the user is using the correct logon ID. Also check if there are any logon violations. Close all browser windows and retry the action.

Action: Look in the WebSphere Commerce error log for other error messages that may indicate why the error occurred.

Action: Don't use this parameter if these conditions could exist or check for these conditions and resolve them prior to calling OrderCopyCmd.

Action: No action required.

Action: Ask the administrator for assistance.

Action:

Action: Either modify the user's e-mail address to the correct address or change the e-mail address being searched for.

Action: Contact WebSphere Commerce support.

Action: Identify the failure command and the corresponding MSGTYPE_ID and make sure the message type has been properly assigned to the correct transport, and that the corresponding mandatory attributes have been set. For example, when sending an e-mail, the sender address must be a valid email address.

Action: If the user requires access to a store in the closed or locked state, ensure that the proper authority is granted.

Action: If the WebSphere Commerce database user registry is used, check the database to ensure that the specified logon ID is valid. If an LDAP user registry is used, check to ensure that the user exists on your LDAP server. If the user does exist, check the LDAP configuration to ensure that the searchbase and mapping attributes are defined correctly in the LDAPEntry.xml file and that the LDAP bind ID has authority to view the subtree.

Action: Check to see if there should be an instance of that job by using the job scheduleer in the Administration Conole or by manually inspecting the SCHCONFIG table.

Action: Ensure that the order ID used is correct and that there is at least 1 item associated with the order.

Action: Ensure that all the required parameters are specified, particularly those that identify a catalog entry (such as partnumber, catEntryId, or productId).

Action: Verify and correct the DTD file corresponding to the command ensuring it contains a mandatory currency element.

Action: Contact your IBM support representative.

Action: Change the nickname, and run the command again.

Action: Log on to WebSphere Commerce and try the update request again.

Action: Ensure that you invoke the setBidQuantity() method in the CheckBidControlCmdImpl command to set the value of the bid quantity before calling it.

Action: Ensure that the request properties included the order reference number.

Action: Ensure the inbound xml message did set the product price, ItemUnitPrice of ListPriceInfo or OfferPriceInfo tag in the xml message.

Action: Ensure that the command that calls the DoPayment task command is correctly setting the totalAmount parameter before calling the execute() method.

Action: Check the WebSphere Application Server EJB error log to find the source of the problem.

Action: Verify that your attribute and value combination is correct and try again.

Action: Check to ensure the correct orders_ID is specified in the calling command.

Action: Check your invocation of this command. Make sure a list of orders in the correct format is supplied.

Action: Check the trace to see what failed.

Action: Run the command again with the appropriate category reference number.

Action: Make sure you specify the parameter URL when you call the command.

Action: Ensure that the command that calls the DoPayment task command is correctly setting the paymentAttributes parameter before calling the execute() method.

Action: Run the command again with the appropriate catalog reference number.

Action: Ensure that the paramters of the command have been set correctly, particularly the catalogID and catalogIdentifier.

Action: Ensure that the request properties object is not null.

Action: Review the WebSphere Commerce log to check if there are any server errors and exceptions.

Action: Enter a value for the year that is numeric, for example, 1961.

Action: Enter a value for the month portion of the time value that is between 1 and 12.

Action: Enter a valid numeric day value for the month, for example, 15.

Action: Enter a value for the hour portion of the time value that is between 0 and 23.

Action: Enter a value for the minute portion of the time value that is between 0 and 59.

Action: Enter a value for the second portion of the time value that is between 0 and 59.

Action: Enter a preferred start time that contains numeric elements.

Action: Ensure the job reference number is not null and is a valid job reference number in the scheduler job entries.

Action: Ensure that all catalog entries in the CATENTRY table also have a record in the CATENTDESC table for each language that the store supports.

Action: Add the attributes to the CATGRPATTR table.

Action: Use the WebSphere Commerce Accelerator to create a new description in the given language, or alternatively add the description to the CATGRPDESC table.

Action: Use the WebSphere Commerce Accelerator to create a new description in the given language, or alternatively add the description to the CATENTDESC table.

Action: Create an association between the catalog entry and the store in the STORECENT table. Alternatively, create an association in the STORECENT table between the catalog entry and a store to which the given store is related in the STOREREL table.

Action: Ensure that the catalog entry exists in the CATENTRY table and that it is associated with the current store or a store that has a catalog relationship to the current store.

Action: Ensure that the catalog group exists in the CATGROUP table and that the STORECCGRP table associates this catalog group to the specified store. Alternatively, ensure that the catalog group has an entry in the STORECGRP table for a store to which the specified store is related. Use the STOREREL table to determine if the specified store is related to any other stores.

Action: Change the calling code to specify only one of the two parameter values.

Action: Inspect the WebSphere Commerce error log to determine the controller command that was executing. Then determine the caller of the command and inspect the calling code to determine why at least one of the specified parameters was not provided.

Action: Create an association between the catalog and the store in the STORECAT table. Alternatively, create an association in the STORECAT table between the catalog and a store to which the given store is related in the STOREREL table.

Action: Ensure that the catalog exists in the CATALOG table and that the STORECAT table associates this catalog to the specified store. Alternatively, ensure that the catalog has an entry in the STORECAT table for a store to which the specified store is related. Use the STOREREL table to determine if the specified store is related to any other stores.

Action: Ensure that the oderItem ID is correct for the order.

Action: Call the appropriate "add to order" command, with each of the bundle components separately defined as parameters to the command.

Action: Check the calling code to determine how the command was invoked on an Order that is not for the current user. If the current user has permission to use the ForUserId parameter, consider specifying the ForUserId parameter, specifying the memberId attribute of the Order.

Action: Refer to the online command documentation to determine possible Order abbreviations for the command. Change the command caller to specify either the reference number of an existing Order object, or a valid Order abbreviation.

Action: Refer to the online command documentation to determine possible OrderItem abbreviations for the command. Change the command caller to specify either the reference number of an existing OrderItem object, or a valid OrderItem abbreviation.

Action: Evaluate your conversion configuration to ensure that it is set up properly.

Action: Add items to the shopping cart before you can call the OrderPrepare command.

Action: Refer to the documentation for the currently installed default implementation of the CheckOrderCopy task command.

Action: Check the error code specified. This should be the cause of the problem. After you determine the source of the error, refer to the Calculation Framework documentation to correct your configuration.

Action: If the original exception is an ECException, examine its accompanying trace and react accordingly. Otherwise, add to the JSP page a catch block that dumps the stack trace.

Action: The hostname or domain of the requested redirect is not in the list of allowed hosts and domains.

Action: Review the WebSphere Commerce log file to check if any I/O stream error was reported.

Action: React accordingly to the wrapped exception.

Action: Inspect the WebSphere Commerce error log to determine the controller command that was executing. Then determine why the command accessed an order that is not owned by the specified store. For example, if the order was specified as an input parameter, determine the caller of the command and inspect the calling code to determine how that input parameter obtained its value. If the Order was created by the OrderSchedule command, check the STOREENT_ID column of the SCHCONFIG table, and the STORE_ID of the Order specified by the corresponding row in the SCHORDERS table.

Action: Check the STORE.ALLOCATIONGOODFOR column to see if ATP inventory is enabled. If ATP inventory is enabled, make sure that all catalog items (CATENTRY.CATENTTYPE_ID ItemBean), packages (CATENTRY.CATENTTYPE_ID PackageBean), and dynamic kits (CATENTRY.CATENTTYPE_ID DynamicKitBean) sold by the store (see the STORECENT table) have a corresponding specified item in the CATENTRY.ITEMSPC_ID column.

Action: Check the SHPARRANG table to make sure an active ShippingArrangement specifies the shipping mode. Check the StartDate and EndDate values.

Action: Use the Store Profile notebook to define a contact address, including the e-mail address, for the Store. To access this notebook, log onto the WebSphere Commerce Accelerator, select the Store menu, then the "Change profile" option.

Action: Check the calling program to understand why it is calling the command specifying an Order that is a child with an inappropriate relationship type.

Action: Check that the uomStandard property in the POLICYCMD table is correct. Check to make sure all the unit of measurement codes that the external system can return are defined in the QTYUNITMAP table for that external unit of measurement standard.

Action: Check that the uomStandard property in the POLICYCMD table is correct. Check to make sure all the unit of measurement codes that the external system can accept are defined in the QTYUNITMAP table for that external unit of measurement standard.

Action: If the currency of the response is correct, then use WebSphere Commerce Accelerator to define and support the specified currency for the specified store. Otherwise, if the currency of the response is not correct, determine why the response specified that currency.

Action: Determine why the response returned amounts in more than one currency.

Action: No action required.

Action: Verify that price and availability responses can be obtained from the external system. If they can be obtained, then this is probably a normal occurrence, due to slow response from the external system, or impatience on the part of the customer.

Action: Refer to the online documentation for the "Order subsystem commands" for a list of valid OrderQuotationRel abbreviations. Use the trace facility to determine the command that was being executed, and determine the caller (usually a java server page) of the command. Change the caller to specify a valid OrderQUotationRel abbreviation.

Action: Inspect the logic of the calling program to determine how an obsolete OrderQuotationRel identifier was obtained. Consider using an OrderQuotationRel abbreviation, if appropriate. (Refer to "Order subsystem commands" in the online documentation.)

Action: The customer can view which orders were not processed, and why. The customer can modify those orders and re-submit them by re-invoking the OrderProcess command.

Action: The customer can view the Order and accept the changed total amount by re-invoking the OrderProcess command.

Action: No action required.

Action: No action required.

Action: Add an order item to the return, change the refund to zero and mark the merchandise as not required to be physically returned.

Action: Make sure that there is an entry in the database for store.rtnffmctr_id.

Action: Make sure the payment system is functioning properly.

Action: Ensure that this product is set to an appropriate buyable status.

Action: Check the access control policy to make sure the user has the correct authority to execute the command. If not, contact your system administrator to set up the correct authority for the user.

Action: Ensure that the interest item list exists and that the catalog entry reference number supplied refers to a valid item.

Action: Ensure that the interest item list exists and that the supplied interest item list identifier is valid.

Action: Verify that the interest item list represented by the interest item list reference number parameter of the command exists in the IITEMLIST table. If necessary, modify the command parameters and retry the delete operation for an interest item list that does exist.

Action: Verify that the interest item represented by the interest item reference number parameter of the command exists in the IITEM table. If necessary, modify the command parameters and retry the delete operation for an interest item that does exist.

Action: Modify the parameters of the command to add the specified interest item into an alternate interest item list.

Action: Ensure that the interest item list reference number command parameter refers to a valid interest item list that is available to the user.

Action: Use the SetInterestItemList command to set at least one interest item list as "current". Alternativley, update the CIITEMLIST table to add current interest item lists for a user.

Action: Administrators should reconcile and remove any duplicate entries in this file.

Action: No action required.

Action: No action required.

Action: Verify that the language ID is valid.

Action: Ensure that the store ID is valid.

Action: Ensure that the end user can only select an order to release to fulfillment that has status "C" or "R"

Action: Ensure that the end user can only select order items that are releasable.

Action: Ensure that the end user can only select order items that are releasable.

Action: Ensure that the user interface only allows the user to select an order that is part of the current store and ensure the correctness of the store ID that is passed to this command.

Action: Check the log for other error messages preceeding this message. Correct the error and retry the command. Alternatively, specify a different fulfillment center assignment for the order item and retry the command.

Action: Check the log for other error messages preceeding this message. Correct the error and retry the command. Alternatively, specify a different fulfillment center assignment for the order items and retry the command.

Action: Specify the order item IDs and retry the command.

Action: Wait for the payment re-authorization to complete and retry the command.

Action: Make sure that the FFMCENTER_ID column of the STORE table specifies a default fulfillment center for the store.

Action: Use the fulfillment user interface to define the specified inventory adjustment code.

Action: Ensure there is a row in the ITEMSPC for all valid part numbers.

Action: Verify the value of "{0}" and parameter "{1}" and try again.

Action: The customer can reduce the requested quantities to be no greater than the availableQuantity attribute values and then re-attempt to process the Order.

Action: Use the AttributeUpdate command to modify the properties of the existing attribute.

Action: Use the AddAttribute command to create the attribute in the specified language.

Action: Verify that the attribute represented by the attribute reference number and language parameters of the command exist in the ATTRIBUTE table. If necessary, modify the command parameters and retry the delete operation for an attribute that does exist.

Action: Use the AttributeValueUpdate command to modify the properties of the existing attribute value.

Action: Use the AttributeValueAdd command to create the attribute value in the specified language.

Action: Verify that the attribute value represented by the attribute value reference number and language parameters of the command exist in the ATTRVALUE table. If necessary, modify the command parameters and retry the delete operation for an attribute value that does exist.

Action: Review the catalog entry parameters and ensure that each is valid for the context in which it is being used. If all parameters appear to be of the expected types, try executing the operation again.

Action: Review the catalog entry update parameters and ensure that each is valid for the context in which it is being used. If all parameters appear to be of the expected types, try executing the operation again.

Action: Check the command parameters including the catalog entry reference number and the catalog entry partnumber.

Action: Use the CatalogEntryUpdate command to modify the properties of the existing catalog entry description.

Action: If the catalog entry object does not exist in the given language, use the CatalogEntryAdd command to create a new catalog entry.

Action: If the catalog group already exists, use the CatalogGroupUpdate command to modify the catalog group object's properties, or the CatalogGroupDelete command to delete the catalog group object.

Action: If the catalog group object does not exist, use the CatalogGroupAdd command to create it.

Action: Check the command parameters including the catalog group reference number and the catalog group identifier.

Action: If the catalog group description object already exists in the given language, use the CatalogGroupUpdate command to modify the catalog group description object's properties.

Action: If the catalog group object does not exist in the given language, use the CatalogGroupAdd command to create a new catalog group.

Action: Either use the CatalogUpdate command to modify the properties of one catalog and give it a unique catalog identifier, or use the CatalogDelete command to delete one of the catalogs.

Action: Use the CatalogAdd command to create the specified catalog, then try the update again.

Action: Verify that the catalog represented by the catalog reference number and catalog identifier parameters of the command exists in the CATALOG table. If necessary, modify the command parameters and retry the delete operation for a catalog that does exist.

Action: If the list price already exists for the catalog entry in the given currency, use the ListPriceUpdate command to modify the amount, or the ListPriceDelete command to delete the list price.

Action: If the catalog entry object does not exist, use the CatalogEntryAdd command to create it.

Action: Check the command parameters including the catalog entry reference number and the currency.

Action: If the offer already exists for the catalog entry, use the OfferUpdate command to modify the offer's properties, or the OfferDelete command to delete the offer.

Action: If the offer object does not exist for the given catalog entry, use the OfferAdd command to create it.

Action: Check the command parameters including the reference numbers of the catalog entry and the offer.

Action: If the specified objects do not exist, use one or more of the following commands to create the missing objects: CatalogAdd, CatalogGroupAdd, or CatalogEntryAdd.

Action: Check the command parameters including the reference numbers of the catalog, catalog group and the catalog entry.

Action: Check the reference numbers for both catalog groups, and ensure that the specified catalog reference number refers to a valid catalog object.

Action: Check the reference numbers for both catalog groups, ensure that the specified catalog reference number refers to a valid catalog object, and validate that this subcategory relationship exists.

Action: Validate the reference numbers for the catalog entry and store objects and ensure that the relationship exists in the STORECENT table.

Action: Validate the reference numbers for the catalog and store and ensure that the relationship does not exist in the STORECAT table.

Action: Validate the reference numbers for the catalog and store objects and ensure that the relationship exists in the STORECAT table.

Action: Validate the reference numbers for the catalog group and store and ensure that the relationship does not exist in the STORECGRP table.

Action: Validate the reference numbers for the catalog group and store objects and ensure that the relationship exists in the STORECGRP table.

Action: Check the reference numbers for the catalog group and ensure that the specified catalog reference number refers to a valid catalog object.

Action: Check the reference numbers for the catalog group and catalog object. Also, validate that this root category relationship exists.

Action: Select another catalog entry, such as a valid product, as the parent of the specified catalog entry.

Action: Enusre that the language id parameter represents a valid langauge as defined in the LANGUAGE table.

Action: Select an alternate type for the assignment.

Action: Check the input that shows in the error message and make sure it conforms to the requirements.

Action: If you replaced the implementation of this class, ensure that the class definition and signatures match the orginal class definition.

Action: If you replaced the implementation of this class, ensure that the class definition and signatures match the orginal class definition.

Action: If you replaced the implementation of this class, ensure that the class definition and signatures match the orginal class definition.

Action: If you replaced the implementation of this class, ensure that the class definition and signatures match the orginal class definition.

Action: If you replaced the implementation of this class, ensure that the class definition and signatures match the orginal class definition.

Action: Refer to the online documentation for "Stored procedure error codes".

Action: To remove catalog entries that exist in previously completed orders, run the Database Cleanup (DBClean) utility to remove the orders that reference the catalog entry. When there are no more orders that reference the catalog entry, run the CatalogEntryDelete command or the DBClean utility to perform the deletion.

Action: Use the Database Cleanup utility (DBClean) to delete outdated orders before attempting to delete the catalog entries prices. Alternatively, set the PUBLISHED field in the OFFER table to indicate that this OFFER should not be used. See the OFFER table schema definition reference to view a list of available values for the PUBLISHED field.

Action: Check that the caller of the DynamicKitConfigurationAdd command specified a quantity amount for each component, and, if prices are specified, a price for each component.

Action: Check the caller of the DynamicKitConfigurationAdd command to make sure that the currency parameter is specified.

Action: Check if any rows can be located from table OICOMPLIST with the configuration ID. Reconfigure the dynamic kit by issuing the DynamicKitConfigurationAdd command. For more information about this command, refer to the online help.

Action: There are multiple causes for this problem. Contact IBM support for assitance with problem determination.

Action: Refer to the WebSphere Commerce online help to learn about the upload file tpyes that are supported, or contact your Site Administrator.

Action: Contact your Site Administrator to troubleshoot the possible file system setup errors.

Action: Ensure that your ZIP file is not corrupted. Use a ZIP utility to check whether the ZIP file is valid.

Action: Check if there is another catalog file in publishing status. If a catalog file is being published, wait until the process is complete before publishing the next catalog file.

Action: Typically, a JSP file only allows a catalog file with the status 'New' to be published. Contact your Site Administrator.

Action: If the error is caused by the errors in the uploaded catalog file, check the catalog file and fix the errors. If the error is caused by file system errors, contact your Site Administrator.

Action: Contact your Site Administrator to troubleshoot possible file system setup errors.

Action: Contact your Site Administrator. The Site Administrator can check the STORECAT table to see if a master catalog is defined for the store. If not, check the STOREREL table to see if this store uses a master catalog from another catalog profile store.

Action: Contact your Site Administrator to troubleshoot store setup errors.

Action: Refer to the CSV catalog file documentation in the WebSphere Commerce information cetner to determine possible errors. After fixing the error, upload the catalog file and publish the catalog again.

Action: Refer to the WebSphere Commerce online help for the supported catalog file formats.

Action: Use the WebSphere Commerce Accelerator to create the root category relationships in the given catalog, or alternatively add the relationships to the CATTOGRP table.

Action: Use the WebSphere Commerce Accelerator to create new product attributes, or alternatively add the attributes and their values to the ATTRIBUTE and ATTRVALUE tables.

Action: Use the WebSphere Commerce Accelerator to create subcategory relationships, or alternatively add the relationships to the CATGPENREL table.

Action: No action required.

Action: Correct the numeric data and try again.

Action: No action required.

Action: Ensure that the credit card number is correct and that the credit card has not expired.

Action: Enter the correct card expiry date and resubmit the request. If the card has expired, use a different card with the corresponding card expiry date.

Action: No action required.

Action: Enter the correct card number and verify the card brand or make sure a correct entry is included in the CCCHECK table, then resubmit the request.

Action: Review your CALRANGE table and ensure that there are no gaps in the span.

Action: Examine previous messages in the log to determine the CatalogEntry, TradingAgreement, ShipMode, and shipping Address for the OrderItem. Check the ShipMode, StartDate and EndDate values for the ShippingArrangements defined in the SHPARRANG table. If the ShippingArrangements specify a ShippingJurisdictionGroup, check that the shipping Address matches one of the ShippingJurisdictions in the ShippingJurisdictionGroup. Check any applicable FulfillmentTC objects in the TERMCOND table. If ATP inventory is not enabled, then check the amount of inventory available in the INVENTORY table.

Action: If this job has an interval of 0 (that is, a job that will only run once), create another WebSphere Commerce scheduler job for the same command to recover this missed run.

Action: Validate the instance by looking up the SCHACTIVE record and ensuring that the SCSINSTREFNUM value matches the specified reference number.

Action: Manually clean up the SCHSTATUS record for the job by changing the state from "R" (running) to the value to which it should be updated in the database. For example, "C" for complete or "CF" for complete but failed.

Action: Ensure the store identifier exists in the store table. Review the WebSphere Commerce log file to check if the servlet has been started successfully.

Action: Edit the command line to correct or remove the incorrect argument.

Action: No action required.

Action: Edit the command line to include the missing argument.

Action: No action required.

Action: No action is required.

Action: Correct the argument.

Action: Type the password for the source database of the staging server.

Action: No action is required.

Action: Correct or remove the specified argument.

Action: Type the password for the destination database.

Action: Edit the command line to provide the missing mandatory arguments.

Action: No action is required.

Action: Check your java runtime classpath to see if the JDBC driver class specified is included.

Action: Type your database password.

Action: Contact your database admininstrator to ensure the isolation level is allowed.

Action: No action required.

Action: No action is required.

Action: Contact your database administrator to ensure auto commit can be turned off before you try again.

Action: No action required.

Action: No action is required.

Action: Check if a name argument is provided or if the format provided is correct.

Action: No action required.

Action: Check if a days argument is provided or if the format is correct.

Action: No action required.

Action: Check if the db type, user name, password, and the schema (if applicable) is correct.

Action: Type the database password and try again.

Action: No action required.

Action: Type the database password and try again.

Action: No action required.

Action: Try again. If it continues to fail, then contact the administrator.

Action: Execute the Database Cleanup utility again, using the correct database password.

Action: No action required.

Action: You might want to check the return code to determine if an error occurred.

Action: Change the KEY column data on either the staging server or the production server to avoid the key value conflict.

Action: Determine why the failed transaction could not be rolled back. Restarting the database usually resolves the issue but should be used as the last resort.

Action: Check the cause if the state represents an error.

Action: Compare the tables on the staging server and the production server, and correct the conflicting data on either the staging server or the production server.

Action: No action required.

Action: Change the command scope parameter to _merchant_, which will include all merchants.

Action: No action required.

Action: Check the Database Cleanup utility log file for errors and ensure that there are no delete restrictions. Run the utility again.

Action: Change the command scope parameter to _merchant_, which will process the table.

Action: Change the command scope parameter to _site_, which will process the table.

Action: No action required.

Action: Correct the index size to match the compression hash table.

Action: No action required.

Action: Check the STAGLOG table and make sure the operations are correct.

Action: No action required.

Action: Ensure that you have enough disk space and that your script directory is correct.

Action: No action required.

Action: Ensure that the specified SQL statement starts with DELETE or UPDATE.

Action: Verify that the input script file exists and can be accessed by the staging server.

Action: Verify that the user ID and password specified to run the Database Cleanup utility are correct. Verify that the database server is running.

Action: Check the column STATEMENT in the CLEANCONF table to ensure that only SELECT, UPDATE, and DELETE SQL statements are in the column.

Action: Check the path and file name, and run the Database Cleanup utility again.

Action: No action required.

Action: Check that the JDBC driver file can be opened and run the Database Cleanup utility again.

Action: Check the Database Cleanup utility log file for errors and run the utility again.

Action: Check the JDBC parameters provided in the customizer file.

Action: Check the Database Cleanup utility log file for errors and run the utility again.

Action: Check the Database Cleanup utility log file to identifiy the problem and run the utility again.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action is required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action is required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action is required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action is required.

Action: No action is required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action is required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: Correct the error and restart DBClean.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: Check the Database Cleanup utility log file for errors.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action is required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action is required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action is required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: No action required.

Action: Check the Database Cleanup utility log file for any errors, and run the utility again.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: Check the Database Cleanup utility log file for any errors.

Action: No action required.

Action: Check the CLEANCONF table and ensure that the SQL statements for the specified object exist.

Action: No action required.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Go through the screen output to identify which trigger creation failed. Check the trigger syntax in the wcs.stage.triggers.sql file.

Action: No action required.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: No action required.

Action: Refer to the staging server log file for detailed information about the cause of the error.

Action: No action required.

Action: Check the file name passed by the parameter -instance, and run the command again.

Action: No action required.

Action: Ensure that you have specified the appropriate file name or directory and run the utility again.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action is required.

Action: No action required.

Action: No action required.

Action: Check the parameters in the cutomizer file.

Action: Check to see if there are any messages that follow this one and give more detailed information.

Action: Check the Configuration Manager server to make sure it is running properly, and that the input instance XML file contains no syntax errors and all the attributes values are correct.

Action: Refer to the log file for the status of creating the database.

Action: Make sure the instance user profile has access to function QIBM_EJB_SERVER_FUNC in product QIBM_EJB_PRODUCT. This can be manually set up through the Application Administration dialog from the iSeries Navigator tool.

Action: Check to make sure the instance exists and that there are no running process reading from the instance's directory.

Action: Refer to the log file for details of populating database with Blaze repository.

Action: Check to make sure the input instance XML file exists and it is well-formed.

Action: Refer to the log file for the status of populating the instance database.

Action: Check the syntax of the input command. The following is the syntax of the valid commands. addInstance [instance xml file location] deleteInstance [instance name] updateInstance [modified xml file location] getInstances getInstanceInfo [instance name] getInstanceConfig [instance name] [[filename to print the instance xml file to]] help exit

Action: Refer to the log file for the status of populating the instance database.

Action: Check the syntax of the input command. The following is the syntax of the valid commands. addInstance [instance xml file location] deleteInstance [instance name] updateInstance [modified xml file location] getInstances getInstanceInfo [instance name] getInstanceConfig [instance name] [[filename to print the instance xml file to]] help exit

Action: Check to make sure the specified instance name exists on the system.

Action: Check the instance default language in the input instance XML file. Valid input are: -1, -2, -3, -4, -5, -6, -7, -8, -9 and -10 with the corresponding language listed below: -1 English -2 French -3 German -4 Italian -5 Spanish -6 Brazilian -7 Simplified Chinese -8 Traditional Chinese -9 Korean -10 Japanese

Action: Remove the instance specific blocks manually from the httpd.conf file. The instance specific blocks start with ########## IBM WebSphere Commerce (Do not edit this section) ################# and end with ########## End of IBM WebSphere Commerce (Do not edit this section) ##########.

Action: The instance can be removed manually. /n1. Under the [instance] tag in the wcs_instances file, locate a line that starts with the instance name to be deleted. /n2. If the line exists, remove the line. /n3. Remove the instance directory from the WC_install_directory/instances directory.

Action: Check if the directory and the file name are correct.

Action: Check the FTP hostname, port number, user ID, and password. Also, check if the FTP server and client are started.

Action: No action required.

Action: One or more errors have occured in configuring components such as the database, WebSphere Appplication Server, and Web server. Refer to the extended messages for the errors for more information.

Action: One or more errors have occured in configuring components such as the database, WebSphere Appplication Server, and Web server. Refer to the extended messages for the errors for more information.

Action: No action required.

Action: Check whether the file exists. If the file exists, check if the file has the correct file permissions. If the file does not exist and no backup file is available, try to reinstall the product.

Action: No action required.

Action: Specify an unique instance name when creating an instance.

Action: Check to make sure the port number is between 0 and 65535.

Action: Check to make sure the WebSphere Application Server information is correct for the instance and that the WebSphere Application Server is running properly.

Action: Check to make sure that there are no invalid manual updates to the instance XML file.

Action: Check to make sure the WebSphere Application Server is started on the port specified in the WebSphere node of your WebSphere Commerce instance XML file.

Action: Check to make sure the WebSphere Application Server is started before attempting to configure WebSphere Commerce.

Action: Please specify to use port 443 for all internal tools ports when using Lotus Domino Web server.

Action: Check to make sure the WebSphere Application Server information for the instance is correct and theWebSphere Application Server is running properly. Also make sure there is enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.

Action: Check to make sure the WebSphere Application Server information for the instance is correct and theWebSphere Application Server is running properly.

Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly. Also make sure there is enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.

Action: Check to make sure the WebSphere Application Server information for the instance is correct and theWebSphere Application Server is running properly.

Action: Check to make sure the WebSphere Application Server information for the instance is correct and theWebSphere Application Server is running properly.

Action: Check to make sure the WebSphere Application Server information for the instance is correct and theWebSphere Application Server is running properly. Also make sure there are enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.

Action: Check to make sure the WebSphere Application Server information for the instance is correct and theWebSphere Application Server is running properly. Also make sure there is enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.

Action: Check to make sure the WebSphere Application Server information for the instance is correct and theWebSphere Application Server is running properly. Also make sure there is enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.

Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly. Also make sure there is enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.

Action: Check to make sure the WebSphere Application Server information and the database information for the instance is correct and the WebSphere Application Server and the database server are running properly.

Action: Please check the wcs.log file located under the instance logs directory. Possible causes could be incorrect database logon information for the WebSphere Commerce datasource or invalid entries in the instance XML file.

Action: One or more Web server configuration related errors have occured. Please refer to the extended messages for the related errors.

Action: One or more Web server configuration related errors have occured. Please refer to the extended messages for the related errors.

Action: One or more Web server configuration related errors have occured. Please refer to the extended messages for the related errors.

Action: One or more Web server configuration related errors have occured. Please refer to the extended messages for the related errors.

Action: Start the Web server manually. In addition, check: whether the value of "ServerRoot" in the httpd.conf file is correct, and whether any other application is hold up the port HTTP Server is trying to use.

Action: No action required.

Action: Check whether "Listen 443" statement exists before the instance Web aliases configuration block in the httpd.conf file. If it does not, add "Listen 443" in the httpd.conf file. Note: Listen 443 should not be commented out. Refer to the httpd.conf.sample file for the right location of "Listen 443" statement location.

Action: No action required.

Action: Check to make sure the Configuration Manager server is running on the port specified. The default port for the Configuration Manager is 1099. If it is started on a non-default port, please use the -port option when running the Configuration Manager client.

Action: Check to make sure the wcsconfig.jar file is in the classpath. If you are using a non-root user to run the Configuration Manager on UNIX, please make sure the non-root user has read and execute permission on the file.

Action: Check if the XML in this file is valid. If the file does not exist and you do not have a backup file, you should reinstall WebSphere Commerce.

Action: Check to make sure the Oracle database is running properly on the specified host/port. Also check to make sure the specified logon information including the Oracle SID is correct.

Action: Check to make sure the Oracle database is running properly on the specified host/port. Also check to make sure the specified logon information including the Oracle SID is correct.

Action: Make sure the system classpath and JDBC level are correct for the database . Also, check the createdb.log file in the instance's logs directory.

Action: Make sure the system classpath and JDBC level are correct for the database . Also, check the createdb.log file in the instance's logs directory.

Action: Choose another database name.

Action: Check to make sure the specified WebSphere Commerce database logon information is correct and the database server is running properly. Also make sure there are no invalid manual updates to the instance XML file.

Action: Install DB2 and make sure it is functioning correctly.

Action: Install Oracle database and make sure it functions correctly.

Action: No action required.

Action: Check if the permissions on the file are correct. Also, check if the file is corrupted.

Action: Check the access permissions of the directory.

Action: Check if the permissions on the file are correct. Also, check if the file system has enough storage space.

Action: Check the permissions of the file.

Action: If the file has been backed up, use the backup file. Also check the file permissions and ownership of the file.

Action: Check the schema.err log file in the instance log folder for more details. Also check if the instance user profile is created.

Action: Check the user profile used to launch the Configuration Manager server to ensure it has the authority to create user profiles.

Action: Before starting the WebSphere Commerce instance, change the instance user profile manually to set the current library to be the instance schema.

Action: Refer to the WebSphere Commerce documentation for a list of supported languages.

Action: Make sure the product is installed correctly and try the task again.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on failure.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the failure occurred.

Action: Specify a value other than null or empty string for the parameter.

Action: If a Payments instance with this name appears to exist, choose a different name for the new Payments instance. If the instance does not appear to exist, verify the following: 1. The database specified is not being used by another Payments instance. 2. The PaymentsInstance.properties file in the Payments instance directory does not exist. Rename the file to PaymentsInstance.properties.old if it does exist. 3. The Payments tables do not exist in the database. If the tables do exist, verify again that the tables do not belong to another Payments instance. If they do not belong to another Payments instance, the tables can be deleted. Back up the tables before they are deleted.

Action: No action is needed if the instance should not exist. Verify the Payments instance name was correctly specified. Verify that the PaymentsInstance.properties file exists in the Payments instance directory. If this file is missing, the Payments instance is corrupted. Contact your IBM support representative for assistance.

Action: See the Configuration Manager documentation for valid properties and property values for Payments instance configuration.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the database connection failed.

Action: Update the database password for this Payments instance through the Configuration Manager.

Action: Verify that the database product is running on the system specified in the URL and that the JDBC URL is set correctly.

Action: Verify that the database specified in the JDBC URL exists on the system. The database specified must exist for a Payments instance to be created. Use the Database Configuration Manager to create a database for a Payments instance.

Action: Verify that the database product that you are using for this instance is correctly installed and configured. Contact your IBM support representative for further assistance.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the instance creation failed.

Action: Manually remove the objects listed to ensure the instance is properly deleted. Running the delete command against this instance again may fail because parts of the instance have been deleted. If the instance is not properly deleted, running the create command for an instance with the same name may fail because parts of the original instance have not been deleted.

Action: Remove the cassettes before deleting the instance. Note that if a cassette is removed, all cassette order data will be lost.

Action: Verify the following: 1. The Web Server is started and listening on the port specified for this Payments instance. 2. The WebSphere Application Server and Payment Servlet started correctly. See the WebSphere logs in the Application Server logs directory for this instance. 3. The WebSphere Application Server plugin-cfg.xml file has the correct entries for the Application Server for this instance. Regenerate the plugin-cfg.xml file if it does not.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the update failed.

Action: Do not attempt to update these properties of a Payments instance.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the password change failed.

Action: Contact the cassette vendor and report this error.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the redeploy failed.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the cassette failed to add.

Action: No action is needed if the cassette status appears to be added and loadable. If the cassette does not have a loadable status, try the Repair Cassette command. Note that if the cassette is removed, all cassette order data will be lost.

Action: No action is needed if the cassette should not exist for this instance. If the cassette does appear to be partially configured for this instance, try the Repair Cassette command and then try to remove the cassette again. Note that if a cassette is removed, all cassette order data will be lost.

Action: Verify the WebSphere Application Server product is installed and functioning properly.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on the failure.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the create failed.

Action: Manually uninstall the WebSphere enterprise application for this instance from the WebSphere Application Server product to complete the deletion of the Payments instance.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the redeploy failed.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the WebServer configuration failed.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the WebServer configuration failed.

Action: This error should not effect the future creation or deletion of Payments instances. Manually delete the WebServer configuration for this Payments instance if desired. See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the delete failed.

Action: Go to the Configuration Manager and re-enable the Unattended Restart feature for this instance.

Action: Check to ensure the zero-argument constructor exists in the class that the current method tries to instantiate. Also ensure that the class that the current method tried to access is declared 'public' if it is in another package.

Action: Ensure that the directory or JAR file that contains the class is in the class path of the WebSphere Commerce Server. The recommended procedure for adding JAR files is to place them in the Stores.war/WEB-INF/lib directory of your application (found, in turn, in the installedApps subdirectory of the WebSphere Application Server installation directory). The recommended procedure for adding classes is to place them in the Stores.war/WEB-INF/classes directory.

Action: Check the parameters of the record and ensure that its values will produce a unique record. Check the database constraint definition of the assocaited table and ensure that all unique indecies are not violated by the data from the new record.

Action: Check the table and remove the duplicated rows.

Action:

Action: Ensure that the structure and contents of the XML document are correct.

Action: Ensure that the views for entity related tasks are defined correctly.

Action: Ensure that the file %1 exists in your file system, or contact WebSphere Commerce support, quoting the error code and providing the file name.

Action: Ensure that the required JDBC driver is loaded and that the CLASSPATH environment variable includes the full path to the JDBC driver. Verify that the correct database name, user ID, or password have been entered.

Action: Disable the firewall. Ensure that the host name is entered correctly. If this does not work, try using the fully qualified host name (for example, myhost.mydomain.myorg.com)

Action: Ensure that the file is not locked by another process when you run the WebSphere Commerce problem determination tool.

Action: This is an internal program error. Contact WebSphere Commerce support, quoting the error code, and providing exact details of the circumstances under which the error occurs.

Action: This is an internal program error. Contact WebSphere Commerce support, providing the XML file that cannot be parsed.

Action: Ensure that the problem determination tool is running on the WebSphere Commerce Server machine.

Action: To resolve the problem: 1) Ensure that the correct hostname is specified. If the short name does not work, try using the fully qualified name instead (for example, myhost.mydomain.com). 2) Disable the firewall.

Action: Contact your IBM support representative.

Action: Contact your IBM Support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: No action required.

Action: No action required.

Action: Contact your IBM support representative.

Action: The user should check the following: 1) The network between the IBM WebSphere Commerce Problem Determination Tool sever and the IBM WebSphere Commerce Problem Determination Tool client is up and running. 2) The correct host name was specified as the input parameter for the IBM WebSphere Commerce Problem Determination Tool client. If the problem persists, contact your IBM Support representative.

Action: The user should check the following: 1) Check that the full path including the directories of the file exist. 2) Ensure that the user has authority to access the directory. 3)Ensure that the drive has sufficient space. If the problem persists, contact your IBM Support representative.

Action: The user should check the following: 1) Check that the full path including the directories of the file exist. 2)Ensure that the user has authority to access and edit the file. 3)Ensure that the file exists and that it is not locked by another process. If the problem persists, contact your IBM Support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: The user should check the following: 1)Check that the CommerceServer55/instances directory exists. 2)Ensure that the user has authority to access and edit the file. 3)Ensure that the file exists and that it is not locked by another process. If the problem persists, contact your IBM Support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM Support representative.

Action: The user should check the following: 1)Check that the full path including the directories of the file exist. 2)Ensure that the user has authority to access the directory. 3)Ensure that the drive has sufficient space. If the problem persists, contact your IBM Support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: The user should check the following: 1)Check that the full path including the directories of the file exist. 2)Ensure that the user has authority to access and edit the file. 3)Ensure that the file exists and that it is not locked by another process. If the problem persists, contact your IBM Support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: The user should check the following: 1)Check that the CommerceServer55/instances directory exists. 2)Ensure that the user has authority to access and edit the file. 3)Ensure that the file exists and that it is not locked by another process. If the problem persists, contact your IBM Support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: The user should check that the follow are true: 1) Check that the full path including the directories of the destination exists. 2) Ensure that the destination drive has sufficient space. 3) Ensure that the user has authority to write to the specified destination. 4) Ensure that if the destination file exists, that it is not locked by another process. 5) Ensure that the drive exists and is not a CD-ROM drive. 6) Ensure that the destination drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.

Action: The user should check that the follow are true: 1) Check that the full path including the directories of the source and destination exist. 2) Ensure that the destination drive has sufficient space. 3) Ensure that the user has authority to read the source file and write to the specified destination. 5) Ensure that the source file exists and that it is not locked by another process. 6) Ensure that if the destination file exists, that it is not locked by another process. 7) Ensure that the destination drive exists and is not a CD-ROM drive. 8) Ensure that the source and destination drives are active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.

Action: No action required.

Action: No action required.

Action: Contact your IBM support representative.

Action: No action required.

Action: The user should check that the follow are true: 1) Ensure that the destination drive has sufficient space. 3) Ensure that the user has authority to read and write to the specified destination. 5) Ensure that the any displayed files exists and are not locked by another process. 6) Ensure that the destination drive exists and is not a CD-ROM drive. 7) Ensure that the destination drive is active in the case of mapped drives or networked drives. If none of the measures correct this issue, contact your IBM support representative.

Action: No action required.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: No action required.

Action: The user should check that the follow are true: 1) Ensure that the product indicated is installed properly on the destination node. 2) Ensure that the product is of a supported level for WebSphere Commerce. If this does not solve your problem, contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Contact your IBM support representative.

Action: Enter a directory which has write-permissions for your user ID.

Action: Contact your IBM support representative.

Action: No action required.

Action: The user should check that the follow are true: 1) Ensure that your operating system locale settings are supported by WebSphere Commerce. 2) Ensure that the destination drive has sufficient space to unpack the resource files. 3) Ensure that the user has access to the default temp directory as assigned by the system. If the problem persists, contact your IBM support representative.

Action: The user should check that the follow are true: 1) Ensure that your operating system locale settings are supported by WebSphere Commerce. 2) Ensure that the destination drive has sufficient space to unpack the resource files. 3) Ensure that the user has access to the default temp directory as assigned by the system. If this does not solve your problem, contact your IBM support representative.

Action: Contact your IBM support representative.

Action: The user should check that the follow are true: 1) Check that the full path including the directories exist. 2) Ensure that the user has authority to read the source file. 3) Ensure that the source file exists and that it is not locked by another process. 4) Ensure that the source drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.

Action: The user should check the following: 1) Check that the full path including the directories of the source file exists. 2) Ensure that the source drive has sufficient space as a copy will be made. 3) Ensure that the user has authority to read the source file and write to the specified destination. 5) Ensure that the source file exists and that it is not locked by another process. 6) Ensure that the source drive exists and is not a CD-ROM drive. 7) Ensure that the source drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.

Action: Contact your IBM support representative.

Action: The user should check the following: 1) Ensure that the user has authority the specified file. 2) Ensure that the XML file exists and are not locked by another process. 3) Ensure that the source drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.

Action: Contact your IBM support representative.

Action: No action required.

Action: The user should check that the follow are true: 1) Check that the full path including the directories of the file exist. 2) Ensure that the user has authority to access the file. 3) Ensure that the file exists and that it is not locked by another process. 4) Ensure that the drive exists and is not a CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.

Action: No action required.

Action: The user should check the following: 1) Check that the full path including the directories of the file exist. 2) Ensure that the user has authority to access and edit the file. 3) Ensure that the file exists and that it is not locked by another process. 4) Ensure that the drive exists and is not a CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.

Action: The user should shut down the specified process before continuing with the installation.

Action: No action required.

Action: The user can: 1) Manually stop the process from the operating system services or command line and retry the installation again. 2) Manually stop any related processes that may prevent the specified process from being stopped and retry the installation again. If the problem persists, contact your IBM support representative.

Action: No action required.

Action: The user should check that the follow are true: 1) The user ID does not contain any special characters or restricted characters. 2) The user ID is not an operating system reserved value. 3) The installation is run as the root user or equivalent to allow access to system services to create a user. 4) The default home directory for this user is a valid path. If the problem persists, contact your IBM support representative.

Action: No action required.

Action: The user should check that the follow are true: 1) The group ID does not contain any special characters. 2) The group ID is not an operating system reserved value. 3) The installation is run as the root user or equivalent to allow access to system services to create a group. If the problem persists, contact your IBM support representative.

Action: No action required.

Action: The user should check the following: 1) Ensure the software package does not have any outstanding prerequisites. 2) Ensure that the destination path has sufficient disk space, including the system temp directory. 3) Ensure that the user has access to the destination path for the software package. 4) Ensure that the correct CD is in the CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. 6) Check that any related processes are not active or locking assets the software package needs to access. 7) Ensure the user running the IBM WebSphere Commerce installer is root. 8) Ensure the that the system registry does not contain any residual information from a previous installation of the product. 9) Ensure that if this product existed previously, that it was cleanly uninstalled. If the problem persists, contact your IBM support representative.

Action: Contact your IBM Support representative.

Action: Ensure the logon account you use has administrative rights. If the problem persists, contact your IBM Support representative.

Action: The user should check the following: 1) Ensure the software package does not have any outstanding prerequisites. 2) Ensure that the destination path has sufficient disk space, including the system temp directory. 3) Ensure that the user has access to the destination path for the software package. 4) Ensure that the correct CD is in the CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. 6) Check that any related processes are not active or locking assets the software package needs to access. 7) Ensure the user running the IBM WebSphere Commerce installer is root. 8) Ensure the that the system registry does not contain any residual information from a previous installation of the product. 9) Ensure that if this product existed previously, that it was cleanly uninstalled. and then attempt another installation of the product upon removal of the failed installed product. If the problem persists, the user may attempt a manual installation from the product CD after exiting the Commerce installer and removing the failed installation. Contact your IBM support representative with all available log information in any event. Logs would be located in the User/System TEMP directory as well as the "<Commerce Install Dir>/logs" directory and the "<WebSphere Application Server Dir>/logs" directory and would include: - log.txt - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log

Action: The user should check the following: 1) Ensure the software package does not have any outstanding prerequisites. 2) Ensure that the destination path has sufficient disk space, including the system temp directory. 3) Ensure that the user has access to the destination path for the software package. 4) Ensure that the correct CD is in the CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. 6) Check that any related processes are not active or locking assets the software package needs to access. 7) Ensure the user running the IBM WebSphere Commerce installer is root. 8) Ensure the that the system registry does not contain any residual information from a previous installation of the product. 9) Ensure that if this product existed previously, that it was cleanly uninstalled. and then attempt another installation of the product upon removal of the failed installed product. If the problem persists, the user may attempt a manual installation from the product CD after exiting the Commerce installer and removing the failed installation. Contact your IBM support representative with all available log information in any event. Logs would be located in the User/System TEMP directory as well as the <Commerce Install Dir>/logs and would include: - db2setup.log - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log

Action: The user should check the following: 1) Ensure the software package does not have any outstanding prerequisites. 2) Ensure that the destination path has sufficient disk space, including the system temp directory. 3) Ensure that the user has access to the destination path for the software package. 4) Ensure that the correct CD is in the CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. 6) Check that any related processes are not active or locking assets the software package needs to access. 7) Ensure the user running the IBM WebSphere Commerce installer is root. 8) Ensure the that the system registry does not contain any residual information from a previous installation of the product. 9) Ensure that if this product existed previously, that it was cleanly uninstalled. and then attempt another installation of the product upon removal of the failed installed product. If the problem persists, the user may attempt a manual installation from the product CD after exiting the Commerce installer and removing the failed installation. Contact your IBM support representative with all available log information in any event. Logs would be located in the User/System TEMP directory as well as the "<Commerce Install Dir>/logs" directory and the "<WebSphere Application Server Dir>/logs" directory and would include: - log.txt - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log

Action: The user should check the following: 1) Ensure the software package does not have any outstanding prerequisites. 2) Ensure that the destination path has sufficient disk space, including the system temp directory. 3) Ensure that the user has access to the destination path for the software package. 4) Ensure that the correct CD is in the CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. 6) Check that any related processes are not active or locking assets the software package needs to access. 7) Ensure the user running the IBM WebSphere Commerce installer is root. 8) Ensure the that the system registry does not contain any residual information from a previous installation of the product. 9) Ensure that if this product existed previously, that it was cleanly uninstalled. and then attempt another installation of the product upon removal of the failed installed product. If the problem persists, the user may attempt a manual installation from the product CD after exiting the Commerce installer and removing the failed installation. Contact your IBM support representative with all available log information in any event. Logs would be located in the User/System TEMP directory as well as the "<Commerce Install Dir>/logs" directory and the "<WebSphere Application Server Dir>/logs" directory and would include: - log.txt - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log

Action: No action is required.

Action: No action required

Action: No action required

Action: No action required

Action: Make sure the JMS Server is available and active, as well as the connection between WebSphere Commerce and the JMS Server.

Action: Make sure the JMS Server is available and active, and, as well, the connection between WebSphere Commerce and JMS Server.

Action: In the first case, make sure the JMS Server is available and active, as well as the connection between WebSphere Commerce and the JMS Server. In the second case, use either java.jms.TextMessage or java.jms.BytesMessage for the inbound message.

Action: The JNDI naming context settings should be checked and users should make sure QueueConnectionFactory is defined as outlined in the product documentation. Re-connection to the JMS Server will happen within 10 minutes by default. This value can be changed under inbound connector configuration using Configuration Manager.

Action: The JNDI naming context settings should be checked and users should make sure the JMS Queue specified is defined as outlined in the product documentation. Re-connection to the JMS Server will happen within 10 minutes by default. This value can be changed under inbound connector configuration using Configuration Manager.

Action: Make sure the JMS Server is available and active, as well as the connection between WebSphere Commerce and JMS Server is available.

Action: Check the JNDI naming context settings to make sure QueueConnectionFactory is defined as outlined in the product documentation. The JMS provider settings (e.g. a MQ Server) should match the requirements of the naming context settings mentioned above. If the JMS Server is a remote server, make sure that the user ID runningWebSphere Application Server and WebSphere Commerce is part of the user group of (or has access to) the JMS provider on the remote machine.

Action: If the problem persists, the networking condition between WebSphere Commerce and the JMS Server should be improved.

Action: Make sure that the JMS Server used by WebSphere Commerce is running and that the connection between JMS Server and WebSphere Commerce is active. If not, restart the JMS server. WebSphere Commerce should re-connect to the JMS Server in 10 minutes by default. If a reply JMS message is expected after sending out a message to a remote system, the sent message will need to be re-sent.

Action: Ensure that the message type used by the command has been properly assigned to the JMS/MQ transport in the Administration Console. Update the WebSphere Application Server namespace definition of the inbound queue with the correct queue information.

Action: Ensure that the message type used by the command has been properly assigned to the JMS/MQ transport in the Administration Console. Update the WebSphere Application Server namespace definition of the outbound queue with the correct queue information.

Action: Ensure the trading agreement XML follows the format as specified in the XSD or DTD files.

Action: Update the jsp file according to the exception information listed in the error message.

Action: Verify the logonId parameter in the inbound message is a valid user ID.

Action: Refer to other related exception information about the same thread for details.

Action: Open the Administrator's Console fromWebSphere Application Server and correct the JNDI name of the user registry EJB according to the information found in the ecmsg log file. Restart the WebSphere Commerce instance

Action: Fix the problem shown in the exception information. There may also be related exception information shown on the same thread.

Action: Correct the situation according to the exception information and re-start WebSphere Commerce if necessary.

Action: Correct the situation according to the error information that has been provided. Verify that the JMS (Java Message Service) configuration has been correctly set up under theWebSphere Application Server JNDI (Java Naming and Directory Interface) namespace. Ensure that the queue and queue manager information are set according to the JMS provider (for example, IBM MQ Server). You can use the IVTRun script to verify this configuration if you are using IBM MQ.

Action: Shut down WebSphere Commerce before shutting down the JMS Server.

Action: Correct the situation according to the exception information and restart WebSphere Commerce if necessary.

Action: Fix the problem according to the exception information and restart WebSphere Commerce if necessary.

Action: Make sure the number of threads defined under Parallel Connectors of the <instance>.xml is larger than 0 but less than the maximum allowable threads created under WebSphere Commerce.

Action: Correct the interfacename and re-execute the command.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

Action: Users will need to fix the XML file according to the error message (as shown) and restart WebSphere Commerce.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

Action: If the reported error is against an XML file, users will need to fix it according to the fatal error message as shown and restart WebSphere Commerce. If the reported error is against an inbound XML message, fix the message according to the fatal error message and resend it.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

Action: Need to fix the XML file if necessary according to the warning message as shown and restart WebSphere Commerce.

Action: Verify the order number and merchant order number parameters in the inbound message is a valid merchant order number.

Action: Correct the content with proper ISO Date Format.

Action: Correct the order ID in the inbound message and re-send the message to WebSphere Commerce.

Action: Correct the content with proper ISO Date Format.

Action: Verify and correct the DTD file corresponding to the command ensuring it contains a mandatory order number and merchant order number elements.

Action: Correct the content with proper ISO Date Format.

Action: Correct the content with proper ISO Date Format.

Action: Make sure there is a unique condition in the system/user message template file for the inbound message to satisfy, in order to invoke a controller command.

Action: Verify the merchant order number parameter in the inbound message has a valid order number.

Action: Correct the sequence number and/or the timestamp and re-send the message to WebSphere Commerce.

Action: Check the appropriate format for the numeric field indicated in the ecmsg log. Make modifications or appropriate type checking in the files that invoke the command (normally either a JSP or a Java class).

Action: Correct the inbound message with proper date format as indicated.

Action: Ensure each order item has the ItemNumber in the inbound message, and resend it.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

Action: Modify the precedence value and/or offer ID in the inbound message and re-send the message to WebSphere Commerce.

Action: Modify the offer price and/or offer ID with the correct values and re-send the message to WebSphere Commerce.

Action: Make sure the inbound message has the correct MEMBER_ID and PARTNUMBER combination, in order to identify a catalog entry in CATENTRY table.

Action: Check the invocation sequence in the ecmsg log. Make modifications to the files that invoke the command (normally either a JSP or a Java class).

Action: Make sure the TradingPositionContainerID provided in the inbound message is correct and the corresponding row in the TRADPOSCN table has been created.

Action: Correct the DTD file corresponding to the command ensuring it contains a mandatory message element.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

Action: Decrease the precedence value of the offer and re-send the message to WebSphere Commerce.

Action: Correct the order item ID and resend the message.

Action: Fix the file according to the failure message indicated in the ecmsg log file and restart the WebSphere Commerce instance.

Action: Contact your IBM support representative.

Action: Verify the specified file exists on the file system.

Action: Verify the content of the specified file.

Action: Add "TemplateTag" node with "Tag" node(s) for the "TemplateDocument" to the message template file and restart WebSphere Commerce.

Action: Add 1 or more "Tag" node(s) to the specified "TemplateTag" node and restart WebSphere Commerce.

Action: Correct the XPath Type to "EMPTY", "PCDATA" or "USERDATA" and restart WebSphere Commerce.

Action: Correct the XPath Type in system/user message file and restart WebSphere Commerce.

Action: Add the field name to XPath in the system/user message template file.

Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.

Action: Add a value to the USERDATA element in the template, and restart the WebSphere Commerce instance.

Action: Correct the XPathType and restart WebSphere Commerce.

Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.

Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.

Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.

Action: Change the FieldInfo as shown in the error message to CDATA in the message template file and restart WebSphere Commerce.

Action: Change the FieldType as shown in the error message to either STRING or DATA in message template file and restart WebSphere Commerce.

Action: Change the XPathType as shown in the error message to one of the supported types in message template file and restart WebSphere Commerce.

Action: Correct the inbound legacy message and re-send it to WebSphere Commerce.

Action: Check the type ID and version fields of the inbound legacy message and make sure the PROLOG_DATA section of the inbound message is correctly formatted.

Action: Please edit the inbound message with the data format specified in the error message and re-send the message to WebSphere Commerce.

Action: Check the field size of the message format and make sure the correct number of bytes is used for the field.

Action: Ensure there is a matching legacy message defined in the ECETMPT table. Resend the inbound message with the correct message type, message version, record type, and record version if necessary.

Action: Ensure the field names and corresponding field types are formatted according to WebSphere Commerce online documentation and resend the message.

Action: Check the requirement set by the corresponding DTD and verify that the mapping between the message and the parameters (used by the command) is correctly done by the message template files.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

Action: Please make sure the store has all the above tables configured properly.

Action: Make sure the jsp (by default, OrderCreateXML.jsp) generating the order create message is using UTF-8 encoding.

Action: Please look up other related errors reported with the same thread id in EC message log file.

Action: Check whether the path and file name are valid for that particular platform (OS), and that no other process is using that particular file.

Action: Check whether another process has the output file locked (still writing to this file).

Action: Check in the ecmsg log file, and verify that the file opened without any problems. Run a disk space check to see whether you have enough free space.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

Action: Ensure that the class listed in the ecmsg log is included in a jar file (wcsruntime.jar by default), and is inside <WebSphere Application Server directory>/installedApps/WC_Enterprise_App_<instance name>.ear/lib.

Action: No action required.

Action: Check the WebSphere Commerce log and the trace file for additional information.

Action: Make sure that the class speicified is loaded for WebSphere Commerce within the WebSphere Application Server.

Action: Make sure that the class speicified is properly loaded for WebSphere Commerce within the WebSphere Application Server.

Action: Please check the message attributes of the message type under Administration Console (under the page assigning the message type to a transport) and make sure attributes are filled with valid data format (e.g. valid email address).

Action: Check the access rights of the user id running WebSphere Commerce and make sure it has access rights to the Messaging.class file.

Action: Check the WebSphere Commerce log and the trace file for additional information.

Action: Ensure the BodyPart class has the following public methods: setDataHandler, setDisposition, and setFileName.

Action: Ensure the underlying implemenation (Java Mail package) supports changes for these headers.

Action: Make sure that the BodyPart or MultiPart class is not an interface or an abstract class.

Action: Ensure that the input parameters match the signatures of the methods.

Action: Make sure that the class speicified is properly loaded for WebSphere Commerce within the WebSphere Application Server.

Action: Please see the related exception information in the same thread for reference.

Action: Check the customized code that set the contents of the message, and make sure it is not passing in a whole object as parameter.

Action: Ensure that an e-mail address is added in the Administration Console by selecting Message Types under the Configuration menu. Set up the recipient using the API in the SendMsgCmd, or the Messaging class in a JSP.

Action: Make sure that the method with name "setAddress" is provided by the class specified under property name "Address" in the TransportConfig section of the <instance>.xml file.

Action: Ensure that the "host" and the "protocol" properties are either set up in the Administration Console by selecting the Transport and Message Type options under the Configuration menu. Create an override in the JSP/Java class.

Action: Check the WebSphere Commerce log for additional information and fix the problem accordingly. For further information, contact your IBM support representative.

Action: Check the connection between the SMTP server and WebSphere Commerce.

Action: Make sure that the property with name "Message" is defined in the TransportConfig section in the <instance>.xml file.

Action: No action required.

Action: Use the Administration Console to properly configure the message type for the specific transport.

Action: Use the Administration Console to properly configure the message type for the specific transport.

Action: Use the Administration Console to properly configure the message type for the specific transport.

Action: Use the Administration Console to properly configure the message type for the specific transport.

Action: Ensure the values specified for the create operation does not violate any database constraints.

Action: Ensure the primary key used for the lookup exists.

Action: Analyse {0} to determine the original error.

Action: If this problem continuously occurs, contact WebSphere Commerce support.

Action: If this problem continuously occurs, contact WebSphere Commerce support.

Action: If the error occurs in Connection/Interaction Properties update, ensure that the foreign key (PROFILE_ID) in either the CSEDITATT or the ISEDITATT database table maps to the primary key (PROFILE_ID) in the PROFILE table. If the error occurs in Transport Status update, open the TRANSPORT database table and check whether there is a valid transport associated with the given STORE_ID and TRANSPORT_ID.

Action: No action required.

Action: Open the <instance>.xml file and verify its content.

Action: Please check whether the class path for WebSphere Commerce is properly configured under WebSphere Application Server. If the problem persists, contact your IBM support representative.

Action: Verify the <instance>.xml file, fix the error and restart WebSphere Commerce.

Action: Based on the attribute name in the ecmsg log, re-insert the XML attribute into <instance_name>.xml and restart the WebSphere Commerce instance.

Action: Ensure the ClassName for the class listed in ecmsg log is valid. If not, correct the problem in <instance_name.xml>. If the ClassName is valid, check whether this class (either packaged as a jar or directory structure) is included in the WebSphere Commerce classpath.

Action: If the error occurs in ConnectorsInfo.java, ensure that the Editable Properties are mapped to public set methods in the Connector. If the error occurs in Messaging, contact your IBM support representatives.

Action: Correct the method name and restart WebSphere Commerce.

Action: Check whether the set method (in the Connection/Interaction Spec) indicated in the ecmsg log conforms to the following: 1 There is not more than one parameter in the method. 2 The parameter is of type Integer, String, Float, Long, or Boolean.

Action: Check to ensure the correct msgtype_ID and store_ID are specified in the calling command.

Action: Check the calling command to ensure that it specifies the correct MSGTYPE_ID.

Action: Check to ensure that the correct MSGTYPE_ID and STORE_ID are specified in the calling command. In addition, ensure that the message type has been assigned to the appropriate active transport of the store or site (STORE_ID = 0).

Action: Ensure that the required message type has been assigned to the required transport (for example, email) under the site or store configuration, using WebSphere Commerce Adminstration Console.

Action: Use the Admin Console to properly configure the message type for the specific transport.

Action: Make sure the TRANSPORT_ID column in the TRANSPORT table is of type Integer and that Transport_ID value in the Property class has not been modified.

Action: Examine the tranport_ID column in the PROFILE tables and make sure that all the TRANSPORT_IDs have the corresponding entries in the TRANSPORT table.

Action: Make sure that there is at least one e-mail address associated with each member during the registration process. Verify this in the ADDRESS database table.

Action: Make sure that MBRBIEWPRF table has a entry with correct PREFERENCE and VIEWNAME for the member with the MEMBER_ID. All the other corresponding tables, for examples USERPVCDEV and DEVICEFMT, should be configured properly.

Action: Ensure that both the transport and the message type have the required connection and interaction specification defined.

Action: Ensure that the member ID is defined in the MEMBER table.

Action: No action required.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

Action: Ensure the message type has been properly assigned to an active and well-defined TRANSPORT by WebSphere Commerce Administration Console. Details on assigning a message type to a transport can be found in the online documentation.

Action: Ensure that only connection and interaction specification properties can be stated for a transport in an <instance>.xml file.

Action: Make sure that the <instance>.xml has the correct connection and interaction specification class name specified and they only contain the valid connection or interaction specification attributes.

Action: Ensure the specification class has a public zero-argument constructor. This class can be found in the <WebSphere Application Server directory>/installedConnectors.

Action: Open the <instance>.xml file and check the specified property and its value.

Action: Contact your IBM support representative.

Action: Open the <instance>.xml file and search for the occurence of the class shown in the error message. Verify the correctness of the package and class name. Verify the class is in the classpath of the WebSphere Commerce log.

Action: No action required.

Action: Open the <instance>.xml file and verify its content.

Action: No action required.

Action: Ensure that the method names specified in properties of the connection or interaction specification of the transport (in instance.xml) have the correct spelling.

Action: Check and verify the specified class is in the classpath setting.

Action: Ensure that the class name and the list of property fields of the Specification Class are both present in the <instance_name>.xml file.

Action: Correct the command to provide the mandatory parameters before calling the message command/system. Consult the WebSphere Commerce Programing Guide for further information.

Action: Make sure that there is at least one e-mail address associated to a member during the registration process. Verify this in the ADDRESS table.

Action: Make sure that the command has set at least 1 MEMBER_ID when calling the messaging system.

Action: Check the LANGUAGE_ID column of the STORE table for the current store and ensure that it is not null.

Action: Check the STOREENT.MARKFORDELETE value of the storeId. If the value is 1, change it to 0. If you are sending email or text messages, make sure you are sending email messages through a valid store.

Action: Correct the store ID and re-send the message.

Action: Check to ensure the correct member_id and viewname are specified in the calling command.

Action: Obsolete. Action same as _ERR_MSG_CFG_NOT_INIT

Action: Correct the JSP file or data bean that supplies the value for the command parameter.

Action: Ensure that the state of the current order is valid to make the requested transition.

Action: Refer to the Payment Manager documentation for details on providing users with the correct authority to configure payments.

Action: Typically, no action required.

Action: Change the value of the configuration file variable to a numeric, and restart the WebSphere Commerce Server.

Action: Avoid using this particular payment method if you expect to use this command to invoke the payment operation for the order.

Action: Verify that the order amount is valid and try again.

Action: Add an entry to the CURCONVERT table that leads from the order's currency to the target currency and retry the operation.

Action: There are two possible corrective actions: 1) Use a different trading agreement that has a sufficient remaining spending limit. 2) Reduce the total value of the order items (for example, by reducing the quantity of each item purchased) until the value is within the remaining spending limit.

Action: There are two possible corrective actions: 1) Use a different purchase order number that has a sufficient remaining spending limit. 2) Reduce the total value of the order (for example, by reducing the quantity of each item purchased) until the expenditure is within the remaining spending limit.

Action: If the account requires that a purchase order number be specified, resubmit the order and specify the number of a predefined purchase order. Otherwise, resubmit the order without specifying a purchase order number.

Action: Specify a different purchase order number and resubmit the order for processing.

Action: Resubmit the order for processing using an active purchase order.

Action: Contact the Seller's Account Representative to determine which credit lines are available for purchases, or select a different payment method.

Action: Do not add order items that use contracts with business accounts different from the ones that are associated with existing contracts. The existing contracts are those used by existing order items in the specified order.

Action: Contact the Seller's Account Representative to determine which accounts are active or select a different contract that references a different account.

Action: Add an entry to the PAYMTHDSUP table for the specified store with the specified payMethodId parameter. Or use the new policyId parameter to identify a payment business policy to use. The policyId parameter identifies the payment business policy to use for payment processing.

Action: Add an entry to the PAYMTHDSUP table for the specified store with the specified payMethodId parameter. Or use the new policyId parameter to identify a payment business policy to use. The policyId parameter identifies the payment business policy to use for payment processing.

Action: Supply a password when creating a logon ID for an administrator. If the logon ID has already been created, add a password. Do not allow the client tool to create an administrator ID without an associated password.

Action: - Ensure the file has a supported file name extension.

Action: Verify that there is at least one price policy which belongs to the specified store and the specified contract. Use the ecmsg.log file to obtain the store ID and contract ID.

Action: This is a system error. Check the WebSphere Application Server EJB error log to find the source of the problem. Follow the recovery action suggested for the problem and retry.

Action: Check the encoding and the file name. If you think both of those are right, please contact your system administrator.

Action: Correct the ACCESSBEAN column in the PATTRIBUTE table for the personalization attribute.

Action: Register a relationship between the personalization attribute and the catalog entry in the PATTRPROD table.

Action: Please make sure a user has at least one entitled contract.

Action: Check the access control policy for the command to make sure the user has authority to run the command.

Action: Ensure that the command implementing the business logic guards is working correctly.

Action: Make sure the transition action is not null. Check the database by running the following SQL query: "select actioninterface from fltransitn where flow_id=? and eventidentifier=? and sourcestate_id=? and targetstate_id=?" You need to replace the ? with the actual values.

Action: Check the Java class for the action command to see if it implements the BusinessFlowCmd interface. If not, modify the class to implement the BusinessFlowCmd interface.

Action: Check the Java class for the resource data bean to see if it implements the BusinessFlowEntityBean interface. If not, modify the data bean class to implement it.

Action: Make sure you have users assigned in the approval member group. Check database by running the following SQL query: "select m.member_id from mbrgrp g, mbrgrpmbr m where g.mbrgrp_id = m.mbrgrp_id and m.exclude = '0' and mbrgrpname = '?' and owner_id = ?" You need to replace the ? with the actual values.

Action: Check the access control policies in the database to see if the user has the access control policy to execute the action with the resources.

Action: Obsolete

Action: Obsolete

Action: Obsolate

Action: Obsolete

Action: Obsolete

Action: Obsolete

Action: Obsolete

Action: Check the WebSphere Commerce log for additional information and fix the problem accordingly. For further information, contact your IBM support representative.

Action: Ensure that the JNDI name which is specified in the outbound connector section of <instance_name>.xml is the same as the "JNDI binding path" that is used to deploy a resource adapter in WebSphere Application Server.

Action: Contact your IBM support representative.

Action: Use the Work with License Information (WRKLICINF) command and select option 2 (Change) to increase the usage limit. The usage limit should be increased only if it will match the limit authorized by the software provider. If the software provider authorized limit has been exceeded, the software provider must be notified immediately to update the authorized limit and start the appropriate order and billing processes.

Action: Ensure that the QWEBCOMM55 library exists. If the library does not exit, the product was not installed correctly.

Action: No action required.

Action: Verify your configuration settings and try the command again.

Action: No action required.

Action: No action required.

Action: Ensure that the code set you specify is UTF-8 compliant.

Action: No action required.

Action: Allow write permission for the file for the user ID under which Configuration Manager is running.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: No action required.

Action: Reinstall WebSphere Commerce.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the mappedConfigPath property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the mappedServerPath property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the webserverHostname property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the iisServerNumber property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the documentRoot property and re-run the configuration.

Action: Make sure the document root path is correct and exists and re-run your cofiguration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the webserverPort property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value for the webserverPort property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the toolsPort property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value for the toolsPort property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneSecurePortConf property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneNonSecurePortConf property and re-run the configuration.

Action: The sunoneToolsPortConf Ant property is required to configure the Web server.

Action: The sunoneAdminPortConf Ant property is required to configure the Web server.

Action: The sunoneOrgAdminPortConf Ant property is required to configure the Web server.

Action: The sunoneSecurePortConf Ant property is required to configure the Web server.

Action: Change the file permissions to allow read and write access on the file specified by the sunoneOrgAdminPortConf property

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneNonSecurePortConf property and re-run the configuration.

Action: Change the file permissions to allow read and write access on the file specified by the sunoneNonSecurePortConf property

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value for the sunoneToolsPortConf property and re-run the configuration.

Action: Change the file permissions to allow read and write access on the file specified by the sunoneToolsPortConf property.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneAdminPortConf property and re-run the configuration.

Action: Change the file permissions to allow read and write access on the file specified by the sunoneAdminPortConf property.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value for the sunoneOrgAdminPortConf property and re-run the configuration.

Action: Change the file permissions to allow read and write access on the file specified by the sunoneOrgAdminPortConf property.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the authenticationMode property and re-run the configuration.

Action: In the< WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value of the isConfigViaFTP property and the isConfigViaNFS property and re-run your configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the remoteInstallPath property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the ftpServerName property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the ftpServerName property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the ftpServerPort property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value for the ftpServerPort property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the ftpUserId property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the ftpUserPwd property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the mappedConfigPath property and re-run the configuration.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the mappedServerPath property and re-run the configuration.

Action: Re-run the previous configuration to make sure the object is created and re-run the current configuration.

Action: The datasource name assigned by Configuration Manager is WebSphere Commerce DB2 DataSource <instanceName> or WebSphere Commerce Oracle DataSource <instanceName>. If the datasource name assigned Configuration Manager is already in use, change the datasource name and re-create the instance using the instance creation wizard. You can also change the value of the datasourceName property in the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file and re-run the configuration.

Action: Correct the database type.

Action: The JAAS Authentication Data Alias name assigned by Configuration Manager is WC_<instanceName> - authDataAlias. If an existing JAAS Authentication Data Alias already used the name assigned by Configuration Manager, remove the instance, change the instance name and re-create the instance using the instance creation wizard. You can also change the value of the instanceName property in the WC_installdir/instances/<instanceName>/properties/createInstance.properties file and re-run the configuration.

Action: Try to re-run the configuration. If problem persists, contact your WebSphere Commerce support representative.

Action: Ensure the application server exists or create the application server and re-run the configuration.

Action: Assign a unique JDBC provider name or delete the existing one and re-run the configuration.

Action: Try to re-run the configuration or manually create the JDBC provider using the WebSphere Application Server. If the problem persists, contact your WebSphere Commerce support representative.

Action: Try to re-run the configuration or manually remove the datasource using the WebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: Try to re-run the configuration or manually remove the JAAS authentication data using the WebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: Try to re-run the configuration or manually remove the JDBC provider using the WebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: Try to re-run the configuration or manually remove the application server using theWebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: If the EAR file is partially installed, clean up and re-run the configuration. Also, try to install the EAR file using the WebSphere Aoolication Server Administrative Console. The EAR file to be installed is located in <WC_installdir>/instances/<instanceName>/<instanceName>.ear. If the problem persists, contact your WebSphere Commerce support representative.

Action: Try to re-run the configuration or manually create the specified virtual host using theWebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: Ensure that the WebSphere Application Server configuration is not corrupted. Also, ensure the <WAS_installdir>/<profileName>/bin/setupCmdLine utility has the correct value for the WAS_NODE variable and re-run the configuration.

Action: No action required.

Action: Try to re-run the configuration or manually create the application server using the WebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: Ensure the WebSphere Application Server configuration is not corrupted. Also, ensure the object exists and re-run the configuration.

Action: Ensure that the specified application server exists or create the application server and re-run the configuration.

Action: Try to re-run the configuration or manually remove the application server on the specified noder using the WebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: No action required.

Action: Try to re-run the configuration or manually create the host alias for the virtual host using the WebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: No action required.

Action: Try to re-run the configuration or manually remove the host alias using theWebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: Try to re-run the configuration or manually remove the object using theWebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: Remove the duplicate application servers using the WebSphere Application Server Administrative Console and re-run the configuration.

Action: Try to re-run the configuration or manually modify or create the object using theWebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: Add the <propertyName>=<propertyValue> at the end of the createInstance.properties file and re-run the configuration. The file is located in the WC_installdir/instances/<instanceName>/properties/createInstance.properties.

Action: Ensure the following directories exist and re-run the configuration: <WC_installdir>/instances/default/xml <WC_installdir>/instances/default/trading Also, ensure that the user running Configuration Manager has write access to the <WC_installdir>/instances/<instanceName> directory.

Action: Examine the <WC_installdir>/instance/<instanceName>/logs/createInstanceANT.log file and correct the problem describe the error messages in the log file. Then, re-run the configuration or remove the instance specific line in the <WC_installdir>/instances/wcs_instances file manually.

Action: Ensure that no application is using any file in the instance's directory. Back up any necessary files and delete the <WC_installdir>/instances/<instanceName> directory manually.

Action: Ensure the file exists and the permissions are set correctly. If you cannot recover from this, you must re-install the product.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, add a line anywhere that reads <property_name>=<property_value>.

Action: Try to re-run the configuration or manually remove the object using theWebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: Try to remove the existing shared library using the WebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

Action: Ensure the parameter is specified so that it is properly passed to the method.

Action: Ensure the business context configuration XML file is well-formed and is in the class path of the WebSphere Commerce Server.

Action: Ensure that the name of the factory class is specified correctly in the busines context configuration file and is in the class path of the WebSphere Commerce Server.

Action: User must log in to WebSphere Commerce Server again in order to obtain a new activity token.

Action: User must log in again in order to retrieve a new activity token.

Action: User must log on again in order to retrieve a new activity token.

Action: If this is a generic-user activity, ensure that the activity exists in the activity cache. If this is a guest-user or registered-user activity, ensure that its business context exists in the CTXDATA database table.

Action: Ensure the attributes of the business context are specified correctly.

Action: If the resource should be locked, then no action is required. To manually unlock the managed resource, delete the record in the CMMETADATA table that has the matching resource container, resource manager, and managed resource keys.

Action: No action necessary.

Action: No action required.

Action: Ensure that the Stores Web application has been started.

Action: No action required.

Action: A status message is available in the audit log to indicate which record might be altered. Examine the audit record to see the current values and to see what data might have been altered.

Action: Ensure the input properties for the attachment asset are valid.

Action: Ensure the input properties for the attachment relation are valid.

Action: Check the attachment asset in the database. The table containing the information is ATCHAST. Ensure that the attachment asset is owned by an attachment target in the same store entity. Ensure that the attachment asset path, together with the store entity and the attachment target, is unique in the database.

Action: Check that the store entity owns both the attachment target and the attachment asset. Check that the path and filename of the attachment asset is valid and is not used by another attachment asset.

Action: Ensure that the row in the database table ATCHAST that contains attachment asset is not locked.

Action: Check that the attachment target is not language-independent, ensure the attachment asset is not already assigned to the language, and do not assign more than one attachment asset in the same attachment target to the same language.

Action: Check the ATCHASTLG database table for the assigned languages for the attachment asset. Ensure the row is not locked.

Action: Check the ATCHREL database table for the attachment relation. Ensure the sure the unique index of the table is not violated. To attach the WebSphere Commerce object to the same target again, use a different usage.

Action: Check the ATCHREL database table for the attachment relation. Ensure that the combination of the object ID, the attachment object type ID, the attachment target ID in the attachment relation and the attachment relation usage ID is unique. Also ensure that the row is not locked.

Action: Check the ATCHREL table in the database for the attachment relation. Ensure the row is not locked.

Action: Check the database table ATCHRELDSC for the description of the attachment relation in the specified language.

Action: Check the ATCHRELDSC database table for the description of the attachment relation. Ensure the row is not locked.

Action: Check the ATCHRELDSC table for the description of the attachment relation in the specified language in the database.

Action: Check the attachment relation usage in the database table ATCHRLUS. Ensure that the unique index is not violated.

Action: Check the ATCHRLUS database table for the attachment relation usage. Ensure the identifier for the attachment relation usage is unique.

Action: Check the ATCHREL database table for the attachment relation. Ensure that no attachment relation is using the attachment relation usage by checking the ATCHRLUS_ID column. If this usage is being used by another attachment relation, assign the attachment realation to a different attachment relation usage and try deletion again.

Action: Check the databaes table ATCHRLUSDS for the description of the attachment relation usage in the specified language.

Action: Check ATCHRLUSDS database table for the description of the attachment relation usage in the specified language.

Action: Check the ATCHRLUSDS database table for the description of the attachment relation usage in the specified language. Ensure the row is not locked.

Action: Check the ATCHTGT database table Ensure that the unique index of the table is not violated.

Action: Check the ATCHTGT databae table. Ensure the combination of the identifier of the attachment target, the store entity that owns the attachment target, and the owner of the attachment target is unique.

Action: Ensure the attachment target is not associatied with any objects before deletion.

Action: Check the ATCHTGTDSC database table for the description of the attachment target in the specified language.

Action: Check database table ATCHTGTDSC for the description of the attachment target in the specified language.

Action: Check the ATCHTGTDSC table in the database for the description of the attachment target. Ensure the row is not locked.

Action: Turn on tracing for attachments and examine the trace file.

Action: If this happens consistently, contact WebSphere Commerce support for assistance.

Action: Contact your system administrator to provide this service by enabling ActivityTokenBased SSO flag in webshpere commerce.

Action: Check the WebSphere Application Server Admininstrative console to ensure that the WebSphere Member Manager application is running. Check to ensure that your LDAP server is running and accessible.

Action: Correct the customized code so that it passes valid reservation amounts and release IDs to EDP.reservePayment().

Action: Correct the customized code and ensure that the correct invalid ID is being passed down to finalize payment.

Action: Check the payment status later. If the payment status is still pending, then call the administrator.

Action: Ensure that the correct payment instruction has been successfully created and the correct order ID and payment instruction ID are being specified.

Action: Ensure that the correct payment details are passed as the protocol data for a payment instruction.

Action: Ensure that the required payment plug-in attributes are specified in the storefront JSP buy page.

Action: Correct the task commands code and pass the finalization amount down to the EDP.finalizePayment request accordingly.

Action: Ensure that the customized code is passing a valid (non-empty) set of release IDs on EDP.reservePayment and a valid release ID on EDP.finalizePayment().

Action: Correct the customized code so that the total order amount is always specified in event-driven payment requests.

Action: Correct the customized code so that it passes a valid reservation amount to EDP.reservePayment().

Action: Ensure that correct parameters are passed for the payment instruction being created and the complete end-to-end configuration of order and payments is correct for available payment methods, payment method configurations, payment system mappings, and plug-in deployment descriptors.

Action: Add a payment instruction to a specified order or modify the order ID to refer to an existing order.

Action: Add a payment instruction to a specified order or modify the order ID to refer to an existing order.

Action: Correct the end-to-end payment method configuration and specify a valid store ID.

Action: Ensure that a valid payment ID is specified and that the payment back-end system is available and can be reached through the network.

Action: Correct the end-to-end refund method configuration and specify a valid store ID.

Action: Ensure that a valid refund (RMA) ID is specified and that the payment back-end system is available and can be reached through the network.

Action: Ensure that a valid payment instruction ID is specified in the task command.

Action: Ensure that the correct payment details are passed as the protocol data for a payment instruction.

Action: Delete the index directory and recreate the search index.