UD Manager (OpenInsight 32-bit)
At 12 FEB 2023 09:28:31AM Bruce Cameron wrote:
Just installed a fresh copy of UD 5.2 on new Win Server 2019 64bit.
All is well is seems.
However, when I fire up the UD 5.2 manager it opens, displays the "Reading Universal Driver…", then closes itself.
I have on occasion had it stay open and operate normally.
There are no window events logged or other notifications that I can find.
Has anyone else experienced this behavior?
Thanks
At 12 FEB 2023 09:32AM Bruce Cameron wrote:
Correction, there are event logs being written:
Faulting application name: OINSIGHT.exe, version: 9.4.3.0, time stamp: 0x5a31256a
Faulting module name: ntdll.dll, version: 6.2.17763.3887, time stamp: 0xfc38179e
Exception code: 0xc0000005
Fault offset: 0x0003ebf7
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
Followed by….
Fault bucket 1720478383579590251, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: OINSIGHT.exe
P2: 9.4.3.0
P3: 5a31256a
P4: ntdll.dll
P5: 6.2.17763.3887
P6: fc38179e
P7: c0000005
P8: 0003ebf7
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAE0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB00.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAFF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB2F.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OINSIGHT.exe_3fbabb6b31effba16c42ee7ab37724d77952ad2_00000000_1f66be0c
Analysis symbol:
Rechecking for solution: 0
Report Id: b0656928-deb4-4b34-9f56-eca98a9f719c
Report Status: 268435456
Hashed bucket: 5f18fa43252259fdd7e05df970ffee6b
Cab Guid: 0
At 12 FEB 2023 02:51PM Barry Stevens wrote:
Correction, there are event logs being written:
Faulting application name: OINSIGHT.exe, version: 9.4.3.0, time stamp: 0x5a31256a
Faulting module name: ntdll.dll, version: 6.2.17763.3887, time stamp: 0xfc38179e
Exception code: 0xc0000005
Fault offset: 0x0003ebf7
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
Followed by….
Fault bucket 1720478383579590251, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: OINSIGHT.exe
P2: 9.4.3.0
P3: 5a31256a
P4: ntdll.dll
P5: 6.2.17763.3887
P6: fc38179e
P7: c0000005
P8: 0003ebf7
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAE0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB00.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAFF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB2F.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OINSIGHT.exe_3fbabb6b31effba16c42ee7ab37724d77952ad2_00000000_1f66be0c
Analysis symbol:
Rechecking for solution: 0
Report Id: b0656928-deb4-4b34-9f56-eca98a9f719c
Report Status: 268435456
Hashed bucket: 5f18fa43252259fdd7e05df970ffee6b
Cab Guid: 0
Exception code: 0xc0000005I have always seen this as a DEP issue. Change to 'essential windows only'
Cant tell you where the setting is, I always forget and have to google it.
At 12 FEB 2023 02:54PM Barry Stevens wrote:
Correction, there are event logs being written:
Faulting application name: OINSIGHT.exe, version: 9.4.3.0, time stamp: 0x5a31256a
Faulting module name: ntdll.dll, version: 6.2.17763.3887, time stamp: 0xfc38179e
Exception code: 0xc0000005
Fault offset: 0x0003ebf7
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
Followed by….
Fault bucket 1720478383579590251, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: OINSIGHT.exe
P2: 9.4.3.0
P3: 5a31256a
P4: ntdll.dll
P5: 6.2.17763.3887
P6: fc38179e
P7: c0000005
P8: 0003ebf7
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAE0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB00.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAFF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB2F.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OINSIGHT.exe_3fbabb6b31effba16c42ee7ab37724d77952ad2_00000000_1f66be0c
Analysis symbol:
Rechecking for solution: 0
Report Id: b0656928-deb4-4b34-9f56-eca98a9f719c
Report Status: 268435456
Hashed bucket: 5f18fa43252259fdd7e05df970ffee6b
Cab Guid: 0
Exception code: 0xc0000005I have always seen this as a DEP issue. Change to 'essential windows only'
Cant tell you where the setting is, I always forget and have to google it.
At 12 FEB 2023 04:27PM Bruce Cameron wrote:
Hi Barry,
Thanks, that's the first thing I tried. Then rebooted the server and it worked - but only once. Now seeing the same behavior. Splash screen, then the manager window, then the "Reading.." message, then closes itself.
Bruce
At 12 FEB 2023 05:00PM Barry Stevens wrote:
Hi Barry,
Thanks, that's the first thing I tried. Then rebooted the server and it worked - but only once. Now seeing the same behavior. Splash screen, then the manager window, then the "Reading.." message, then closes itself.
Bruce
I assume your OI application run ok, if so, then copy the ntdll.dll from it to the UD Manager's one.
At 13 FEB 2023 09:55AM Bruce Cameron wrote:
Hi Barry,
There is no ntdll.dll in my OI application root or under. or in the C:\Revsoft\Universal Driver 5.2\UD_Manager
I have 1 in c:\windows\system32 (1.90Mb) and 1 in c:\windows\sysWOW64 (1.60Mb)
Any info is much appreciated.
At 13 FEB 2023 02:58PM Barry Stevens wrote:
Hi Barry,
There is no ntdll.dll in my OI application root or under. or in the C:\Revsoft\Universal Driver 5.2\UD_Manager
I have 1 in c:\windows\system32 (1.90Mb) and 1 in c:\windows\sysWOW64 (1.60Mb)
Any info is much appreciated.
Sorry, must have got it mixed up with something else - just back of mind memory.