Upgrade Express: problems with "Transfer customer data to the target location"

• Article Type: General
• Product: Aleph
• Product Version: 20, 21, 22, 23

Description:
We ran the Upgrade Express 22-23 Source Step 3 ("Transfer customer data to the target location"). It failed each time. This is what we see in the logs:

** transfer_customer_data log 1:**

Step begin transfer_customer_data at 2010-02-24 17:09:03

sftp the archived data to the target server
sftp'ng ^[@aleph1.abc.edu


** transfer_customer_data log 2:**

Step begin transfer_customer_data at 2010-02-24 09:12:54


ftp the archived data to the target server
ftp'ng aleph1.abc.edu
A_ERROR: : transfer customer data par_file not uploaded
ftp: connect to address ::ffff:149.105.5.30: Connection refused
ftp: connect to address ::ffff:149.105.5.30: Connection refused
ftp: connect: Connection refused
Trying ::ffff:149.105.5.30...
Trying ::ffff:149.105.5.30...
Not connected.
Not connected.
Local directory now /br/aleph/upgrade_express_2201_2301/data
Not connected.
Not connected.
Not connected.
Not connected.
Not connected.
Local directory now /br/aleph/upgrade_express_2201_2301/conf
Not connected.
Not connected.
Not connected.

Step end : transfer customer data 2010-02-24 09:14:52


** transfer_customer_data log 3:**

Step begin transfer_customer_data at 2010-03-01 09:33:05

sftp the archived data to the target server
sftp'ng aleph@aleph1.abc.edu

A_ERROR: : transfer customer data nothing Uploaded
A_ERROR: : transfer customer data par_file not uploaded
Step end : transfer customer data 2010-03-01 10:27:47

Resolution:
If you continue to have problems with this, you could just

• manually ftp (or sftp) the ./upgrade_express_2201_2301/data/a20_1.tar.gz file  to the /upgrade_express_2201_2301/data/ directory and then 
• manually ftp (or sftp) the ./upgrade_express_2201_2301/conf/par_file  to the /upgrade_express_2201_2301/conf/ directory.

• Article last edited:  24-Sep-2020