Look familiar? My logs are full of clntfile.exe errors, have been for years, and now that I support numerous businesses running TAM, looks like I wasn't alone. A number of years ago I went on a crusade digging up all these TAM related errors in my log and tried to get answers from Applied as to why they are there and what can be done to reduce the frequency of such apparent application crashes. I got absolutely nowhere.
Additional Error details:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Time: 1:17:45 PM
Faulting application clntfile.exe, version 0.0.0.0, faulting module msvbvm60.dll, version 188.8.131.52, fault address 0x00020d87.
I'd be the first to admit, clntfile isn't the only application crashing on these boxes, but nothing does it with as much frequency. Applications crash, as sure as the sun will set, but nothing needs to crash this often. The other thing is, this behaviour has transcended version after version.
It's not only clntfile though, homebase.exe and letter32.exe are also common figures in this 3 act play.
Perhaps I'm alone here, or perhaps I desire clean logs a little too much, but I just find it somewhat unacceptable to run software with a 9-dot-something version that has the same annoying, all-to-common hiccups as it did in 7-dot-something.
At the very least, I would like to know what is at the center of these issues - well I mean beyond the frequent mention of msvbvm60.dll - which I will take a stab at - is Microsoft Visual Basic Virtual Machine? Doesn't anyone code in C++ anymore? I won't even get started on wowexec or ntvdm...
Event Type: Information
Event Source: DrWatson
Event Category: None
Event ID: 4097
Time: 1:17:45 PM
The application, H:\WINTAM\clntfile.exe, generated an application error The error occurred on 02/25/2010 @ 13:17:45.934 The exception generated was c0000005 at address 73590D87 (MSVBVM60!_vbaStrComp)