Item Count 0; Gathering hung?

Douglas,
Basically, the FT Catalog is not being properly populated for some reason
and we need to discover that reason, correct it and then you should be good
to go... There may be a post-SP3a issue here, depending upon if this server
was upgraded from SQL Server 7.0 or this SQL 2000 server is a named instance
with a SQL Server 7.0 default installation. Checkout KB article - "814035
(Q814035) FIX: A Full-Text Population Fails After You Apply SQL Server 2000
Service Pack 3" at:
http://support.microsoft.com/default...b;en-us;814035
When you changed the account under which SQL is running, did you do this
via the Enterprise Manager's server security tab? If not, then you must
"re-change" the changed the account under which SQL is running via the EM.
Checkout KB article - "277549 (Q277549) PRB: Unable to Build Full-Text
Catalog After You Modify MSSQLServer Logon Account Through [NT4.0) Control
Panel [or Win2K Component Services]" at
http://support.microsoft.com/default...B;EN-US;277549
Regards,
John
"Douglas Steen" <dug@.pobox.com> wrote in message
news:#lzgWozFEHA.3372@.TK2MSFTNGP09.phx.gbl...
> I use a simple test server with SQL and MSSearch for development work and
up
> until recently it was handling full-text searching just fine. I updated
the
> box to Win2K3, and still no problems. But then I modified noise.eng, and
in
> the process rebuilt the catalog. Now whenever I try to populate the
catalog
> I am permanently stuck "in progress" with an item count of 0, a catalog
size
> of 1 MB, and a unique key count of 1.
> Here's what I've tried:
> - I have tried full & incemental populations, starting, stopping services
&
> rebooting
> - I've waited for hours for any sort of progress beyond item count 0, but
to
> no avail
> - the Application event log shows nothing but the standard start/stop
> messages. If I stop the population myself, I do get warnings, but they're
> of the "user stopped process" variety
> - similarly, the gather logs show only start/stop and "user stopped
process"
> messages
> - I've installed SQL Server SP3a
> - I've changed the account under which SQL is running, moving it to a
system
> account and then back to the original account, starting & stopping SQL and
> MSSearch as described in
> http://support.microsoft.com/default...b;en-us;295051 (I've done
> this twice now)
> I'm at the end of the line here; any help would be appreciated.
> Sincerely,
> Douglas R. Steen
>
John -
Thanks for the response.
Unfortunately, we're using SQL 2000, so I'm not sure this applies. And
yes, I did use Enterprise Manager to change the account, so I don't think
that's it either.
Here's some more information that might affect what happened:
The change that was made was to update the noise.eng file with a noise.eng
file that had been manually edited & emailed around for a while. Is it
possible that permissions on that file are confusing the service? I tried
setting correct permissions by clicking the checkbox on the security tab for
the containing folder that says "Apply security settings to all children",
so now the permissions are the same for all files in the Config folder, but
still no luck.
Also, we're now seeing this same problem on another sql server installation.
We have two identical databases (one is a test database) on that sql server:
in one case, we didn't delete and rebuild the catalog and it's working fine;
in the other, we did have to delete and rebuild the catalog and it's broken.
And it was the case on both that server and my own that we had not rebuilt
the catalog after upgrading to Win2003 (from Win2000) until just yesterday,
when this problem started occurring.
Unfortunately, the new sql server installation & database where we're
seeing this problem is our production server/database, so the problem has
moved to urgent priority. Any more thoughts you might have would be
welcome; and thanks for the help you've given already.
Douglas R. Steen
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OEXzSy0FEHA.2208@.TK2MSFTNGP09.phx.gbl...
> Douglas,
> Basically, the FT Catalog is not being properly populated for some reason
> and we need to discover that reason, correct it and then you should be
good
> to go... There may be a post-SP3a issue here, depending upon if this
server
> was upgraded from SQL Server 7.0 or this SQL 2000 server is a named
instance
> with a SQL Server 7.0 default installation. Checkout KB article - "814035
> (Q814035) FIX: A Full-Text Population Fails After You Apply SQL Server
2000
> Service Pack 3" at:
> http://support.microsoft.com/default...b;en-us;814035
> When you changed the account under which SQL is running, did you do this
> via the Enterprise Manager's server security tab? If not, then you must
> "re-change" the changed the account under which SQL is running via the
EM.
> Checkout KB article - "277549 (Q277549) PRB: Unable to Build Full-Text
> Catalog After You Modify MSSQLServer Logon Account Through [NT4.0) Control
> Panel [or Win2K Component Services]" at
> http://support.microsoft.com/default...B;EN-US;277549
> Regards,
> John
>
> "Douglas Steen" <dug@.pobox.com> wrote in message
> news:#lzgWozFEHA.3372@.TK2MSFTNGP09.phx.gbl...
and
> up
> the
and
> in
> catalog
> size
services
> &
but
> to
they're
> process"
> system
and
done
>
|||You're welcome, Douglas,
First of all, both KB articles apply to SQL Server 2000 as well. Secondly,
the noise.* files are just text files and there should not be any permission
issues. Although, changing the file permissions and "clicking the checkbox
on the security tab for the containing folder that says "Apply security
settings to all children" has me a bit concerned. On another server where
SQL Server 2000 is installed, could you confirm the modified folder has the
same permissions (and owner) as the un-modified folder?
I now *believe* that there might be some issue caused by the upgrading to
Win2003 from Win2000 as this upgrade also affects the MSSearch service as
well as the OS-supplied wordbreaker dll's. If so, then the complexity of
this, has just gone up a notch or two..
Were any other changes made to the SQL Servers? Specifically, any changes to
BUILTIN\Administrator ? If so, what were those changes?
As for your production server/database, you might want to consider calling
Microsoft PSS SQL Server support as and get their help in resolving this
more urgent issue as newsgroups are not the best place to get
production-level support.
Regards,
John
"Douglas Steen" <dug@.pobox.com> wrote in message
news:efN7P$0FEHA.4084@.TK2MSFTNGP11.phx.gbl...
> John -
> Thanks for the response.
> Unfortunately, we're using SQL 2000, so I'm not sure this applies. And
> yes, I did use Enterprise Manager to change the account, so I don't think
> that's it either.
> Here's some more information that might affect what happened:
> The change that was made was to update the noise.eng file with a noise.eng
> file that had been manually edited & emailed around for a while. Is it
> possible that permissions on that file are confusing the service? I tried
> setting correct permissions by clicking the checkbox on the security tab
for
> the containing folder that says "Apply security settings to all children",
> so now the permissions are the same for all files in the Config folder,
but
> still no luck.
> Also, we're now seeing this same problem on another sql server
installation.
> We have two identical databases (one is a test database) on that sql
server:
> in one case, we didn't delete and rebuild the catalog and it's working
fine;
> in the other, we did have to delete and rebuild the catalog and it's
broken.
> And it was the case on both that server and my own that we had not rebuilt
> the catalog after upgrading to Win2003 (from Win2000) until just
yesterday,
> when this problem started occurring.
> Unfortunately, the new sql server installation & database where we're
> seeing this problem is our production server/database, so the problem has
> moved to urgent priority. Any more thoughts you might have would be
> welcome; and thanks for the help you've given already.
> Douglas R. Steen
>
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:OEXzSy0FEHA.2208@.TK2MSFTNGP09.phx.gbl...
reason
> good
> server
> instance
"814035
> 2000
this
> EM.
Control
> and
updated
> and
catalog
> services
> but
> they're
> and
> done
>
|||John -
As it turns out, our production issues were solved by using QueryAnalyzer
instead of the Enterprise Manager to do the creation/population/etc.
Unfortunately, I wasn't so lucky: it hasn't worked for me. No idea why one
would work and not the other, but it is feeling like it has something to do
with the Win2K3 upgrade and permissions.
This is just a dev machine, so if all else fails (though I'd hate to do
it), I can reinstall everything (starting with SQL server). I'm going to
let it stew for a while & see if any other ideas come up. In the meantime,
I've gotta get back to work. Thanks for your efforts.
"John Kane" <jt-kane@.comcast.net> wrote in message
news:eVo7QR1FEHA.3568@.tk2msftngp13.phx.gbl...
> You're welcome, Douglas,
> First of all, both KB articles apply to SQL Server 2000 as well. Secondly,
> the noise.* files are just text files and there should not be any
permission
> issues. Although, changing the file permissions and "clicking the checkbox
> on the security tab for the containing folder that says "Apply security
> settings to all children" has me a bit concerned. On another server where
> SQL Server 2000 is installed, could you confirm the modified folder has
the
> same permissions (and owner) as the un-modified folder?
> I now *believe* that there might be some issue caused by the upgrading to
> Win2003 from Win2000 as this upgrade also affects the MSSearch service as
> well as the OS-supplied wordbreaker dll's. If so, then the complexity of
> this, has just gone up a notch or two..
> Were any other changes made to the SQL Servers? Specifically, any changes
to
> BUILTIN\Administrator ? If so, what were those changes?
> As for your production server/database, you might want to consider calling
> Microsoft PSS SQL Server support as and get their help in resolving this
> more urgent issue as newsgroups are not the best place to get
> production-level support.
> Regards,
> John
>
>
> "Douglas Steen" <dug@.pobox.com> wrote in message
> news:efN7P$0FEHA.4084@.TK2MSFTNGP11.phx.gbl...
And
think
noise.eng
tried
> for
children",
> but
> installation.
> server:
> fine;
> broken.
rebuilt
> yesterday,
has
> reason
> "814035
> this
must
the
> Control
work
> updated
noise.eng,
> catalog
0,
start/stop
a
SQL
(I've
>
|||Douglas,
If you can manage the FT Catalog via the system stored procs, then this is
NOT a Win2003 upgrade issue, but a specific SQL Server FTS issue.
If your production and dev machines are configured similarly, and you can
manage the FT Catalog via the system stored proc, but not via the EM, you
might be using "local accounts" and checkout the following KB article -
"270671 (Q270671) PRB: Full Text Search Menus Are Not Enabled for Local
Windows NT Accounts" at:
http://support.microsoft.com/default...;en-us;q270671
Regards,
John
"Douglas Steen" <dug@.pobox.com> wrote in message
news:OYTvY01FEHA.2732@.tk2msftngp13.phx.gbl...
> John -
> As it turns out, our production issues were solved by using
QueryAnalyzer
> instead of the Enterprise Manager to do the creation/population/etc.
> Unfortunately, I wasn't so lucky: it hasn't worked for me. No idea why
one
> would work and not the other, but it is feeling like it has something to
do
> with the Win2K3 upgrade and permissions.
> This is just a dev machine, so if all else fails (though I'd hate to do
> it), I can reinstall everything (starting with SQL server). I'm going to
> let it stew for a while & see if any other ideas come up. In the
meantime,
> I've gotta get back to work. Thanks for your efforts.
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:eVo7QR1FEHA.3568@.tk2msftngp13.phx.gbl...
Secondly,
> permission
checkbox
where
> the
to
as
changes
> to
calling
> And
> think
> noise.eng
it
> tried
tab
> children",
folder,
> rebuilt
we're
> has
be
Server
> must
> the
Full-Text
> work
> noise.eng,
the
> 0,
> start/stop
stopped
to
> a
> SQL
> (I've
>
sql