Hello-
Normally our mssearch.exe CPU is less than 5% even at peak times, and
falls to 0 at night. But for the last few days mssearch.exe CPU usage
remains close to 25% even when all the catalogs are idle and search
queries are very infrequent.
This happened a few months ago, and was fixed only by restarting
mssearch.exe. This time I'd like to discover what is causing the
problem. How can I figure out what mssearch.exe is doing?
SQL Server 2000 sp4 on Windows 2003 Server sp1, 4-processor, in an
active-active cluster, 3.5GB memory. 6 tables all with "Update Index in
background" option, each in their own catalog. The largest is 417MB
from 350k rows, the rest are much smaller.
Thanks for your help!
-Steve
www.vin.com
You can trace any SQL related activities of the MS Search service by running
SQL Profiler.
Perhaps - provided you're using task manager - what you see is the MS Search
service indexing your file system.
ML
http://milambda.blogspot.com/
|||Those are good suggestions, so thanks, but nothing was showing up on
profiler or perfmon that I could see, and nothing in the regular
filesystem was being indexed.
Here's how I resolved this, and it turns out that another issue I'd
been having was related to this one. There was a sql process (a
normally quick FT query) that was hanging for a couple of days and was
not responding to the KILL request. In the wee hours I restarted
mssearch.exe, the CPU dropped down to it's typical nearly nothing, and
the unkillable process finally dies. So I suppose mssearch was running
rampant and had locked up a sql process. Glad that's over but wish I
knew what caused mssearch to bork.
Cheers,
Steve
ML wrote:
> You can trace any SQL related activities of the MS Search service by running
> SQL Profiler.
> Perhaps - provided you're using task manager - what you see is the MS Search
> service indexing your file system.
Showing posts with label mssearchexe. Show all posts
Showing posts with label mssearchexe. Show all posts
Wednesday, March 28, 2012
MSSearch.exe error window: "Tracer"
My company has a client using SQLServer 2000 SP3a.
Every so often (approx. once a week), the full-text indexing will fail on
one of our database tables. We are unsure why, but have noticed some rather
bizarre behavior associated with this failure. (Normally, we restart the
MSSearch service and everything works again.)
Just today, the client called to tell us it didn't work. So, using
LogMeIn.com, I controlled their server computer to see what was going on.
Immediately I noticed a messagebox window with a title of "Tracer" and text
of "Release products should NOT call tracer!". The only button was "OK".
I didn't know for sure where this message was coming from, so I used
SysInternals' Process Explorer to list the processes and their window titles.
Lo and behold, MSSearch.exe was the process tied to "Tracer".
Obviously, this is a SQL Server bug, but I've not found reference to it in
any online searches. Has anyone seen this? Is it fixable by upgrading to
SP4 (this client is still using NT4, though).
Thanks for any information.
John,
Basic troubleshooting of SQL Server 2000 and MSSearch is somewhat of a black
art (as I can attest to), but the first place you should look for
information on what is causing the full-text indexing failure is the
server's Application event log as this is the only place where errors,
warning and information events are recorded for the MSSearch service. Look
for all related "Microsoft Search" or MssCi source events (errors, warning
and information) near the time of the failure. This will be the best source
of info as to what is causing the problem.
While I've never have used LogMeIn.com, I have known Microsoft to attach
debuggers to both SQL Server and the MSSearch.exe to identify bugs. If you
believe this to be a bug, then I'd highly recommend that you open a support
case with Microsoft PSS SQL Server support and get this resolved for your
client.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"John" <John@.discussions.microsoft.com> wrote in message
news:FAE1B226-FF90-41EC-9465-575285E412FF@.microsoft.com...
> My company has a client using SQLServer 2000 SP3a.
> Every so often (approx. once a week), the full-text indexing will fail on
> one of our database tables. We are unsure why, but have noticed some
> rather
> bizarre behavior associated with this failure. (Normally, we restart the
> MSSearch service and everything works again.)
> Just today, the client called to tell us it didn't work. So, using
> LogMeIn.com, I controlled their server computer to see what was going on.
> Immediately I noticed a messagebox window with a title of "Tracer" and
> text
> of "Release products should NOT call tracer!". The only button was "OK".
> I didn't know for sure where this message was coming from, so I used
> SysInternals' Process Explorer to list the processes and their window
> titles.
> Lo and behold, MSSearch.exe was the process tied to "Tracer".
> Obviously, this is a SQL Server bug, but I've not found reference to it in
> any online searches. Has anyone seen this? Is it fixable by upgrading to
> SP4 (this client is still using NT4, though).
> Thanks for any information.
|||We have the same thing happening sparodically at one of clients as well, The Tracer message pops up, the fulltext search quits working, if we restart mssearch it starts working again.
Only real difference I see, is that our client is running Small Bussiness Server, (Windows 2000, SP4) and I was blaming it on that, since they have all kinds of strange limitations they try to put in it.
I am switching it to update at 4AM each day instead of the continuas background update, and see if that makes a difference.
It only causes trouble when indexing 1 of the two tables we are indexing. The table has 550,000 items and a 5303 MB catalog, with a key count 6 million.
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
Every so often (approx. once a week), the full-text indexing will fail on
one of our database tables. We are unsure why, but have noticed some rather
bizarre behavior associated with this failure. (Normally, we restart the
MSSearch service and everything works again.)
Just today, the client called to tell us it didn't work. So, using
LogMeIn.com, I controlled their server computer to see what was going on.
Immediately I noticed a messagebox window with a title of "Tracer" and text
of "Release products should NOT call tracer!". The only button was "OK".
I didn't know for sure where this message was coming from, so I used
SysInternals' Process Explorer to list the processes and their window titles.
Lo and behold, MSSearch.exe was the process tied to "Tracer".
Obviously, this is a SQL Server bug, but I've not found reference to it in
any online searches. Has anyone seen this? Is it fixable by upgrading to
SP4 (this client is still using NT4, though).
Thanks for any information.
John,
Basic troubleshooting of SQL Server 2000 and MSSearch is somewhat of a black
art (as I can attest to), but the first place you should look for
information on what is causing the full-text indexing failure is the
server's Application event log as this is the only place where errors,
warning and information events are recorded for the MSSearch service. Look
for all related "Microsoft Search" or MssCi source events (errors, warning
and information) near the time of the failure. This will be the best source
of info as to what is causing the problem.
While I've never have used LogMeIn.com, I have known Microsoft to attach
debuggers to both SQL Server and the MSSearch.exe to identify bugs. If you
believe this to be a bug, then I'd highly recommend that you open a support
case with Microsoft PSS SQL Server support and get this resolved for your
client.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"John" <John@.discussions.microsoft.com> wrote in message
news:FAE1B226-FF90-41EC-9465-575285E412FF@.microsoft.com...
> My company has a client using SQLServer 2000 SP3a.
> Every so often (approx. once a week), the full-text indexing will fail on
> one of our database tables. We are unsure why, but have noticed some
> rather
> bizarre behavior associated with this failure. (Normally, we restart the
> MSSearch service and everything works again.)
> Just today, the client called to tell us it didn't work. So, using
> LogMeIn.com, I controlled their server computer to see what was going on.
> Immediately I noticed a messagebox window with a title of "Tracer" and
> text
> of "Release products should NOT call tracer!". The only button was "OK".
> I didn't know for sure where this message was coming from, so I used
> SysInternals' Process Explorer to list the processes and their window
> titles.
> Lo and behold, MSSearch.exe was the process tied to "Tracer".
> Obviously, this is a SQL Server bug, but I've not found reference to it in
> any online searches. Has anyone seen this? Is it fixable by upgrading to
> SP4 (this client is still using NT4, though).
> Thanks for any information.
|||We have the same thing happening sparodically at one of clients as well, The Tracer message pops up, the fulltext search quits working, if we restart mssearch it starts working again.
Only real difference I see, is that our client is running Small Bussiness Server, (Windows 2000, SP4) and I was blaming it on that, since they have all kinds of strange limitations they try to put in it.
I am switching it to update at 4AM each day instead of the continuas background update, and see if that makes a difference.
It only causes trouble when indexing 1 of the two tables we are indexing. The table has 550,000 items and a 5303 MB catalog, with a key count 6 million.
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
mssearch.exe easting up memory
Hi ,
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdR
You should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdR
You should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>
mssearch.exe easting up memory
Hi ,
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdRYou should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdRYou should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>
mssearch.exe easting up memory
Hi ,
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdRYou should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>sql
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdRYou should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>sql
mssearch.exe CPU utilization increased with SP4
Hi,
after installing SP4 I am having trouble with mssearch.exe using excess
CPU. Typically all is fine for some hours, then the utilization jumps
up to 60% and more. mssearch.exe can then only be stopped via killing
the process. After a restart all is fine again.
Any known problems with SP4 and the Fulltext engine?
TIA, Regards
DC
None that I am aware of - however have you checked the gatherer logs to
determine what is happening at this point? You can enable logging for more
details about exactly what is happening in this timeframe.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"DC" <dc@.upsize.de> wrote in message
news:1136211283.315556.324940@.f14g2000cwb.googlegr oups.com...
> Hi,
> after installing SP4 I am having trouble with mssearch.exe using excess
> CPU. Typically all is fine for some hours, then the utilization jumps
> up to 60% and more. mssearch.exe can then only be stopped via killing
> the process. After a restart all is fine again.
> Any known problems with SP4 and the Fulltext engine?
> TIA, Regards
> DC
>
|||Hi,
thanks for the hint, Hilary. I have rebuild all Fulltext Catalogs from
scratch and that seems to have solved my problem.
Regards
DC
after installing SP4 I am having trouble with mssearch.exe using excess
CPU. Typically all is fine for some hours, then the utilization jumps
up to 60% and more. mssearch.exe can then only be stopped via killing
the process. After a restart all is fine again.
Any known problems with SP4 and the Fulltext engine?
TIA, Regards
DC
None that I am aware of - however have you checked the gatherer logs to
determine what is happening at this point? You can enable logging for more
details about exactly what is happening in this timeframe.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"DC" <dc@.upsize.de> wrote in message
news:1136211283.315556.324940@.f14g2000cwb.googlegr oups.com...
> Hi,
> after installing SP4 I am having trouble with mssearch.exe using excess
> CPU. Typically all is fine for some hours, then the utilization jumps
> up to 60% and more. mssearch.exe can then only be stopped via killing
> the process. After a restart all is fine again.
> Any known problems with SP4 and the Fulltext engine?
> TIA, Regards
> DC
>
|||Hi,
thanks for the hint, Hilary. I have rebuild all Fulltext Catalogs from
scratch and that seems to have solved my problem.
Regards
DC
Mssearch.exe consuming High CPU over extended time period
Hello,
We are running SQL 2000 sp4 with full text search, recently we are
getting 100% CPU over extended period of time and the only way to
resolve this is by killing the Mssearch.exe process. (we tried to
restart the service but it hang) the Microsoft search service is
running under local system account.
our system topology is active/passive cluster with NAS disks, 4GB RAM
and 4 CPU for each server.
May be some one can help me?
The issue happen randomly with no specific job running at that time or
any thing, and when it happen the SQL queries are running very very
slow.
Thank you
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93706&SiteID=1
In your particular case, when did the problem start? After upgrade, some configuration change, resource change, database size change?
This may help understand the problem.
Thanks,
Boris.|||I asked our dev team and there are no known problems of this kind. I would recommend contacting product support services and have them look at your particular configuration. Most likely the problem you are seeing is caused by the content being indexed.|||Hi,
We appear to be experiencing the same thing. There is no disk activity - just mssearch running at 100% utilization.
Have you found an answer yet?|||We used Microsoft support and nothing found we tried rebuild all catalogs , Fix some snapshot problem on the NAS and still we got the same problem finally we changed the affinity mask of the Mssearch and the SQL (SQL use CPU 1 and 2 and Mssearch the rest) we are still waiting to see if it help to solve the problem for now (4 days) it look fine even though the Mssearch took 100% the SQL continue to give services and the CPU drop back to normal with out human interference. So I will have more clear answer with in a week.
Monday, March 26, 2012
Mssearch.exe consuming High CPU over extended time period
Hello,
We are running SQL 2000 sp4 with full text search, recently we are
getting 100% CPU over extended period of time and the only way to
resolve this is by killing the Mssearch.exe process. (we tried to
restart the service but it hang) the Microsoft search service is
running under local system account.
our system topology is active/passive cluster with NAS disks, 4GB RAM
and 4 CPU for each server.
May be some one can help me?
The issue happen randomly with no specific job running at that time or
any thing, and when it happen the SQL queries are running very very
slow.
Thank you
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93706&SiteID=1
In your particular case, when did the problem start? After upgrade, some configuration change, resource change, database size change?
This may help understand the problem.
Thanks,
Boris.|||I asked our dev team and there are no known problems of this kind. I would recommend contacting product support services and have them look at your particular configuration. Most likely the problem you are seeing is caused by the content being indexed.|||Hi,
We appear to be experiencing the same thing. There is no disk activity - just mssearch running at 100% utilization.
Have you found an answer yet?
|||We used Microsoft support and nothing found we tried rebuild all catalogs , Fix some snapshot problem on the NAS and still we got the same problem finally we changed the affinity mask of the Mssearch and the SQL (SQL use CPU 1 and 2 and Mssearch the rest) we are still waiting to see if it help to solve the problem for now (4 days) it look fine even though the Mssearch took 100% the SQL continue to give services and the CPU drop back to normal with out human interference. So I will have more clear answer with in a week.
Subscribe to:
Posts (Atom)