Application Error OINSIGHT.EXE (OpenInsight 32-Bit)
At 16 JUN 2005 01:12:14PM Warren Auyong wrote:
OI v7.1 (runtime and development)
Win XP Pro workstation
On a couple of workstations whenever the user closes OI they get an Application Error: "The instruction at "0x5ce423ea" referenced memory at "0x02cb3958". The memory could not be "read".
I tried this with both the MU runtime (250 users) and the development versions of OI v7.1
All other XP pro and Win2K pro workstation exit OI without the error message.
I'm suspecting a rights issue, but don't know where to look. Has anybody encountered this too?
At 20 JUL 2005 01:11AM Warren Auyong wrote:
Bump
Still not solved. Tried signing on with NT Admin access, error still occurs
At 20 JUL 2005 06:00PM Richard Bright wrote:
If this is a OS / network environment issue, you might care to detail that environment. Presumably NT server (SP?) in domain context but no active directory. Users loged in as Workgroup or Domain users? Sorry if pedantic but if it's a rights, drive share etc issue some info might help.
At 22 JUL 2005 12:57AM Warren Auyong wrote:
All XP Pro, same patch level, same model HP/Compaq workstations. Win2003 Server, LH Service 2.1
All users are in same domain, workgroup, and user groups. Tried login as domain administrator on failing workstations and still got error message.
I went through local and domain policies item by item between a non-failing workstation and a failing station and could see no obvious difference (which doesn't mean anything since the Windows admin tools are pretty piss poor).
At 22 JUL 2005 03:53AM support@sprezzatura.com wrote:
Asking the obvious - you have checked Oinsight.ini for the dreaded reporter in side tool bar list?
support@sprezzatura.com
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 22 JUL 2005 12:19PM Warren Auyong wrote:
There normally is no OINSIGHT.INI as normal users do not have write access to the Windows directory. When I gave them write access, the INI was created but still got the error.
At 22 JUL 2005 03:02PM support@sprezzatura.com wrote:
Well the system has to default to something - perhaps the default is the problem default. Can you enable writing the ini to test?
support@sprezzatura.com
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 22 JUL 2005 03:36PM Warren Auyong wrote:
The workstations that do not give the error message users do not have write access to the Window dir either. One of the first things I checked.
At 25 OCT 2005 06:57PM Warren Auyong wrote:
Bump on this one. It turns out when we register a Windows Script (WSC) that we use to run merges to documents we get this error.
The workstations with that were not getting the error message did not have the script registered (and the users didn't say anything until today that the couldn't print the documents).
As a test we unregistered the script. Error went away. We call the script via OLE on a form.
Any ideas?