EViews7 not starting up

[EViewsUser11]

I have installed EViews 7 on a Win 2008 R2 64 bit Server with 32 Cores and 64 GB Memory. After clicking on the Icon the splash screen comes up for a few seconds and then disappears.
Is there a log or something to figure out what this app is doing ?

[EViews Jason]

Is EViews still listed in the task manager as a running process or does EViews in fact crash?

If it is crashing try modifying your EViews ini file. Depending on when EViews is crashing, it is possible you may not have one. If one does not exist, it is created on startup.

Replace 'myusername' with the appropriate username but the file can be found here:

C:\Users\myusername\AppData\Roaming\Quantitative Micro Software\EViews\eviews32.ini

In the ini file, by default you will find the line 'pool threads=0'. Change that to 'pool threads=1'. See if this fixes the problem. For your information, this setting determines the maximum threads used for statistical calculations. It is possible, this may be causing the problem.

[EViews Jason]

Actually, regardless if EViews is crashing or not, try making the INI file change.

[EViewsUser11]

Are you sharing some code with Matlab ? I found the problem, EViews7 has a bug which can't deal with 32 cores. I did start eviews with "start /affinity 7fffffff" (disabling one core) and then it comes up and all is working fine. 2 apps in one day that can't deal with modern hardware :O
Either there are some common components that both share or maybe they had the same developers at one time ?

[EViews Gareth]

As Jason mentioned, you can set the number of cores that EViews uses by changing the EViews ini file.

[EViewsUser11]

Well in my case it never reaches till the ini file. So without affinity switch it won't work. Independent of what is written in the .ini

For such a bug, how long does it normally take to get a fix ?

[EViews Gareth]

We usually fix bugs within a few days. Bugs that are more difficult to track down may take a bit longer. We don't have a 32 core machine on hand

Are you saying that changing the ini file didn't work, or are you speculating? Knowing either way helps us identify it.

[EViewsUser11]

I followed your advise, but there was no .ini file. So I created the .ini file with the line you suggested, but it didn't have an influence on the startup behaviour (clearly a crash since in the task manager there was no process left). From my experience today with MatLab R2011a and the line you suggested for the .ini
I figured it would be worth a try with the affinity switch and that did the trick.

So feel there is a tiny piece of very old code that can store 31 as a value for the number of cores, but not 32, so I assume somebody did choose the wrong data type and this comes around today and bites.

If you have a fix, I'm more than happy to test it on our playground.

[EViews Gareth]

Is your profile email address a good one to contact you on?

[EViews Jason]

When you created the EViews32.ini file, the 'pool threads' line must be within the 'options' section. Your Ini file should therefore read

Code: Select all

[Options]
Pool Threads=1


Please try that.

Also, is your server intel based?

[EViewsUser11]

Ok, putting it under [Options] does the trick as well, good as another workaround. The email in my profile is the right one to reach me.

Machine: Intel Xeon X7550 2 GHz (32 Cores)
Memory: 64 GB
OS is Win Server 2008 R2 Enterprise 64bit

Just found out that the trick with *.ini doesn't work for us, since we are using it with RDS on this Server and therefore the
user appdata will only be created when a user is logging on.

[EViews Jason]

Please check your email for testing instructions