Hi, I have recently updated from WSS 3 to MOSS 2007. Now I am not able to create SSP because I am not able to enable indexers. When I am going to Operations-->Services on Server I am not able to find Office sharepoint search. Also the custom is selected as serices you choose run on this server. Any help will be appreciated. Thanks & Regards, Rahul Rashu

Assuming this is a stand-alone server, could you try to run the following via STSADM stsadm -o osearch -action start Here is a link to the command ref... http://technet.microsoft.com/en-us/library/cc262920(office.12).aspx Could you follow up and let us know if this changed the appearance of the Office SharePoint Search start selection within Central AdminKris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog

Hi Kris, I applied your suggestion but after running the command I am getting this message "No Search Service". Any help in this regard will be useful. Thanks & Regards, Rahul Rashu

Rahul, I doesn't sound like all the binaries for MOSS were installed. How did you run the upgrade, please explain the steps and patches used. Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog

Hi Kris, I was using WSS 3 before. I had no issues in search over there. Recently I migrated to MOSS. To do this I installed MOSS 2007. Everythings i working fine other than this indexer. Thanks & Regards, Rahul Rashu

Hi Kris, I was using WSS 3 before. I had no issues in search over there. Recently I migrated to MOSS. To do this I installed MOSS 2007. Everything is working fine other than this indexer. Thanks & Regards, Rahul Rashu

I recommend reinstalling MOSS over your current application at this point (it's nothing more than running the exe again and then running the wizard to refesh all the installed files.... If you can wait another day or so the Microsoft team will review the post. Have you looked into the server logs and event logs... is there anything at all that looks to be an error?Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog

Hi Mike, There are no errors in the event viewer. When I do the search I get this error message on the page itself An unexpected error has occurred. Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator. Troubleshoot issues with Windows SharePoint Services. I will wait for the Microsoft guys or your post for one more days. Thanks & Regards, Rahul Rashu

Hi, Please explain the approach of your WSS3 to SP2007 Upgrade What version of WSS3 did youhave installed and what version of SP2007 did you install, alos what steps did you follow? plerase provide as much detail as possible.. -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.

Please respond to Ivan on the process... I.E. - Downloaded Microsoft Office SharePoint Server 2007, extracted files, made CD.. ect.. http://technet.microsoft.com/en-us/library/cc262342(office.12).aspx This link outlines the steps to upgrade then this outlines the steps to configure the product once installed. http://technet.microsoft.com/en-us/library/cc262079(office.12).aspx#section10 based on the web page error here I'm assuming you did an inplace upgrade, the new page might be using the MOSS search but if it's not installed or started then this error makes sense but the big problem was in the install... The steps will help pin point the error.Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog

Hi, I downloaded the software. Then I installed using command prompt. Everything was normal. During my installation I selected web front end server so that more servers can be added to it. I tried to repair the product now but no luck. Please help. Thanks & Regards, Rahul Rashu

Hey, Could you see the following services in your Server.Go to service ( run > services.msc) and check following service are there 1. Office SharePoint Server Search 2. Windows SharePoint Services Search Try to start the service and check the eventviewer what the error you are getting. So we could make sure that search service is installed in your Server. Go to sharepoint Central admin site web.config and change the trust level to full.Then check your webpart errror. You could also look at the ULS LOG ( C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS ) so we could get some information about the issue you have.

Hi Shyjumohan, I am able to find the Windows Sharepoint Services Search in my services.msc but the first one Office sharepoint server search services are not present. Is there any way I can install this services on my machine? Any help will be highly appreciated. Thanks & Regards, Rahul Rashu

Shyjumohan - if you read the thread you'll see there was no service to start therefore it wouldn't show up in services. Rashu... No you cannot install the service on its own, you must reinstall the entire product over the current install. Please go into C.A. and tell me the version you're running. Also, installed by command line is very little information... What is the command you ran? Did you run the SharePoint Tech Config Wizard when you were done? Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog

Hi Kris, The version is 12.0.0.6421. Well I followed these steps: 1. I changed to the directory on my machine containing setup files and then I entered setup.exe and enter. 2. After competion of the installation, I ran the sharepoint configuration wizard manually and not through the command prompt. 3.This completed in 8 steps . I tried repairing the product but no luck after completion , I started the configuration wizard also . This also completed successfully but no luck. Still the same. I checked the indexing services on my machine in control panel and found that it was running fine. Instead of reinstall, is there any hotfix available? Is there any .dll responsible for it? So that I can place it manually in a folder. Thanks & Regards, Rahul Rashu

Hi Rahul, You need to always choose complete for the installation type, a WFE installation is only fopr WFE and even if you have many WFEs you should still use Complete this allows you to transfer central admin and other services to any of the servers in your farm inxase of a disaster... Install the the binaries again, choose COMPLETE and run the PSConfigUI. The services on server should now appear for you to configure. The WebFront end version does not have all of the services, its a deprecated set of features for deployment on WFEs, I have never deployed the WFE version to production... In the future you will need to be more detailed in the steps you followed provide the links where you downloaded etc. Also, when reparing the product the first step is to run PSConfigUI and not detaching from the farm. As an Example for future consideration be more specific on how you performed repair. If you dont provide enough information it will be impossible to help you without a number ofnposts going back and forth... Cheers, -Ivan

If after a complete reinstall (there is no hotfix for a broken install) and you can’t resolve your issues please contact Microsoft support at this point, support can help you walk thru all issues and help support your product and production environment. This thread is going in circles and is not helping you but more people adding items are confusing you and your situation. http://support.microsoft.com/ph/935/en-us#tab0 https://support.microsoft.com/oas/default.aspx?Gprid=11373&st=1&wfxredirect=1&sd=gn Option: “Setup a support topic” Sub-topic: “An upgrade has failed from MOSS 2007” Choose your support option (Enterprise Agreement, Software Assurance or Open Account). One of these would have been provided when you purchased SharePoint 2007. Contact your software purchaser for help with you Microsoft ID and how to open a support case with Microsoft at no cost. Locking thread at this time. Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog