Traditionally here we resolve it by upgrading the client to the latest 
version of iSeries Access.  Having went through numerous OS/400 upgrades 
quite often we had to scramble around to several PC's and upgrade them 
when they started getting this message.  Not all - just some.  Kept 
getting it on one fellow's pc even after upgrading iSeries Access.  Laying 
him off solved that issue.

Rob Berendt

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.