Is anyone having problems with the VFP 6.01.8629 driver?
We installed the debug tool and have narrowed down the
problem to VFP. What are the ramifications of
reinstalling the driver?
What is happening is that when a person comes to any of
the .asp pages that contain calls to a FoxPro database it
cause the application pool to crash. We've broken up the
sites into separate application pools, but still having
problems with "the site failed to respond to a ping
error". The machine is a dual Xeon, with 4GB RAM and is
currently using about 1.4 GB of it. With so many
application pools and then adding the _IISchagent.exe to
monitor the sites is putting a bit of load on the system.
Is there more information that can be found with the crash
agent? This is what the log entrees are currently
reporting:
Event Type: Information
Event Source: IISCrashHangAgent
Event Category: None
Event ID: 10005
Date: 7/21/2004
Time: 1:26:44 PM
User: N/A
Computer: WEB1
Description:
The service was started.
IISCrashHangAgent Settings:
Crash agent only is enabled.
Debug level: 0.
Crash agent settings:
LogLocation: \\?\C:\IISDebugTools\logs\.
MaxLogFiles: 10.
It's not following the MaxLogFiles rules because I have
about 50 of them so far. My IISchagent.ini has the
following lines:
[Global]
DebugLevel=2
[CrashAgent]
Enable=1
MaxLogFiles=20
Thanks for you suggestions!
>> Stay informed about: ADODB connection to FoxPro causing problems