Unable to index (Documentindexingtaskschedule running behind server time)

Unable to index (Documentindexingtaskschedule running behind server time)

Please follow the steps below to solve this issue. 


Go to Support link --> SupportCenter Plus application status section --> Scheduled Activities
If the Next scheduled time is greater than the current server time, please restart the application. Check this solves the issue, still issue persists, follow the steps to solve the issue

Please find the schedule id for the 'DocumentIndexingTaskSchedule' process from the above link
1. Stop the application
2. Connect to the database, execute the below queries one by one
delete from INDEXDETAILS;
delete from INDEXDETAILSQUEUE;
delete from task_input where Schedule_id=x;
Replace 'x' with the scheduled id taken from the scheduled activities link
3. Execute indexdata.bat or indexdata.sh from the C:\\ManageEngine\\SupportCenter\\bin 
4. Then start the application.
5. This will solve the issue.
Please refer the below link to connect to the database
https://www.manageengine.com/products/support-center/faq-general.html


Note: 1. Use indexdata.bat --help  to index the data module and year wise..

2. 
change the parameter to true in indexdetails.txt file from  C:\\ManageEngine\\SupportCenter\\applications\\extracted\\AdventNetSupportCenter.eear\\AdventNetServiceDeskWC.ear\\AdventNetServiceDesk.war\\conf-files folder, if you invoke this process in the application running status
Out of Memory during indexing process:
1. Update the JVM parameters to higher values.
2. You can reduce the loop count to 25 or less and then perform the indexing process
update Globalconfig set paramvalue=25 where category='search';

                New to ADManager Plus?

                  New to ADSelfService Plus?

                    • Related Articles

                    • 8121 Index fix jar (contact module corruption)

                      This is compatible with 8121 At times , the contact search is not working and that leads to mail fetching issues also. This fix might work in certain instances. Please check it. However the permanent solution is available from 11.0 version. It is ...
                    • Migration of SCP from one server to another

                      1. Stop the application on the production server. 2. Take a trimmed backup of the application (backup without attachments) if you are using the default PgSQL database. If you are using MSSQL, you can take a SQL backup (.bak). 3. Download and install ...
                    • Steps to fix DocumentIndexing or Search is not working properly or startout.log file is growing too much issue

                      This KB is applicable only for 8121 Builds We came across several cases, where the search is not working properly due to the index file corruption or Indexing thread gets locked in 8.1 series builds. This also leads Mail fetching issue.For which we ...
                    • Trying to start PostgresSQL server failed - While Upgrading

                      Error Trace. Trying to start PostgresSQL server failed java.net.ConnectException: Trying to start PostgresSQL server failed at com.adventnet.db.adapter.postgres.DefaultPostgresDBInitializer.startDBServer(DefaultPostgresDBInitializer.java:177) at ...
                    • How to setup Python on the Server

                      This article explains how to set up the ServiceDesk plus server to run python scripts. 1. The first step is to install python on the application server and you can download it from here. Any version above 3.4.1 should work fine. Start the setup and ...