Geeks With Blogs

Mike H. - Another Geek In Need... WebLog

After successfully upgrading MOSS B2TR to RTM (or thinking all was successful) - I started to see this error in the Application Event Log - every 60 seconds. It was preceded by:

The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition - threw an exception. More information is included below.

The device is not ready.

Like many of you before me - and very likely after me, I Googled to my heart's content - and suffice to say my heart was never satisified.

I'd kept a collective 94MB document of each painfully executed step of the upgrade.

  1.    The B2TR deployment was pretty much out of the box (OOB)
  2.    A single SSP (shared service provider) had been created, leaving the default name SharedServices1 in place, and 2 search scopes created.
  3.    I drilled on this for quite some time - invariably finding that a) I was on my own, and b) strangely enough, the RTM upgrade went very well - but hosed the permissions of my search scope? Not entirely - just the permissions of the service account!!! Very interesting.

The error is representative of not being able to create a search index because the scope it is looking for - it cannot get to, or more specifically, it thinks is busy and so it keeps coming back trying to get at it.

Solution / or not? Not finding any meat/potatoes online, I tried the following:

  1. stsadm -o osearch -action stop
    1. Warning: The Office SharePoint Server Search service that was enabled on this server will uninstall and all index files for all SSPs will be deleted. Are you sure you want to permanently delete all data in the index for all SSPs? [y/n]
  2. NOTE: Only do this if you have not crawled / indexed content that cannot be re-indexed. If this is the case, then you open a support ticket with MSFT and work through it. Otherwise, hit Y
  3. Now issue: stsadm -o osearch -action start -role index
    1. You may receive the errror 'start' action failed. Additional information: the handle is invalid. Wait 30-60 secs and re-issue the command. It should go through fine.
  4. Open Central Admin - select your SSP
  5. Check / validate your search service configuration.

After all of this - and all looking fine, normal, just dandy! I continued to see errors regarding the 'device' that was not ready for a search indexing service run. Interesting.

Finding nothing else online and getting no immediate feedback - I took the plunge.

1) Within the Central Admin - I stopped both search service/server processes.

2) I re-created these - basically using the same service account as before.

3) When to the event log and validated that all is now operating normally.

Invariably, what I found is that my service account simply did not have permission to run the job any longer. I did not have to re-create a service account - I simply stopped (essentially terminating and deleting existing indexes in my search database), and re-created the search database.

 Please feel free to share your experience in this area - if / when you hit it.

Posted on Thursday, December 21, 2006 9:03 AM Microsoft Office SharePoint Server 2007 (MOSS) | Back to top


Comments on this post: Application Server Admnistration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance - The device is not ready.

# re: Application Server Admnistration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance - The device is not ready.
Requesting Gravatar...
I had the same thing happen to our servers and this did the trick. Thanks!
Left by Sarah on Mar 19, 2007 3:29 PM

# re: Application Server Admnistration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchService
Requesting Gravatar...
Thanks for the tip...yup I had the wrong password for my services account. :)
Left by Kevin on Sep 17, 2007 3:28 PM

# re: Application Server Admnistration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchService
Requesting Gravatar...
I had a very similar error and performed the following:
1) net stop osearch
2) net start osearch
3) iisreset /noforce

This did the trick for me.
Left by Ross on Apr 07, 2008 3:17 PM

# re: Application Server Admnistration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchService
Requesting Gravatar...
The above worked for me too:

I had a very similar error and performed the following:
1) net stop osearch
2) net start osearch
3) iisreset /noforce

Thank you very very much!
Left by Bill on Sep 18, 2008 9:20 AM

Your comment:
 (will show your gravatar)


Copyright © Michael J. Hamilton, Sr. | Powered by: GeeksWithBlogs.net