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 2000 instance from domain machines

Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use jus
t
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:

> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!