|
|
You're in the
sql server full text search
group:urgent help needed: error 7342 (full text search problem)
sql server full text search:
I would be very grateful for advice or suggestions for the following
problem. I have had no problem with Full Text Search in SQL2000 on my PC under XP Pro using the Developers Version of SQL 2000. However, I have created another copy of the same relatively small (100mb) database on a notebook (originally purchased with XP Home and then upgraded to XP Pro /SP2). On the notebook I am getting an error whenever I run a fulltext query in QA. The notebook has 1GB RAM and a 1.7ghz CPU. Both my PC and this notebook used the same install CD of the SQL Developer Version. The query: Select * from MedArticles where CONTAINS(keywords, 'mysearcharg') always yields error: 7342 Unexpected NULL value returned for column '[FULLTEXT:MEDARTICLES].KEY' from the Ole db provider 'Full-Text Search Engine'. This column cannot be null. Troubleshooting steps taken so far: 1. Select FULLTEXTSERVICEPROPERTY('IsFullTextInstalled') = 1 2.<sqlpath>FTDATA\<sqlserver>\Config\schema.txt same as on CD (Developer Edition of SQL2000) 3. @@version = Microsoft SQL Server 2000 -- 8.00.194 4. The MSSearch service is running. 5. I've dropped and recreated the catalog and have rebuilt the index. 6. Event log shows the start_full build completes without incident.("The index build for project <my project> has completed." 7. Have reinstalled Full Text Search from CD 8. Have restarted the MSSearch service from management console 9. tquery.dll is same version/size/date on PC where full text is working and on notebook where fulltext gets error 7342. 10. Have manually registered tquery.dll with success message. Thanks Timo
Can you create and successfully query a full text catalog on another table
in another database? If so the problem is with this catalog as opposed to your installation. -- 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 [quoted text, click to view] "Timo" <timo@noneofyer.biz> wrote in message news:u62yHT4FFHA.3648@TK2MSFTNGP10.phx.gbl... > I would be very grateful for advice or suggestions for the following > problem. > > I have had no problem with Full Text Search in SQL2000 on my PC under XP Pro > using the Developers Version of SQL 2000. However, I have created another > copy of the same relatively small (100mb) database on a notebook (originally > purchased with XP Home and then upgraded to XP Pro /SP2). On the notebook I > am getting an error whenever I run a fulltext query in QA. The notebook has > 1GB RAM and a 1.7ghz CPU. Both my PC and this notebook used the same install > CD of the SQL Developer Version. > > The query: > Select * from MedArticles where CONTAINS(keywords, 'mysearcharg') > > always yields error: 7342 > Unexpected NULL value returned for column '[FULLTEXT:MEDARTICLES].KEY' from > the Ole db provider > 'Full-Text Search Engine'. This column cannot be null. > > Troubleshooting steps taken so far: > 1. Select FULLTEXTSERVICEPROPERTY('IsFullTextInstalled') = 1 > 2.<sqlpath>FTDATA\<sqlserver>\Config\schema.txt same as on CD (Developer > Edition of SQL2000) > 3. @@version = Microsoft SQL Server 2000 -- 8.00.194 > 4. The MSSearch service is running. > 5. I've dropped and recreated the catalog and have rebuilt the index. > 6. Event log shows the start_full build completes without incident.("The > index build for project <my project> has completed." > 7. Have reinstalled Full Text Search from CD > 8. Have restarted the MSSearch service from management console > 9. tquery.dll is same version/size/date on PC where full text is working and > on notebook where fulltext gets error 7342. > 10. Have manually registered tquery.dll with success message. > > Thanks > Timo > > >
Timo,
In regards to error "Msg 7342 Unexpected NULL value returned for column '[FULLTEXT:MEDARTICLES].KEY' from the Ole db provider 'Full-Text Search Engine'. This column cannot be null." Could you confirm that the file schema.txt located at \FTDATA\SQLServer\Config\ (where you have SQL Server installed) is not "corrupted", missing &/or otherwise altered from the version that is on the SQL Server CD? If so, replace it with the version that is on the SQL Server CD and reboot your server. Thanks, John -- SQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ [quoted text, click to view] "Timo" <timo@noneofyer.biz> wrote in message news:u62yHT4FFHA.3648@TK2MSFTNGP10.phx.gbl... > I would be very grateful for advice or suggestions for the following > problem. > > I have had no problem with Full Text Search in SQL2000 on my PC under XP Pro > using the Developers Version of SQL 2000. However, I have created another > copy of the same relatively small (100mb) database on a notebook (originally > purchased with XP Home and then upgraded to XP Pro /SP2). On the notebook I > am getting an error whenever I run a fulltext query in QA. The notebook has > 1GB RAM and a 1.7ghz CPU. Both my PC and this notebook used the same install > CD of the SQL Developer Version. > > The query: > Select * from MedArticles where CONTAINS(keywords, 'mysearcharg') > > always yields error: 7342 > Unexpected NULL value returned for column '[FULLTEXT:MEDARTICLES].KEY' from > the Ole db provider > 'Full-Text Search Engine'. This column cannot be null. > > Troubleshooting steps taken so far: > 1. Select FULLTEXTSERVICEPROPERTY('IsFullTextInstalled') = 1 > 2.<sqlpath>FTDATA\<sqlserver>\Config\schema.txt same as on CD (Developer > Edition of SQL2000) > 3. @@version = Microsoft SQL Server 2000 -- 8.00.194 > 4. The MSSearch service is running. > 5. I've dropped and recreated the catalog and have rebuilt the index. > 6. Event log shows the start_full build completes without incident.("The > index build for project <my project> has completed." > 7. Have reinstalled Full Text Search from CD > 8. Have restarted the MSSearch service from management console > 9. tquery.dll is same version/size/date on PC where full text is working and > on notebook where fulltext gets error 7342. > 10. Have manually registered tquery.dll with success message. > > Thanks > Timo > > >
Thanks for the reply. Although I am able to create a new catalog on another
table and build the index without error, a query results in the same 7342 error. Timo [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:#X117m4FFHA.2824@tk2msftngp13.phx.gbl... > Can you create and successfully query a full text catalog on another table > in another database? > > If so the problem is with this catalog as opposed to your installation. > > -- > 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 > > "Timo" <timo@noneofyer.biz> wrote in message > news:u62yHT4FFHA.3648@TK2MSFTNGP10.phx.gbl... > > I would be very grateful for advice or suggestions for the following > > problem. > > > > I have had no problem with Full Text Search in SQL2000 on my PC under XP > Pro > > using the Developers Version of SQL 2000. However, I have created another > > copy of the same relatively small (100mb) database on a notebook > (originally > > purchased with XP Home and then upgraded to XP Pro /SP2). On the notebook > I > > am getting an error whenever I run a fulltext query in QA. The notebook > has > > 1GB RAM and a 1.7ghz CPU. Both my PC and this notebook used the same > install > > CD of the SQL Developer Version. > > > > The query: > > Select * from MedArticles where CONTAINS(keywords, 'mysearcharg') > > > > always yields error: 7342 > > Unexpected NULL value returned for column '[FULLTEXT:MEDARTICLES].KEY' > from > > the Ole db provider > > 'Full-Text Search Engine'. This column cannot be null. > > > > Troubleshooting steps taken so far: > > 1. Select FULLTEXTSERVICEPROPERTY('IsFullTextInstalled') = 1 > > 2.<sqlpath>FTDATA\<sqlserver>\Config\schema.txt same as on CD (Developer > > Edition of SQL2000) > > 3. @@version = Microsoft SQL Server 2000 -- 8.00.194 > > 4. The MSSearch service is running. > > 5. I've dropped and recreated the catalog and have rebuilt the index. > > 6. Event log shows the start_full build completes without incident.("The > > index build for project <my project> has completed." > > 7. Have reinstalled Full Text Search from CD > > 8. Have restarted the MSSearch service from management console > > 9. tquery.dll is same version/size/date on PC where full text is working > and > > on notebook where fulltext gets error 7342. > > 10. Have manually registered tquery.dll with success message. > > > > Thanks > > Timo > > > > > > > >
Sorry, Timo,
I posted before I completely read your (very complete) list of troubleshooting steps! My bad... I also see that you "reinstalled Full Text Search from CD", when you did this where you logged on a Administrator or as a member of the Admin. Group? If not, then some of the required registry keys may or may not be properly configured or setup correct. If so, then based upon your troubleshooting steps, I'd recommend that you call and open a support case with Microsoft PSS SQL Server support as they have methods for enabling extended debugging that can identify the true source of error Msg 7342. Regards, John -- SQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ [quoted text, click to view] "Timo" <timo@noneofyer.biz> wrote in message news:en$zOd6FFHA.1408@TK2MSFTNGP10.phx.gbl... > John, > Yes, covered in my troubeshooting steps already taken, #2. > Timo > > "John Kane" <jt-kane@comcast.net> wrote in message > news:u$R0KU6FFHA.3336@TK2MSFTNGP10.phx.gbl... > > Timo, > > In regards to error "Msg 7342 Unexpected NULL value returned for column > > '[FULLTEXT:MEDARTICLES].KEY' from the Ole db provider 'Full-Text Search > > Engine'. This column cannot be null." Could you confirm that the file > > schema.txt located at \FTDATA\SQLServer\Config\ (where you have SQL Server > > installed) is not "corrupted", missing &/or otherwise altered from the > > version that is on the SQL Server CD? If so, replace it with the version > > that is on the SQL Server CD and reboot your server. > > > > Thanks, > > John > > -- > > SQL Full Text Search Blog > > http://spaces.msn.com/members/jtkane/ > > > > > > > > > > "Timo" <timo@noneofyer.biz> wrote in message > > news:u62yHT4FFHA.3648@TK2MSFTNGP10.phx.gbl... > > > I would be very grateful for advice or suggestions for the following > > > problem. > > > > > > I have had no problem with Full Text Search in SQL2000 on my PC under XP > > Pro > > > using the Developers Version of SQL 2000. However, I have created > another > > > copy of the same relatively small (100mb) database on a notebook > > (originally > > > purchased with XP Home and then upgraded to XP Pro /SP2). On the > notebook > > I > > > am getting an error whenever I run a fulltext query in QA. The notebook > > has > > > 1GB RAM and a 1.7ghz CPU. Both my PC and this notebook used the same > > install > > > CD of the SQL Developer Version. > > > > > > The query: > > > Select * from MedArticles where CONTAINS(keywords, 'mysearcharg') > > > > > > always yields error: 7342 > > > Unexpected NULL value returned for column '[FULLTEXT:MEDARTICLES].KEY' > > from > > > the Ole db provider > > > 'Full-Text Search Engine'. This column cannot be null. > > > > > > Troubleshooting steps taken so far: > > > 1. Select FULLTEXTSERVICEPROPERTY('IsFullTextInstalled') = 1 > > > 2.<sqlpath>FTDATA\<sqlserver>\Config\schema.txt same as on CD (Developer > > > Edition of SQL2000) > > > 3. @@version = Microsoft SQL Server 2000 -- 8.00.194 > > > 4. The MSSearch service is running. > > > 5. I've dropped and recreated the catalog and have rebuilt the index. > > > 6. Event log shows the start_full build completes without incident.("The > > > index build for project <my project> has completed." > > > 7. Have reinstalled Full Text Search from CD > > > 8. Have restarted the MSSearch service from management console > > > 9. tquery.dll is same version/size/date on PC where full text is working > > and > > > on notebook where fulltext gets error 7342. > > > 10. Have manually registered tquery.dll with success message. > > > > > > Thanks > > > Timo > > > > > > > > > > > > > > >
There is something wrong with your environment. Could you look in the
application log using event viewer for informational messages coming from MSSearch or MSSCI? Also check out this kb article. This lists the most common reason for full text errors - although your error seems a little different. http://support.microsoft.com/default.aspx?scid=kb;en-us;277549 Also what sp are you at? I helped one guy through this error once before - it involved a reinstallation of SQL FTS. I can guide you through the steps if the kb article won't help. -- 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 [quoted text, click to view] "Timo" <timo@noneofyer.biz> wrote in message news:%2376P3W5FFHA.560@TK2MSFTNGP15.phx.gbl... > Thanks for the reply. Although I am able to create a new catalog on another > table and build the index without error, a query results in the same 7342 > error. > Timo > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:#X117m4FFHA.2824@tk2msftngp13.phx.gbl... > > Can you create and successfully query a full text catalog on another table > > in another database? > > > > If so the problem is with this catalog as opposed to your installation. > > > > -- > > 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 > > > > "Timo" <timo@noneofyer.biz> wrote in message > > news:u62yHT4FFHA.3648@TK2MSFTNGP10.phx.gbl... > > > I would be very grateful for advice or suggestions for the following > > > problem. > > > > > > I have had no problem with Full Text Search in SQL2000 on my PC under XP > > Pro > > > using the Developers Version of SQL 2000. However, I have created > another > > > copy of the same relatively small (100mb) database on a notebook > > (originally > > > purchased with XP Home and then upgraded to XP Pro /SP2). On the > notebook > > I > > > am getting an error whenever I run a fulltext query in QA. The notebook > > has > > > 1GB RAM and a 1.7ghz CPU. Both my PC and this notebook used the same > > install > > > CD of the SQL Developer Version. > > > > > > The query: > > > Select * from MedArticles where CONTAINS(keywords, 'mysearcharg') > > > > > > always yields error: 7342 > > > Unexpected NULL value returned for column '[FULLTEXT:MEDARTICLES].KEY' > > from > > > the Ole db provider > > > 'Full-Text Search Engine'. This column cannot be null. > > > > > > Troubleshooting steps taken so far: > > > 1. Select FULLTEXTSERVICEPROPERTY('IsFullTextInstalled') = 1 > > > 2.<sqlpath>FTDATA\<sqlserver>\Config\schema.txt same as on CD (Developer > > > Edition of SQL2000) > > > 3. @@version = Microsoft SQL Server 2000 -- 8.00.194 > > > 4. The MSSearch service is running. > > > 5. I've dropped and recreated the catalog and have rebuilt the index. > > > 6. Event log shows the start_full build completes without incident.("The > > > index build for project <my project> has completed." > > > 7. Have reinstalled Full Text Search from CD > > > 8. Have restarted the MSSearch service from management console > > > 9. tquery.dll is same version/size/date on PC where full text is working > > and > > > on notebook where fulltext gets error 7342. > > > 10. Have manually registered tquery.dll with success message. > > > > > > Thanks > > > Timo > > > > > > > > > > > > > > >
John,
Yes, covered in my troubeshooting steps already taken, #2. Timo [quoted text, click to view] "John Kane" <jt-kane@comcast.net> wrote in message news:u$R0KU6FFHA.3336@TK2MSFTNGP10.phx.gbl... > Timo, > In regards to error "Msg 7342 Unexpected NULL value returned for column > '[FULLTEXT:MEDARTICLES].KEY' from the Ole db provider 'Full-Text Search > Engine'. This column cannot be null." Could you confirm that the file > schema.txt located at \FTDATA\SQLServer\Config\ (where you have SQL Server > installed) is not "corrupted", missing &/or otherwise altered from the > version that is on the SQL Server CD? If so, replace it with the version > that is on the SQL Server CD and reboot your server. > > Thanks, > John > -- > SQL Full Text Search Blog > http://spaces.msn.com/members/jtkane/ > > > > > "Timo" <timo@noneofyer.biz> wrote in message > news:u62yHT4FFHA.3648@TK2MSFTNGP10.phx.gbl... > > I would be very grateful for advice or suggestions for the following > > problem. > > > > I have had no problem with Full Text Search in SQL2000 on my PC under XP > Pro > > using the Developers Version of SQL 2000. However, I have created another > > copy of the same relatively small (100mb) database on a notebook > (originally > > purchased with XP Home and then upgraded to XP Pro /SP2). On the notebook > I > > am getting an error whenever I run a fulltext query in QA. The notebook > has > > 1GB RAM and a 1.7ghz CPU. Both my PC and this notebook used the same > install > > CD of the SQL Developer Version. > > > > The query: > > Select * from MedArticles where CONTAINS(keywords, 'mysearcharg') > > > > always yields error: 7342 > > Unexpected NULL value returned for column '[FULLTEXT:MEDARTICLES].KEY' > from > > the Ole db provider > > 'Full-Text Search Engine'. This column cannot be null. > > > > Troubleshooting steps taken so far: > > 1. Select FULLTEXTSERVICEPROPERTY('IsFullTextInstalled') = 1 > > 2.<sqlpath>FTDATA\<sqlserver>\Config\schema.txt same as on CD (Developer > > Edition of SQL2000) > > 3. @@version = Microsoft SQL Server 2000 -- 8.00.194 > > 4. The MSSearch service is running. > > 5. I've dropped and recreated the catalog and have rebuilt the index. > > 6. Event log shows the start_full build completes without incident.("The > > index build for project <my project> has completed." > > 7. Have reinstalled Full Text Search from CD > > 8. Have restarted the MSSearch service from management console > > 9. tquery.dll is same version/size/date on PC where full text is working > and > > on notebook where fulltext gets error 7342. > > 10. Have manually registered tquery.dll with success message. > > > > Thanks > > Timo > > > > > > > >
Hilary,
Event viewer shows no errors. I have already reinstalled FTS from the CD, and I've just now applied SP2, so SQLServer is now at 8.00.534. Services have been stopped and restarted. System has been rebooted. Error 7342 persists. I'd be happy to try anything else. Do you have a way of reinstalling FTS other than adding components from the installation CD? Thanks Timo [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:OHw7Zq5FFHA.1456@TK2MSFTNGP09.phx.gbl... > There is something wrong with your environment. Could you look in the > application log using event viewer for informational messages coming from > MSSearch or MSSCI? > > Also check out this kb article. This lists the most common reason for full > text errors - although your error seems a little different. > > http://support.microsoft.com/default.aspx?scid=kb;en-us;277549 > > Also what sp are you at? I helped one guy through this error once before - > it involved a reinstallation of SQL FTS. I can guide you through the steps > if the kb article won't help. > > -- > 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 > > "Timo" <timo@noneofyer.biz> wrote in message > news:%2376P3W5FFHA.560@TK2MSFTNGP15.phx.gbl... > > Thanks for the reply. Although I am able to create a new catalog on > another > > table and build the index without error, a query results in the same 7342 > > error. > > Timo > > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > > news:#X117m4FFHA.2824@tk2msftngp13.phx.gbl... > > > Can you create and successfully query a full text catalog on another > table > > > in another database? > > > > > > If so the problem is with this catalog as opposed to your installation. > > > > > > -- > > > 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 > > > > > > "Timo" <timo@noneofyer.biz> wrote in message > > > news:u62yHT4FFHA.3648@TK2MSFTNGP10.phx.gbl... > > > > I would be very grateful for advice or suggestions for the following > > > > problem. > > > > > > > > I have had no problem with Full Text Search in SQL2000 on my PC under > XP > > > Pro > > > > using the Developers Version of SQL 2000. However, I have created > > another > > > > copy of the same relatively small (100mb) database on a notebook > > > (originally > > > > purchased with XP Home and then upgraded to XP Pro /SP2). On the > > notebook > > > I > > > > am getting an error whenever I run a fulltext query in QA. The > notebook > > > has > > > > 1GB RAM and a 1.7ghz CPU. Both my PC and this notebook used the same > > > install > > > > CD of the SQL Developer Version. > > > > > > > > The query: > > > > Select * from MedArticles where CONTAINS(keywords, 'mysearcharg') > > > > > > > > always yields error: 7342 > > > > Unexpected NULL value returned for column '[FULLTEXT:MEDARTICLES].KEY' > > > from > > > > the Ole db provider > > > > 'Full-Text Search Engine'. This column cannot be null. > > > > > > > > Troubleshooting steps taken so far: > > > > 1. Select FULLTEXTSERVICEPROPERTY('IsFullTextInstalled') = 1 > > > > 2.<sqlpath>FTDATA\<sqlserver>\Config\schema.txt same as on CD > (Developer > > > > Edition of SQL2000) > > > > 3. @@version = Microsoft SQL Server 2000 -- 8.00.194 > > > > 4. The MSSearch service is running. > > > > 5. I've dropped and recreated the catalog and have rebuilt the index. > > > > 6. Event log shows the start_full build completes without > incident.("The > > > > index build for project <my project> has completed." > > > > 7. Have reinstalled Full Text Search from CD > > > > 8. Have restarted the MSSearch service from management console > > > > 9. tquery.dll is same version/size/date on PC where full text is > working > > > and > > > > on notebook where fulltext gets error 7342. > > > > 10. Have manually registered tquery.dll with success message. > > > > > > > > Thanks > > > > Timo > > > > > > > > > > > > > > > > > > > > > > > >
John,
I've always been logging in as Administrator. I will take your advice, and open the support call tomorrow AM. Regards Timo [quoted text, click to view] "John Kane" <jt-kane@comcast.net> wrote in message news:OU#YZA7FFHA.2876@TK2MSFTNGP12.phx.gbl... > Sorry, Timo, > I posted before I completely read your (very complete) list of > troubleshooting steps! My bad... > I also see that you "reinstalled Full Text Search from CD", when you did > this where you logged on a Administrator or as a member of the Admin. Group? > If not, then some of the required registry keys may or may not be properly > configured or setup correct. If so, then based upon your troubleshooting > steps, I'd recommend that you call and open a support case with Microsoft > PSS SQL Server support as they have methods for enabling extended debugging > that can identify the true source of error Msg 7342. > > Regards, > John > -- > SQL Full Text Search Blog > http://spaces.msn.com/members/jtkane/ > > > "Timo" <timo@noneofyer.biz> wrote in message > news:en$zOd6FFHA.1408@TK2MSFTNGP10.phx.gbl... > > John, > > Yes, covered in my troubeshooting steps already taken, #2. > > Timo > > > > "John Kane" <jt-kane@comcast.net> wrote in message > > news:u$R0KU6FFHA.3336@TK2MSFTNGP10.phx.gbl... > > > Timo, > > > In regards to error "Msg 7342 Unexpected NULL value returned for column > > > '[FULLTEXT:MEDARTICLES].KEY' from the Ole db provider 'Full-Text Search > > > Engine'. This column cannot be null." Could you confirm that the file > > > schema.txt located at \FTDATA\SQLServer\Config\ (where you have SQL > Server > > > installed) is not "corrupted", missing &/or otherwise altered from the > > > version that is on the SQL Server CD? If so, replace it with the version > > > that is on the SQL Server CD and reboot your server. > > > > > > Thanks, > > > John > > > -- > > > SQL Full Text Search Blog > > > http://spaces.msn.com/members/jtkane/ > > > > > > > > > > > > > > > "Timo" <timo@noneofyer.biz> wrote in message > > > news:u62yHT4FFHA.3648@TK2MSFTNGP10.phx.gbl... > > > > I would be very grateful for advice or suggestions for the following > > > > problem. > > > > > > > > I have had no problem with Full Text Search in SQL2000 on my PC under > XP > > > Pro > > > > using the Developers Version of SQL 2000. However, I have created > > another > > > > copy of the same relatively small (100mb) database on a notebook > > > (originally > > > > purchased with XP Home and then upgraded to XP Pro /SP2). On the > > notebook > > > I > > > > am getting an error whenever I run a fulltext query in QA. The > notebook > > > has > > > > 1GB RAM and a 1.7ghz CPU. Both my PC and this notebook used the same > > > install > > > > CD of the SQL Developer Version. > > > > > > > > The query: > > > > Select * from MedArticles where CONTAINS(keywords, 'mysearcharg') > > > > > > > > always yields error: 7342 > > > > Unexpected NULL value returned for column '[FULLTEXT:MEDARTICLES].KEY' > > > from > > > > the Ole db provider > > > > 'Full-Text Search Engine'. This column cannot be null. > > > > > > > > Troubleshooting steps taken so far: > > > > 1. Select FULLTEXTSERVICEPROPERTY('IsFullTextInstalled') = 1 > > > > 2.<sqlpath>FTDATA\<sqlserver>\Config\schema.txt same as on CD > (Developer > > > > Edition of SQL2000) > > > > 3. @@version = Microsoft SQL Server 2000 -- 8.00.194 > > > > 4. The MSSearch service is running. > > > > 5. I've dropped and recreated the catalog and have rebuilt the index. > > > > 6. Event log shows the start_full build completes without > incident.("The > > > > index build for project <my project> has completed." > > > > 7. Have reinstalled Full Text Search from CD > > > > 8. Have restarted the MSSearch service from management console > > > > 9. tquery.dll is same version/size/date on PC where full text is > working > > > and > > > > on notebook where fulltext gets error 7342. > > > > 10. Have manually registered tquery.dll with success message. > > > > > > > > Thanks > > > > Timo > > > > > > > > > > > > > > > > > > > > > > > >
Before calling it quits for the night, I decided to uninstall SQLServer and
reinstall using Custom Install because the Typical Install had not included Full Text Search and FTS had to be installed afterwards using Add Components. Then I applied SP2. And then I tried to create a fulltext catalog on the publishers table in pubs. It seems we're back in business! I was able to create a fulltext catalog and run CONTAINS queries against it. Timo
Timo,
Great News! Sometimes, if things don't work it is necessary to re-install, apply a Service Pack or even re-boot as I've seen all of these simple tasks resolve SQL FTS issues! In this case it could of been either the re-installation or applying SP2 that did the trick. Regards, John -- SQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ [quoted text, click to view] "Timo" <timo@noneofyer.biz> wrote in message news:e9YqEOBGFHA.2876@TK2MSFTNGP12.phx.gbl... > Before calling it quits for the night, I decided to uninstall SQLServer and > reinstall using Custom Install because the Typical Install had not included > Full Text Search and FTS had to be installed afterwards using Add > Components. Then I applied SP2. And then I tried to create a fulltext > catalog on the publishers table in pubs. It seems we're back in business! I > was able to create a fulltext catalog and run CONTAINS queries against it. > Timo > > >
There is another way where you can install it off the service pack
directory - however I am not convinced this will help. I think your best opportunity is to call PSS at this point. [quoted text, click to view] "Timo" <timo@noneofyer.biz> wrote in message news:e2Jxi%236FFHA.1924@TK2MSFTNGP14.phx.gbl... > Hilary, > Event viewer shows no errors. > I have already reinstalled FTS from the CD, and I've just now applied SP2, > so SQLServer is now at 8.00.534. > Services have been stopped and restarted. > System has been rebooted. > Error 7342 persists. > > I'd be happy to try anything else. Do you have a way of reinstalling FTS > other than adding components from the installation CD? > Thanks > Timo > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:OHw7Zq5FFHA.1456@TK2MSFTNGP09.phx.gbl... >> There is something wrong with your environment. Could you look in the >> application log using event viewer for informational messages coming from >> MSSearch or MSSCI? >> >> Also check out this kb article. This lists the most common reason for >> full >> text errors - although your error seems a little different. >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;277549 >> >> Also what sp are you at? I helped one guy through this error once >> before - >> it involved a reinstallation of SQL FTS. I can guide you through the >> steps >> if the kb article won't help. >> >> -- >> 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 >> >> "Timo" <timo@noneofyer.biz> wrote in message >> news:%2376P3W5FFHA.560@TK2MSFTNGP15.phx.gbl... >> > Thanks for the reply. Although I am able to create a new catalog on >> another >> > table and build the index without error, a query results in the same > 7342 >> > error. >> > Timo >> > >> > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >> > news:#X117m4FFHA.2824@tk2msftngp13.phx.gbl... >> > > Can you create and successfully query a full text catalog on another >> table >> > > in another database? >> > > >> > > If so the problem is with this catalog as opposed to your > installation. >> > > >> > > -- >> > > 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 >> > > >> > > "Timo" <timo@noneofyer.biz> wrote in message >> > > news:u62yHT4FFHA.3648@TK2MSFTNGP10.phx.gbl... >> > > > I would be very grateful for advice or suggestions for the >> > > > following >> > > > problem. >> > > > >> > > > I have had no problem with Full Text Search in SQL2000 on my PC > under >> XP >> > > Pro >> > > > using the Developers Version of SQL 2000. However, I have created >> > another >> > > > copy of the same relatively small (100mb) database on a notebook >> > > (originally >> > > > purchased with XP Home and then upgraded to XP Pro /SP2). On the >> > notebook >> > > I >> > > > am getting an error whenever I run a fulltext query in QA. The >> notebook >> > > has >> > > > 1GB RAM and a 1.7ghz CPU. Both my PC and this notebook used the >> > > > same >> > > install >> > > > CD of the SQL Developer Version. >> > > > >> > > > The query: >> > > > Select * from MedArticles where CONTAINS(keywords, 'mysearcharg') >> > > > >> > > > always yields error: 7342 >> > > > Unexpected NULL value returned for column > '[FULLTEXT:MEDARTICLES].KEY' >> > > from >> > > > the Ole db provider >> > > > 'Full-Text Search Engine'. This column cannot be null. >> > > > >> > > > Troubleshooting steps taken so far: >> > > > 1. Select FULLTEXTSERVICEPROPERTY('IsFullTextInstalled') = 1 >> > > > 2.<sqlpath>FTDATA\<sqlserver>\Config\schema.txt same as on CD >> (Developer >> > > > Edition of SQL2000) >> > > > 3. @@version = Microsoft SQL Server 2000 -- 8.00.194 >> > > > 4. The MSSearch service is running. >> > > > 5. I've dropped and recreated the catalog and have rebuilt the > index. >> > > > 6. Event log shows the start_full build completes without >> incident.("The >> > > > index build for project <my project> has completed." >> > > > 7. Have reinstalled Full Text Search from CD >> > > > 8. Have restarted the MSSearch service from management console >> > > > 9. tquery.dll is same version/size/date on PC where full text is >> working >> > > and >> > > > on notebook where fulltext gets error 7342. >> > > > 10. Have manually registered tquery.dll with success message. >> > > > >> > > > Thanks >> > > > Timo >> > > > >> > > > >> > > > >> > > >> > > >> > >> > >> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |