If the problem persists, restore the file from a backup copy.ĥ. At the command prompt, type CHKDSK /F, and then press ENTER.Ĥ. To run CHKDSK, click Start, click Run, type CMD, and then click OK. Check and repair the file system by running CHKDSK. It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.ģ. 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. This situation might be a temporary problem that corrects itself when the program runs again.Ģ. The error value is listed in the Additional Data section.ġ.
UNIPAAS RUNTIME HAS STOPPED WORKING DRIVERS
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. 18007, time stamp: 0x55c4bc8eįaulting application start time: 0x01d1278ebe2d0953įaulting application path: \\fileserver\path\myapp.exeįaulting module path: C:\Windows\SYSTEM32\ntdll.dll 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!įaulting application name: myapp.exe, version: 1., time stamp: 0x5046f3d2įaulting module name: ntdll.dll, version. 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 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įile 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 Will just crash for no reason and leave an error in the event viewer 1000 followed by 1005 (added the details below). Basically we have around 100 - 130 users at one time using our custom application and through out the day the application I have a question about some odd behavior we are seeing using RemoteApp and our application.