LDN - Luminis Developer Network

Hello everyone,

I have been working with support since Dec. on this problem and we haven't really gotten anywhere, so I decided to look elsewhere for help.

We keep getting the same error when we attempt to migrate from LumIII.3.3.64 to LPIV. The error occurs during the "executing operation: transform the pds ldif file" portion of the migration. For some reason the migration reports the progress rate has dropped below 50% so it ends the pass, and begins a new one. Unfortunately when this loop starts, it doesn't end.

We have one successful migration, and although we have taken the exact same steps and followed the same instructions to migrate, we cannot get this software to migrate properly. We originally had a similar problem with the working LPIV system, but reindexing the userRoot seemed to do the trick. We have reindexed the userRoot to no avail in our latest efforts, and to be honest I am quickly running out of options and patience.

What really makes the problem annoying that when the error occurs it is recorded as an internal error, and the actual error and/or bad records are never logged. ANYWHERE!!! The only reference to the error is:
[31/Mar/2008:11:55:22 -0400] - import userRoot: Decided to end this pass because the progress rate has dropped below the 50% threshold.
[31/Mar/2008:11:55:22 -0400] - import userRoot: Ending pass number 1 ...
[31/Mar/2008:11:55:22 -0400] - import userRoot: Foreman is done; waiting for workers to finish...
[31/Mar/2008:11:55:22 -0400] - import userRoot: Workers finished; cleaning up...
[31/Mar/2008:11:55:27 -0400] - import userRoot: Workers cleaned up.
[31/Mar/2008:11:55:27 -0400] - DEBUG - conn=-1 op=-1 msgId=-1 - internal error: 52 entries not processed remaining in import queue
[31/Mar/2008:11:55:27 -0400] - import userRoot: Sweeping files for merging later...
[31/Mar/2008:11:55:34 -0400] - import userRoot: Sweep done.
[31/Mar/2008:11:55:34 -0400] - import userRoot: Beginning pass number 2

Which is recorded in the importplatform.properties file.

These loops all display the same message and go on forever. Once, I let it run over night and sure enough ...the next morning it was on like pass 256. There are no error message recorded in any of the other log files. Go figure?!?

Has anyone seen this before or have any ideas? What would really be helpful is if someone could suggest how we might actually be able to identify the 52 entries remaining in teh import que that the error message is referring to.

Thanks,
Kevin B.