Just in case anyone ever runs into this issue...
We have some automated jobs that use CoreFTP and one particular job was writing a log file to a directory after it was finished. Cleanup was not done on this directory and files built up to 26,000+ in number. When CoreFTP would try and write to this directory, it would throw an unhandled exception. CoreFTP would still finish its processing but a bunch of windows showing the visual studio just-in-time debugger would pop up on the console and eventually would shut the server down. Clearing the files out of the directory fixed the issue for me. If you ever see the following information in the coredump.log, then take a look at all of the tasks (automated or not) and make sure they aren't writing to a directory that has a bunch of files in it.
coreftp build #1823 (LE), caused an Access Violation (0xc0000005)
in module coreftp.exe at 001b:00440aee.
Exception in Exception - CThDirs.
Error occurred at 12/30/2014 12:54:48.
c:\Program Files\CoreFTP\coreftp.exe, run by XXXXXX.
Operating system: Windows 2003 Server (5.2.3790).
1 processor(s), type 586.
45% memory in use.
2048 MBytes physical memory.
1119 MBytes physical memory free.
2667 MBytes paging file.
1717 MBytes paging file free.
2048 MBytes user address space.
2004 MBytes user address space free.
Write to location 015d0d60 caused an access violation.
An unhandled win32 exception occurred in coreftp.exe.
-
- Posts: 2
- Joined: Tue Dec 30, 2014 8:00 pm