Hi, I have a problem with my site. Every minute I have the same thing in LOGs: 03/16/2010 11:39:33.53 OWSTIMER.EXE (0x114C) 0x0958 Search Server Common MS Search Administration 90e6 Medium SQL: dbo.proc_MSS_AddConsumer 'shared' 03/16/2010 11:39:33.53 OWSTIMER.EXE (0x114C) 0x0958 Search Server Common MS Search Administration 90gf Medium SQL: dbo.proc_MSS_PropagationGetQueryServers 03/16/2010 11:39:33.54 OWSTIMER.EXE (0x114C) 0x0958 Search Server Common MS Search Administration 8wni High Resuming default catalog with reason 'GPR_PROPAGATION' for application 'SharedServices1'... 03/16/2010 11:39:33.55 OWSTIMER.EXE (0x114C) 0x0958 Search Server Common MS Search Administration 8wnj High Resuming anchor text catalog with reason GPR_PROPAGATION' for application 'SharedServices1'... 03/16/2010 11:39:33.60 mssearch.exe (0x10CC) 0x0FF4 Search Server Common GatherStatus 0 Monitorable Remove crawl 10284 from inprogress queue - File:d:\office\source\search2\search\gather\server\gatherobj.cxx Line:6651 03/16/2010 11:39:33.60 mssearch.exe (0x10CC) 0x12F4 Search Server Common GatherStatus 0 Monitorable Advise status change 4, project AnchorProject, crawl 10284 - File:d:\office\source\search2\search\gather\server\gatherobj.cxx Line:4781 03/16/2010 11:39:33.61 mssearch.exe (0x10CC) 0x0FF4 Search Server Common GatherStatus 0 Monitorable Unlock Queue - File:d:\office\source\search2\search\gather\server\gatherobj.cxx Line:2879 03/16/2010 11:39:33.62 OWSTIMER.EXE (0x114C) 0x0958 Search Server Common MS Search Administration 7hkw Medium Search application '98cc123a-d80e-4828-9254-49b3119fef39': Verify correctness of incremental crawl schedule on content source 'Lokalne witryny programu Office SharePoint Server'. 03/16/2010 11:39:33.62 OWSTIMER.EXE (0x114C) 0x0958 Search Server Common MS Search Administration 7hky Medium Search application '98cc123a-d80e-4828-9254-49b3119fef39': Verify correctness of full crawl schedule on content source 'Lokalne witryny programu Office SharePoint Server'. 03/16/2010 11:39:33.62 OWSTIMER.EXE (0x114C) 0x0958 Search Server Common MS Search Administration 8dvl Medium Search application '98cc123a-d80e-4828-9254-49b3119fef39': Provision start addresses in default content source. 03/16/2010 11:39:33.63 OWSTIMER.EXE (0x114C) 0x0958 Search Server Common MS Search Administration 7hmi High Begin SearchUpgradeProvisioner::ProvisionSearchKeywordInfo. 03/16/2010 11:39:33.63 OWSTIMER.EXE (0x114C) 0x0958 Search Server Common MS Search Administration 7hmj High SearchUpgradeGetKeywordPropertyBag keywordsPropertyBag is null 03/16/2010 11:39:34.55 w3wp.exe (0x0AB0) 0x0778 ULS Logging Unified Logging Service 8wsw High Now terminating ULS (w3wp.exe, Microsoft.Office.Server.Native.dll) 03/16/2010 11:39:34.55 w3wp.exe (0x0AB0) 0x0778 ULS Logging Unified Logging Service 8wsw High Now terminating ULS (w3wp.exe, onetnative.dll) When there problem appears with Search Server, there ULS is restarting. From front side perspective: everything works fine and once o minute page is loading for about 15-20 seconds. I tried to change crawl shaedule settings but with no success. Does anybody know what's wrong whit configuration? Regards, xaze

What is the layout of your farm (server count and roles)? Also, what, if any restrictions, firewalls, etc are there between servers? Any info you can give on the schedules for incremental and full crawls for your farm would help too.Thanks....

Everything is on one server and this is its configuration: Windows 2008 STD on (Intel 2x3GHz, 4GB RAM) AD WSS Search Server Express hMailServer Kaspersky Antivirus - turned off Incremential crawl info: Everyday form 1:00 every 10 min for 24h Full crawl info: Everyday at 5:00PM Regards, xaze

Do you have standalone or web farm configuration?Oleg

This is standalone configuration. I'm wondering why ULS is restarting. I compared logs with another server containg the same system. There is no ifnormation about ULS restarting and it works fine, quite fast. Thanks, xaze

Can you check a server status on Search Administration page?Oleg

Search status: idle Index elements: 2007 Server status: SRV-JST C: 200GB Propagation state: propagation not required Default account for access to content: intranet\jstsystem Proxy server: none Range update status: idle Sheduled range update: automatically planned Ranges requiring update: 0 Search alert status: On Query registration: On xaze

Additionally, I noticed that w3wp.exe process is killed and then it starts again. I think that's the reason why ULS is restarted. But question is what causes IIS process restart. Is this important error? <msgtype>DeleteFile</msgtype><name>c:\program files\microsoft office servers\12.0\data\office server\applications\98cc123a-d80e-4828-9254-49b3119fef39\projects\portal_content\indexer\cifiles\0001000E.00000008.csd</name><HR>0x80070002</HR> - File:d:\office\source\search2\ytrip\common\util\fsutil.cxx Line:260 Before restarting w3wp.pl processes there is following error repeated. Is it could be the main reaseon for problem? An SPRequest object was not disposed before the end of this thread. To avoid wasting system resources, dispose of this object or its parent (such as an SPSite or SPWeb) as soon as you are done using it. This object will now be disposed. Allocation Id: {C07879E7-2A1F-43CD-B7AC-0C32B3FC2F75} To determine where this object was allocated, create a registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\HeapSettings. Then create a new DWORD named SPRequestStackTrace with the value 1 under this key. Thanks, xaze

One time I had the exception like that when the cumulative update was applied unsuccessfully.I think make sense to apply latest updates on your SharePoint and reset indexes.Oleg

My problem is solved! The problem was, that application pool for SharePoint - 80 was set to 100 MB, while it should be set to about 1500MB. After changing this value everything works excellent. Additionally, I added value for HTTP header in ISS for SharePoint - 80: cache-control: max-age=3600, no-check It works fast now. xaze