too many client tasks?!

You can read more about the IIS 6 application recycle and web garden here: http://msdn.microsoft.com/library/default.asp?url=/library/e n-us/cpguide/html/cpconperformanceapplicationpoolsettings.as p

If they do isolate the pool, Web gardens should be disabled for your application pool and worker processes should be set to 1. That should fix the issue for you.

And let us know how it works after the changes are made for you!

Edited by Techno Geek

Is this a problem of being on a server that's too busy?

We don't know. It is possible.

How do we use/add a DSN? Do we do it or does the host?

If the host provides a control panel, then you might be able to setup the ODBC Datasource. If not, then the host can setup the DSN and point it to /fpdb/shop.mdb (make sure that you setup a username and password on there).

It sounds like it's just another connection method... doesn't SalesCart already have ODBC conection scripting? If the server is saying there are too many tasks, how is that going to solve the problem?

Out of the box it will use the DSN-less connection but you can switch the a DSN. With the DSN you would be using the system resources and that could help the issue.

One other possiblity is to ask the host to Isolate your website in the application pool and disable the session recycle and the web garden. That should help the issue.


Edited by Techno Geek

This is a combination of many things:

1. Server hardware
2. Server OS
3. Number of concurrent connections made to the database
4. How many other websites using the drivers

DSN Defined:

Short for Data Source Name. Data Source Name provides connectivity to a database through an ODBC driver. The DSN contains database name, directory, database driver, UserID, password, and other information. Once you create a DSN for a particular database, you can use the DSN in an application to call information from the database.

There are three types of DSNs:
(1) System DSN -- can be used by anyone who has access to the machine. DSN info is stored in the registry.

(2) User DSN -- created for a specific user. Also stored in the registry.

(3) File DSN -- DSN info is stored in a text file with .DSN extension.

DSN is often used by Active Server Pages (ASP) and Visual Basic programs when a query to a database is necessary to retrieve information.

There is also what is known as a "DSN-less connection." Instead of using a DSN to connect to a database, the developer specifies the necessary information right in the application. With a DSN-less connection the developer is free to use connection standards other than ODBC, such as OLE DB.

I recommended that you try to use a DSN. You other alternative it to use a SQL database.

That code is already there so you can tell your host to chill out and not try to blame the software...

Try switching to a System DSN and see if that helps.

Yep, this is a common issue amongst the Windows 2003 customers. Here is one MS Article: http://support.microsoft.com/default.aspx?scid=kb;en-us;1548 69

We do close the connections on a number of pages. For example on receipt2.asp you'll see it:

<%     Set SimpleAdo = Nothing      Set RS = Nothing      Session.Abandon %>

You can try using a System DSN, though that would end up giving you the same results. I don't think switching to MySQL would work, at least not yet and I'm sure the code would have to change so the syntax is compatible with MySQL.