Windows 7 and Windows server 2008 (OpenInsight 32-bit Specific)
At 13 JAN 2011 10:28:33PM B.J. J Ray wrote:
Hi all.
We have been having problems with running oinsight8 on Server 2008, We have been able to get around this by tweaking the "Data Execution Prevention" DEP, however this requires that the Server be restarted, which is not always good as people are often using it.
We have also had some problems with oinsight crashing when closing (and then only half closes) in windows 7.
Has anyone had any similar problems? Or any ideas on what we could do to prevent these problems?
Thanks in advance
B.J. Ray
At 13 JAN 2011 11:20PM Ray Chan wrote:
Hi BJ
…by tweaking the "Data Execution Prevention" DEP…
What do you mean by tweaking DEP? You should only need to do this one-time?
Also more info on your environment would be helpful, E.G., which networking product are you using. Can we assume that you are using Windows 7 Professional?
Others may jump in.
Ray Chan
At 14 JAN 2011 04:52PM Jared Bratu wrote:
OpenInsight 9 is DEP compatible and I would encourage you to look at the upgrade. Most systems administrators frown on having to disable DEP. The issue with DEP exists in all prior versions of OpenInsight. The work around is to disable DEP.
Regarding the crash, does the OENGINE.EXE or OINSIGHT.EXE process remain in the task manager process list or do you get a windows generated program fault message. If so, what are the details and what module does the fault occur in?
At 26 JAN 2011 11:21PM B.J. J Ray wrote:
Thanks for your response,
We have a lot of clients, the Windows 7 could be professional or Personal, I would lean towards professional.
When I say Tweak the DEP, we add the OINSIGHT.exe and OENGINE.exe into the exceptions list.
It is the OINSIGHT.exe that remains in the process list, sometimes the OENGINE.exe, and if used the Form Designer, - seems to depend on the environment.
The industry we support is sort of government funded, they've just gotten a grant for hardware, not including software (except OS and office), OINSIGHT 9 is too expensive and not an option.
At 27 JAN 2011 01:25PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
See this thread.
World leaders in all things RevSoft
At 14 MAR 2011 11:16PM B.J. J Ray wrote:
I'm not authorized to view that thread.
At 23 MAR 2011 09:01AM Jared Bratu wrote:
Try disabling DEP completely. There have been sporadic reports of adding OI to the exclusions list but it is recommended that it be disabled.
From a command prompt that you started "as administrator" try this command:
bcdedit.exe /set {current} nx AlwaysOff
Does that resolve the hung process?
At 23 MAR 2011 09:13AM Jared Bratu wrote:
The article is on the premium Works support section of the website. If you do not have a Works account you can upgrade your current login by purchasing a Works developer support account or your regional VAR may be able to assist you further.