I’ve submitted a ticket on this but I was hoping to get feedback from others. We have many 32 Core servers that cannot run any Bes client (we are at 7.2.5.22 currently). The service runs for a few seconds then crashes. These are Xeon 3.4 GHz 16-way Dual Core systems. They are over 2 years old, So I was hoping there would be a fix by now. Has anyone else experienced this problem. Is the problem 16 sockets? or 32 Cores?
We have 4-way Quad Core servers and 4-way Hex Core systems that run fine. These are the only 32-Way servers running windows that use the Bes Client. Anyone else experience this issue?
Yes… We are tracking this issue and it should hopefully be fixed in the next version… The trick is that it is hard to test since we don’t currently have one of these computers… I see we have a debug version available… You should ask your support technician to see if you can use it because it should fix your issue and we can incorporate the change in our next version…
Kent Thomas sent us QNA version 8.0.153.0 and we ran some tests below:
q: number of processors
q: brand id of main processor
q: brand string of main processor
q: extended family of main processor
q: extended model of main processor
q: family name of main processor
q: family of main processor
q: feature mask of main processor
q: model of main processor
q: speed of main processor
q: stepping of main processor
q: type of main processor
q: vendor name of main processor
q: logical processor count
q: physical processor count
q: hyperthreading capable
q: hyperthreading enabled
All came back fine. On the 7.2.5.22 QNA it would crash if I ran the commands twice in the same session. On 8.0.153.0 I had no problems. I will ask support if We can test the debug version or beta 8 version.