I'm having some issues with my SharePoint server at the moment, in regards
to search.
Basically we tried to put some patches onto our sharepoint box, we didnt
like it, so we rolled back a ghost image that we took right before the
patches went on, so in theory everything should have gone back to being the
way it was.
Anyway everything looks to be fine, except the search service wont work
properly. I am getting the following errors in my event log:
Application Server Administration job failed for service instance
Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(51f911ae-54c4-4869-ad7b-ac3e82d7dad5).
Reason: The database connection string is not available.
Techinal Support Details:
System.Runtime.InteropServices.COMException (0xC0041228): The database
connection string is not available.
at
Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1
remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32
versionIn)
at Microsoft.Office.Server.Search.Administration.SearchApi.AddApp(Role
role)
at
Microsoft.Office.Server.Search.Administration.SearchServiceInstance.InstallGathererApplicationIf()
at
Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at
Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
and this one ...
The database connection string is not available.
Context: Application 'abf7b70e-c5c4-4b4e-a3ce-3bed5e8bde96'
When I go to the SSP search settings page I get "The search service is
currently offline. Visit the Services on Server page in SharePoint Central
Administration to verify whether the service is enabled. This might also be
because an indexer move is in progress." but when I check the services on
server page in the central administration site I can see that the service is
running.
I'm not sure what could be causing this, I have restarted services and this
still happens. Any help with this would be great.
Thanks in advance
- Brian Farnhill
"The search service is currently offline. Visit the Services on Server page
in SharePoint Central Administration to verify whether the service is
enabled. This might also be because an indexer move is in progress."
Brain,
I am also facing exactly the same problem,
when I go to SSP---->Search settings I am gettign the error message
"The search service is currently offline. Visit the Services on Server
page in SharePoint Central Administration to verify whether the
service is enabled. This might also be because an indexer move is in
progress"
had you resolved this issue sir?
Thanks In Advance
Regards
Gopi
Anyone know what could be causing this?
1. Stop the search services on the search on server page
2. Start them again (They would only start with the local admin acocunt)
3. Assign the indexer to the SSP in the settings page for the SSP
4. Start a new crawl over all your content
Given that I am now using a local account to index content, I had to put
that account into the site collection administrators group so it could see
everything. I know thats not good practice, but seeing as for me its only on
a test box Im not too fussed.
If this helps anyone figure out a better solution, let me know!
We had this problem, proxy autodetection was causing it. editing
webconfig in SSP site helped.
<defaultProxy>
<proxy autoDetect="true" />
</defaultProxy>
changed to
<defaultProxy>
<proxy autoDetect="false" />
</defaultProxy>
Regards,
Dmitrij
As far as we can understand this is to do with Office search, not
WSS.
On Nov 22, 1:36 am, Brian Farnhill
<BrianFarnh...@discussions.microsoft.com> wrote:
> OK I got it, I started the service using the credentials of a local
> administrator account on the server, as opposed to the domain account that is
> in the administrators group. So here is what I did
>
> 1. Stop the search services on the search on server page
> 2. Start them again (They would only start with the local admin acocunt)
> 3. Assign the indexer to the SSP in the settings page for the SSP
> 4. Start a new crawl over all your content
>
> Given that I am now using a local account to index content, I had to put
> that account into the site collection administrators group so it could see
> everything. I know thats not good practice, but seeing as for me its only on
> a test box Im not too fussed.
>
> If this helps anyone figure out a better solution, let me know!
>
> "Brian Farnhill" wrote:
> > No luck resolving this one yet - I have been playing around with it this
> > morning and after stopping the services on the server I am now unable to
> > start the search service again. On the services on server page I can see the
> > "Windows SharePoint Services Search" service is stopped, and when i click on
> > start and give it the credentials of a domain account that is in the local
> > admin group of the server (exactly what it was while it was working) and the
> > name of a new database it sits there processing for a while and comes back
> > with an error of "File not found".
>
> > Anyone know what could be causing this?
>