Sage 100

We are planning an upgrade from 2013 Premium to 2017... on the same server as an active Sage 300 install (about which I know nothing). Are there any conflicts I need to be aware of with Sage 300 on the server too? (They do use Intelligence on 300 and we will be setting SI up for 100 during the upgrade). Obviously we don't want to break anything with their Sage 300 when we install Sage 100 v2017 Premium. (A new SQL instance is being created). Any / all tips of things to watch out for would be appreciated.

Test a vanilla install before proceeding too far. I seem to remember when Sage Advisor first came out I could not get both 100 & 300 running on the same VM. I didn't spend a whole lot of time on it - I just created separate VMs. There may be a Crystal mismatch - Sage 300 has moved on to Crystal 2013 & 2016. @LloydSmith - have you run across this?

@PhilMcIntosh @KevinMoyes - There are crystal runtime dll conflicts and Sage intelligence conflicts. The reports in intelligence will need to be recreated as the connectors are different, table and fields as well. I do have them both installed in an instance but on the Sage 100 install I didn't install Intelligence (due to the conflict) and I set the windows\crystal folder to read only to prevent any files getting installed into the folder. I also uninstalled sage advisor service, as we do on all installation now.

@LloydSmith - So it would be your recommendation to not have production Sage 100 & Sage 300 on the same server, correct?

That is correct.

Thanks @PhilMcIntosh and @LloydSmith . Now I am very wary of proceeding, knowing a separate server will be a hard sell... the have both co-existing currently.

Talked with Sage 100 support and Sage 300 support... neither had even as much information as you both provided. *sigh*