Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Full-Text Search / August 2005

Tip: Looking for answers? Try searching our database.

Not the usual Error 7635: The Microsoft Search Service Cannot . (l

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
BC DBA - 15 Aug 2005 11:28 GMT
Hi all,

No BUILTIN\ADMINISTRATORS has not been removed or altered :>

We aquired a new box to replace an existing server that was out of warranty.
Working with the developers we have gradually moved all the databases from
the old box to the new box and everything was working fine.

Until . . . .

I noticed that there were some Jobs in SQL Agent that were disabled. Talking
to the developer he realised that they were used by the Full text service on
one of our systems. No he hadn't copied the Catalogs. So we try and drop the
catalogs . . . No can do as they don't exist, and the drive structure is
different between the boxes. So I copy over all the Catalog files, into the
same directory structure as on the old box, and then edited the
sysFullTextCatalogs table (DON'T TRY THIS AT HOME!) and restared SQL server
Service.

Whenever we try and do anything sp_fulltext_database 'enable', Or use
Enterprise Manager to Drop the catalogs, or the Full Text Wizard to create a
new catalog in a different database we get the "Error 7635: The microsoft
Search Service cannot be administered under the present user account". The
"present user account" is a memeber of the sysadmins role, and also is the
SQL Service Startup account.

As I said earlier I haven't removed BUILTIN\ADMINISTRATORS, which has master
as its Default database, and is a member of sysadmin.

I have even done the workaround as described here

http://support.microsoft.com/default.aspx?scid=kb;en-us;277549

as I might have broken FTS by changing the startup account via service
control panel (Although thats not something I usually do). All the googling
I've done has revealed that Its down to removing Builltin administrators,
which is something I usually do, but we decided that it was pointless on this
particular box as access to it is very tightly controlled.

This has really got me stumped ATM any ideas?

Signature

Regards

Tony

John Kane - 15 Aug 2005 15:27 GMT
BC DBA,
Hmm... most likely you didn't copy over required registry keys for the FT
Catalog and possibly other system tables are not set correctly. I've seen
this "catch-22" situation before and I have a manual sysadimn-level script
that can fix it. However, it is SQL Server version specific. Could you post
the full output of SELECT @@version ? Please, email me directly (jt-kane at
comcast dot net) as this is as you say in the category of "don't try this at
home", and not for the faint of heart...

Thanks,
John
Signature

SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/

> Hi all,
>
[quoted text clipped - 46 lines]
>
> This has really got me stumped ATM any ideas?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.