All,

I'm working on a project and have been trying import products, but I am getting timeout message after it runs for about 2 minutes.  The files are approximately ~ 6MB in size (15,000+ products) and importing the products into the catalook database.  I'm running a Win 2003 box with SQL 2005 Express with DNN 4.5.3.  I've googled everything I could possibly think of for solving timeout messages and checked on catalooks forum and on this forum for similar issues.  Here are the things that I did:

1. Changed httpruntimes in web.config to this ==> <httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="1000000" requestLengthDiskThreshold="1000000" />
2. Changed timeout timer from default to 300s in IIS
3. Added max connections to db in web.config in connection strings ==> <add name="SiteSqlServer" connectionString="Data Source=xxxxx;Initial Catalog=xxxx;User ID=xxxxxxx;Password=xxxxxxx;Max Pool Size=20;Pooling=True;" providerName="System.Data.SqlClient" />
4. Edited the import query in Store Admin --> Store Settings to bare minimum to speed up the import process (item code, description, price, catimport1ID)
5. Shut down all other websites from using SQL

I'm about out of ideas as far as keeping the DNN framework intact.  Are there any other additional tweaks that I could do to work around this?  If you know of any, I would greatly appreciate any help or am willing to share ideas.

Below is a message from the event viewer:

AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)at System.Data.SqlClient.SqlConnection.Open()at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues)at DotNetNuke.Services.Scheduling.DNNScheduling.SqlDataProvider.GetSchedule(String Server)at DotNetNuke.Services.Scheduling.DNNScheduling.SchedulingController.GetSchedule(String Server)at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.LoadQueueFromTimer()at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.Start()
Source:

Thanks in advance,

-E