OI 9.4 closing unexpectedly (OpenInsight 64-bit)
At 15 NOV 2022 09:47:07AM Karl Pozmann wrote:
I migrated a client from Windows Server 2012 R2 to Windows 11 Pro as a file server. Using the LH.DLL dated 7/26/2012 2:30pm which I believe is version 4. Everything seemed to work well initially until accounting tried to do some processing and that is where OI will close unexpectedly. The accounting piece uses files in a separate directory, ACCTNG for what it's worth and yes there are indexes. I did find one index that was corrupt and deleted it but the problem persists. The 2012 server is still up and I went back on that machine and the programs still work fine. This past weekend I went as far as creating a new copy of the app on the old server and migrating the data from the new server directory by directory and verifying each time a directory moved that the programs still worked. In the end I had a copy on the old server with the new data that was working so I moved that back to the new Windows 11 Pro machine and the problem persisted. I even deleted the revparam file prior to that experiment hoping that would help which it did not. Also, need to point out the code works fine on the Windows 11 Pro server - just not on the workstations. Have run clientsetup.exe a few times now on the workstations which hasn't helped.
The workstations use shortcuts to oinsight.exe with mapped drives.
And yes, I verified the app still works on the old server from a workstation.
Finally, just want to point out again that this appears to be limited to the parts of the code that use the ACCTNG folder data tables. After hours I may try to delete the indexes on that volume and see if that helps.
At 15 NOV 2022 10:05AM Andrew McAuley wrote:
What's in the Windows event log?
World leaders in all things RevSoft
At 15 NOV 2022 11:31AM Karl Pozmann wrote:
Recorded when the OI window closed
Faulting application name: OINSIGHT.exe, version: 9.4.0.0, time stamp: 0x51ad1331
Faulting module name: KERNELBASE.dll, version: 6.2.22000.1219, time stamp: 0x554c45b0
Exception code: 0xc0000005
Fault offset: 0x00150a9e
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Faulting package full name: %14
Faulting package-relative application ID: %15
At 15 NOV 2022 11:33AM Andrew McAuley wrote:
That normally indicates a memory error of some sort. I'd be tempted to run a profile log and see if a routine has gone recursive. Failing that it might be an old RCL4.DLL and DEP?
World leaders in all things RevSoft
At 15 NOV 2022 11:45AM Karl Pozmann wrote:
Thanks Andrew - forgive my ignorance but how would I run a profile log? I'll probably have to wait until after hours in any event.
At 15 NOV 2022 11:49AM Andrew McAuley wrote:
In the OI subdir create a blank text file called oeprofile.log. When you start OI (which will run a LOT slower) it will add all calls to oeprofile_processId.log. The last entry in the log will be where OI terminated. The latest OI Beta makes this a lot easier.
World leaders in all things RevSoft
At 15 NOV 2022 11:54AM Karl Pozmann wrote:
Got it. I've been considering upgrading them to 10 thinking it might work better.
Thanks again
At 15 NOV 2022 12:22PM Karl Pozmann wrote:
Nice feature! Here are the last entries which doesn't tell me much
SI.MFS 48765 0
GL_PERIOD 48765GL_PERIOD 48765 0SI.MFS 48765RTP57 48765RTP57A 48765RTP57A 48765 0RTP57 48765 0SI.MFS 48765 0GL_PERIOD 48765GL_PERIOD 48765 0SI.MFS 48765RTP57 48765RTP57A 48765RTP57A 48765 0RTP57 48765 0SI.MFS 48765 0GL_PERIOD 48765GL_PERIOD 48765 0RTP57 48765RTP57A 48765RTP57A 48765 0RTP57 48765 0SI.MFS 48765RTP57 48765RTP57A 48765RTP57A 48781 16RTP57 48781 16SI.MFS 48781 16RTP57 48781RTP57A 48781
At 16 NOV 2022 09:40AM Karl Pozmann wrote:
So I removed the indexes in ACCTNG yesterday after hours and it worked on a workstation. This morning, now that more users are logged on, it is once again failing.
At 19 NOV 2022 03:53PM Barry Stevens wrote:
So I removed the indexes in ACCTNG yesterday after hours and it worked on a workstation. This morning, now that more users are logged on, it is once again failing.
This looks like DEP:- Exception code: 0xc0000005
Log on to the server.
Open the Control Panel.
Click System and Security > System > Advanced System Settings.
On the Advanced tab, next to the Performance heading, click Settings.
Click the Data Execution Prevention tab.
Select Turn on DEP for essential Windows programs and services only.
At 19 NOV 2022 04:04PM Barry Stevens wrote:
Nice feature! Here are the last entries which doesn't tell me much
SI.MFS 48765 0
GL_PERIOD 48765GL_PERIOD 48765 0SI.MFS 48765RTP57 48765RTP57A 48765RTP57A 48765 0RTP57 48765 0SI.MFS 48765 0GL_PERIOD 48765GL_PERIOD 48765 0SI.MFS 48765RTP57 48765RTP57A 48765RTP57A 48765 0RTP57 48765 0SI.MFS 48765 0GL_PERIOD 48765GL_PERIOD 48765 0RTP57 48765RTP57A 48765RTP57A 48765 0RTP57 48765 0SI.MFS 48765RTP57 48765RTP57A 48765RTP57A 48781 16RTP57 48781 16SI.MFS 48781 16RTP57 48781RTP57A 48781</QUOTE>RTP57(x) is LH Filing system - so do a LH verify on ALL tables (OI & yours)