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
that can fix it. However, it is SQL Server version specific. Could you post
"BC DBA" <BCDBA@discussions.microsoft.com> wrote in message
news:AA9DFF57-5469-43B4-B8CE-4CD0B38AA0CA@microsoft.com...
> 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?
>
> --
> Regards
>
> Tony