R
RandallBaker1970
Guest
We have an application that was written 15 + years ago and has been maintained and used in thousands of computers on every version of the Windows OS from Windows 98/Windows NT through Windows 10/Windows Server 2019. We use it daily on Windows 8, 8.1, 10, Server 2012, 2016 and 2019.
We have customers using this on physical machines as well as virtualized environments including Hyper-V, VMWare, even Virtual Box without any issues. We also use all of these options in our lab.
We have one customer that is using our software on a Dell VxRail Hyper-Converged Infrastructure Appliance as a host for their Windows Server 2019 VM. I don't know of any other customers currently using this platform for their VM hosts and running our software on it. I don't know if this environment is somehow impacting our software or not, but it is one of the large unknown entities so far.
I do want to point out that our software is a suite of about 30 or so C++ and C# .net 4.7 applications, and all of the applications work correctly except for one, and it crashes before we even actually start as one of the first 10-15 instructions is to start a log file in the Public Documents, and we never even reach that point.
The worst part is that out of about 50 systems in our lab, not one is now or has ever had this issue, so we are having a really hard time troubleshooting it.
We have asked them to install a clean Windows Server 2019 installation on their VxRail from the Server 2019 ISO image instead of deploying a premade VM and they get the same crashing issue they experience in the premade VM on the VxRail. Where the Server 2019 VMs we have running under Hyper-V does not experience the crashing issue.
We have taken a look at the Event Viewer for the application crash, and that doesn't really seem to help much, just pointing to a Access Violation, but no real help as to why.
Faulting application name: ViewPoint.exe, version: 6.4.0.20300, time stamp: 0x5f971171
Faulting module name: ViewPoint.exe, version: 6.4.0.20300, time stamp: 0x5f971171
Exception code: 0xc0000005
Fault offset: 0x0000e94e
Faulting process id: 0x72c
Faulting application start time: 0x01d6eac8b34d7ae3
Faulting application path: C:\Program Files (x86)\Maxxess\Axxess Workstation\bin\ViewPoint.exe
Faulting module path: C:\Program Files (x86)\Maxxess\Axxess Workstation\bin\ViewPoint.exe
Report Id: 16f69466-2f35-4b60-8dea-af58046af518
Faulting package full name:
Faulting package-relative application ID:
Any help figuring out what is causing the Access Violation on this one customer's VM would be greatly appreciated.
Continue reading...
We have customers using this on physical machines as well as virtualized environments including Hyper-V, VMWare, even Virtual Box without any issues. We also use all of these options in our lab.
We have one customer that is using our software on a Dell VxRail Hyper-Converged Infrastructure Appliance as a host for their Windows Server 2019 VM. I don't know of any other customers currently using this platform for their VM hosts and running our software on it. I don't know if this environment is somehow impacting our software or not, but it is one of the large unknown entities so far.
I do want to point out that our software is a suite of about 30 or so C++ and C# .net 4.7 applications, and all of the applications work correctly except for one, and it crashes before we even actually start as one of the first 10-15 instructions is to start a log file in the Public Documents, and we never even reach that point.
The worst part is that out of about 50 systems in our lab, not one is now or has ever had this issue, so we are having a really hard time troubleshooting it.
We have asked them to install a clean Windows Server 2019 installation on their VxRail from the Server 2019 ISO image instead of deploying a premade VM and they get the same crashing issue they experience in the premade VM on the VxRail. Where the Server 2019 VMs we have running under Hyper-V does not experience the crashing issue.
We have taken a look at the Event Viewer for the application crash, and that doesn't really seem to help much, just pointing to a Access Violation, but no real help as to why.
Faulting application name: ViewPoint.exe, version: 6.4.0.20300, time stamp: 0x5f971171
Faulting module name: ViewPoint.exe, version: 6.4.0.20300, time stamp: 0x5f971171
Exception code: 0xc0000005
Fault offset: 0x0000e94e
Faulting process id: 0x72c
Faulting application start time: 0x01d6eac8b34d7ae3
Faulting application path: C:\Program Files (x86)\Maxxess\Axxess Workstation\bin\ViewPoint.exe
Faulting module path: C:\Program Files (x86)\Maxxess\Axxess Workstation\bin\ViewPoint.exe
Report Id: 16f69466-2f35-4b60-8dea-af58046af518
Faulting package full name:
Faulting package-relative application ID:
Any help figuring out what is causing the Access Violation on this one customer's VM would be greatly appreciated.
Continue reading...