every day, the first accessed pages return a error, and together with the Error Message we get a System Log Entry:Event Type:ErrorEvent Source:Windows SharePoint Services 3Event Category:Runtime Event ID:6610Date:14.07.2009Time:10:00:34User:N/AComputer:SharePoint01Description:(DE) Der sichere Modus konnte nicht erfolgreich gestartet werden. Der Thread wurde abgebrochen.(US) Critical Safe mode did not start successfully. Thread was being aborted. If you refresh the Page by pressing F5 no other failures will be displayed within the next ~24Hours and the System willrun without any (known) problems. So what's the problem? We have only one Web Front End together with the SSP and a own SQL Server. All works fine, just except this error message which will be displayed every day. Its not a ciritcal Problem at all really but itdoesnt look very good for those pioneers which are the first on the day.btw. here the last 27 seconds before the Failure appears - 12 HIVE LOG:07/20/2009 08:26:00.77 OWSTIMER.EXE (0x2C14) 0x2E78 SharePoint Portal Server User Profiles 8zzy Medium Aborting sweepsynch for guid instance be960c07-234c-4ee0-bd39-6eec1126195b due to null or non-online content database 07/20/2009 08:26:00.77 OWSTIMER.EXE (0x2C14) 0x2954 SharePoint Portal Server User Profiles 8zzy Medium Aborting sweepsynch for guid instance d3478813-e2af-41d7-abae-3734fb08195e due to null or non-online content database 07/20/2009 08:26:09.86 OWSTIMER.EXE (0x2C14) 0x2BD0 Excel Services Excel Services Administration 8tqi Medium ExcelServerSharedWebApplication.Synchronize: Starting synchronize for instance of Excel Services in SSP 'SSPTest'. 07/20/2009 08:26:09.86 OWSTIMER.EXE (0x2C14) 0x2BD0 Excel Services Excel Services Administration 8tqj Medium ExcelServerSharedWebApplication.Synchronize: Successfully synchronized instance of Excel Services in SSP 'SSPTest'. 07/20/2009 08:26:18.44 mssdmn.exe (0x252C) 0x2C38 SharePoint Portal Server Business Data 79bv High Initiating BDC Cache Invalidation Check in AppDomain 'DefaultDomain' 07/20/2009 08:26:18.44 mssdmn.exe (0x252C) 0x2C38 SharePoint Portal Server Business Data 79bx High Completed BDC Cache Invalidation Check in AppDomain 'DefaultDomain' 07/20/2009 08:26:20.80 OWSTIMER.EXE (0x2C14) 0x2DCC Windows SharePoint Services Topology 0 Medium Adding OurDomain\mosssspservice to local group 2. 07/20/2009 08:26:20.80 OWSTIMER.EXE (0x2C14) 0x2DCC Windows SharePoint Services Topology 0 Medium Adding OurDomain\mosssspservice to local group 0. 07/20/2009 08:26:20.89 OWSTIMER.EXE (0x2C14) 0x2DCC Windows SharePoint Services Topology 0 Medium Adding OurDomain\mosssspservice to local group 2. 07/20/2009 08:26:20.91 OWSTIMER.EXE (0x2C14) 0x2DCC Windows SharePoint Services Topology 0 Medium Adding OurDomain\mosssspservice to local group 0. 07/20/2009 08:26:21.02 OWSTIMER.EXE (0x2C14) 0x2DCC Search Server Common MS Search Administration 90gf Medium SQL: dbo.proc_MSS_PropagationGetQueryServers 07/20/2009 08:26:21.05 OWSTIMER.EXE (0x2C14) 0x2DCC Search Server Common MS Search Administration 8wni High Resuming default catalog with reason 'GPR_PROPAGATION' for application 'SSPTest'... 07/20/2009 08:26:21.05 OWSTIMER.EXE (0x2C14) 0x2DCC Search Server Common MS Search Administration 8wnj High Resuming anchor text catalog with reason GPR_PROPAGATION' for application 'SSPTest'... 07/20/2009 08:26:21.07 OWSTIMER.EXE (0x2C14) 0x2DCC Search Server Common MS Search Administration 9e4t High Successfully resumed catalog with reason 'GPR_PROPAGATION' for application 'SSPTest'. 07/20/2009 08:26:21.10 OWSTIMER.EXE (0x2C14) 0x2DCC Search Server Common MS Search Administration 8dvl Medium Search application 'ac2f251d-a6ef-4525-b2d0-9d442c75fa0b': Provision start addresses in default content source. 07/20/2009 08:26:21.11 OWSTIMER.EXE (0x2C14) 0x2DCC Search Server Common MS Search Administration 7hmi High Begin SearchUpgradeProvisioner::ProvisionSearchKeywordInfo. 07/20/2009 08:26:21.11 OWSTIMER.EXE (0x2C14) 0x2DCC Search Server Common MS Search Administration 7hmj High SearchUpgradeGetKeywordPropertyBag keywordsPropertyBag is null 07/20/2009 08:26:21.14 OWSTIMER.EXE (0x2C14) 0x2DCC Windows SharePoint Services Topology 0 Medium Adding OurDomain\mosssspservice to local group 2. 07/20/2009 08:26:21.14 OWSTIMER.EXE (0x2C14) 0x2DCC Windows SharePoint Services Topology 0 Medium Adding OurDomain\mosssspservice to local group 0. 07/20/2009 08:26:23.77 OWSTIMER.EXE (0x2C14) 0x2FE8 SharePoint Portal Server SSO 8inc Medium In SSOService::Synch(), sso database conn string: 07/20/2009 08:26:27.11 w3wp.exe (0x2BD4) 0x0F5C Windows SharePoint Services Runtime 6610 Critical Safe mode did not start successfully. Thread was being aborted.

I've found a couple of sites which are solved the Problem with their ownConfiguration:http://www.eventid.net/display.asp?eventid=6610&eventno=9897&source=Windows%20SharePoint%20Services%203&phase=1--> describes the 6610 problem in context with: if you have two or more WebFrontEnds which are installed on different DriveLetters.--> doesnt solve my Problem because we have only one WebFrontEnd...

I'll take a few punts at this - as I doubt your going to get an answer saying "do this and its fixed" I would point my finger at the lines showing " Aborting sweepsynch for guid instance XXX due to null or non-online content database " and guess there is an issue with your DB, or more specifically reaching your DB as MOSS sees it as offline. 6610 is a fairly generic error as it occurs in MOSS, Exchange, SQL etc. and usually these common errors can be a nightmare to identify- but focussing on SQL rather than MOSS there could be a lot of causes such as this one: http://support.microsoft.com/default.aspx/kb/941105 Perhaps you have a network glitch between your MOSS and SQL, like someone has set SQL to wake on LAN - and its not awake when the first request is made - total guess that mind you - but you get the idea! Regards John Timney (MVP)

I don't it is an 'old' post but I have a similar problem with different variation...it happens on my MOSS app server.... Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Runtime Event ID: 6610 Date: 19/04/2010 Time: 9:29:16 AM User: N/A Computer: PEBDAP62 Description: Safe mode did not start successfully. Thread was being aborted. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ======================= that's all very well but it does not say WHICH control is causing the problem...can anyone give me a hint? Thanks