I am receiving the following error message intermittently,
and have no idea what it might indicate. Can anyone give me an idea
where to look for possible solutions?...
IP Address: 70.61.58.65
Browser: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; WOW64; InfoPath.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Date/Time: Tue Jan 02 08:59:08 EST 2007
HTTP Referer:
Query String: do=browse&SecOpen=1&SecID=138&SubSecID=31813
Template: /default.cfm
Diagnostics: Error Executing Database Query. [Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][ODBC Microsoft Access Driver] System resource exceeded.
The error occurred on line 59.
This application retrieves data from an access database, and has run successfully for many years. The server is a windows 2000 Advanced server running IIS5. The server's resources do no appear to be over utilized in any way. The error will appear intermittently: the same page will come up once, then it won't. Other pages will come up, then the next one won't. There doesn't appear to be a discernable pattern in the failures.
Thanks for any troubleshooting tips or previous experiences with this error message.
IP Address: 70.61.58.65
Browser: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; WOW64; InfoPath.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Date/Time: Tue Jan 02 08:59:08 EST 2007
HTTP Referer:
Query String: do=browse&SecOpen=1&SecID=138&SubSecID=31813
Template: /default.cfm
Diagnostics: Error Executing Database Query. [Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][ODBC Microsoft Access Driver] System resource exceeded.
The error occurred on line 59.
This application retrieves data from an access database, and has run successfully for many years. The server is a windows 2000 Advanced server running IIS5. The server's resources do no appear to be over utilized in any way. The error will appear intermittently: the same page will come up once, then it won't. Other pages will come up, then the next one won't. There doesn't appear to be a discernable pattern in the failures.
Thanks for any troubleshooting tips or previous experiences with this error message.