I am trying to "Define full text indexing" on a table but
when it attempts to create the catelog, I get the
following error:
Execution of the full text operation failed. The
directory name is invalid.
Any ideas? I check to ensure the directory is correct....
Mike B
What is the path? Normally if the path is too long you get a very specific
error message stating that. Also are you trying to create your catalog on a
fixed disk?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mike B" <mbujak@.psi-hci.com> wrote in message
news:0a7701c46e71$f0b72230$a301280a@.phx.gbl...
> I am trying to "Define full text indexing" on a table but
> when it attempts to create the catelog, I get the
> following error:
> Execution of the full text operation failed. The
> directory name is invalid.
> Any ideas? I check to ensure the directory is correct....
> Mike B
|||
>--Original Message--
>What is the path? Normally if the path is too long you
get a very specific
>error message stating that. Also are you trying to
create your catalog on a[vbcol=seagreen]
>fixed disk?
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"Mike B" <mbujak@.psi-hci.com> wrote in message
>news:0a7701c46e71$f0b72230$a301280a@.phx.gbl...
but[vbcol=seagreen]
correct....
>
>.
>
I was using the default path :
C:\Program Files\Microsoft SQL Server\MSSQL\FTDATA
I also created a testing folder on C where the catelog
directory name would have been
C:\Tesging
Fixed disk, yes, right on the server c:
Mike B
|||Mike,
What is the <value> for the following registry key on the server where this
problem exists?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\<named_instance>\MSSQLServer
FullTextDefaultPath= <value>
Do you get the same error if you specify a specific path for your new FT
Catalog name <Cat_Address>?
There should be no invisible or un-printable characters in the above <value>
for FullTextDefaultPath. Could you use Regedit and delete the current string
and re-enter it? In the past I've had customer's who had un-printable
(un-viewable) characters in this Registry key value cause similar
problems...
Regards,
John
<anonymous@.discussions.microsoft.com> wrote in message
news:0b1d01c46e7a$38535f70$a301280a@.phx.gbl...
> get a very specific
> create your catalog on a
> but
> correct....
> I was using the default path :
> C:\Program Files\Microsoft SQL Server\MSSQL\FTDATA
> I also created a testing folder on C where the catelog
> directory name would have been
> C:\Tesging
> Fixed disk, yes, right on the server c:
> Mike B
>
Showing posts with label butwhen. Show all posts
Showing posts with label butwhen. Show all posts
Wednesday, March 21, 2012
Monday, March 19, 2012
Invalid Descriptor Index on SQL 2005 sp 1
We have an app that use ODBC and works on SQL server 2000 but
when running the same app and same ODBC driver on 2005 sp 1 we get
Invalid Descriptor Index
Why?
Regards,
DavidMaybe if you show us the actual code that is causing the issue we could make
a more informed answer.
Andrew J. Kelly SQL MVP
"David@.StreamServe" <david.svennevid@.gmail.com> wrote in message
news:1147860037.905325.193680@.j55g2000cwa.googlegroups.com...
> We have an app that use ODBC and works on SQL server 2000 but
> when running the same app and same ODBC driver on 2005 sp 1 we get
> Invalid Descriptor Index
>
> Why?
> Regards,
> David
>
when running the same app and same ODBC driver on 2005 sp 1 we get
Invalid Descriptor Index
Why?
Regards,
DavidMaybe if you show us the actual code that is causing the issue we could make
a more informed answer.
Andrew J. Kelly SQL MVP
"David@.StreamServe" <david.svennevid@.gmail.com> wrote in message
news:1147860037.905325.193680@.j55g2000cwa.googlegroups.com...
> We have an app that use ODBC and works on SQL server 2000 but
> when running the same app and same ODBC driver on 2005 sp 1 we get
> Invalid Descriptor Index
>
> Why?
> Regards,
> David
>
Subscribe to:
Posts (Atom)