Hi,

I just upgraded from 4.9.2 to 5.2.3 and it says it is successful during the upgrade.  But after clicking some pages, my site just goes down.  After restarting IIS, my site is ok again and this seems to happen randomly.

This is the environment where I set up the DNN upgrade.
Server: Microsoft Windows Server 2003 Enterpise Edition SP2
IIS: IIS6
Sql Server: Sql Server 2005
.Net Framework: 3.5 sp1


====================GENERAL EXCEPTION=========================================================================
AssemblyVersion: 5.2.3
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 3d294f35-34ef-4c68-9efd-9b38abe776a7
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: 0
FileColumnNumber: 0
Method: System.Data.ProviderBase.DbConnectionFactory.GetConnection
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.Data.SqlDataProvider.GetPortals(String CultureCode) at DotNetNuke.Entities.Portals.PortalController.GetPortals() at DotNetNuke.Services.ModuleCache.PurgeModuleCache.DoWork()
Source:
Server Name: WHUKVPS8304

====================SCHEDULER EVENT FAILURE===============================================================================
THREAD ID: 1
TYPE: DotNetNuke.Services.ModuleCache.PurgeModuleCache
EXCEPTION: 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.
RESCHEDULED FOR: 5/18/2010 9:57:58 AM
SOURCE: STARTED_FROM_TIMER
ACTIVE THREADS: 1
FREE THREADS: 0
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 1
IN QUEUE: 4
Server Name: WHUKVPS8304

======================SCHEDULER EXCEPTION===========================================================

AssemblyVersion: 5.2.3
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 655e5ed8-cb0d-4e23-878e-42128d1a4b97
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: 0
FileColumnNumber: 0
Method: System.Data.ProviderBase.DbConnectionFactory.GetConnection
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.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Services.Scheduling.DNNScheduling.SqlDataProvider.UpdateScheduleHistory(Int32 ScheduleHistoryID, DateTime EndDate, Boolean Succeeded, String LogNotes, DateTime NextStart) at DotNetNuke.Services.Scheduling.DNNScheduling.SchedulingController.UpdateScheduleHistory(ScheduleHistoryItem objScheduleHistoryItem) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.UpdateScheduleHistory(ScheduleHistoryItem objScheduleHistoryItem)
Source:
Server Name: WHUKVPS8304

Does anyone have a clue?

Another side question: Installing DNN 5.2.3 in IIS6 should'nt cause any problems right?  I just want to confirm though.

Thanks,
Mysteria