| Groups | Blog | Home |
sql server full text search : Fulltext Stops (Deadlocks Occurs)
How can I determine if I need to use the SQL Server Fulltext services? This error messages occurs when the CPU is greater than 80% for extended period of time. Usually the error message occurs when the system has a major deadlock and is using all the resources to resolve the deadlock. Please help me resolve this issue. Thank You, Mike Error Messages from Cluster: JobID = 881 KSName = 1838:General_EventLogV1-DBSpecial MC MachineName = GHLDBB01A Object Name = <NT_MachineFolder:GHLDBB01A> EventMsg = 10 NT Events from System - batch 7 LongMsg = Type mm/dd/yyyy hh:mm:ss Source Category Event User MachineName Description Error 4/17/2004 7:34:45 PM ClusSvc (4) 1069 N/A GHLDBB01A Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' failed. Error 4/17/2004 7:34:45 PM Service Control Manager None 7031 N/A GHLDBB01A The Microsoft Search service terminated unexpectedly. It has done this 5 time(s). The following corrective action will be taken in 0 milliseconds: No action. Error 4/17/2004 7:34:46 PM ClusSvc (4) 1069 N/A GHLDBB01A Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' failed. Error 4/17/2004 7:36:39 PM Service Control Manager None 7009 N/A GHLDBB01A Timeout (30000 milliseconds) waiting for the Microsoft Search service to connect. Error 4/17/2004 7:36:49 PM Service Control Manager None 7000 N/A GHLDBB01A The Microsoft Search service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Error 4/17/2004 7:36:50 PM DCOM None 10005 ecmsvc GHLDBB01A DCOM got error '%%%1' attempting to start the service %2 with arguments '%3' in order to run the server: %4 Error 4/17/2004 7:38:23 PM Service Control Manager None 7009 N/A GHLDBB01A Timeout (30000 milliseconds) waiting for the Microsoft Search service to connect. Error 4/17/2004 7:38:32 PM Service Control Manager None 7000 N/A GHLDBB01A The Microsoft Search service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Error 4/17/2004 7:38:38 PM DCOM None 10005 ecmsvc GHLDBB01A DCOM got error '%%%1' attempting to start the service %2 with arguments '%3' in order to run the server: %4 Error 4/17/2004 7:38:46 PM ClusSvc (4) 1069 N/A GHLDBB01A Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' failed.
Mike,
First of all, can I assume that this is a SQL Server 2000 clustered environment? Could you post the full output of SELECT @@version -- as this is helpful in troubleshooting SQL FTS issues. Secondly, could you post any "Microsoft Search" or MssCi source events (warnings & errors) from your server JSQL_OLTP that occurred at or near the time of the below error messages? As well as any Microsoft Search entries in the cluster.log file. Yes, the "Microsoft Search" (mssearch.exe) service and does use up to 90% of CPU usage, for brief periods of time, either during shadow merge or master merge that occurs during either Full or Incremental Populations or at midnight. How long is the "extended period of time" that the CPU is greater than 80%? Does the MSSearch service ever hit 100% CPU usage or does it just peak at 80% and then go down to normal usage levels? Also, do this server have multiple CPU's? If so, then the MSSearch service can be "assigned" or bound to a specific or set of specific CPU's, while SQL Server 2000 can be set to a specific set of CPU's (via sp_configure), such that the MSSearch CPU usage will not affect your SQL Server 2000 processing. Regards, John [quoted text, click to view] "Mike" <anonymous@discussions.microsoft.com> wrote in message news:12c001c42642$0cd095f0$a001280a@phx.gbl... > > How can I determine if I need to use the SQL Server > Fulltext services? This error messages occurs when the > CPU is greater than 80% for extended period of time. > Usually the error message occurs when the system has a > major deadlock and is using all the resources to resolve > the deadlock. > > Please help me resolve this issue. > > Thank You, > > Mike > > > Error Messages from Cluster: > > JobID = 881 > KSName = 1838:General_EventLogV1-DBSpecial > MC MachineName = GHLDBB01A > Object Name = <NT_MachineFolder:GHLDBB01A> > EventMsg = 10 NT Events from System - batch 7 > LongMsg = Type mm/dd/yyyy hh:mm:ss Source > Category Event User MachineName > Description > > Error 4/17/2004 7:34:45 PM ClusSvc > (4) 1069 N/A GHLDBB01A > Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' failed. > > > Error 4/17/2004 7:34:45 PM Service Control Manager > None 7031 N/A GHLDBB01A > The Microsoft Search service terminated unexpectedly. It > has done this 5 time(s). The following corrective action > will be taken in 0 milliseconds: No action. > > > Error 4/17/2004 7:34:46 PM ClusSvc > (4) 1069 N/A GHLDBB01A > Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' failed. > > > Error 4/17/2004 7:36:39 PM Service Control Manager > None 7009 N/A GHLDBB01A > Timeout (30000 milliseconds) waiting for the Microsoft > Search service to connect. > > > Error 4/17/2004 7:36:49 PM Service Control Manager > None 7000 N/A GHLDBB01A > The Microsoft Search service failed to start due to the > following error: > The service did not respond to the start or control > request in a timely fashion. > > > > Error 4/17/2004 7:36:50 PM DCOM > None 10005 ecmsvc GHLDBB01A > DCOM got error '%%%1' attempting to start the service %2 > with arguments '%3' > in order to run the server: > %4 > > > Error 4/17/2004 7:38:23 PM Service Control Manager > None 7009 N/A GHLDBB01A > Timeout (30000 milliseconds) waiting for the Microsoft > Search service to connect. > > > Error 4/17/2004 7:38:32 PM Service Control Manager > None 7000 N/A GHLDBB01A > The Microsoft Search service failed to start due to the > following error: > The service did not respond to the start or control > request in a timely fashion. > > > > Error 4/17/2004 7:38:38 PM DCOM > None 10005 ecmsvc GHLDBB01A > DCOM got error '%%%1' attempting to start the service %2 > with arguments '%3' > in order to run the server: > %4 > > > Error 4/17/2004 7:38:46 PM ClusSvc > (4) 1069 N/A GHLDBB01A > Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' failed. > >
I tried to answer several questions listed below. Thank You, The server CPU can be greater than 90% for 5 - 7 minutes. The server has 8 processors at 2 GHZs. ___________________________________________________________ Event Viewer Errors Cluster resource 'SQL Server Fulltext (VSQL_OLTP)' failed. The Microsoft Search service terminated unexpectedly. It has done this 5 time(s). The following corrective action will be taken in 0 milliseconds: No action. DCOM got error "The service did not respond to the start or control request in a timely fashion. " attempting to start the service mssearch with arguments "" in order to run the server: {C731055A-AC80-11D1-8DF3-00C04FB6EF4F} Timeout (30000 milliseconds) waiting for the Microsoft Search service to connect. ___________________________________________________________ Select @@Version Output: Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3) (1 row(s) affected) [quoted text, click to view] >-----Original Message-----
>Mike, >First of all, can I assume that this is a SQL Server 2000 clustered >environment? Could you post the full output of SELECT @@version -- as this >is helpful in troubleshooting SQL FTS issues. > >Secondly, could you post any "Microsoft Search" or MssCi source events >(warnings & errors) from your server JSQL_OLTP that occurred at or near the >time of the below error messages? As well as any Microsoft Search entries in >the cluster.log file. > >Yes, the "Microsoft Search" (mssearch.exe) service and does use up to 90% of >CPU usage, for brief periods of time, either during shadow merge or master >merge that occurs during either Full or Incremental Populations or at >midnight. How long is the "extended period of time" that the CPU is greater >than 80%? Does the MSSearch service ever hit 100% CPU usage or does it just >peak at 80% and then go down to normal usage levels? > >Also, do this server have multiple CPU's? If so, then the MSSearch service >can be "assigned" or bound to a specific or set of specific CPU's, while SQL >Server 2000 can be set to a specific set of CPU's (via sp_configure), such >that the MSSearch CPU usage will not affect your SQL Server 2000 processing. > >Regards, >John > > > >"Mike" <anonymous@discussions.microsoft.com> wrote in message >news:12c001c42642$0cd095f0$a001280a@phx.gbl... >> >> How can I determine if I need to use the SQL Server >> Fulltext services? This error messages occurs when the >> CPU is greater than 80% for extended period of time. >> Usually the error message occurs when the system has a >> major deadlock and is using all the resources to resolve >> the deadlock. >> >> Please help me resolve this issue. >> >> Thank You, >> >> Mike >> >> >> Error Messages from Cluster: >> >> JobID = 881 >> KSName = 1838:General_EventLogV1-DBSpecial >> MC MachineName = GHLDBB01A >> Object Name = <NT_MachineFolder:GHLDBB01A> >> EventMsg = 10 NT Events from System - batch 7 >> LongMsg = Type mm/dd/yyyy hh:mm:ss Source >> Category Event User MachineName >> Description >> >> Error 4/17/2004 7:34:45 PM ClusSvc >> (4) 1069 N/A GHLDBB01A >> Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' failed. >> >> >> Error 4/17/2004 7:34:45 PM Service Control Manager >> None 7031 N/A GHLDBB01A >> The Microsoft Search service terminated unexpectedly. It >> has done this 5 time(s). The following corrective action >> will be taken in 0 milliseconds: No action. >> >> >> Error 4/17/2004 7:34:46 PM ClusSvc >> (4) 1069 N/A GHLDBB01A >> Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' failed. >> >> >> Error 4/17/2004 7:36:39 PM Service Control Manager >> None 7009 N/A GHLDBB01A >> Timeout (30000 milliseconds) waiting for the Microsoft >> Search service to connect. >> >> >> Error 4/17/2004 7:36:49 PM Service Control Manager >> None 7000 N/A GHLDBB01A >> The Microsoft Search service failed to start due to the >> following error: >> The service did not respond to the start or control >> request in a timely fashion. >> >> >> >> Error 4/17/2004 7:36:50 PM DCOM >> None 10005 ecmsvc GHLDBB01A >> DCOM got error '%%%1' attempting to start the service %2 >> with arguments '%3' >> in order to run the server: >> %4 >> >> >> Error 4/17/2004 7:38:23 PM Service Control Manager >> None 7009 N/A GHLDBB01A >> Timeout (30000 milliseconds) waiting for the Microsoft >> Search service to connect. >> >> >> Error 4/17/2004 7:38:32 PM Service Control Manager >> None 7000 N/A GHLDBB01A >> The Microsoft Search service failed to start due to the >> following error: >> The service did not respond to the start or control >> request in a timely fashion. >> >> >> >> Error 4/17/2004 7:38:38 PM DCOM >> None 10005 ecmsvc GHLDBB01A >> DCOM got error '%%%1' attempting to start the service %2 >> with arguments '%3' >> in order to run the server: >> %4 >> >> >> Error 4/17/2004 7:38:46 PM ClusSvc >> (4) 1069 N/A GHLDBB01A >> Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' failed. >> >> > > >.
You're welcome, Mike,
Relative to DCOM on this server, have you made any changes to the default DCOM configuration? Specifically, confirm that the 'Default Authentication Level' in the DCOMCNFG's Default Properties tab is set to "None" and that the 'Default Impersonation Level' (on the same tab) is set to "Anonymous". Both are the default DCOM settings. Also, I should of been more specific with the event log messages.... The "Microsoft Search" and MssCi are only recorded in the Application event log and not the System log. Please, review the Application event log as well for related messages. Finally, the server's CPU usage of greater than 90% for 5 - 7 minutes, is normal and expected during either the "shadow merge" or "Master Merge" processes that the MSSearch service does to merge new "word lists" into it's file system and then at the end of this process or at midnight (controllable via a registry key). This process occurs during either a Full or Incremental Population. Do you have frequently scheduled SQLServerAgent jobs that execute either a Full or Incremental Population? If so, you may want to either reduce the frequency or checkout the new SQL Server 2000 feature "change tracking" and "update index in background" that will give you near real-time updates of the FT Catalog when the FT-enable table(s) column(s) are updated. Review the SQL Server 2000 BOL for more info on CT and UIiB. Once the "Microsoft Search service terminated unexpectedly" issue is identified and resolved, and if the MSSearch CPU usage is affecting your SQL Server process, I can show you how to set the MSSearch process to one or more of your 8 procs. Regards, John [quoted text, click to view] "Mike" <anonymous@discussions.microsoft.com> wrote in message
news:138a01c4265b$cb6eeb60$a401280a@phx.gbl... > > I tried to answer several questions listed below. > > Thank You, > > > > The server CPU can be greater than 90% for 5 - 7 minutes. > The server has 8 processors at 2 GHZs. > ___________________________________________________________ > Event Viewer Errors > > Cluster resource 'SQL Server Fulltext (VSQL_OLTP)' failed. > > The Microsoft Search service terminated unexpectedly. It > has done this 5 time(s). The following corrective action > will be taken in 0 milliseconds: No action. > > DCOM got error "The service did not respond to the start > or control request in a timely fashion. " attempting to > start the service mssearch with arguments "" in order to > run the server: > {C731055A-AC80-11D1-8DF3-00C04FB6EF4F} > > Timeout (30000 milliseconds) waiting for the Microsoft > Search service to connect. > > ___________________________________________________________ > Select @@Version > > Output: > > Microsoft SQL Server 2000 - 8.00.760 (Intel X86) > Dec 17 2002 14:22:05 > Copyright (c) 1988-2003 Microsoft Corporation > Enterprise Edition on Windows NT 5.0 (Build 2195: > Service Pack 3) > > > (1 row(s) affected) > > > > > > > >-----Original Message----- > >Mike, > >First of all, can I assume that this is a SQL Server 2000 > clustered > >environment? Could you post the full output of SELECT > @@version -- as this > >is helpful in troubleshooting SQL FTS issues. > > > >Secondly, could you post any "Microsoft Search" or MssCi > source events > >(warnings & errors) from your server JSQL_OLTP that > occurred at or near the > >time of the below error messages? As well as any > Microsoft Search entries in > >the cluster.log file. > > > >Yes, the "Microsoft Search" (mssearch.exe) service and > does use up to 90% of > >CPU usage, for brief periods of time, either during > shadow merge or master > >merge that occurs during either Full or Incremental > Populations or at > >midnight. How long is the "extended period of time" that > the CPU is greater > >than 80%? Does the MSSearch service ever hit 100% CPU > usage or does it just > >peak at 80% and then go down to normal usage levels? > > > >Also, do this server have multiple CPU's? If so, then the > MSSearch service > >can be "assigned" or bound to a specific or set of > specific CPU's, while SQL > >Server 2000 can be set to a specific set of CPU's (via > sp_configure), such > >that the MSSearch CPU usage will not affect your SQL > Server 2000 processing. > > > >Regards, > >John > > > > > > > >"Mike" <anonymous@discussions.microsoft.com> wrote in > message > >news:12c001c42642$0cd095f0$a001280a@phx.gbl... > >> > >> How can I determine if I need to use the SQL Server > >> Fulltext services? This error messages occurs when the > >> CPU is greater than 80% for extended period of time. > >> Usually the error message occurs when the system has a > >> major deadlock and is using all the resources to resolve > >> the deadlock. > >> > >> Please help me resolve this issue. > >> > >> Thank You, > >> > >> Mike > >> > >> > >> Error Messages from Cluster: > >> > >> JobID = 881 > >> KSName = 1838:General_EventLogV1-DBSpecial > >> MC MachineName = GHLDBB01A > >> Object Name = <NT_MachineFolder:GHLDBB01A> > >> EventMsg = 10 NT Events from System - batch 7 > >> LongMsg = Type mm/dd/yyyy hh:mm:ss Source > >> Category Event User MachineName > >> Description > >> > >> Error 4/17/2004 7:34:45 PM ClusSvc > >> (4) 1069 N/A GHLDBB01A > >> Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' > failed. > >> > >> > >> Error 4/17/2004 7:34:45 PM Service Control Manager > >> None 7031 N/A GHLDBB01A > >> The Microsoft Search service terminated unexpectedly. > It > >> has done this 5 time(s). The following corrective > action > >> will be taken in 0 milliseconds: No action. > >> > >> > >> Error 4/17/2004 7:34:46 PM ClusSvc > >> (4) 1069 N/A GHLDBB01A > >> Cluster resource 'SQL Server Fulltext (JSQL_OLTP)' > failed. > >> > >> > >> Error 4/17/2004 7:36:39 PM Service Control Manager > >> None 7009 N/A GHLDBB01A > >> Timeout (30000 milliseconds) waiting for the Microsoft > >> Search service to connect. > >> > >> > >> Error 4/17/2004 7:36:49 PM Service Control Manager > >> None 7000 N/A GHLDBB01A > >> The Microsoft Search service failed to start due to the > >> following error: > >> The service did not respond to the start or control > >> request in a timely fashion. > >> > >> > >> > >> Error 4/17/2004 7:36:50 PM DCOM > >> None 10005 ecmsvc GHLDBB01A > >> DCOM got error '%%%1' attempting to start the service %2 > >> with arguments '%3' > >> in order to run the server: > >> %4 > >> > >> > >> Error 4/17/2004 7:38:23 PM Service Control Manager > >> None 7009 N/A GHLDBB01A > >> Timeout (30000 milliseconds) waiting for the Microsoft > >> Search service to connect. > >> > >> > >> Error 4/17/2004 7:38:32 PM Service Control Manager > >> None 7000 N/A GHLDBB01A > >> The Microsoft Search service failed to start due to the > >> following error: > >> The service did not respond to the start or control
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |