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...Administration ...Administration ...upgrade to 4.0 now Search not workingupgrade to 4.0 now Search not working
Previous
 
Next
New Post
9/25/2006 8:25 PM
 

Hello everyone- check out my newest dnn installation at http://westlat.sci-isp.net

I upgraded to 4.0 from 3.2 and when i did, the search stopped working.  I set the search up in the skin [SEARCH] and it is not working - it simply defaults back to the homepage.

Does anyone have any idea why this is happening or how to fix?

 
New Post
9/26/2006 12:03 PM
 

I just set up a DNN site on GoDaddy's $3.99 hosting account and most of it is working ok, but search  fails with "A critical error has occurred. Object reference not set to an instance of an object."

 

 


/Dave S
 
New Post
9/27/2006 9:22 AM
 

I'm having an issue with this as well.  Updgraded to 4.3.5 on both development and production servers.  Search fails and returns Object reference not set to an instance of an object.

From LogViewer:

AssemblyVersion: 04.03.05
PortalID: 0
PortalName: XXX
UserID: 1
UserName: host
ActiveTabID: 120
ActiveTabName: Search Results
RawURL: /Default.aspx?tabid=120&Search=welcome
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.XXX.com/Default.aspx?tabid=119
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; Maxthon; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 14f43dc5-36be-4462-b7c8-61ec9da4226a
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Services.Search.SearchDataStore.GetSetting
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Services.Search.SearchDataStore.GetSetting(String txtName) at DotNetNuke.Services.Search.SearchDataStore.GetSearchResults(Int32 PortalID, String Criteria) at DotNetNuke.Modules.SearchResults.SearchResults.BindData() at DotNetNuke.Modules.SearchResults.SearchResults.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name: SKNET82

 

Any ideas?

 
New Post
9/27/2006 1:40 PM
 
DavidWSnow wrote

I just set up a DNN site on GoDaddy's $3.99 hosting account and most of it is working ok, but search  fails with "A critical error has occurred. Object reference not set to an instance of an object."

For those with the "critical error" message, try going to the host tab, search admin, and click on re-index. That fixed my issue on www.modmyspaces.com

As for the first post, I'd start by making sure you have a search results page with the search results module on it.


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
9/27/2006 6:21 PM
 
christoc wrote

For those with the "critical error" message, try going to the host tab, search admin, and click on re-index. That fixed my issue on www.modmyspaces.com



I had the same experience after upgrading to 4.3.5 a few days ago.  Re-indexing fixed the error on my main portal site but for some reason, child portals are still showing that error.

Any ideas?
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...upgrade to 4.0 now Search not workingupgrade to 4.0 now Search not working


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