kallatech
asked on
Sharepoint services 3 search is not working wont show any data
I stopped the windows sharepoint services search service and changed the search database name. I got notices in event viewer that Successfully imported the application configuration snapshot into the registry.
Context: Application '0548d194-4a35-4850-9b1d-3
I am using the same domain admin account for both the service account and the content access account.
Prior to all this I could search older content but not newer content.
Now since I renamed the search database I can't search any content.
I do have the registry fix for the loopback.
Context: Application '0548d194-4a35-4850-9b1d-3
I am using the same domain admin account for both the service account and the content access account.
Prior to all this I could search older content but not newer content.
Now since I renamed the search database I can't search any content.
I do have the registry fix for the loopback.
ASKER
A new query machine, 'servername', has been added to the query rotation based on changes to farm topology. Component: 0548d194-4a35-4850-9b1d-34
That was the message I mean to put in the above comment.
That was the message I mean to put in the above comment.
ASKER
The start address <sts3s://smllc003/contentd
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
An unrecognized HTTP response was received when attempting to crawl this item. Verify whether the item can be accessed using your browser. (0x80041204)
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
An unrecognized HTTP response was received when attempting to crawl this item. Verify whether the item can be accessed using your browser. (0x80041204)
I would suggest stopping the SharePoint Search Service in Central Admin (which will effectively remove it/disable it) and then recreate it. When you renamed it, sounds like you busted something. There is no data to lose here, so better that you just clean up and move on.
I documented the steps here in a blog post some time ago, though I stopped Search from STSADM (Command line) instead of Central Admin.
http://blog.brainlitter.com/archive/2009/01/31/how-to-fix-broken-wss-crawlsearch.aspx
I documented the steps here in a blog post some time ago, though I stopped Search from STSADM (Command line) instead of Central Admin.
http://blog.brainlitter.com/archive/2009/01/31/how-to-fix-broken-wss-crawlsearch.aspx
ASKER
I will try that again.
I did stop the search service once and then renamed it to a different database.
I did a reboot but didn't do the iis reset.
I did stop the search service once and then renamed it to a different database.
I did a reboot but didn't do the iis reset.
ASKER
Alright I did that and renamed the database.
I am using the same domain admin account for both the service and the content.
sharepointsearch.docx
I am using the same domain admin account for both the service and the content.
sharepointsearch.docx
ASKER
After doing that here are the messages I received in event viewer.
Some people say to use the same domain admin account for both and others say to use a different domain admin account for each one.
I had one person tell me to use a local server account.
Which one is it?
sharepoint-errors.docx
Some people say to use the same domain admin account for both and others say to use a different domain admin account for each one.
I had one person tell me to use a local server account.
Which one is it?
sharepoint-errors.docx
I've heard others say that too, though it hasn't been my experience. You want one account to have enough priveleges to launch/run as a service (the search service account) and you want one account with just domain user rights to be the one that 'crawls' your content.
I'd suggest at this point, if you have your loopback properly defined (maybe double check you have it set right), that you do the following two things:
1. Download SQL Server Studio Express and connect to your SQL Server instance and check the permissions and make sure there are no errors reported on the SQL Side about access
2. Onethe console of the server itself, try and login to the SharePoint Site using the account you are using for the Search content (content access account) and try to visit the site. If that account can't login to the site, it is either loopback, DNS (can't resolve the site locally) or permissions... if it can't login, it can't crawl.
I'd suggest at this point, if you have your loopback properly defined (maybe double check you have it set right), that you do the following two things:
1. Download SQL Server Studio Express and connect to your SQL Server instance and check the permissions and make sure there are no errors reported on the SQL Side about access
2. Onethe console of the server itself, try and login to the SharePoint Site using the account you are using for the Search content (content access account) and try to visit the site. If that account can't login to the site, it is either loopback, DNS (can't resolve the site locally) or permissions... if it can't login, it can't crawl.
ASKER
I downloaded and installed Windows sharepoint Services 3 with service pack 2 on another server.
I loaded it with defaults.
I used two different domain admin accounts one for the service and the other for the content.
I saw in even viewer that a new server had been added to the rotation.
I uploaded a word document and then waited a few minutes to do a search.
The search worked.
I made the same changes on the old install and waitedn and got the same events.
Prior to that I got the message shown below.
I got this four times before event ids 2424 and 2436 appeared again.
The description for Event ID 2803 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
1
Object Plans
The specified resource type cannot be found in the image file
The databases were moved at one time do to lack of space on the c drive.
Could it be that the search can't find the database and is looking at the default location?
I loaded it with defaults.
I used two different domain admin accounts one for the service and the other for the content.
I saw in even viewer that a new server had been added to the rotation.
I uploaded a word document and then waited a few minutes to do a search.
The search worked.
I made the same changes on the old install and waitedn and got the same events.
Prior to that I got the message shown below.
I got this four times before event ids 2424 and 2436 appeared again.
The description for Event ID 2803 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
1
Object Plans
The specified resource type cannot be found in the image file
The databases were moved at one time do to lack of space on the c drive.
Could it be that the search can't find the database and is looking at the default location?
ASKER
I will leave at 4pm EST time today and will not be able to try anything until monday around 7am EST.
ASKER
Is it possible to move my existing setup to another server and have it run the same way?
I was thinking of moving it to the new install of sharepoint services 3 with service pack 2.
I still have been unable to get the search to work but the content is fine.
I was thinking of moving it to the new install of sharepoint services 3 with service pack 2.
I still have been unable to get the search to work but the content is fine.
ASKER
I was able to login to the local site (https://ipaddress) with a domain account that has domain user rights and an account that has domain admin rights.
I have the registry fix for loopback in the registry from when I first setup sharepoint services 3.
spserverreg.docx
I have the registry fix for loopback in the registry from when I first setup sharepoint services 3.
spserverreg.docx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Does this process take sharepoint offline while it does the backup?
ASKER
Thanks for the help.
ASKER
After the install I did get this message but then it was followed by the 2424 and 2436.