Quick Search still doesn't work after minor release
Problem reported by Emanuele Tomasi - 10/24/2015 at 5:38 AM
I installed (perfectly without problems) the minor release that was supposed to solve the bug of the quick-search,
initially seems to be ok, but analyzing better, I see that with the quick search I can find only tickets that have an
opening date less than 30 days, if I try to find a ticket that has more than 31 days (and it exists!) don't find
Someone can help me? Because its a serious problem for our organization.
Thanks a lot!

3 Replies

Reply to Thread
Emanuele Tomasi Replied
I tried to do this

select count(*) as KBsLeft from st_kbArticles where IsIndexed = 0;
select count(*) as TicketsLeft from st_Tickets where IsIndexed = 0;
select count(*) as TicketCommentsLeft from st_TicketComments where IsIndexed = 0;
select count(*) as ChatsLeft from st_Chats where IsIndexed = 0;
select count(*) as ChatCommentsLeft from st_ChatComments where IsIndexed = 0;
select count(*) as CallLogsLeft from st_CallLogs where IsIndexed = 0;
select count(*) as TasksLeft from st_Tasks where IsIndexed = 0;
select count(*) as TaskCommentsLeft from st_TaskComments where IsIndexed = 0;
select count(*) as ThreadsLeft from st_Threads where IsIndexed = 0;

truncate table st_SearchTokenStats;
truncate table st_SearchTokensInTickets;
truncate table st_SearchTokensInKBArticles;
truncate table st_SearchTokensInChats;
truncate table st_SearchTokensInCallLogs;
truncate table st_SearchTokensInTasks;
truncate table st_SearchTokensInThreads;
delete from st_SearchTokens;
update st_Chats set isindexed = 0;
update st_ChatComments set IsIndexed = 0;
update st_KbArticles set IsIndexed = 0;
update st_Tickets set IsIndexed = 0;
update st_TicketComments set IsIndexed = 0;
update st_CallLogs set IsIndexed = 0;
update st_Tasks set IsIndexed = 0;
update st_TaskComments set IsIndexed = 0;
update st_Threads set IsIndexed = 0;

-> i see 98119 ticketleft
-> and 36921 ticketcommentleft

But return me this error :

(0 row(s) affected)

(7 row(s) affected)

(0 row(s) affected)

(3 row(s) affected)
Msg 512, Level 16, State 1, Procedure UPD_Object, Line 8
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
The statement has been terminated.

Employee Replied
Employee Post
I tested this locally and was able to find tickets with idle times > 36 days. Hmmm... Does this happen on all computers? Try clearing your cache, or changing browsers? There could be a search value stuck in your cache from old advanced searches possibly... If that does not help and this is critical i would recommend contacting our support so that we may take a closer look at your install and get this fixed for you. 
Emanuele Tomasi Replied

I tried with all browser, cleaning cache, but on all pc of our users that use it, the quick search has this problem.

Now i write to the support.


Reply to Thread