Hello,

Trying to upgrade to 5.6.1 from 4.9.5 and I'm getting the following error whilst the 05.01.00 Application Upgrades are executing:
<LogProperties>
  <LogProperty>
    <PropertyName>AssemblyVersion</PropertyName>
    <PropertyValue>5.6.1</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>PortalID</PropertyName>
    <PropertyValue>-1</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>PortalName</PropertyName>
    <PropertyValue />
  </LogProperty>
  <LogProperty>
    <PropertyName>UserID</PropertyName>
    <PropertyValue>-1</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>UserName</PropertyName>
    <PropertyValue />
  </LogProperty>
  <LogProperty>
    <PropertyName>ActiveTabID</PropertyName>
    <PropertyValue>-1</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>ActiveTabName</PropertyName>
    <PropertyValue />
  </LogProperty>
  <LogProperty>
    <PropertyName>RawURL</PropertyName>
    <PropertyValue>/Install/install.aspx</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>AbsoluteURL</PropertyName>
    <PropertyValue>/Install/install.aspx</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>AbsoluteURLReferrer</PropertyName>
    <PropertyValue />
  </LogProperty>
  <LogProperty>
    <PropertyName>UserAgent</PropertyName>
    <PropertyValue>Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>DefaultDataProvider</PropertyName>
    <PropertyValue>DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>ExceptionGUID</PropertyName>
    <PropertyValue>b98fee6c-5d60-4688-899a-6c5054d02f92</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>InnerException</PropertyName>
    <PropertyValue>Thread was being aborted.</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>FileName</PropertyName>
    <PropertyValue />
  </LogProperty>
  <LogProperty>
    <PropertyName>FileLineNumber</PropertyName>
    <PropertyValue>0</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>FileColumnNumber</PropertyName>
    <PropertyValue>0</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>Method</PropertyName>
    <PropertyValue>N/A - Reflection Permission required</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>StackTrace</PropertyName>
    <PropertyValue />
  </LogProperty>
  <LogProperty>
    <PropertyName>Message</PropertyName>
    <PropertyValue>System.Threading.ThreadAbortException: Thread was being aborted.     at SNIReadSync(SNI_Conn* , SNI_Packet** , Int32 )     at SNINativeMethodWrapper.SNIReadSync(SafeHandle pConn, IntPtr&amp; packet, Int32 timeout)     at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()     at System.Data.SqlClient.TdsParserStateObject.ReadByte()     at System.Data.SqlClient.TdsParser.GetTokenLength(Byte token, TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParser.GetDataLength(SqlMetaDataPriv colmeta, TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParser.ProcessColumnHeader(SqlMetaDataPriv col, TdsParserStateObject stateObj, Boolean&amp; isNull)     at System.Data.SqlClient.SqlDataReader.ReadColumnHeader(Int32 i)     at System.Data.SqlClient.SqlDataReader.ReadColumn(Int32 i, Boolean setTimeout)     at System.Data.SqlClient.SqlDataReader.GetValueInternal(Int32 i)     at System.Data.SqlClient.SqlDataReader.GetValue(Int32 i)     at DotNetNuke.Entities.BaseEntityInfo.FillInternal(IDataReader dr)     at DotNetNuke.Security.Permissions.PermissionInfo.FillInternal(IDataReader dr)     at DotNetNuke.Security.Permissions.PermissionInfoBase.FillInternal(IDataReader dr)     at DotNetNuke.Security.Permissions.TabPermissionInfo.Fill(IDataReader dr)     at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)     at DotNetNuke.Common.Utilities.CBO.CreateObjectFromReader(Type objType, IDataReader dr, Boolean closeReader)     at DotNetNuke.Common.Utilities.CBO.FillObject[TObject](IDataReader dr, Boolean closeReader)     at DotNetNuke.Security.Permissions.PermissionProvider.GetTabPermissionsCallBack(CacheItemArgs cacheItemArgs)</PropertyValue>
  </LogProperty>
  <LogProperty>
    <PropertyName>Source</PropertyName>
    <PropertyValue />
  </LogProperty>
</LogProperties>

The eventlog now has 2090 rows, the previous four messages to this in the eventlog were to do with language settings (enableURLLanguage, EnableBrowserLanguage) followed by upgrade to Net 3.5, then app shutdown (change in app level config).

The upgrade process can be quite slow (00.05.00 app upgrades took about 2.5 minutes); before starting the upgrade process I have cleared eventlog and sitelog tables, I have ensured that EN-US is enabled in the portal, I have removed XML module temporarily, the dbms is SQL 2008, database is set to compatibility level 100, and the user is dbo.

So, any pointers as to what this errors means would be gratefully accepted ;)

Many thanks

Barry

According to upgrade test performed by DNN QA, upgrades from 4.9.5 to latest version should perform without issues, but due to the variety of use cases for DNN web sites, there are a number of upgrade issues reported in the forums. According to Westa, you should always upgrade modules first before upgrading the core - and in any case, start with a restorable backup!!!

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Hey Barry, While in theory it is possible to upgrade in a single jump there are a whole lot of parameters that can never fully be tested - and the things that happen on a client server can sometimes lead to the occasional weirdness. Thats the reason why some of the steps are a help - the 5.4.4 gets you up into the 5.x world before some of the major structural changes that occurred in 5.5.x and can lead to a smoother transition. Note one of the common issues has to do with updates to the telerik modules - which caught up some of my client sites. Westa