Products

Solutions

Learn More

Partners

Community

Blog

About

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...Performance and...Performance and...General Exceptions running wildGeneral Exceptions running wild
Previous
 
Next
New Post
9/30/2016 11:16 AM
 

I have a portal that was upgraded from 6.2 to 8.0.4.  For the most part things seem to be working.  However, the other day I tried to open Host Settings and got a DNN Error "object reference not set ...."  I saw this earlier and fixed it for the Host Extensions page (orphaned skin issue). When I opened the event viewer to see what the problem was for this issue it was flooded with General Exceptions.  I am seeing a ton of these:

AbsoluteURL:

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID:a99025bf-5b9e-40a4-a19d-7f8af8ce8530

AssemblyVersion:

PortalId:-1

UserId:-1

TabId:-1

RawUrl:

Referrer:

UserAgent:

ExceptionHash:JGBBl/XeE72KWRZWvoV1Sg==

Message:Conversion failed when converting the nvarchar value 'Mr' to data type int.

StackTrace:

   at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
   at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
   at System.Data.SqlClient.SqlDataReader.Read()
   at DotNetNuke.Services.Search.UserIndexer.FindModifiedUsers(Int32 portalId, DateTime startDateLocal, IDictionary`2 searchDocuments, IList`1 profileDefinitions, IList`1& indexedUsers, Int32& startUserId)
   at DotNetNuke.Services.Search.UserIndexer.IndexSearchDocuments(Int32 portalId, ScheduleHistoryItem schedule, DateTime startDateLocal, Action`1 indexer)

 

InnerMessage:

InnerStackTrace:


 

Source:.Net SqlClient Data Provider

FileName:

FileLineNumber:0

FileColumnNumber:0

Method:

Server Name: KGISCCPRWEB1

----------------------------------------------

and a bunch of these:

AbsoluteURL:/Portal_803/Default.aspx

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID:36ff8cf5-6e5e-45a4-a794-710173cec0d5

AssemblyVersion:

PortalId:-1

UserId:-1

TabId:-1

RawUrl:

Referrer:

UserAgent:

ExceptionHash:lH+7/efea9nQxuu5aby0og==

Message:IsSystem

StackTrace:

   at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
   at System.Data.SqlClient.SqlDataReader.get_Item(String name)
   at DotNetNuke.Entities.Tabs.TabInfo.Fill(IDataReader dr)
   at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)

 

InnerMessage:

InnerStackTrace:


 

Source:System.Data

FileName:

FileLineNumber:0

FileColumnNumber:0

Method:

Server Name: KGISCCPRWEB1

 

I have tried several things but I have no idea where the problem might be.  Any suggestions?  I have tried the TurboDNN DBConfig and "AdjustDNN..." scripts but they didn't help any although they ran successfully.

 
New Post
9/30/2016 11:58 AM
 

Bryan,

 

the issue seem to be caused by the search indexer, when calling FindModifiedUsers (which calls GetAvailableUsersForIndex stored procedure).

 

For some reason it tries to convert a setting value to a number ("Conversion failed when converting the nvarchar value 'Mr' to data type int") - did you encounter any issues during the upgrade?

 

 

 


Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group   European Network of DotNetNuke Professionals

Speed up your DNN Websites with TurboDNN
 
New Post
9/30/2016 12:33 PM
 

Yes and I assume that is part of the problem.  When I upgraded from 8.0.3 to 8.0.4  I forgot to run the TurboUnSchema script before I attempted the upgrade.  When the upgrade failed, I went back and ran the TurboUnschema and attempted the upgrade again.  Seems like it failed again (can't remember been a couple of days) but when I opened the site everything seemed to be working.  When I tried to look at my host settings yesterday it failed to load the page and that is when I started to look into the issue.

I have backups and will simply roll back and attempt again if needed.  However, I would like to know where the problem is in case it happens again in the future.

For future reference, if the upgrade fails because I forget to run the Unschema script, should I restore the DB from backup, restore the DNN files and then try it again from scratch?

Thanks

 
New Post
9/30/2016 7:37 PM
 
Bryan,
I'd like to provide some background on my scripts: While TurboDNN does most of the Schema adjustments and data corrections as well as improving indexes and improving numerous stored procedures with more stable and better performing code, TurboSchema script binds many functions and views to the schema, in order to add indexes onto the views, so they behave not just functional but as well performance wise like a single table. Once schema binding has been applied to a view or function, the definition of the tables being used cannot be modified without removing the bound objects - that's what TurboUnschema is doing and should be applied prior to any DNN upgrade, allowing DNN upgrade scripts to add, alter or remove columns.
When upgrading from DNN 8.0.3 to 8.0.4, the following scripts are executed: 08.00.04.sqldataprovider and 08.00.04.01.sqldataprovider. The first one is empty (don't ask me, why) and the second contains a lot of code, including a couple of statements adjusting string size of SettingValue column in a couple of tables (which was contained in one of the pull requests, I submitted - and by accident, this single one got accepted). Another statements add a column to files table.
To fix your situation, where you missed to run TurboUnschema upfront:
- Download latest version of my scripts and execute TurboUnschema.sql
- execute /providers/dataproviders/sqldataprovider/08.00.04.01.sqldataprovider script
- run TurboDNN.sql
- run TurboSchema.sql
- restart DNN
- check the results and report it here.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group   European Network of DotNetNuke Professionals

Speed up your DNN Websites with TurboDNN
 
New Post
10/3/2016 9:26 AM
 
Thanks for the information Sebastian.

I restored my DB and file system before I got your last message so I won't be able to run the steps that you have provided.

I NEED to find a way to prevent myself from doing something stupid like forgetting to run the unschema script before running the upgrade. I am planning to handle upgrades differently in the future - pushing code and db to a new directory and database before upgrading - so forgetting will not be a huge deal breaker. I ran the upgrade to 8.0.4 after a couple of weeks of working with 8.0.3 (which was upgraded from 6.2) so this time - when it crashed - it really threw me for a loop.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...General Exceptions running wildGeneral Exceptions running wild


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.
DNN Launch Webinar
REGISTER NOW
DNN Launch Webinar
REGISTER NOW
DNN Launch Webinar
REGISTER NOW