Microsoft Search

For the past week my W2k3 Ent has been running very slow.
When I checked the Event Viewer I noticed that I have
tons of entries of Microsoft Search, saying this: "The
crawl on project <SQLServer SQL00008000005> has started."
then this: "The end of the incremental crawl for project
<SQLServer SQL00008000005> has been detected. The
Gatherer successfully processed 36 documents totaling OK.
It failed to filter 0 documents. 36 documents were
modified. 0 URLs could not be reached or were denied
access.".
Every 15 minutes I get this pair of entries in the EV. My
HD and the DVD-ROM lights goes on and off every second.
Is this something really bad? Can someone tell me what's
happening?
Thanks so much.Perheps you don't need MS Search Service. You can stop it
from the Services, or run following command on the DOS
command prompt:
net stop mssearch
If that improves the performance, then I would suggest to
go to Services and change the StartType to Manual so that
it won't start again at reboot.
hth.
>--Original Message--
>For the past week my W2k3 Ent has been running very slow.
>When I checked the Event Viewer I noticed that I have
>tons of entries of Microsoft Search, saying this: "The
>crawl on project <SQLServer SQL00008000005> has started."
>then this: "The end of the incremental crawl for project
><SQLServer SQL00008000005> has been detected. The
>Gatherer successfully processed 36 documents totaling OK.
>It failed to filter 0 documents. 36 documents were
>modified. 0 URLs could not be reached or were denied
>access.".
>Every 15 minutes I get this pair of entries in the EV. My
>HD and the DVD-ROM lights goes on and off every second.
>Is this something really bad? Can someone tell me what's
>happening?
>Thanks so much.
>.
>sql

Meta Data Services SQL 2000 "msdb database could not be opened"

Hello anyone / everyone,

If you are having trouble accessing Meta Data Services on W2k3 and SQL 2000 and get the error that the "msdb database could not be opened" I found that hot fix 912812 on the operating system is the culprit. Remove it and Meta Data goes back to working, although I am being asked to approve the ActiveX control every time the page refreshes.

Hope this helps somebody, to took me long enough to track it down.

If anyone has a resolution to the ActiveX question I'd love to know the answer.

Thank you,

Uncle Davy

Use "Internet Options" in Internet Explorer and on the security tab, select a "custom level." There you can adjust various properties relating to prompting for and enabling ActiveX controls.

Donald

|||

That would seem the logical choice. However, I tried permitting every activeX and it was still giving me the error!

|||

I have the same error.

SQL 2000 running on Server 2003 SP1.

The hotfix isn't in the list to remove and the permissions have all been granted for activex as well as ensuring database user persmissions are ok.

|||I also removed the "Internet Explorer Enhanced Security Settings" from the server. If you haven't done so try it (Add remove programs -> Add remove windows componenets -> IE enhanced security settings uncheck this).

This was the only issue I ever found (the hotfix) no one ever posted anything about it that was useful.

Of course once I removed the hot fix, I never went back...

Good luck.

Meta Data Services SQL 2000 "msdb database could not be opened"

Hello anyone / everyone,

If you are having trouble accessing Meta Data Services on W2k3 and SQL 2000 and get the error that the "msdb database could not be opened" I found that hot fix 912812 on the operating system is the culprit. Remove it and Meta Data goes back to working, although I am being asked to approve the ActiveX control every time the page refreshes.

Hope this helps somebody, to took me long enough to track it down.

If anyone has a resolution to the ActiveX question I'd love to know the answer.

Thank you,

Uncle Davy

Use "Internet Options" in Internet Explorer and on the security tab, select a "custom level." There you can adjust various properties relating to prompting for and enabling ActiveX controls.

Donald

|||

That would seem the logical choice. However, I tried permitting every activeX and it was still giving me the error!

|||

I have the same error.

SQL 2000 running on Server 2003 SP1.

The hotfix isn't in the list to remove and the permissions have all been granted for activex as well as ensuring database user persmissions are ok.

|||I also removed the "Internet Explorer Enhanced Security Settings" from the server. If you haven't done so try it (Add remove programs -> Add remove windows componenets -> IE enhanced security settings uncheck this).

This was the only issue I ever found (the hotfix) no one ever posted anything about it that was useful.

Of course once I removed the hot fix, I never went back...

Good luck.