Products

Solutions

Learn More

Partners

Community

Blog

About

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 ...Error in Scheduled Search Indexing (I think)Error in Scheduled Search Indexing (I think)
Previous
 
Next
New Post
11/28/2014 6:08 PM
 
there seem to be an issue with GetAvailableUsersForIndexing stored procedure.
One of the columns seem to be Null instead of a valid Date.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/29/2014 9:15 AM
 
Sebastian,

In looking at the stored procedure, it seems to be calling from the Users table for dates, and looking at the Users table, several users have NULL for the Last Modified On Date (186 users). Could that be the issue? These are all old users (been around since 2009) and even their Created on Date is NULL (this site has been around for years, upgraded from version 3.x at some point in the distant past, I upgraded it to 5.4.4 in August of 2010...

-----
Cheers
Dave
 
New Post
11/30/2014 4:53 AM
 
Dave, that could be the issue, I'd update the dates to non-null values, e.g.run the following statement in Host > SQL:
UPDATE {databaseOwner}[{objectQualifer}Users] SET CreatedOnDate = GetDate() WHERE CreatedOnDate Is Null

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/30/2014 10:09 AM
Accepted Answer 
Sebastian Leupold wrote:
Dave, that could be the issue, I'd update the dates to non-null values, e.g.run the following statement in Host > SQL:
UPDATE {databaseOwner}[{objectQualifer}Users] SET CreatedOnDate = GetDate() WHERE CreatedOnDate Is Null

 Sebastian,

Could you have meant changing the LastModifiedOn Date rather than the CreatedOnDate?  Checking the stored procedure, LastModifiedOnDate is being called:

                 ValidUsers AS
                  (
                                      SELECT UserId FROM ( SELECT   UserId, ROW_NUMBER() OVER(ORDER BY UserId ASC) AS rownumber
                         FROM ( SELECT DISTINCT
                                            ( u.UserID )
                                  FROM      dbo.[Users] u
                                            INNER JOIN dbo.[UserPortals] up ON up.UserId = u.UserID
                                            INNER JOIN dbo.[vw_Profile] p ON p.UserID = u.UserID
                                            INNER JOIN dbo.[ProfilePropertyDefinition] pd ON pd.PropertyDefinitionID = p.PropertyDefinitionID AND pd.Visible = 1 AND pd.PortalID = @PortalId
                                            INNER JOIN ValidDataType dt ON dt.EntryID = pd.DataType
                                  WHERE     (up.PortalId = @PortalId OR up.PortalId IS NULL)
                                            AND (u.LastModifiedOnDate > @StartDate OR (p.LastUpdatedDate IS NOT NULL AND (p.LastUpdatedDate > @StartDate OR pd.LastModifiedOnDate > @StartDate)))
                                            AND ((p.PropertyValue IS NOT NULL AND p.PropertyValue <> '''') OR p.LastUpdatedDate IS NULL OR p.LastUpdatedDate > @StartDate)
                                ) AS T WHERE UserID > @startUserId) AS T
                                WHERE rownumber <= @numberOfUsers
                     )

And in the Schedule History for the Search indexer, I was seeing this:

 Search: Site Crawler Starting. Content change start time 11/30/2014 6:40 AM
  Tabs Indexed: 0
  Modules (Metadata) Indexed: 0
  Modules (Content) Indexed: 30782
  Users Indexed: 5
  Deleted Objects: 0
Total Items Indexed: 30787
Indexing Successful

Looking at the Users Table, User #6 had a valid LastModifiedOnDate, while User 7 did not. 

So with that in mind, I changed the SQL script for LastModifiedOnDate from CreatedOnDate and ran the script.  Looking at the users table in SQL Management, everything was updated nicely.  I waited for about 15 minutes and then I checked the logs, and no errors!  Looking at the search index schedule history and I see:

Search: Site Crawler Starting. Content change start time 11/30/2014 6:48 AM
  Tabs Indexed: 0
  Modules (Metadata) Indexed: 0
  Modules (Content) Indexed: 30782
  Users Indexed: 1722
  Deleted Objects: 0
Total Items Indexed: 32504
Indexing Successful

1722 users indexed instead of 5, although the first job after the 1722 users indexed actually indexed 5 users (which freaked me out for a second), however checking the event log shows no errors and the subsequent index job indexed 4 users.

Thanks so much for all of your help, I could not have done this without you!


-----
Cheers
Dave
 
New Post
11/30/2014 7:20 PM
 
Dave, sorry, I meant the column being used in the procedure, which might be Null

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Error in Scheduled Search Indexing (I think)Error in Scheduled Search Indexing (I think)


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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out