Appendix A       Troubleshooting


This chapter describes operations you perform after you have installed BuyerXpert and offers troubleshooting tips you can try before you contact Technical Support.

I Can't Log In to Administrator.apm or Express.npm When Creating and Verifying PM Cluster

Try restarting iWS.

I Cannot Add to the Cart with Sample Data

Make sure the initXXX.ora (where XXX is the ORACLE_SID) file has open_cursors set to a value greater than 100.

When Trying to Restart iWS Instance from Web Server Admin, the Following Error Displayed:

[https-hostname]: start failed (2: unknown early startup error)

[https-hostname]: failure: watchdog could not connect to notification port ( Connection refused )

Remove the file named wdnotify under https-web-server/logs.

I Get a Login Error When Trying to Log in Using the Sample Data

Try removing the LDAP server that was created for membership and recreate a new one. Then, run the following two scripts:

1. Create LDAP schema:

   IAS_HOME/shared/bin/ldapmodify -h hostname -p LDAP_port_number -c -a -D irectory_user -w directory_user_password -f

   IAS_HOME/buyer/sample_data/directory_ldif/buyer/iplanet/schema.ldif

For example:

/export/IAS60/shared/bin/ldapmodify -h colonial -p 20000 -c -a -D "cn=Directory Manager" -w adminadmin -f

/export/IAS60/sample_data/directory_ldif/buyer/iplanet/schema.ldif)

2. Import LDAP data:

   IAS_HOME/shared/bin/ldapmodify -h hostname -p LDAP_port_number -c -a -D directory_user -w directory_user_password -f

   IAS_HOME/buyer/sample_data/directory_ldif/buyer/iplanet/BuyerXpertS ample.ldif

where:

IAS_HOME is the location where IAS is installed

hostname is the machine name

LDAP_port_number the port number when creating the LDAP instance

directory user is the name you used to the directory server. For the case of sample data, the directory user is cn=Directory Manager

directory user password the password for the directory user

For example:

/export/IAS60/shared/bin/ldapmodify -h colonial -p 20000 -c -a -D "cn=Directory Manager" -w adminadmin -f /export/IAS60/sample_data/directory_ldif/buyer/iplanet/BuyerXpertSa mple.ldif)

I Cannot See the Sample Catalog After Installation

• Make sure you have InterMedia Text installed in Oracle.

• Be sure that you have enabled the catalog using the Catalog Manager.

If neither of the above works, you need to re-populate the database by running the create_schema.sh and import_data.sh scripts as follows:

1. Verify that the iPlanet Application Server is running.

2. Run the create_schema.sh script.

   This script creates the user accounts and all the tables/indexes in the user accounts, then loads the seed data for the whole application, including sample catalog.

   IAS_HOME/ias/bin/KIVAes.sh stop

   IAS_HOME/buyer/sample_data/impexp_file/create_schema.sh -r IAS_HOME -u user_name/password -s system user/password-d ORACLE_SID -o ORACLE_HOME -t DATA TABLE_SPACE -i INDEX TABLE_SPACE

where:

IAS_HOME is the location where IAS is installed

user_name is the user to be created in oracle

password is the user password created in Oracle

Example
/export/IAS60/buyer/sample_data/impexp_files/create_shcema.sh -r /export/IAS60 -u bx/bx -s system/manager -d BXM3 -o /export/oracle816 -t TS01 -i TS02

3. Run the import_data.sh script.

   This script imports the sample policy book and all the importable sample data for the application. The data includes:

   • Policy book

   • Unit Sample data

   • Sample Price Lists

   • Sample Adjustment templates

   • Shipment Method and Freight Term sample data

   • Sample Policy instances

   • Office Furniture catalog for Staples, Inc.

     IAS_HOME/ias/bin/KIVAes.sh start

     IAS_HOME/buyer/sample_data/impexp_files/import_data.sh -s -r IAS_HOME -u URL -n login name -p password -o organization_name

where:

IAS_HOME is the location where the iPlanet Application Server is installed

URL is where BuyerXpert is running

login name is the user login name of the Admin interface

password is the user password

organization_name is the user organization name

Example
/export/IAS60/buyer/sample_data/impexp_files/import_data.sh -s -r /export/IAS60 -u http://colonial.red.iplanet.com:8080 -n admin -p admin -o mercury.com

Workflow deployment failed; descriptor failed an internal sanity check.

This failure of workflow deployment is associated with the Process Manager. If it occurs during deployment, you need to remove the bx40_mercu_data table from the cluster (for example, Process Manager) Oracle user, and import the workflow again.

SQL> select table_name from all_tables;

TABLE_NAME
------------------------------

DUAL
SYSTEM_PRIVILEGE_MAP
STMT_AUDIT_OPTION_MAP
AUDIT_ACTIONS
PSTUBTBL
AURORA$IIOP$SYSTEM$PROPERTIES
MD$DICTVER
OGIS_SPATIAL_REFERENCE_SYSTEMS
CS_SRS
HELP

TABLE_NAME
------------------------------

BX40_KLMNL_DATA
BX40_MERCU_DATA
DYNAMIC_GROUP
HISTORY
KLMNL_SP2_DATA
KLMNL_SP3
PROCESS_INSTANCE
WF_BLOBS
WF_ID_RANGE
WORK_ITEM

21 rows selected.

SQL> drop table bx40_mercu_data;

Table dropped.

SQL> commit;