Are you using package configurations?

Are you deploying it to the server using the build and deploy?

Might want to put this in a SQL Server 2000 forum, but here's a head start:

http://www.codeproject.com/KB/database/xyprocedure.aspx

I'm guessing you just removed it from SQL Server and not the builtin administrators group in windows. Go have a look to make sure it's still there. You could possibly...

we reaped huge benefits from breaking a stored procedure down like that. We ended up having a master stored procedure that had the most used condition in the first If...

a few things to note.

-running multiple instances means that you have to manually set the memory for each instance.

-I believe x86 does better with multiple instances.

-Fire up profiler and use...

funny thing is, the registry didn't show the expected entries but the folders did even after uninstall.

I'm in the middle of it now.

You could try to audit login events in a SQL Server profiler trace. That wouldn't go backwards for you though.

I haven't gotten to dig into this much but here's a link:

http://sqlcat.com/[/url]

you probably want to check some of the flash sites that have tutorials. It's been a while since I did that but I'm assuming that there are still some good...

Do you have a network guy you can check with?

Does this article help? http://www.sqlservercentral.com/articles/SS2K5+-+Full+Text+Searching/2819/[/url]

I believe you have to drop and recreate if I remember correctly.

well, that's the x86 install for that sp. Are you positive you aren't running IA64 or x64?

I've had better luck with the commands vs the gui.

EXECUTE sp_addlinkedserver @server='remoteserver', @srvproduct='SQL Server'

EXECUTE sp_addlinkedsrvlogin @rmtsrvname='remoteserver', @useself='false',

@rmtuser='username', @rmtpassword='password'

I stopped trying to figure that out.

Regarding #3 then.

I have had a similar experience where it fixed it:

Look here: http://support.microsoft.com/kb/839279