Troubleshooting: Publishing

If you experience problems while publishing a store archive:

  1. Review the following log files:
    • activity.log
    • trace.log
    • message.txt
    • trace.txt
    • i5/OSiSeries RESWCSID.txt
    • SystemOut.log and SystemErr.log
    For more information and locations for each log file, see Publish log files.
  2. To configure logging for the Loader package, including increasing the logging level, see Customizing logging for the Loader package.
  3. Enable the WC_DEVTOOLS trace log.
    1. If the problem occurred while executing a particular task, you should configure tracing for the corresponding component. For example, if it the contractimport or accountimport command fails, enable the corresponding component, WC_Contract.
  4. If an error occurs during the data loading phase of publishing, the error displays on the Publish Details page in the Administration Console. To view the Publish Details page for your store archive, see Viewing publish status.

Business Edition onlyRepublishing contract or account

If a message in the activity.log or the Publish Details page reports a duplicate contract exception, but publishing has completed successfully:

If a message in the activity.log or the Publish Details page reports a duplicate account exception, but publishing has completed successfully, ignore this warning.

Publishing is successful but store does not display or does not function properly

If publish is stated to be successful, but you can't launch the store, or the store isn't functioning properly, check the activity.log file for errors.

AIXSun Solaris Operating EnvironmentLinuxWindowsTransaction log for the database is full

If the message, "Transaction log for the database is full" displays in the message.txt log, you have the following options:

Business Edition onlyPublishing a component store archive results in a duplicate store name in the Store Creation wizard

After publishing a component store archive (for example, B2BDirectHostedStorefrontAssetStore.sar, ConsumerDirectResellerStorefrontAssetStore.sar, or CatalogAssetStore.sar), you may notice duplicate store names displayed in the Store Creation wizard. To avoid this problem, execute the following SQL statement every time upon completing publishing a component store archive:

update storeentds set displayname='store_name'
where storeent_id=(select storeent_id from storeent where identifier='store_identifier')
and lang_id=-1

where:

store_name
The name that you want to be displayed in the Store Creation wizard.
store_identifier
The value of the store identifier parameter you have provided during the publishing of the component store archive.

Feedback