I was getting the same error a few minutes ago. I was able to fix it by doing the .ASC dance.
I understood your meaning and it seems to have worked.
Your phrasing tells me this is a regular method of solving problems with PADS. Do you find yourself doing this often within the span of a single project or is once usually enough to clear out the cobwebs? I guess what I'm implicitly asking is if your workflow has turned into: "if error, rotate .asc"?
Does the community know the proximal cause; the high risk maneuvers?
No, just every now and then. Sometimes things just get a little strange and that will usually fix it. Actually it's usually easier to go into the router and then back into layout to fix things. In this case that obviously wouldn't help, so I resorted to the old .asc dance. Going in/out of the router has actually been suggested by Mentor Support.
I believe the optional synchronization is just a resource thing. With sync. on, I must still click the layout/router button to swap the software context for related tasks but I no longer have to wait for the displays to clear and repopulate during the swap. Also, pan and zoom are "cross probed" between both windows.
Thanks for the help