This comes from a very old thread, but I seem to be having a problem of this nature. I'm working on migrating Listserv 15.0 on a Solaris SPARC V9 machine (64-bit big-endian) to Listserv 16.0 on a Red Hat x86_64 machine (little-endian.) I can re-hash the signup files, and everything looks ok except for a problem with PERMVARS.FILE. If I copy PERMVARS.FILE to the new server, I get many errors like this at the start of Listserv's log file: >>> Invalid PERMVARS FILE entry (KL=4096 LL=130) with the numeric values changing. All the data is not getting copied. For example, there is no longer a list of served off addresses. Is there any solution to this, or will we have to use a new PERMVARS file and live with that as part of the migration? Peter Eric Thomas wrote: > You normally see this error when migrating between servers of different > architectures, for instance Windows vs. unix, or just unix brand 1 vs. unix > brand 2. Not every file can be copied over and reused as is, some files > contain information specific to the system LISTSERV is running on, there are > also subtle differences between Windows and unix, between 32-bit and 64-bit > systems, and so on. But from Windows x86 to Windows x86, you should be able > to copy the whole directory tree and not worry about it, assuming of course > that the target directories match the source directories. That is, if you > are transferring from C:\LISTSERV to E:\Products\L-Soft\LISTSERV, it is not > going to work as is because all your paths are different. > > The particular error you are getting indicates that PERMVARS.FILE cannot be > updated. I cannot tell you more without a larger excerpt from the log, > either way 1.8d is very old and the source code I am looking at probably > does not match the source code used to compile what you are running. > > Eric ############################ To unsubscribe from the LSTSRV-L list: write to: mailto:[log in to unmask] or click the following link: http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTSRV-L&A=1