"Martijn Saly" <martijn@thany.org> wrote in message
news:%23P05%239g2FHA.1140@tk2msftngp13.phx.gbl...
> This is an old one, but I haven't been able to fix this just yet. We have
> a Win2k SP4 server which runs SQL server 2000 with the latest service
> packs and updates and everything. The server is a webserver that's being
> hosted at a hosting provider. There's absolutely nothing special or exotic
> about its configuration. Just Win2k, SQL2k and IIS5.
>
> The problem is that when I connect to this server from the EM, all options
> regarding fulltext indexing are disabled. With our local developemnt
> server we had this problem as well, but I solved it by executing "exec
> sp_fulltext_database 'enable'" and reconnecting to that server. But that
> doesn't work for the webserver...
>
> I know for a fact that fulltext indexing is working perfectly fine on the
> webserver. First of, because of the fact that there's a database that's
> already using fulltext indexing successfully. Secondly, because I can use
> the sp_fulltext_* procedures successfully. So why would the EM still
> refuse to let me use it?
>
> --
> Thanks,
>
> Martijn Saly

"Martijn Saly" <martijn@thany.org> wrote in message
news:%23P05%239g2FHA.1140@tk2msftngp13.phx.gbl...
> This is an old one, but I haven't been able to fix this just yet. We
> have a Win2k SP4 server which runs SQL server 2000 with the latest
> service packs and updates and everything. The server is a webserver
> that's being hosted at a hosting provider. There's absolutely nothing
> special or exotic about its configuration. Just Win2k, SQL2k and IIS5.
>
> The problem is that when I connect to this server from the EM, all
> options regarding fulltext indexing are disabled. With our local
> developemnt server we had this problem as well, but I solved it by
> executing "exec sp_fulltext_database 'enable'" and reconnecting to that
> server. But that doesn't work for the webserver...
>
> I know for a fact that fulltext indexing is working perfectly fine on
> the webserver. First of, because of the fact that there's a database
> that's already using fulltext indexing successfully. Secondly, because I
> can use the sp_fulltext_* procedures successfully. So why would the EM
> still refuse to let me use it?
>
> --
> Thanks,
>
> Martijn Saly

John Kane wrote:
> Martijn Saly,
> The behavior you are seeing is by design for SQL Server 2000 as the
> "Microsoft Search" service is an external service and cannot be directly
> controlled by the EM when accessed across the Internet or when the server is
> registered using an IP address or server alias. However, as you had found
> using the system stored procs sp_fulltext_* does succeed. For now, your
> best solution is to continue to use the sp_fulltext_* procedures.

"Martijn Saly" <martijn@thany.org> wrote in message
news:Od$BhCv2FHA.3876@TK2MSFTNGP09.phx.gbl...
> John Kane wrote:
>> Martijn Saly,
>> The behavior you are seeing is by design for SQL Server 2000 as the
>> "Microsoft Search" service is an external service and cannot be directly
>> controlled by the EM when accessed across the Internet or when the server
>> is registered using an IP address or server alias. However, as you had
>> found using the system stored procs sp_fulltext_* does succeed. For now,
>> your best solution is to continue to use the sp_fulltext_* procedures.
>
> So if the EM can't find the search service, it decides it is not started?
> I wonder why the EM doesn't just try to do what I ask and then give an
> error if it didn't work (for whatever reason).
>
> So if the Search service can't be found or can't be accessed, the EM
> shouldn't simply decide for itself that the service is stopped. That's
> just very unhandy (or as some people would say: MS logic) ;)
>
> Do you know whether this is fixed with SQL 2005?
>
> --
> Thanks,
>
> Martijn Saly