Can't enable Full Text on database

Got a strange problem.
Had a SQL 7.0 Box with FTS on a database. Worked fine except for one quirk
we never tracked down. Starting up the MSSearch Service would fail 1/2 the
time due to timeout. Other 1/2 would take a long time (like sometimes an
hour) to start.
Upgraded to SQL 2000, no SP.
Upgrade went fine, similar startup problems.
Applied SP4.
Got the usual warning about having to recreate indices, etc. Not a problem
since we were releasing new code specifically for SQL 2000 FT.
Now... well it just doesn't work.
For example, if I try to start an index build on a table, I get Error 15601:
Full-Text Search is not enabled for the current database...
Ok, no problem.. try
sp_fulltext_database 'enable'
get
Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line 46
The Microsoft Search service cannot be administered under the present user
account
First thought was try to synchronize the passwords (i.e. start/stop SQL
Server, change to local account and then back to the domain account so that
MSSearch can talk to it.)
No Joy.
So, at this point I'm either facing calling Microsoft, or taking the server
offline for a day while I uninstall SQL 2000, reinstall it and re-attach the
databases and hope that works.
Suggestions?
--
Greg D. Moore
President Green Mountain Software
Personal: http://stratton.greenms.com
SQL Server Consulting sql at greenms.com
Hi Greg,
Yep, I remember your SQL 7.0 box & the related FTS problems as FTS in SQL
7.0 was problematic at best...
In regards to error "The Microsoft Search service cannot be administered
under the present user account", have you removed or altered the
BUILTIN\Administrators login? If so, then this breaks FTS as the MSSearch
service uses this account to login into SQL Server. If you cannot add back
this login or cannot alter the login back to all of its default for security
reasons, you can use the following SQL code to enable the localsystem
account to have the proper security as a workaround:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
See KB article 263712 "INF: How To Prevent Windows NT Administrators From
Administering a Clustered SQL Server" at
http://support.microsoft.com/default...;EN-US;q263712 for details.
Hope that helps,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:8Ln0f.8178$QE1.857@.newsread2.news.atl.earthli nk.net...
> Got a strange problem.
> Had a SQL 7.0 Box with FTS on a database. Worked fine except for one
> quirk
> we never tracked down. Starting up the MSSearch Service would fail 1/2
> the
> time due to timeout. Other 1/2 would take a long time (like sometimes an
> hour) to start.
> Upgraded to SQL 2000, no SP.
> Upgrade went fine, similar startup problems.
> Applied SP4.
> Got the usual warning about having to recreate indices, etc. Not a
> problem
> since we were releasing new code specifically for SQL 2000 FT.
> Now... well it just doesn't work.
> For example, if I try to start an index build on a table, I get Error
> 15601:
> Full-Text Search is not enabled for the current database...
> Ok, no problem.. try
> sp_fulltext_database 'enable'
> get
> Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line
> 46
> The Microsoft Search service cannot be administered under the present user
> account
> First thought was try to synchronize the passwords (i.e. start/stop SQL
> Server, change to local account and then back to the domain account so
> that
> MSSearch can talk to it.)
> No Joy.
> So, at this point I'm either facing calling Microsoft, or taking the
> server
> offline for a day while I uninstall SQL 2000, reinstall it and re-attach
> the
> databases and hope that works.
> Suggestions?
>
>
> --
> --
> Greg D. Moore
> President Green Mountain Software
> Personal: http://stratton.greenms.com
> SQL Server Consulting sql at greenms.com
>
|||"John Kane" <jt-kane@.comcast.net> wrote in message
news:eDz9GhVyFHA.720@.TK2MSFTNGP15.phx.gbl...
> Hi Greg,
> Yep, I remember your SQL 7.0 box & the related FTS problems as FTS in SQL
> 7.0 was problematic at best...
Oh good. :-)

> In regards to error "The Microsoft Search service cannot be administered
> under the present user account", have you removed or altered the
> BUILTIN\Administrators login?
Not that I am aware of.

> If so, then this breaks FTS as the MSSearch
> service uses this account to login into SQL Server. If you cannot add back
> this login or cannot alter the login back to all of its default for
security
> reasons, you can use the following SQL code to enable the localsystem
> account to have the proper security as a workaround:
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
Tried this, still no joy.
Did notice the database in question the name dbo was mapped to a login
called MONITOR (one of our internal accounts) instead of sa or
domain\administrator.
I've removed that mapping. So far hasn't helped.

> See KB article 263712 "INF: How To Prevent Windows NT Administrators From
> Administering a Clustered SQL Server" at
> http://support.microsoft.com/default...;EN-US;q263712 for
details.
>
Nothing here stood out.
Thanks though.

> Hope that helps,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
message[vbcol=seagreen]
> news:8Ln0f.8178$QE1.857@.newsread2.news.atl.earthli nk.net...
an[vbcol=seagreen]
Line[vbcol=seagreen]
user
>
|||Hi Greg,
Hmm... It is possible it is something new &/or affected by SP4. I take it
you upgraded to SP4 directly from RTM, and not RTM to SP3 then to SP4.
Correct? I've not heard of any new FTS related bugs in SP4 that are
directly related to this error. However, there are two FIX kb articles
(http://support.microsoft.com/?kbid=900390 - post-SP4 and
http://support.microsoft.com/default...b;en-us;890043 - post SP3)
that I've blogged about in August, neither are well written IMHO.
The below workaround has in the past resolved this issue, however, in all
cases it was pre-SP4. As this is related to a possible SP4 issue, you might
want to open that support issue with MS PSS SQL Server support... :-(
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:zFP0f.9074$vw6.4605@.newsread1.news.atl.earthl ink.net...
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:eDz9GhVyFHA.720@.TK2MSFTNGP15.phx.gbl...
> Oh good. :-)
>
> Not that I am aware of.
> security
> Tried this, still no joy.
> Did notice the database in question the name dbo was mapped to a login
> called MONITOR (one of our internal accounts) instead of sa or
> domain\administrator.
> I've removed that mapping. So far hasn't helped.
>
> details.
> Nothing here stood out.
> Thanks though.
> message
> an
> Line
> user
>

Cant Create Subscription...

I've got a strange problem that I can't quite figure out. Whenever I go to setup a new subscription for a report (any report) I can't select a schedule or create the subscription.
I get to the Subscription page, but pressing any of the buttons: "Ok", "Cancel", "Select Schedule" does nothing.
Anyone else ever have this issue?
Any feedback would be greatly appreciated.

Hi
can you able to see SubscriptionProperties.aspx Page after clicking on New Subscription.
Thanx
Rohit|||

Yeah, pressing "New Subscription" takes me to the form (SubscriptionProperties.aspx), but not matter what button I press on the form - Ok, Cancel, Select Schedule... nothing happens.
It's as if you were creating an .aspx form and set "AutoPostBack" on a control to false. Clicking on any of the buttons does nothing. Therefore, I'm not able to create a new subscription or alter
any of the subscriptions schedules that I currently have.
I've restarted the reportserver service and I've restarted the application pool. Neither helps.

|||

Just wanted to follow up on this in case that someone else runs accross this. This was a framework issue with SP1. Not really related to Reporting Services, but possibly relevant nonetheless.

http://channel9.msdn.com/showpost.aspx?postid=21650

Can't create fulltextcatalogs

Hello
I have a strange problem. I'm trying to create some fulltext catalogs using
management studio 2005, and it works great. But on one table I have a
composite key (?) PRIMARY KEY(A,B), and when I rightclick table and pick
create new fulltext catalog and press next it says that no indexes are
avalible :(
Howto solve this? Mess with the table and set just A or B as primary key?
doesn't feel right to do that.
/Lassefull text indexes can't be created on composite keys. Create a unique index
on another column or add an identity column and create a unique index on
that column.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Lasse Edsvik" <lasse@.nospam.com> wrote in message
news:e%23O6ppAnGHA.964@.TK2MSFTNGP05.phx.gbl...
> Hello
> I have a strange problem. I'm trying to create some fulltext catalogs
> using
> management studio 2005, and it works great. But on one table I have a
> composite key (?) PRIMARY KEY(A,B), and when I rightclick table and pick
> create new fulltext catalog and press next it says that no indexes are
> avalible :(
> Howto solve this? Mess with the table and set just A or B as primary key?
> doesn't feel right to do that.
> /Lasse
>

Cant copy database, strange error

I'm trying to copy a database from my web host to local Sql Server 2005 instance using the Copy Database wizard. I get this error:

An exception occurred while executing a Transact-SQL statement or batch.

Server user 'celestine' is not a valid user id database 'db2'.

However, 'db2' isn't the database I was trying to copy! I am trying to copy db1, but this error is complaining about db2, which is in fact somebody else's database that I don't have a login for. Why am I getting an error about db2 when I'm not trying to do anything with db2?

I can however export the tables from db1 just fine using Export. But then I have to go back and generate script to re-create the stored procs, views, etc., so it is rather tedious to do it that way.

This may be possible. For example if there is a view in db1 which references a table in db2, and the celestine login does not have access to db2, you may encounter this error.

So to avoid such issue, you can move/copy database by taking a full backup of the source database and then restore it on the destination server.

|||

Good idea but -- No, this is not the case. This is a shared hosting situation, the 2nd database is owned by someone else, I have absolutely no access to it at all. There is no relationship whatsoever between the databases.

I can't do a backup/restore either because I don't have access to the remote filesystem.

|||

Urgh...that's really a trouble. Then check whether your login has sufficient permissions to perform copy database task:

Required permissions

For the Copy Database Wizard to work, you must have the correct permissions, depending on how you are copying the database, as follows:

For the Detach and Attach Method, you must be a member of thesysadmin fixed server role on the both source and destination servers.

|||Right. But a) I do have correct permissions for both source/destination for the database I'm trying to copy, and b) The error is not pertaining to the database I want to copy. The error mentions a different database, that I have zero permissions for, that I will never have permissions for, that I don't want permissions for. I am trying to copy db1 and the error says "you don't have permissions for db2". Why is it even checking anything for db2?