I have the following setup:

Report: v5.5.0
DNN: 6.2.9

I have several Reports modules throughout my site for customers to retrieve information. Many of them are based on using the @UserID SQL Token. The modules work great, but the problem I am finding is that every time the system kicks off it's Search Indexing routine, every single Reports module using those SQL based tokens crash, leaving a error in the LOG. How can I stop these errors from being generated? Is there a way I can exclude these modules from being indexed, they really should be excluded as the data changes based on which user is viewing it.

-Ben

I am assuming the only way to do that is to manually update the records in the DesktopModules table using SQL?

Would the following statement be correct?

UPDATE DNN_DesktopModules
 SET SupportedFeatures = 1
 WHERE FriendlyName = 'Reports'

- Ben

Mark,

The SQL code listed below is the only way.

UPDATE DesktopModules
    SET SupportedFeatures = 1
    WHERE FriendlyName = 'Reports'

I have found that the Reports Modules completely IGNORES any of the exposed settings available that is support to disable indexing. So if you disable indexing on the module level or the page level, doesn't matter, the Reports Module still indexes. The only option is to turn off the supported feature of indexing for the entire Reports Module installation by using the SQL above. This in essence tells DNN that the Reports module does not support indexing, and so it is ignored.

I figured that since data displayed in the Reports Module is something that is dynamically generated...it really should never be indexed. So I thought it was logical to just shut indexing down for all Report Modules.