Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrading 5.01.04 to 5.02.03 - Timeout Expired ErrorUpgrading 5.01.04 to 5.02.03 - Timeout Expired Error
Previous
 
Next
New Post
3/24/2010 11:53 AM
 

While upgrading I got the following errors:
Upgrading DotNetNuke
Current Assembly Version: 05.02.03
Current Database Version: 05.01.04


Upgrade Status Report
00:00:00.046 - Upgrading to Version: 05.02.03
00:00:00.578 -   Executing Script: 05.02.00.SqlDataProvider Error! (see 05.02.00.log for more information)
00:01:11.861 -   Executing Script: 05.02.01.SqlDataProvider Error! (see 05.02.01.log for more information)
00:01:45.425 -   Executing Script: 05.02.02.SqlDataProvider Error! (see 05.02.02.log for more information)
00:02:20.395 -   Executing Script: 05.02.03.SqlDataProvider Error! (see 05.02.03.log for more information)

00:02:52.068 -   Executing Application Upgrades: 05.02.00 Success
00:03:03.005 -   Executing Application Upgrades: 05.02.01 Success
00:03:03.396 -   Executing Application Upgrades: 05.02.02 Success
00:03:03.396 -   Executing Application Upgrades: 05.02.03 Success
00:03:03.396 -   Cleaning Up Files: 05.02.00 Success
00:03:03.412 -   Cleaning Up Files: 05.02.01 Success
00:03:03.412 -   Cleaning Up Files: 05.02.02 Success
00:03:03.412 -   Cleaning Up Files: 05.02.03 Success
00:03:03.412 -   Updating Config Files: 05.02.00 Success
00:03:03.443 -   Updating Config Files: 05.02.01 Success
00:03:03.458 -   Updating Config Files: 05.02.02 Success
00:03:03.458 -   Updating Config Files: 05.02.03 Success
00:03:03.458 - Performing General Upgrades
00:03:03.724 - Installing Optional Modules:
00:03:03.740 -   Installing Package File HTML_Community_05.02.00_Install:  Success
00:03:32.272 - Installing Optional Skins:
00:03:32.288 - Installing Optional Containers:
00:03:32.288 - Installing Optional Languages:
00:03:32.288 - Installing Optional Providers:
00:03:32.303 -   Installing Package File AspNetMembershipProvider_05.02.00_Install:  Success
00:03:32.616 -   Installing Package File CorePermissionProvider_05.01.01_Install:  Success
00:03:32.725 -   Installing Package File DatabaseLoggingProvider_05.01.01_Install:  Success
00:03:32.850 -   Installing Package File DNNMembershipProvider_05.01.03_Install:  Success
00:03:32.959 -   Installing Package File DNNMenuNavigationProvider_05.01.00_Install:  Success
00:03:33.194 -   Installing Package File DNNTreeNavigationProvider_05.01.00_Install:  Success
00:03:33.319 -   Installing Package File FckHtmlEditorProvider_02.00.04_Install:  Success
00:03:36.647 -   Installing Package File FileBasedCachingProvider_05.01.03_Install:  Success
00:03:36.881 -   Installing Package File FileModuleCachingProvider_05.02.01_Install:  Success
00:03:37.210 -   Installing Package File MemoryModuleCachingProvider_05.02.01_Install:  Success
00:03:37.413 -   Installing Package File SchedulingProvider_05.02.01_Install:  Success
00:03:37.647 -   Installing Package File SearchIndexProvider_05.01.00_Install:  Success
00:03:37.756 -   Installing Package File SearchProvider_05.01.01_Install:  Success
00:03:37.850 -   Installing Package File SolpartMenuNavigationProvider_05.01.00_Install:  Success
00:03:38.069 - Installing Optional AuthSystems:
00:03:38.131 -   Installing Package File LiveID_01.00.01_Install:  Success
00:03:38.413 -   Installing Package File OpenID_02.00.00_Install:  Success
00:03:38.616 - Installing Optional Packages:
Upgrade Complete


I looked at the log files in question and they all have the same content:

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='XYZ_user')  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 [XYZ_user]'        execute (@exec)        fetch sp_cursor into @name       end     deallocate sp_cursor  end

 

The site seems to be working fine but I can I make sure it is ok?

Thanks

 
New Post
3/25/2010 1:56 AM
 
You probably should try to rerun the SQL script that failed. I believe this issue was resolved in the recent 5.3.1 release (it was actually fixed in 5.3.0 which was released and pulled shortly there after)

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
3/25/2010 4:41 AM
 

you may rerun latest scripts in ascending order, starting with /providers/dataproviders/sqldataprovider/05.02.00sqldataprovider file.

To avoid timeouts on upgrades, I suggest streamlining the database first:  

  • make sure, database transaction log is truncated by frequent backups
  • truncate eventlog, schedule history and maybe even search tables.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/25/2010 11:04 AM
 
I'd suggest you roll back to your backup of the original version and try using 5.3.1 - the 5.2.3 build had a bug that caused sql timeouts in some cases. This was resolved for 5.3.0/5.3.1. Alternatively you can use 5.2.3 but please consider following the advice at http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/2504/Workaround-for-some-installations-seeing-sql-timeouts-when-upgrading-or-installing-modules.aspx .

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/25/2010 2:29 PM
 

[To avoid timeouts on upgrades, I suggest streamlining the database first:  

  • make sure, database transaction log is truncated by frequent backups
  • truncate eventlog, schedule history and maybe even search tables.]

Sebastian, can you give me more details on how to truncate eventlog, schedule history and maybe even search tables?

Thanks,

Eric

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrading 5.01.04 to 5.02.03 - Timeout Expired ErrorUpgrading 5.01.04 to 5.02.03 - Timeout Expired Error


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out