Can't create a new FT Catalog

Hi
We are having a problem creating a Full-Text catalog on our production
server and would appreciate any pointers to a solution.
The scenario is as follows:
1. Existing version of product running perfectly happily on production
server with Full Text indexing enabled and running. Lets call it Server 1
(Running SQL 2000 stndard sp3 on W2K Server )
2. New product developed on development server (Server 2). Full-text
indexing enabled and running.
3. Database transferred from Server 2 to Server 1 using DTS
4. Attempted to create FT catalog on new database on Server 1 using
Enterprise Manager. Failed, error given is:
An unknown full-text failure (80004005) occurred in function EnumCatalogs on
full-text catalog
Meanwhile it is still possible to create a new FT catalog on the existing db
(still on server 1)
We have done the usual web-searching to find a solution but anything turned
up appears to address the issue that it is impossible to create a FT catalog
on the server, this isn't our case, our problem is that we can't create the
FT index on the new db.
Any ideas?
Also if you need more info please ask.
Regards
Russell Wyatt
have you referred to this kb article yet?
http://support.microsoft.com/default...b;en-us;295772
"Russell Wyatt" <russellw_REMOVE_THIS_TO_REPLY_@.ihs.com.au> wrote in message
news:%23VcY80SxEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Hi
> We are having a problem creating a Full-Text catalog on our production
> server and would appreciate any pointers to a solution.
> The scenario is as follows:
> 1. Existing version of product running perfectly happily on production
> server with Full Text indexing enabled and running. Lets call it Server 1
> (Running SQL 2000 stndard sp3 on W2K Server )
> 2. New product developed on development server (Server 2). Full-text
> indexing enabled and running.
> 3. Database transferred from Server 2 to Server 1 using DTS
> 4. Attempted to create FT catalog on new database on Server 1 using
> Enterprise Manager. Failed, error given is:
> An unknown full-text failure (80004005) occurred in function EnumCatalogs
> on
> full-text catalog
> Meanwhile it is still possible to create a new FT catalog on the existing
> db
> (still on server 1)
> We have done the usual web-searching to find a solution but anything
> turned
> up appears to address the issue that it is impossible to create a FT
> catalog
> on the server, this isn't our case, our problem is that we can't create
> the
> FT index on the new db.
> Any ideas?
> Also if you need more info please ask.
> Regards
> Russell Wyatt
>
|||Thanks Hilary
Yes, we have referred to the article. (I say "we" because my colleague and
myself are trying to solve the problem). However, we can create a full-text
catalog on a different (already existing) database just not on the new one.
So catalog creation isn't completely broken, just for new databases. AFAIK
the kb article is useful if catalog creation doesn't work at all.
Russell
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eBqVoSTxEHA.2624@.TK2MSFTNGP11.phx.gbl...
> have you referred to this kb article yet?
> http://support.microsoft.com/default...b;en-us;295772
> "Russell Wyatt" <russellw_REMOVE_THIS_TO_REPLY_@.ihs.com.au> wrote in
message[vbcol=seagreen]
> news:%23VcY80SxEHA.2172@.TK2MSFTNGP14.phx.gbl...
1[vbcol=seagreen]
EnumCatalogs[vbcol=seagreen]
existing
>

cant connect to sql server, error

hi if someone could help, i appreciate: i have windows 2003 server and sql server 2000, i have a few machines connected via odbc and seems to work fine, my problem is when i try to make a new connection via odbc, appears: sql server odbc error: ConnectionOpen and server does not exist or access denied, i try few things, make a ping to the server and i got response, check the users and passwords, the mdac, check that the port 1433 is established in the client network utility, etc, now when i do a telnet to the server the port 1433, appears and error: couldnt connect,i believe this is why i cant make a odbc connection, but i cant figure it out how to make the port listens my petitions., now if itsa supossed to be closed, why the others machines cant connect just fine?

Do you already review the firewall for sql server ports?

http://support.microsoft.com/kb/287932/en