Problem running full text search - it's broken!

I have a 2-tier application
The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
This works fine for ALL database calls, except when it requires a full text
query. The error message received is:
Microsoft OLE DB Provider for SQL Server error '80040e14'
Execution of a full-text operation failed. The catalog does not exist or is
currently unavailable. Please retry the action again later and if this
symptom persists, contact the system administrator.
However...I know that the full text catalogue DOES exist on the data tier
(I've rebuilt & repopulated it).
I also have an "identical" pair of machines and it works fine on that
one... By identical, I mean all the ASP code running under IIS is the
same.
No idea what I should be checking. The ADODB connection is identical on
both machines (uses a SQL Server account with identical access permissions)
and SQLServer is running under the ADMINISTRATOR account on both servers.
Thanks
Griff
Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Griff" <Howling@.The.Moon> wrote in message
news:e9f62cw3FHA.3628@.TK2MSFTNGP12.phx.gbl...
> I have a 2-tier application
> The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
> This works fine for ALL database calls, except when it requires a full
text
> query. The error message received is:
> --
> Microsoft OLE DB Provider for SQL Server error '80040e14'
> Execution of a full-text operation failed. The catalog does not exist or
is
> currently unavailable. Please retry the action again later and if this
> symptom persists, contact the system administrator.
> --
> However...I know that the full text catalogue DOES exist on the data tier
> (I've rebuilt & repopulated it).
> I also have an "identical" pair of machines and it works fine on that
> one... By identical, I mean all the ASP code running under IIS is the
> same.
> No idea what I should be checking. The ADODB connection is identical on
> both machines (uses a SQL Server account with identical access
permissions)
> and SQLServer is running under the ADMINISTRATOR account on both servers.
> Thanks
> Griff
>
>
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hi Hilary
I'm afraid not. The only messages state that the catalogues were built
successfully, e.g.:
Master merge has completed on
d:\mssql\ftdata\sql0000700005\build\indexer\cifile s.
The only warning mentioned is:
SuperSocket info: (SpnRegister) : Error 1355.
Griff
|||Griff,
I think we need additional information from the server to understand why
this error OLE DB '80040e14' is being raised and that you have confirmed
that the full text catalogue DOES exist on this server. Could you set trace
flag 7300 on, you can get extended OLEDB error info?
dbcc traceon (3604, 7300)
Could you also post the exact CONTAINS* or FREETEXT* query that you're using
along with the search word or phrase, and re-run the query and post the
extended OLEDB error info?
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Griff" <Howling@.The.Moon> wrote in message
news:uUpfG%2343FHA.3628@.TK2MSFTNGP12.phx.gbl...
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Hi Hilary
> I'm afraid not. The only messages state that the catalogues were built
> successfully, e.g.:
> Master merge has completed on
> d:\mssql\ftdata\sql0000700005\build\indexer\cifile s.
> The only warning mentioned is:
> SuperSocket info: (SpnRegister) : Error 1355.
> Griff
>
sql

Problem running full text search - it's broken!

I have a 2-tier application
The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
This works fine for ALL database calls, except when it requires a full text
query. The error message received is:
--
Microsoft OLE DB Provider for SQL Server error '80040e14'
Execution of a full-text operation failed. The catalog does not exist or is
currently unavailable. Please retry the action again later and if this
symptom persists, contact the system administrator.
--
However...I know that the full text catalogue DOES exist on the data tier
(I've rebuilt & repopulated it).
I also have an "identical" pair of machines and it works fine on that
one... By identical, I mean all the ASP code running under IIS is the
same.
No idea what I should be checking. The ADODB connection is identical on
both machines (uses a SQL Server account with identical access permissions)
and SQLServer is running under the ADMINISTRATOR account on both servers.
Thanks
GriffAre there any pertinent messages from MSSearch or MSSCI in the event log?
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Griff" <Howling@.The.Moon> wrote in message
news:e9f62cw3FHA.3628@.TK2MSFTNGP12.phx.gbl...
> I have a 2-tier application
> The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
> This works fine for ALL database calls, except when it requires a full
text
> query. The error message received is:
> --
> Microsoft OLE DB Provider for SQL Server error '80040e14'
> Execution of a full-text operation failed. The catalog does not exist or
is
> currently unavailable. Please retry the action again later and if this
> symptom persists, contact the system administrator.
> --
> However...I know that the full text catalogue DOES exist on the data tier
> (I've rebuilt & repopulated it).
> I also have an "identical" pair of machines and it works fine on that
> one... By identical, I mean all the ASP code running under IIS is the
> same.
> No idea what I should be checking. The ADODB connection is identical on
> both machines (uses a SQL Server account with identical access
permissions)
> and SQLServer is running under the ADMINISTRATOR account on both servers.
> Thanks
> Griff
>
>|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hi Hilary
I'm afraid not. The only messages state that the catalogues were built
successfully, e.g.:
Master merge has completed on
d:\mssql\ftdata\sql0000700005\build\indexer\cifiles.
The only warning mentioned is:
SuperSocket info: (SpnRegister) : Error 1355.
Griff|||Griff,
I think we need additional information from the server to understand why
this error OLE DB '80040e14' is being raised and that you have confirmed
that the full text catalogue DOES exist on this server. Could you set trace
flag 7300 on, you can get extended OLEDB error info?
dbcc traceon (3604, 7300)
Could you also post the exact CONTAINS* or FREETEXT* query that you're using
along with the search word or phrase, and re-run the query and post the
extended OLEDB error info?
Thanks,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Griff" <Howling@.The.Moon> wrote in message
news:uUpfG%2343FHA.3628@.TK2MSFTNGP12.phx.gbl...
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
>> Are there any pertinent messages from MSSearch or MSSCI in the event log?
> Hi Hilary
> I'm afraid not. The only messages state that the catalogues were built
> successfully, e.g.:
> Master merge has completed on
> d:\mssql\ftdata\sql0000700005\build\indexer\cifiles.
> The only warning mentioned is:
> SuperSocket info: (SpnRegister) : Error 1355.
> Griff
>

Problem running full text search - it's broken!

I have a 2-tier application
The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
This works fine for ALL database calls, except when it requires a full text
query. The error message received is:
Microsoft OLE DB Provider for SQL Server error '80040e14'
Execution of a full-text operation failed. The catalog does not exist or is
currently unavailable. Please retry the action again later and if this
symptom persists, contact the system administrator.
However...I know that the full text catalogue DOES exist on the data tier
(I've rebuilt & repopulated it).
I also have an "identical" pair of machines and it works fine on that
one... By identical, I mean all the ASP code running under IIS is the
same.
No idea what I should be checking. The ADODB connection is identical on
both machines (uses a SQL Server account with identical access permissions)
and SQLServer is running under the ADMINISTRATOR account on both servers.
Thanks
Griff
Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Griff" <Howling@.The.Moon> wrote in message
news:e9f62cw3FHA.3628@.TK2MSFTNGP12.phx.gbl...
> I have a 2-tier application
> The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
> This works fine for ALL database calls, except when it requires a full
text
> query. The error message received is:
> --
> Microsoft OLE DB Provider for SQL Server error '80040e14'
> Execution of a full-text operation failed. The catalog does not exist or
is
> currently unavailable. Please retry the action again later and if this
> symptom persists, contact the system administrator.
> --
> However...I know that the full text catalogue DOES exist on the data tier
> (I've rebuilt & repopulated it).
> I also have an "identical" pair of machines and it works fine on that
> one... By identical, I mean all the ASP code running under IIS is the
> same.
> No idea what I should be checking. The ADODB connection is identical on
> both machines (uses a SQL Server account with identical access
permissions)
> and SQLServer is running under the ADMINISTRATOR account on both servers.
> Thanks
> Griff
>
>
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hi Hilary
I'm afraid not. The only messages state that the catalogues were built
successfully, e.g.:
Master merge has completed on
d:\mssql\ftdata\sql0000700005\build\indexer\cifile s.
The only warning mentioned is:
SuperSocket info: (SpnRegister) : Error 1355.
Griff
|||Griff,
I think we need additional information from the server to understand why
this error OLE DB '80040e14' is being raised and that you have confirmed
that the full text catalogue DOES exist on this server. Could you set trace
flag 7300 on, you can get extended OLEDB error info?
dbcc traceon (3604, 7300)
Could you also post the exact CONTAINS* or FREETEXT* query that you're using
along with the search word or phrase, and re-run the query and post the
extended OLEDB error info?
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Griff" <Howling@.The.Moon> wrote in message
news:uUpfG%2343FHA.3628@.TK2MSFTNGP12.phx.gbl...
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Hi Hilary
> I'm afraid not. The only messages state that the catalogues were built
> successfully, e.g.:
> Master merge has completed on
> d:\mssql\ftdata\sql0000700005\build\indexer\cifile s.
> The only warning mentioned is:
> SuperSocket info: (SpnRegister) : Error 1355.
> Griff
>

Problem running full text search - it's broken!

I have a 2-tier application
The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
This works fine for ALL database calls, except when it requires a full text
query. The error message received is:
--
Microsoft OLE DB Provider for SQL Server error '80040e14'
Execution of a full-text operation failed. The catalog does not exist or is
currently unavailable. Please retry the action again later and if this
symptom persists, contact the system administrator.
However...I know that the full text catalogue DOES exist on the data tier
(I've rebuilt & repopulated it).
I also have an "identical" pair of machines and it works fine on that
one... By identical, I mean all the ASP code running under IIS is the
same.
No idea what I should be checking. The ADODB connection is identical on
both machines (uses a SQL Server account with identical access permissions)
and SQLServer is running under the ADMINISTRATOR account on both servers.
Thanks
GriffAre there any pertinent messages from MSSearch or MSSCI in the event log?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Griff" <Howling@.The.Moon> wrote in message
news:e9f62cw3FHA.3628@.TK2MSFTNGP12.phx.gbl...
> I have a 2-tier application
> The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
> This works fine for ALL database calls, except when it requires a full
text
> query. The error message received is:
> --
> Microsoft OLE DB Provider for SQL Server error '80040e14'
> Execution of a full-text operation failed. The catalog does not exist or
is
> currently unavailable. Please retry the action again later and if this
> symptom persists, contact the system administrator.
> --
> However...I know that the full text catalogue DOES exist on the data tier
> (I've rebuilt & repopulated it).
> I also have an "identical" pair of machines and it works fine on that
> one... By identical, I mean all the ASP code running under IIS is the
> same.
> No idea what I should be checking. The ADODB connection is identical on
> both machines (uses a SQL Server account with identical access
permissions)
> and SQLServer is running under the ADMINISTRATOR account on both servers.
> Thanks
> Griff
>
>|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hi Hilary
I'm afraid not. The only messages state that the catalogues were built
successfully, e.g.:
Master merge has completed on
d:\mssql\ftdata\sql0000700005\build\inde
xer\cifiles.
The only warning mentioned is:
SuperSocket info: (SpnRegister) : Error 1355.
Griff|||Griff,
I think we need additional information from the server to understand why
this error OLE DB '80040e14' is being raised and that you have confirmed
that the full text catalogue DOES exist on this server. Could you set trace
flag 7300 on, you can get extended OLEDB error info?
dbcc traceon (3604, 7300)
Could you also post the exact CONTAINS* or FREETEXT* query that you're using
along with the search word or phrase, and re-run the query and post the
extended OLEDB error info?
Thanks,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Griff" <Howling@.The.Moon> wrote in message
news:uUpfG%2343FHA.3628@.TK2MSFTNGP12.phx.gbl...
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Hi Hilary
> I'm afraid not. The only messages state that the catalogues were built
> successfully, e.g.:
> Master merge has completed on
> d:\mssql\ftdata\sql0000700005\build\inde
xer\cifiles.
> The only warning mentioned is:
> SuperSocket info: (SpnRegister) : Error 1355.
> Griff
>

Problem Related to Package execution in SSIS

Hi,

I have the hierarchy of packages..

there are three levels..

first package (say L1) calls two child packages.(say L2_1 , L2_2)

the parameters are passed to L2_1 from L1 and it executes completely and successfully.

next step is L1 calls L2_2 without any parameters.. and package fails with error as execution of L2_2 failed.

when I executed L2_2 individually it successfully executes.

L2_2 itself calls 5 other packages (at level 3)..

Am not able to identify the possible reason for failure..

I suggest you turn on package logging in each package (right click on the control flow and select logging) and then come back here with specific error messages once captured.|||

Thanks for you help phil...

now I can see the errors due to which my package is failing..

sql

Problem of Parent-Child package with ASP.Net

I have an ASP.NET application that calls a SSIS package. The SSIS package internally calls some other child packages. I observed that sometimes some child pacakges are not even called by the parent. and the behaviour is very indeterminate. sometimes they work fine. sometimes they don't. There is no clue available for this behaviour when the pacakges are not executed. (One general observation is that the memory consumption is very high. but that is the case always.)

I have enabled logging on all child packages. The log is not updated at all when the child packages failed to execute. i.e. the package execution does not start.

Could somebody explain why this is happening? any suggestions/ similar experiences?

Regards

Saurabh

One more observation: if i run the same parent package as a stand-alone. (i.e. not through the asp.net application) it always executes fine. it calls all the child packages very well always. what is different in the asp.net context?

Problem looping DTS and BCP within a Stored procedure

All,

This is the scenerio

SP=Stored Procedure

I call SP1 which calls a DTS package.

DTS package calls SP2 and SP2 calls SP3 and SP 4 using an IF condition

SP3 has 3 BCP OUT commands after which it calls SP1 again

Now, the problem is that if I follow all the steps, then only 1 of the BCP command executes and the control exits out of SP3 and returns control to SP1.

If I ignore SP1 and DTS and run SP2 independently, then all BCP steps in SP3 are executed and control returns to SP2

I ma not sure if using DTS and BCP in SQL stored procedures might cause any problems

Appreciate your helpIt seems like your DTS is executing under a different security context than when you execute your SP3 from QA. Are you checking for errors after each BCP in your SP3? If you're calling your BCP using xp_cmdshell, - consider doing INSERT @.temp_tbl exec master.dbo.xp_cmdshell [....].

Problem inserting time stamp 24:00:00.000 into a datetime column

Hi,
Problem inserting time stamp 24:00:00.000 to an SQL 2K database. App
code(EJB-SQL JDBC) constantly receives reading and it calls add procedure to
insert reading datetime. So, if reading comes exactly at midnight, the inser
t
fails.
Any help is really appreciated.
thanksHi
Midnight is 00:00:00.000!
John
"Ajay" <Ajay@.discussions.microsoft.com> wrote in message
news:E8F82952-F6C0-45D7-AED2-245D745A6273@.microsoft.com...
> Hi,
> Problem inserting time stamp 24:00:00.000 to an SQL 2K database. App
> code(EJB-SQL JDBC) constantly receives reading and it calls add procedure
> to
> insert reading datetime. So, if reading comes exactly at midnight, the
> insert
> fails.
> Any help is really appreciated.
> thanks
>