When upgrading a site, one or more conversion scripts may not run due to a timeout or other error or because the user interrupted the process at startup. In these situations, the scripts that have not run can be determined by checking the IPSError.log.
A successful script run will have three lines like this:
20170131 18:55:25.0133 0h 0m 27s Conversion Script 46 not yet done. Setting Flag to Run.
20170131 18:55:25.0148 0h 0m 27s Running Conversion Script 46...
20170131 18:55:25.0148 0h 0m 27s Completed Running Conversion Script 46
An unsuccessful script may have this line:
20170131 18:55:25.0538 0h 0m 27s Conversion Script 45 not yet done. Setting Flag to Run.
But it will be missing the other lines that indicate it was run and it completed.
When this happens, a registry trigger can be used to force the script to run:
1. Use IPSUtils to Close Suite.
2. Set the following registry setting to 1:
HKLM\SOFTWARE\Idealpos Solutions\Idealpos\Conversions\ConversionScript_45
(A sample REG file is attached which can be used, or, if done manually, you may need to create the \Conversions key.)
3. Restart IdealposPOS, and it should attempt to run the script.
4. Check the IPSError.log to ensure that the script completed.
Internal Support Info
