I have read this with interest as I got the same SQL time out error today when trying to install a module on one of my sites (DNN 5.1.1 version) .. I emailed the supplier of the module to see if they had any idea.. however in the mean time I went to do and upgrade from 5.0.0 to the latest 5.1.4 version on another site i run that's hosted with the same hosting company (site is stand alone and not through a portal in dnn) and i got the following..
Current Assembly Version: 05.01.04
Current Database Version: 05.00.00
Upgrade Status Report
00:00:00.031 - Upgrading to Version: 05.01.04
00:00:01.140 - Executing Script: 05.00.01.SqlDataProvider Error! (see 05.00.01.log for more information)
00:00:56.968 - Executing Script: 05.01.00.SqlDataProvider Error! (see 05.01.00.log for more information)
00:01:52.921 - Executing Script: 05.01.01.SqlDataProvider Error! (see 05.01.01.log for more information)
00:02:31.750 - Executing Script: 05.01.02.SqlDataProvider Error! (see 05.01.02.log for more information)
00:03:07.453 - Executing Script: 05.01.03.SqlDataProvider Error! (see 05.01.03.log for more information)
00:03:39.062 - Executing Script: 05.01.04.SqlDataProvider Error! (see 05.01.04.log for more information)
00:04:24.671 - Executing Application Upgrades: 05.00.01 Success
00:04:26.625 - Executing Application Upgrades: 05.01.00 Success
00:04:52.109 - Executing Application Upgrades: 05.01.01 Success
00:04:52.125 - Executing Application Upgrades: 05.01.02 Success
00:04:52.125 - Executing Application Upgrades: 05.01.03 Success
00:04:58.640 - Executing Application Upgrades: 05.01.04 Success
00:04:58.640 - Cleaning Up Files: 05.00.01 Success
00:04:59.156 - Cleaning Up Files: 05.01.00 Success
00:04:59.250 - Cleaning Up Files: 05.01.01 Success
00:04:59.250 - Cleaning Up Files: 05.01.02 Success
00:04:59.250 - Cleaning Up Files: 05.01.03 Success
00:04:59.250 - Cleaning Up Files: 05.01.04 Success
00:04:59.250 - Updating Config Files: 05.00.01 Success
00:04:59.250 - Updating Config Files: 05.01.00 Success
00:04:59.250 - Updating Config Files: 05.01.01 Success
00:04:59.250 - Updating Config Files: 05.01.02 Success
00:04:59.250 - Updating Config Files: 05.01.03 Success
00:04:59.250 - Updating Config Files: 05.01.04 Success
00:04:59.250 - Performing General Upgrades
00:04:59.390 - Installing Optional Modules:
00:04:59.390 - Installing Package File HTML_Community_05.01.04_Install: Error!
00:05:36.625 - Installing Optional Skins:
00:05:36.625 - Installing Optional Containers:
00:05:36.625 - Installing Optional Languages:
00:05:36.625 - Installing Optional Providers:
00:05:36.625 - Installing Package File AspNetMembershipProvider_05.01.03_Install: Success
00:05:37.171 - Installing Package File CorePermissionProvider_05.01.01_Install: Success
00:05:37.484 - Installing Package File DatabaseLoggingProvider_05.01.01_Install: Success
00:05:37.984 - Installing Package File DNNMembershipProvider_05.01.03_Install: Success
00:05:38.781 - Installing Package File DNNMenuNavigationProvider_05.01.00_Install: Success
00:05:39.593 - Installing Package File DNNTreeNavigationProvider_05.01.00_Install: Success
00:05:40.656 - Installing Package File FckHtmlEditorProvider_02.00.04_Install:
Server Error in '/' Application.
Now looking at the log for the sqldataprovider errors they all come up with the sql time out error:
System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText)
at DotNetNuke.Data.SqlDataProvider.GrantStoredProceduresPermission(String Permission, String LoginOrRole)
if exists (select * from dbo.sysusers where name='vogardnnusr') begin declare @exec nvarchar(2000) declare @name varchar(150) declare sp_cursor cursor for select o.name as name from dbo.sysobjects o where ( OBJECTPROPERTY(o.id, N'IsProcedure') = 1 or OBJECTPROPERTY(o.id, N'IsExtendedProc') = 1 or OBJECTPROPERTY(o.id, N'IsReplProc') = 1 ) and OBJECTPROPERTY(o.id, N'IsMSShipped') = 0 and o.name not like N'#%%' and (left(o.name,len('')) = '' or left(o.name,7) = 'aspnet_') open sp_cursor fetch sp_cursor into @name while @@fetch_status >= 0 begin select @exec = 'grant EXECUTE on ' + @name + ' to [vogardnnusr]' execute (@exec) fetch sp_cursor into @name end deallocate sp_cursor end
I can only assume that this has to do with the way the hosting company has configured his sql server set up as I cannot see any other reason to get the same time out error from two different sites on the same host?
What I need to know now is how to rectify this upgrade failure also..