PureConnect

 View Only
Discussion Thread View
  • 1.  2017 R3 Migrator Error

    Posted 11-21-2017 14:27
    Hi All, seeing a strange issue with the new migrator. Our system is currently 2016 R4 Patch 5 which i used Migrator 2017 R3 to export configurations. I am then use Migrator 2017 R3 to import some of the configuration into my dev Enviorment: When it runs it stops with this error: " Error: Unsupported Version Migration, can only migrate forward in version" The configuration that it is stopping on are: Audio Sources Client Button Queue Columns Control Roles I compare the configuration between the 2 system on the configs the error pops on and they look identical; so my question is does migration compare the configuration and if identical not allow you to overwrite? or is there something else going on? Any insight would be appreciated. Thank you, Scott


  • 2.  RE: 2017 R3 Migrator Error

    GENESYS
    Posted 11-21-2017 19:07
    Scott, Just going by what you describe, not having tested anything, it sounds like Migrator thinks the version of IC in your test environment is older than the version of Migrator. What is the patch level on each?


  • 3.  RE: 2017 R3 Migrator Error

    Posted 11-22-2017 21:12
    That is what the Migrator Logs show, even though both are 2016 R4 patch 5. I3 has kicked this up to their Development team as even the INNProduct tool shows both version are the same. Thank you, Scott


  • 4.  RE: 2017 R3 Migrator Error

    GENESYS
    Posted 11-22-2017 22:33
    Both servers may be the same version, but you are trying to use the 2017 R3 version of Migrator to restore files to a 2016 R4 server. Won't work.


  • 5.  RE: 2017 R3 Migrator Error

    Posted 12-06-2017 16:08
    Hi George, I Originally thought that, but support says Migrator Version should not matter as they are backwards compatible. The underlying issue was that in the registry HKLM\Software\Wow6432Node\InteractiveIntelligence\EIC\DirectoryServices\Root\CustomerSite\Production the Key VersionMajor was stating we were running 15, meaning 2015 when in fact we really were 16. Once we adjusted that Key to say 16 migrator ran successfully. Thank you, Scott


  • 6.  RE: 2017 R3 Migrator Error

    GENESYS
    Posted 12-06-2017 18:46
    By now, I should know better than to make a bold, definitive statement regarding what the product will or won't do. I'm glad you got it working!