"d krage" <dkrage@discussions.microsoft.com> wrote in message
news:8F7D817F-B35C-4689-97E4-C79B711842B8@microsoft.com...
> Thanks for your reply John. As it turns out the error indicated a problem
> with user rights, however, the problem turns out to be a bad install of
> MSSearch.
>
> Here is what corrected the problem...from Google groups.
> http://groups.google.com/group/microsoft.public.sqlserver.fulltext/browse_thread/thread/145e986463b924b2/7cb7c7692a0e2ff1?q=success&rnum=2#7cb7c7692a0e2ff1
>
> According to Google search results, there should be a
> HKLM\Software\Microsoft\Search\1.0\Applications\SQL Server key. This did
> not
> exist, but existed on two of our other servers. The article said to go to
> regedit under HKLM\Software\Microsoft\MSSQLServer\Tracking and rename the
> key
> {E07FDDA7-5A21-11d2-9DAD-00C04F79D434}. I renamed the key by putting an X
> in
> front of the name. This makes the SQL Server think that the Search service
> is
> not installed with SQL Server.
>
> After this, shut down all affected services and ran the SQL 2000 install
> from CD and did a Custom to modify the installation. All components were
> already checked except the Search, so checked the search. Did not uncheck
> other components or this would uninstall the other components.
>
> After doing this and rebooting, catalog creation appeared to work. Added
> item to database and number of items in catalog increased. Reapplied
> Service
> pack 4 to update the SQL search files. Rebooted. Our SQL app search
> function
> is now working.
>
> Hope this can help someone else out there.
>
> d Krage
>
> "John Kane" wrote:
>
>> D Krage,
>> As you have reviewed KB 277549 (Q277549) PRB: Unable to Build Full-Text
>> Catalog After You Modify MSSQLServer Logon Account Through [NT4.0)
>> Control
>> Panel [or Win2K Component Services] at
>> http://support.microsoft.com/default.aspx?scid=KB;EN-US;277549, did you
>> do
>> all of the "Steps to Reproduce Behavior", including stopping &
>> re-starting
>> the MSSearch & MSSQLServer?
>>
>> The error you're getting (Logon failure: unknown user name or bad
>> password)
>> is typical of the above. Additionally, have you or anyone else removed or
>> altered the BUILTIN\Administrators login? If so, can you re-add it or
>> alter
>> it back to its original values, including the master database and with
>> sysadmin rights?
>>
>> You may also want to review KB article 317746 "PRB: SQL Server Full-Text
>> Search Does Not Populate Catalogs" at
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;317746
>> However, since you've moved ahead with re-installing the MSSearch
>> components
>> via the procedures in KB 827449, the above most likely no longer applies.
>> At
>> this time, the following is the primary error: "Microsoft search service
>> cannot be administered under present user account." and usually, this
>> error
>> indicates a missing or altered BUILTIN\Administrators login, but you
>> might
>> also want to checkout the steps at
>> http://www.doughughes.net/index.cfm/page-blogLink/entryId-126 as others
>> have
>> had success with this method in correcting this error.
>>
>> Hope that helps!
>> John
>> --
>> SQL Full Text Search Blog
>> http://spaces.msn.com/members/jtkane/
>>
>>
>>
>> "d krage" <d krage@discussions.microsoft.com> wrote in message
>> news:4C845DC5-B0D7-4F45-A0FC-FB3DCF5F8427@microsoft.com...
>> > We are having problems with Full-Text searching...
>> >
>> > Recently we installed a SQL application that needs to access full-text
>> > searching.
>> >
>> > It gave the following error:
>> > "The crawl seed <MSSQL75://SQLServer/0539c240> in project <SQLServer
>> > SQL0001400006> cannot be accessed. Error: 8007052e - Logon failure:
>> > unknown
>> > user name or bad password."
>> >
>> > Upgrading from SQL2kSP3a to SQL2kSP4 didn't change our situation.
>> >
>> > Changing to system account following instructions in KB277549 also
>> > didn't
>> > fix the problem.
>> >
>> > We decided to reinstall the MSSearch service following commands in
>> > KB827449.
>> >
>> > We received the following error:
>> > "Full-Text Search is not enabled for the current database. Use
>> > sp_fulltext_database to enable full-text search for the database."
>> >
>> > Then we ran EXEC sp_fulltext_database 'enable'.
>> >
>> > This didn't resolve the problem as we received error message:
>> > "Microsoft search service cannot be administered under present user
>> > account."
>> >
>> > Current Status recap:
>> > * MSSearch service is started
>> > * In EM > Support Services > Full Text Search is running
>> > * In EM > R-click on Full-Text Catalogs > Rebuild All Catalogs produces
>> > error:
>> > "Microsoft search service cannot be administered under present user
>> > account."
>> > * In EM > R-click on catalog within Full-Text Catalog > Rebuild Catalog
>> > produces error:
>> > "Full-Text Search is not enabled for the current database. Use
>> > sp_fulltext_database to enable full-text search for the database."
>> >
>> > Not sure if this is user account related or bad install of MSSearch.
>> >
>> > Before reloading SQL or contacting MS Support, any advice is
>> > appreciated.
>> >
>> > Thanks!
>>
>>
>>