System Resource Exceeded

[gabe19]

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.

[ksmith]

Perhaps your application is trying to create multiple simultaneous connections
to access. Access is a single-user desktop database and only accepts 1
connection at a time. Try updating the advanced settings of your datasource:
1) Make sure maintain connections is unchecked
2) Check limit connections and set to 1.

You could also do some maintanence on your Access DB. The access ODBC driver
allows you to optimize the database. Better yet, if it is an old Access file
that you have continued to use try importing it into a new version of Access.

You could also try updating to the latest version of Sequellink 5.4 and its
service pack 11:
[url]http://www.adobe.com/go/e917887[/url]
[url]http://www.adobe.com/go/4378f5a4[/url]

Finally, consider a real DBMS which Access isn't. Over the many years your
application has been running your server and OS have gotten much faster. Also
CFMX is many thousands of times faster than CF3 or CF4. Access may not be up
to the task anymore.

[gabe19]

Thanks for the pointers. I tried each suggestion (other than changing RDBMS) to
no avail. In fact, the change to sequeLink 54 just caused the error to be
consistent rather than intermittent. While that could be good for total system
troubleshooting, it didn't lead me to anything obvious.

I tracked down a few seemingly unrelated posts on the internet concerning this
type of system error which were pointing to text buffer overruns. I increased
the odbc text buffer size, and that seems to have mitigated the issue.

Thanks again for the help.