I sent you a similar message back in Jan. 2003 on this same "Error:
8007042b - The process terminated unexpectedly".
"The process terminated unexpectedly" is actually ERROR_PROCESS_ABORTED,
which is returned when the async I/O does not complete in time. The default
is 20 seconds. This is desired for distributed crawls across the network,
where you don't want other systems hang the crawls, but on a local system
that may be busy with other things, it should be longer.
This *could* (but most likely not) be resolved by increasing the Microsoft
Search connect timeout parameter via:
sp_fulltext_service 'connect_timeout', <value_in_seconds> -- default = 20
You can set this value to 120 (2 minutes) and while it did resolved this
error for some customers, however for others it did NOT resolve this error.
Is your server and"un-usually" busy server, i.e., multiple apps/services
running, heavy i/o, memory & CPU usage?
It's also possible that specific rows are causing this error and running a
dbcc checktable is always a good idea to confirm no corruption in your
FT-enable table structures.
If the above steps do NOT resolve this error, can you upgrade this server to
either SP3 or SP4 As this would be preferred.
However, I know that for FTS functionality reasons, you're unable to upgrade
past SP2 at this time on this server. SQL Server 7.0 is "problematic" for
these types of issues and you might want consider opening a support case
with MS PSS SQL Support for these issues, but remind them that you're unable
to upgrade and tell them why (give them the KB#).