"Could not access remote file" during swinstall
Kyle Barton
on the machine. Now when I run any swinstall, interactive or not, it
errors out during the actual install. The error is always a variation
of "Could not access remote file --- in software item ---, due to an
internal error on the remote system." In each case it will have
replaced the file with a zero length file. Is this something anyone
else has run across? And if so what was the solution?
For reference here is a logfile example of what I am talking about:
ERROR: Could not access remote file "/usr/lib/pa20_64/libCsup.2" in
software item "PHSS_28879.CORE-64SLIB,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fr=1.0,
due to an internal error on the remote system.
ERROR: Failed installing fileset "PHSS_28879.CORE-64SLIB,r=1.0". Check
the above output for details.
* Retry number 1 of 1 for loading files for fileset
"PHSS_28879.CORE-64SLIB,r=1.0".
* Installing fileset "PHSS_28879.CORE-64SLIB,r=1.0" (1 of 4).
ERROR: Could not access remote file "/usr/lib/pa20_64/libCsup.2" in
software item "PHSS_28879.CORE-64SLIB,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fr=1.0,
due to an internal error on the remote system.
ERROR: Failed installing fileset "PHSS_28879.CORE-64SLIB,r=1.0". Check
the above output for details.
NOTE: The Install Phase has suspended. Check the above output for
reasons.
Thanks
Kyle Barton
Steve K Hamilton
You might try setting the option "All targets to resolve the source locally"
in 'swinstall' when attempting the install. I have seen it resolve the type
of problem before...
HTH.
--
Steve Hamilton
Beechglen Development, Inc.
Email: ste...@SPAM-NOTHANKS.beechglen.com
"Kyle Barton" <kyle....@asg.com> wrote in message
news:34dde80f.04072...@posting.google.com...
V
If you are you may try to ftp the *.depot file on the local machine. Then do
interactive swinstall and point to the path of that *.depot file.
Kinda weird but I remember it working for me a while back.
"Kyle Barton" <kyle....@asg.com> wrote in message
news:34dde80f.04072...@posting.google.com...