New
#1
ERP Software Crashes After 2 Hours
Hello everyone-
Our company runs DTR/Aptean TMM at one of our plants for our ERP system, we are on the latest version and Service Pack. Technically Windows 10 is currently unsupported by TMM, but the software installs fine and seems to run well. However, every 2 hours (like clockwork) the app will crash, and log 2 messages in the Event Viewer. The ERP software is hosted on a Windows Server 2003 R2 server, and we don't have these issues on any of our Windows 7 computers (I've only upgraded 2 PC's to Windows 10 and they both have this issue). The P: drive you see mentioned below is a network share on the ERP server. Both systems are running Windows 10 TH2 x64 with quad core processors and 8 GB of RAM (one is a Lenovo desktop, the other is a Hyper-V Virtual Machine).
The errors:
Message 1:
Log Name: Application
Source: Application Error
Date: 12/28/2015 3:04:49 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: xxxx.xxxx.local
Description:
Faulting application name: prowin32.exe, version: 10.1.3.1526, time stamp: 0x4dde63d5
Faulting module name: prow32.dll, version: 10.1.3.1526, time stamp: 0x4dde63c9
Exception code: 0xc0000006
Fault offset: 0x00226610
Faulting process id: 0x17d0
Faulting application start time: 0x01d14188cbf19132
Faulting application path: P:\oe10\bin\prowin32.exe
Faulting module path: P:\oe10\bin\prow32.dll
Report Id: 50960fb9-ced0-492e-93f8-7a6401bc4374
Faulting package full name:
Faulting package-relative application ID:
Message 2:
Log Name: Application
Source: Application Error
Date: 12/28/2015 3:04:49 PM
Event ID: 1005
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: xxxx.xxxx.local
Description:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Progress Client because of this error.
Program: Progress Client
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: C00000C4
Disk type: 0
From the research I've done a lot of people suggested disabling Oplocks on the server. I disabled it on both the Server and the Windows 10 workstations, but it doesn't seem to make a difference. It seems like the software is losing its connection to the network drives, but the drives always show connected. The network drives are mapped via GPO (Windows Server 2008 R2 Domain Functional Level). Has anyone else had similar issues? Any suggestions?
Quote