I get the impression it is eating user counts as well. :(

We've seen this with different (auto-posting) scheduled tasks, but have not tried the search index feature yet.
One tip: don't include more than one task per schedule. Combining a module posting with the DTR always gave us problems.

Thanks for the input Kevin.

The build search index is the only thing set up in the task scheduler in all instances.

Can't really say if it is a bug or something in the way it was set up since in all cases I am the one who set it up for the client.

Hadn't run across it sooner because I hadn't been paying attention to the fact that my start and stop dates were on the same day. Ooops. Didn't notice until a client was wondering why some newer customers were not showing up in the search.

Hey Tom,

I'm having someone review this here at R&D. If there is any info you can provide can you please send it to me?

Thanks
Elliott

Sage 100 Advanced 2017.1

Windows Server 2008 R2

Set up in the task scheduler:

The activity log is showing the buildindex - Beginning job BUILDINDEX().

  Buildindex - Beginning task Build Search Index

  Buildindex - the task is complete

  Buildindex - The job is completed

As best as I can tell, the build index is actually occurring..

No error messages.

Just discovered this new clue.  I haven't seen this on any of my client's servers,  but when I looked at my server.   There are multiple pop up windows  that say "Sage 100 -  Missing selection table for column $."

When I close the windows I get another window for a second that says

Processing Task Schedule Log and a progress bar that then closes.

After closing all these windows the hung sessions are disappearing from the master console,  so they appear to be related.

I just went to look at the Library Master Task Scheduler Log and the "Missing selection table for column $" is popping up.  Then eventually it prints the log (although only showing the tasks for this morning).

Let me know if there is anything else you might want.

Hi Tom,

That message is coming up because of an error when it tries to print the activity log at the end of the job. Do you have any previously saved report settings for the activity log report?

Check SY_ReportSelection for:

Module: SYS
CompanyId: nnnnnnnnn
ReportID: SY_ActivityLogReport_ui

If you do have a saved setting maybe the record in there is corrupt.

E

The activity log has parameters or saved settings? It just runs the moment you click the menu task.

There is nothing in SY_ReportSelection for it.

Today I discovered article 75776 regarding having a default printer setup. Unfortunately that doesn't seem to be the solution.

I've also noticed that if the server is not logged in you don't see the previously mentioned error messages when you login in. If the server is logged in you get the popup error messages.

Problem continues to exist after installing 2017 PU 2.

Tom, not the activity log itself, there is an activity log report. But, I'm guessing that if you haven't seen it then you don't have any saved settings for it.