Cannot enable full text indexing

I also have the 'greyed-out' menu problem for full-text indexing and have
researched every post and article available.
The MSSEARCH service is running, and the SQL Server 2000 is upgraded through
SP3a. The Security tab for the server is set for "SQL Server and Windows"
authentication and the Startup Service Account is "System account". The EM
will not allow a change to "This account ... LocalSystem"--it changes back to
"System account" when the change is made.
I have also tried executing sp_fulltext_database in Query Analyzer and
receive this error:
"Full-Text Search is not installed, or a full-text component cannot be
loaded."
There are no icons for full-text indexing under Support Services in EM and I
am wondering if SQL Server itself needs to be re-installed. I have
re-installed SP3, but have not done a complete SQL Server re-install.
I am running this server under XP Professional on a local machine.
What is missing here?
seeker
can you run this script on your problem machine? Post the results back here.
save this script as a vbs file and run it from the command prompt
You many need to do a cscript.exe //H:CScript if you get a lot of dialog
boxes.
Set objSearchAdmin=CreateObject("MSSearch.Admin")
Set infoNT=CreateObject("WinNTSystemInfo")
wscript.echo"Host Name: "& objSearchAdmin.HostName
objSearchAdmin.HostName =InfoNT.ComputerName
Set objApplications=objSearchAdmin.Applications
wscript.echo "Number of Search Applications serviced by this Build Server: "
& objApplications.Count
for each application in objApplications
wscript.echo "Application Name: " & application.name
next
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"seeker" <seeker@.discussions.microsoft.com> wrote in message
news:75D2062B-0704-4847-9388-0D16866D9AF0@.microsoft.com...
> I also have the 'greyed-out' menu problem for full-text indexing and have
> researched every post and article available.
> The MSSEARCH service is running, and the SQL Server 2000 is upgraded
through
> SP3a. The Security tab for the server is set for "SQL Server and Windows"
> authentication and the Startup Service Account is "System account". The
EM
> will not allow a change to "This account ... LocalSystem"--it changes back
to
> "System account" when the change is made.
> I have also tried executing sp_fulltext_database in Query Analyzer and
> receive this error:
> "Full-Text Search is not installed, or a full-text component cannot be
> loaded."
> There are no icons for full-text indexing under Support Services in EM and
I
> am wondering if SQL Server itself needs to be re-installed. I have
> re-installed SP3, but have not done a complete SQL Server re-install.
> I am running this server under XP Professional on a local machine.
> What is missing here?
> --
> seeker
|||Thank you for your note, Hilary.
I resolved this problem with a re-install of SQL Server (Developer). When I
put in the CD, I discovered that it had been installed with Full Text
Indexing unchecked, which is the default.
I took it all the way through the SP3 update, and at the point the Full Text
Indexing selection was enabled.
"Hilary Cotter" wrote:

> can you run this script on your problem machine? Post the results back here.
> save this script as a vbs file and run it from the command prompt
> You many need to do a cscript.exe //H:CScript if you get a lot of dialog
> boxes.
> Set objSearchAdmin=CreateObject("MSSearch.Admin")
> Set infoNT=CreateObject("WinNTSystemInfo")
> wscript.echo"Host Name: "& objSearchAdmin.HostName
> objSearchAdmin.HostName =InfoNT.ComputerName
> Set objApplications=objSearchAdmin.Applications
> wscript.echo "Number of Search Applications serviced by this Build Server: "
> & objApplications.Count
> for each application in objApplications
> wscript.echo "Application Name: " & application.name
> next
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "seeker" <seeker@.discussions.microsoft.com> wrote in message
> news:75D2062B-0704-4847-9388-0D16866D9AF0@.microsoft.com...
> through
> EM
> to
> I
>
>
sql

Cannot edit SQL Job in Management Studio.

Hello,

In SQL Management Studio, I cannot edit a SQL Job. When I double-click on a sql job or select properties on the context menu, I get a "New Job" window. This was working fine a few days back. Any help will be appreciated.

Thanks,

Ashish.

What happens when you right click and select properties on the job?|||Try installing SQL Server 2005 SP2 on the client. This should solve your problem.|||

I installed SP2 on the client. It didn't help. Thanks for replying back to my post.

Also, we have 3 other developers in the team who are having the same problem.

|||

Thanks for your reply. When I right-click and select properties, I still get the "New Job" window.

|||It could be an issues with SQL tools, have you tried accessing the same job from another client's machine.|||

Hi Satya,

Thanks for your reply. I tried editing the sql job from another computer. I was able to edit it. I know it's issue with the client tools, but cannot figure out to resolve the problem. I installed SP2 on the client side. That also didn't help.

|||You may need to uninstall the client tools, and reinstall them, and also add SP2 again.

cannot debug class liberary sproc

im trying to debug a sproc that was written as a class liberary, in c#. i go to the debug menu in visual studio, and click "attach to process". i attach to the sqlsevr process. but now, any breakpoints i create give the message :

"he breakpoint will not currently be hit. no symbols have been loaded for this document"

and no matter how i execute the sproc in sql server, my breakpoints are never hit. what is wrong here?

Have you uploaded the debug symbols file to SQL Server?

ALTER ASSEMBLY your_asm_name
add file from 'some location'

You better check the syntax for ALTER ASSEMBLY as I wrote it from memory and I don't have BOL handy at the moment.

Niels|||Hmm, I was almost certain I had replied to this a couple of minutes ago (I apologize if this post appears twice).

Have you uploaded the debug symbols file from your assembly to the database?

The syntax is as follows:

ALTER ASSEMBLY your_asm_name
ADD FILE FROM 'path_to_debug_symbols'

You better check the syntax above, as I wrote it from memory and I don't have BOL handy.

Nielssql

Cannot connect to SQL 2000 remotely

On the server, from the Start menu, point to All Programs, point to
Microsoft SQL Server, and then click Server Network Utility. That utility
should help you understand if SQL Server is using the IPX/SPX or TCP/IP
protocols, which might indicate a problem. On the client there is a similar
program, the Client Network Utility. Obviously the client and server should
be using the same protocols.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
> I'm trying to install a bespoke application for a new client, and am
> embarassed by not being able to connect to their DB Server.
> The server and clients are XP all running on a workgroup called OFFICE
> File access is not problem and the DB Server name appears in a dropdown
> box of SQL servers on the network - e.g. when trying to create an ODBC
> DSN.
> The SQL Server is now configured to accept Windows and SQL authentication
> connection requests - and restarted.
> I have switched off or uninstalled everything that looks like a firewall
> on both server and clients.
> When trying to set up local ODBC DSN to connect as sa, I can connect no
> problem, but from one of the client laptops I just get the error:
> "Access denied or SQL Server does not exist"
> Can anyone tell me where else to look or what else to try?
> Is there a step by step procedure which could take me to the cause of the
> problem?
> The network is a wireless Lan - and IPX/SPX is featuring in the network
> stack. Could that be something to do with it?
> Any help very very much appreaciated!
> Thank you
> Clive (London UK)
>
>
>
>
Glad to help. I recognize customers stress and confusion as a problem that
we (Microsoft) often cause... and have an obligation to resolve.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
news:O7J9R4pzHHA.3400@.TK2MSFTNGP03.phx.gbl...
> Apologies for flame throwing. Default of DisableNetworkProtocols WAS the
> problem, but in any case
> thank for taking the time and trouble to get back to me Rick.
> Clive Elsworth
>
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
>