OK, I did this to myself. Michel set me on the right track when he told me I had created a program with an infinite loop.
So, over the weekend I was updating my config and changed a bunch of devices. When going through the programs looking for places I had to change devices which no longer existed I looked at the Query All program and it had an error in the Then statement. I deleted that statement and put in Run Program - Query All - which just caused it to run itself. I should have put in:
Set 'Barn EISY' Query
So, I assume this is fixed and will close this thread. I don't know how the query all program got messed up originally but I know that I made it worse.
Thanks, Michel.
Andy
OK, started the whole migration over again using the same backup as before and this time it worked.
1. On the EISY admin console, did File - Restore ISY
2. After the reboot of the EISY, checked the links tables and they still show the old PLM (of course)
3. Did a File - Restore Modem (PLM)
That is pretty much the same thing I did the first time. But this time, it worked and now there are many more links in the PLM and the EISY is being notified on all device changes. I guess the technical explanation is that all the controller links were in place after the migration but none of the responder links - or the other way around - not an expert on that, obviously!
Don't have a clue why the first migration failed, but happy that it worked the second time. I guess my only advice out of this is don't spend hours trying to troubleshoot a migration which is partially working and just start over again.
Thanks to everyone for your support and suggestions!
Andy
