Search Function not working

[Killy]

On a W2K member server of a domain, when I click Start ->
SEARCH -> Files or Folders , nothing comes up on the
screen. On another similar server I get a proper Search
window. Could it be any group/local policy doing this? if
so, which one? Is there any diagnostic tool I can use to
determine what's causing it?

Thanks in advance fro your help.

 

[Vsevolod Titov [MSFT]]

I don't think it is due to policy. It sounds more like a configuration issue
or a bug. If search for files and folders would be disabled, then you
wound't see the "Files and Folders" button at all. If you want to see policy
settings applied to Windows 2000 machine, then launch cmd window and type:

gpresult /v

This will print out all policy settings applied to the computer. See if
there is any differences between the two machines.

 

[Guest]

Similer situation for me.

We are running Win 2000 advanced server ( terminal services) in an NT 4 domain with SBS 4.5. I have tried my best to get to work. No luck. Also having issues with IE 6.1 as to updates. I have read trhough the threads, I have an idea where to start on that.

After countless hours, I am not sure that I have the policy settings working or disabled in the W2000K server

My question is in a mixed domain like this, what steps can I take to make sure that the registry and settings for a mixed environment are correct?

Thanks - Terry

----- Vsevolod Titov [MSFT] wrote: -----

I don't think it is due to policy. It sounds more like a configuration issue
or a bug. If search for files and folders would be disabled, then you
wound't see the "Files and Folders" button at all. If you want to see policy
settings applied to Windows 2000 machine, then launch cmd window and type:

gpresult /v

This will print out all policy settings applied to the computer. See if
there is any differences between the two machines.

 

[Buz [MSFT]]

Hello Killy,

This does not seem policy related, if you were to disable search via you
wouldn't have the Search option at all. My first thought on this would be a
local resource problem of some sort. If you disable programs that are
running in the background (AV software, backup software, etc..) does the
problem still occur? An easy first step troubleshooting method is to
determine if the problem will occur in Safe mode. If possible boot to safe
mode and see if you can search. If so there is a third party program or
process running in the background that may be causing this issue.


I also found this sort of oddball issue that references Dcomcnfg.exe and may
relate to the issues Terry is reporting as well:
274696 Actions Such as Search and Drag and Drop Do Not Work Because the
Default http://support.microsoft.com/?id=274696

 

[Bobby Davies]

I don't think this is the problem. Have you tried using the f3 key. We are
able to use it to get the search box but cannot click on the search in the
start menu.

Thanks

 

[Buz [MSFT]]

So it is only search off the Start menu where the problem occurs?

Does this issue occur regardless of who logs in? Have you tried to log in as
a new user to see if the issue still occurs?

One thing I noticed is that when we search off of Start we enumerate all
drives, when we F3 off the desktop we default to the desktop for "look in"

Will disk management run OK, do you have anything unusual wiht your drive
configuration going on?

Sorry if this one is a dupe but did you go through this as well as trying
the action in safe mode?

274696 Actions Such as Search and Drag and Drop Do Not Work Because the
Default
http://support.microsoft.com/?id=274696

My last suggestion would be to use regmon from www.sysinternals.com and try
to figure out where the pause or failure is occuring.

Buz Brodin
MCSE NT4 / Win2K
Microsoft Enterprise Domain Support

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

 

[Guest]

I have tried the regmon route, and could not figure it out. My solution is a complete reinstall, no new patches applied, except sp4. Then, back the whole thing up, and start to apply the various updates, makeing notes of the order and the process as a whole.

I am in the middle of the process now. Unfortunately for me, I cannot spend the time to try to "tinker" with things any longer. A really great tool would be the ability to re-install registry sections from a "default" set up. I tried to use the Resource Kit registry documents, but found that I was just chewing up time. This is frustrating for me, becuase I would have liked to know what caused it, so I can aviod it. I still think that it has to do with a mixed environment.

Somewhere on another post (similier symptoms) I saw someone recommend a reinstall. For us, Safe Mode did not make a difference, and the f3 key worked only in windows explorer. Prior to the decision to reinstall, I also removed our virus software, ServerProtect by Trend Micro without success.

Unfortunately, I have lost a great deal of work this way. So far things work ok. If I find a issue that I can identify, I will post. The time spent on trying to solve this is unfortunate. I am CPA by trade, not an IT person. Consequently, my understanding of the registry, security and other issues is self taught by needs.

 

[Buz [MSFT]]

Ok Terry,

I would agree that a problem such as this does not warrant a great deal of
troubleshooting. Obviously besides a reinstall you could ignore or
workaround the issue (press F3 as you had stated). Just to let you know we
have had no cureent reported problems with the Search off the Start Menu
after the latest hotfixes or Service Packs have been installed so I don't
think you will have the problem after the reinstall.

Buz Brodin
MCSE NT4 / Win2K
Microsoft Enterprise Domain Support

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

I have tried the regmon route, and could not figure it out. My solution

is a complete reinstall, no new patches applied, except sp4. Then, back the
whole thing up, and start to apply the various updates, makeing notes of
the order and the process as a whole.

I am in the middle of the process now. Unfortunately for me, I cannot

spend the time to try to "tinker" with things any longer. A really great
tool would be the ability to re-install registry sections from a "default"
set up. I tried to use the Resource Kit registry documents, but found that I
was just chewing up time. This is frustrating for me, becuase I would have
liked to know what caused it, so I can aviod it. I still think that it has
to do with a mixed environment.

Somewhere on another post (similier symptoms) I saw someone recommend a

reinstall. For us, Safe Mode did not make a difference, and the f3 key
worked only in windows explorer. Prior to the decision to reinstall, I also
removed our virus software, ServerProtect by Trend Micro without success.

Unfortunately, I have lost a great deal of work this way. So far things

work ok. If I find a issue that I can identify, I will post. The time spent
on trying to solve this is unfortunate. I am CPA by trade, not an IT person.
Consequently, my understanding of the registry, security and other issues is
self taught by needs.

 

[Guest]

Well, AS USUAL, you guys were right. I finished reinstalling, and guess what? I found the problem. I was able to reproduce this problem exactly. I was installing Shutdown Plus 5.2 (not 5.3, the current version) from WM Software. Each time I installed, I got the problem. By uninstalling the software, the problem goes away. So, if anyone else is experiencing similier problems, before reinstalling, they should check the version of this program if it is being used.

As I said, it was version 5.2 not the current version 5.3 . The moral to this tale is to be deligient in the installation process of setting servers. Keep records of the installation process and make sure you have the right version of software.

Thanks to all who attempted to help !!! Back to taxes !!!!
Terry

 

[Buz [MSFT]]

Thanks for the update Terry,

I went ahead and added a short note to our database (as customer verified)
just in case this issue comes up again.

Buz Brodin
MCSE NT4 / Win2K
Microsoft Enterprise Domain Support

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

Well, AS USUAL, you guys were right. I finished reinstalling, and guess

what? I found the problem. I was able to reproduce this problem exactly. I
was installing Shutdown Plus 5.2 (not 5.3, the current version) from WM
Software. Each time I installed, I got the problem. By uninstalling the
software, the problem goes away. So, if anyone else is experiencing similier
problems, before reinstalling, they should check the version of this program
if it is being used.

As I said, it was version 5.2 not the current version 5.3 . The moral to

this tale is to be deligient in the installation process of setting servers.
Keep records of the installation process and make sure you have the right
version of software.