We recently added a lot more users, and accordingly, a lot more documents, to one of our applications. In the largest database in the application, there are upwards of 3,000 more documents being received on a daily basis with these new users.
On the past two Mondays (which happens to be the day of the week with the most activity), the error message “Maximum number of concurrently open objects has been exceeded”, was returned while @DbLookup calls were made to another database.
Additionally, yesterday most of our agents which run “After New Mail Has Arrived”, decided to stop running, even though lots of new mail was arriving in their databases. Overnight, those agents started working again.
In reading previous posts on this error message, there doesn’t seem to be a definitive solution to this type of problem. For us, it seems related to intervals where there is a high volume of activity on the servers.
Unfortunately, the server is administered by another vendor, who at the moment is suggesting there may be a problem with our agents. They are also reluctant to tweak server parameters like Max_Sessions and Server_Timeout, because they may adversely affect other things. From what I’ve read, reducing those parameters could conceivably free up these “open objects”.
Our application does perform a lot of @DbLookup calls to a central database for every document that’s created. Perhaps this is contributing to the error? However, we’re hoping that there’s an easier solution than rewriting the application to perform fewer lookups.
Any suggestions? Thanks!