That is close to what I ran. I moved the users over first along with the universes and some other dependent items.
The script I use for the Favorites reports is a little different than yours.
exportQuery1=SELECT TOP 100000 static, relationships, SI_PARENT_FOLDER_CUID, SI_OWNER, SI_PATH FROM CI_INFOOBJECTS WHERE DESCENDANTS("SI_NAME='Folder Hierarchy'", "(SI_KIND='FavoritesFolder')") And SI_INSTANCE = 0
This query only moves the reports themselves, no instances. We are doing this to shorten our outage window for the upgrade. I have another script that I ran later to migrate any recurring instances.
exportQuery1=SELECT TOP 100000 static, relationships, SI_PARENT_FOLDER_CUID, SI_OWNER, SI_PATH FROM CI_INFOOBJECTS WHERE DESCENDANTS("SI_NAME='Folder Hierarchy'", "SI_ID in (23)") And SI_INSTANCE = 1 And SI_RECURRING = 1
After these are run we will bring our environment up. Afterward, we will migrate any instances with this code:
exportQuery1=SELECT TOP 100000 static, relationships, SI_PARENT_FOLDER_CUID, SI_OWNER, SI_PATH FROM CI_INFOOBJECTS WHERE DESCENDANTS("SI_NAME='Folder Hierarchy'", "(SI_KIND='FavoritesFolder')") And SI_INSTANCE = 1 AND SI_RECURRING = 0
The only other difference other than the query that I see in my properties file from yours is I set
includeSecurity=true
I successfully migrated the following:
[list]2,176 Users and Groups
3,201 Favorites Reports with folders
14 Recurring instances
32 historical instances[/list]
This error almost sounds like the Windows AD might not be installed or something wrong with it. The Pattern Book says to configure it but then disable it while you are doing the migration. It doesn’t mean it’s not possible to perform the migration if you don’t do this. In my test, Windows AD was still configured and active in the source environment because I can’t bring it down right now. The source environment did not have Windows AD configured at all.
One thing that might help you figure out what the error is would be to add
-Dtracelog.logdir="D:\PromotionScripts\Logs\." -Dtracelog.configfile="D:\PromotionScripts\LCMCLI_trace.ini"
to your lcm_cli.bat file. You can put the locations where ever you want and set the LCMCLI_trace.ini settings to the information that you want. This will provide you with more specific log files while you are running lcm.cli.bat.