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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsReportsReportsre-indexing content do not work any more after installing 5.0 reportre-indexing content do not work any more after installing 5.0 report
Previous
 
Next
New Post
2/1/2008 8:34 AM
 

I found out on one of my server that the content re-indexing is not working anymore after the install of Report Module 5.0. The portal is running DNN 4.8.0.

I get the same error message when I click on re-index content in the Host > Search Admin :

/1/2008 2:20:49 PM   Module Load Exception   host     ModuleId: 337; ModuleDefId: 85; FriendlyName ...
ModuleId: 337
ModuleDefId: 85
FriendlyName: Search Admin
ModuleControlSource: Admin/Search/SearchAdmin.ascx
AssemblyVersion: 04.08.00
PortalID: 2
PortalName: Translation Development portal
UserID: 1
UserName: host
ActiveTabID: 29
ActiveTabName: Search Admin
RawURL: /translation/Host/Search Admin/tabid/29/portalid/2/language/en-US/Default.aspx
AbsoluteURL: /translation/Default.aspx
AbsoluteURLReferrer: http://cygnus-2003se/translation/Host/Search%20Admin/tabid/29/portalid/2/language/en-US/Default.aspx
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: af317cd3-ddda-4360-a09c-1dd262ea6202
InnerException: Value cannot be null. Parameter name: format
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.String.Format
StackTrace:

Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Value cannot be null. Parameter name: format ---> System.ArgumentNullException: Value cannot be null. Parameter name: format at System.String.Format(IFormatProvider provider, String format, Object[] args) at System.String.Format(String format, Object[] args) at DotNetNuke.Modules.Reports.Exceptions.ReportsModuleException.get_Message() at System.Exception.ToString() at DotNetNuke.Services.Log.EventLog.ExceptionLogController.AddLog(Exception objException, ExceptionLogType LogType) at DotNetNuke.Services.Exceptions.Exceptions.LogException(Exception exc) at DotNetNuke.Services.Search.ModuleIndexer.GetSearchIndexItems(Int32 PortalID) at DotNetNuke.Services.Search.SearchEngine.GetContent(IndexingProvider Indexer) at DotNetNuke.Services.Search.SearchEngine.IndexContent() at DotNetNuke.Modules.Admin.Search.SearchAdmin.cmdReIndex_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

 

Source:
Server Name: CYGNUS-2003SE

I have spend 12 hours to check where this could come from because I have 2 other hosts which works fine whith the same DNN and Report version. However there is one difference : on this specific host which fails the databaseOwner is not dbo.

If you have any work around that will be great because  I need to publish RSS feeds from this  Host, and that's not possible while the search indexer is out.

 

Thanks for your help.


Bruno Généré
 
New Post
2/2/2008 3:15 AM
 

I've created a bug for this, I'll try to get a work-around going if you need this fixed ASAP. Otherwise, I'll make sure it gets fixed in 5.1

Here's the Bug Report so you can track it if you want: RPT-7025


Andrew Nurse
DotNetNuke Core Team Member and Reports Module Project Lead
Microsoft Certified Professional Developer

 
New Post
2/4/2008 2:58 AM
 

Thanks for that Andrew.

Do you have any idea about 5.1 release date ?

I need to have this portal running by the end of this month, so I have 3 options : wait for 5.1, get a work-around from you or move portal database to a new one with owner DBO.

Option New Database is probably a 5 days work, so any quicker and less risky option is welcome.


Bruno Généré
 
New Post
2/4/2008 3:54 PM
 

5.1 is a ways off unfortunately, I'm aiming for an April-May release though I may be able to do a minor bug-fix release earlier. Since I am a full-time student, I don't have large amounts of time during the Spring and Fall to work on the module (though I may put out a call for some team members soon). As a temporary workaround, if you don't need Search Indexing on the Reports Module itself, you should be able to stop that from happening by changing the SupportedFeatures column in the DesktopModules table (see this thread for details). This SHOULD stop the Search Indexer from indexing the Reports Module, thus avoiding the exception and allowing the other modules to be indexed properly.

If you need the Reports Module indexing features, I'll have to fix that bug to give you a workaround, but I should be able to do that relatively quickly and provide you with a quick patch if you need it urgently.


Andrew Nurse
DotNetNuke Core Team Member and Reports Module Project Lead
Microsoft Certified Professional Developer

 
New Post
2/5/2008 2:49 AM
 

Brilliant !!!

Search is working again and so I have my RSS feed back on other modules. I do not care to have search on reports at this moment.

Thank you very much you saved my time !

 


Bruno Généré
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsReportsReportsre-indexing content do not work any more after installing 5.0 reportre-indexing content do not work any more after installing 5.0 report


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