Running Jet Essentials on terminal server. We are moving to a new terminal server.
== Old terminal server ==
OS: Windows Server 2008 x64
CPU: Intel Xeon X3440 @ 2.5GHz
Memory: 30GB
7200 RPM harddisks
Jet Essentials 2013 update 1 14.1.14133.0
Microsoft Office 2007
== New terminal server ==
OS: Windows Server 2012 R2 x64
CPU: Intel Xeon E5-2630 v3 @ 2.4GHz
Memory: 32GB
SSD's instead of harddisks
Jet Essentials 2015 15.1.15224.0
Microsoft Office 2013
We're using Navision 4.0 SP3.
Running a report on the old terminal server takes 20 minutes. Running the same report on the new terminal server takes very long time. After running for more than an hour I cancelled it.
Disk access on the new server is faster. Speed of the network on the new server is faster.
I've done some research:
Office 2007 + JetReports 2013 = OK
Office 2007 + JetReports 2015 = OK
Office 2010 + JetReports 2013 = Not OK
Office 2010 + JetReports 2015 = Not OK
Office 2013 + JetReports 2013 = Not OK
Office 2013 + JetReports 2015 = Not OK
Date
Votes
1 comment
-
Jet Reports Historic Posts Hello -
While there are some things that can make later versions of Excel run slower than previous versions (e.g., running a report with the Advanced Application setting 'Preserve Conditional Formatting in Excel 2010 or later'), this may require some expertise to examine.
My best suggestion on this (especially if [a] this issue is occurring with more than one report and you still have the older environment up and running) would be:
1) Run a report (one that's as small as possible but still exhibits the issue) on the Server 2008 environment - with Jet Logging enabled (this feature is on the "Logging" tab of the Jet Essentials Application Settings).
2) Run the same report on the Server 2012 environment - again, with Logging enabled.
3) Contact Jet Reports Technical Support (support.jetreports.com), describing the issue and letting them know that you've got the log files (*if* the files are small enough, you can just send them).
Jet's Technical staff should be able to compare the log files to see what's driving the issue.
P.S., be sure to turn Logging off… for performance and disk space reasons, it's not something you want to leave turned on.
Please sign in to leave a comment.