In this article all known problems which were found at the previous upgrades are located.
Issue: During PBA for Windows upgrade to version 5.5 MS SQL transaction log file can grow to a very large size, depending on size of the installation.
Cause: During upgrade some modifications are done for heavy loaded tables. To lessen upgrade time, scripts require MS SQL transaction log to grow.
Resolution: Before upgrade, check size of tables "DeliverLine", "ARDocArc", "OrdDetArc", "DocDetArc", "SalesOrderArc", "SubscrParamArc". Make sure that free space on the hard disk where MS SQL transaction logs are stored is at least 5-10 times more than size of the largest table. After upgrade, shrink MS SQL transaction log using standard MS SQL mechanisms.
Issue: During PBA Linux upgrade/installation, post-upgrade script fails to restart "httpd". Error looks like:
Stopping httpd failed with error: Could not reliably determine the server's fully qualified domain name, using cent6x64.com for ServerName Starting httpd failed with error: Could not reliably determine the server's fully qualified domain name, using cent6x64.com for ServerName (98)Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs
Cause: PBA application server cannot resolve PBA hostname, as a result "httpd" service starts for a very long time.
Resolution: Make sure PBA hostname is resolved by PBA application server.
Issue: PBA-E installer may fail with following error in /tmp/product_installer.log:
WARNING: package xmlrpc-c-1.16.24-1209.1840.el6.x86_64 (which is newer than xmlrpc-c-1.16.24-1200.1840.el6_1.4.x86_64) is already installed
WARNING: package xmlrpc-c-client-1.16.24-1209.1840.el6.x86_64 (which is newer than xmlrpc-c-client-1.16.24-1200.1840.el6_1.4.x86_64) is already installed
Cause: Bug #PBA-52048
Resolution: Correponding packages could be replaced with rpms from PBA-E distribution /tmp/pba-installer/ with options '-Uhv --oldpackage' or tempoarary uninstalled by '-e --justdb --nodeps'.
Issue: Upgrade procedure breaks while check xml customization
Applicable only for PBA 5.5.1-091 Linux installation
In case you install any of the listed containers:
take the following actions:
1. Run the following commands after installing PBA application:
rm -f /usr/local/bm/conf/wnd/RUSSIANMARKET/RUSSIANMARKET
rm -f /usr/local/bm/conf/wnd/RUSSIANMARKET/customization.RUSSIANMARKET
rm -f /usr/local/bm/conf/wnd/PVERIFICATION/PVERIFICATION
rm -f /usr/local/bm/conf/wnd/PVERIFICATION/customization.PVERIFICATION
rm -f /usr/local/bm/conf/wnd/FSTELMEX/FSTELMEX
rm -f /usr/local/bm/conf/wnd/FSTELMEX/customization.FSTELMEX
2. Re-run configure.pl
Issue: If RUSSIANMARKET container was installed, after upgrade to 5.5 Subscription Expiration notifications will not be sent to the customers.
In case you install RUSSIANMARKET container please follow related KB article to resolve the issue: