Hi all,
I have a question about some odd behavior we are seeing using RemoteApp and our application. Basically we have around 100 - 130 users at one time using our custom application and through out the day the application
will just crash for no reason and leave an error in the event viewer 1000 followed by 1005 (added the details below). We have 2 RD session host and its the same error on either one what usually fixes the problem is disconnecting the users that are using their
file server share to the application (we use multiple shares with the customers name to the application on a single file server so \\fileserver\customer1\files\app.exe \\fileserver\customer2\files\app.exe) So the question I have seems more like an issue
with multiple users accessing the same files eventually crashes the application and I read on this one site something about Opportunistic locking Opportunistic Locking and
Read Caching Can someone recommend how I could troubleshoot an issue like this to see why we are having these crashes? Any help is greatly appreciated!
1000 Error
Faulting application name: myapp.exe, version: 1.9.1.1043, time stamp: 0x5046f3d2
Faulting module name: ntdll.dll, version: 6.3.9600.18007, time stamp: 0x55c4bc8e
Exception code: 0xc0000006
Fault offset: 0x0006d2d7
Faulting process id: 0x2e0c
Faulting application start time: 0x01d1278ebe2d0953
Faulting application path: \\fileserver\path\myapp.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 0257147e-93b2-11e5-943e-0050569e0b27
Faulting package full name:
Faulting package-relative application ID:
1005 Error
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
uniPaaS runtime because of this error.
Program: uniPaaS runtime
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