Speaking of index SERVER, I did not use a lot of myself, but the previous two days to do a search index, I find a lot of information from the Internet, carefully analyzed the Indexing Service, and the design of the ASP program, the first day of the program to run normally, the results the next morning, When I went to work, I found that the ASP program querying the index server was not working, prompting for Server.createrecordset ("nonsequential") error, and then IIS could not parse the ASP file, and I made my own repeated attempts of the day, Including I stopped the Indexing Service, removed the catalog, reinstalled IIS and couldn't recover, and finally I re-made my system with ghost, and it just went back to normal. Then I began to look for more information, carried out more explorations, and finally found the crux of the problem: The catalog cannot be stored in the directory you want to index. Failure to do so will cause IIS to lock the index file to prevent updates, resulting in an infinite index loop, causing IIS and index servers and the system to suffer varying degrees of damage, only to reinstall the system.
below will I in the Index Server and ASP to build a search engine in the process of finding a few points to pay attention to the problems to provide to everyone for reference, discussion;
1, the catalog must be stored in the directory that needs to be indexed, especially the IIS service directory;
2, before using the index server, be sure to save the following IIS settings for future recovery;
3, the Indexing Service needs to use the permissions of the system account, the Indexing Service cannot index the file without this level of permissions;
4, Indexing Service will not be encrypted file index, if the index is later encrypted, will also be deleted by the Indexing Service.
5. When providing Indexing Service, do not perform anti-virus or backup software, because such programs lock files and cause Indexing Service to time out when indexing or updating.
6, Indexing Service in the default state, when the user has operations on the disk, it will be temporarily stopped, you can stop the service, adjust the performance------------You can change this situation immediately, of course, the system resources will be occupied more.
7, in the query to do a good setup, to provide users with a friendly interface, improve the accuracy of the query, reduce the query on the system resource occupancy rate.
I use Index Server is not much, there is the wrong place, I hope you put forward to discuss together.
