There was a problem loading the comments.

Will Report Runner Run On Windows X Operating System?

Support Portal  »  Knowledgebase  »  Viewing Article


Q: Will Report Runner Run On Windows X Operating System?

A: To answer this question, we need to answer based on the version of our software that you're using. We will give a short answer first, then give a long answer as to why.

2016 Users: 2013 (previously 2011 and 2012 and 2013) was written from-the-ground-up to run on Windows 7 and later operating systems. It also runs very well on XP. So, 2016 runs on XP, Vista, Windows 7, Windows 8, Server 2003, Server 2008, Server 2012, Server 2016, or Windows 10 (and ANY future ".Net" enabled Windows OS).

Legacy 10.9, 11, 2008 Users: These will run OK on XP, Server 2003. We do not support the legacy software on later operating systems. You must upgrade to 2013. 2013 will run anything that 10.9, 11, and 2008 will run just fine, with very, very, very few exceptions. With that in mind, as of January 1st, 2013, we have increased the renewal costs for 10.9, 11, and 2008 users who require a legacy LIC file.

Legacy 8.5 Users: This version will only run on XP and Server 2003. It is technically possible to get this software running on later OS's, but it requires disabling all of the built-in security the later OS's implemented and were designed for. And from a Jeff-Net support standpoint, we do not support using 8.5 on any OS other than XP and Server 2003. If you have reasons for staying on 8.5, then you need to stay on XP or Server 2003.


Q: What about 64-bit or virtual machines?

A: You will need to install 2013. Note, for 64-bit machines, you will still need to create a 32-bit DSN, because the Crystal runtime engine only supports 32-bit DSNs (a 64-bit engine is in the works). 32-bit DSNs are created by using the ODBC administrator found in the Window\SysWow64 folder, not the default ODBC administrator on the 64-bit OS. The default ODBC administrator on a 64-bit OS creates 64-bit DSNs.


Q: Why isn't 8.5 supported on later OS's?

A: Our software depends on the Crystal runtime engine(s) to process your Crystal Reports templates (and the engine comes directly from SAP/Business Objects - the manufacturer of Crystal Reports). The 8.5 Crystal runtime engine was never designed to run on operating systems past XP. Why? Because the Crystal runtime engine installs it's files to the Windows\System32 directory, and that's a big no-no now-a-days in software deployment. And with the later OS's (after XP and Server 2003), it's such a no-no, that they, by default, copy any System32 files to a virtual System32, not the "real" System32 directory (and our 8.5 software only works if it's in the "real" System32 directory). The part of the newer operating systems that forces this use of the virtual System32 directory is called UAC (User Account Control). UAC can technically be disabled system wide to get our software to run, but it is not recommended, and it opens your machine up to be taken over by "bad" software (ie. viruses).

So, if you are dependant on 8.5 of our software, do NOT upgrade your machines to later OS's. Stay on XP or Server 2003.


Microsoft's explanation of UAC:

Share via

Related Articles

© Support @ Jeff-Net