Product Migration:unable to download the archive file because of an IOException
I have got an error while using product migration wizard: 'Target system was unable to download the archive file because of an IOException: java.io.IOException: Server returned HTTP response code: 401 for URL'.
I have verified that '/..../tomcat-users.xml' has the username and password that has been used to create an instance of the Data-Admin-System-Security class in source system. Also verified that I can ping target system from the source system. I went over this issue in PDN discussion that recommends to verify user in appserver, and create the instance which I did but did not resolve the issue.
What could be the root cause and resolution for this issue Pega in 7.1.9?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
IN
401 always indicates that there is authorization problem.
Can you try with some other system to see the issue is persisted or not ?
Pegasystems Inc.
US
Check the system granting access on DASS record (see image below) and make sure it matches the value you are pinging as well as the host name in the product migration page.
Tata Consultancy Services
US
Hi Paul,
Thank you for your reply. I can ping the servers by IP Addresses as well as by the server names (hostnames). I configured the DASS as well. However, I am not able to migrate the product. I still see the same error:
First I see the message: The migration request has been received, and when we click the product migration work object, the message is 'Target system was unable to download the archive file because of an IOException: java.io.IOException: Server returned HTTP response code: 401 for URL: '
If anyone has resolved this issue, please share your thoughts.
Accepted Solution
Pegasystems Inc.
IN
401 always indicates that there is authorization problem.
Can you try with some other system to see the issue is persisted or not ?